01
Free · 45 minutes
You talk us through how work actually moves through your business — who touches an enquiry, where it sits, what gets re-typed into a second system, which tool everyone quietly avoids. We ask a lot of questions, and we tell you what we think on the call rather than in a follow-up deck.
02
Paid · typically two to four weeks
We go inside the workflow properly. We sit with the people doing the job rather than the org chart, follow a real job from first enquiry to invoice, open the settings of the systems you already pay for, and find where the week is going. This is the part most agencies skip and most consultancies stop at.
03
Included in discovery
Three lists. What to change in how you work. What to switch on in software you already pay for. What actually needs building. In that order, because that is usually the order of cheapest to most expensive — and because the first two lists often make the third one much shorter.
04
Quoted, phased, optional
If the third list has anything on it, we quote it — already split into phases before you see it, each one scoped so it is worth having on its own. You can take all of it, some of it, or none of it.
45 minutes, with the person who would do the work
Not a salesperson working from a discovery script. You will be talking to whoever would actually be inside your systems, which is why the questions are specific and why you get an answer on the call.
Bring one process that annoys you, a list of what you pay for monthly, and ideally whoever actually does the work. We have done this inside brokerages, clinics, retailers and design studios, so we usually know where to look.
A good number of these calls end with us saying you do not need to build anything yet. We would rather tell you that in the first forty-five minutes than in month three of a project.
What it is not
A price list only works when the thing being sold is the same every time. Ours is not. Two companies ask for “a website”: one needs eight pages that load fast and rank, the other needs a platform where forty non-technical editors publish under separate brands. One number on a page would be a guess dressed up as transparency. What we can tell you before you ever speak to us is what moves the number.
Building against your live CRM, your real inventory and your actual customer data is faster than starting from nothing. Sometimes dramatically faster.
One integration is a task. Six is an architecture, and architecture is where the cost lives — not in the number of screens.
A booking flow is known work. An agent that reads DWG floor plans and returns a rendered apartment is not.
A site three people update is a different build from a platform your whole team edits without calling us. Self-sufficiency is a design decision with a price attached.
Compression costs money. Sequence is almost always cheaper than speed, which is why we quote in phases.
Replacing a system nobody depends on yet is straightforward. Replacing one your team uses every day, without stopping them working, is the harder engineering.
The rules we work to
What that looked like
A Dubai brokerage came to us for a new website. Phase one was not a website. It was time spent inside the CRM they were already paying full price for and using at a fraction of its capability — no action plans, no automations, plain-text email going out of a product that ships branded templates as standard.
Fixing that took no new code and it paid for itself before we wrote a line.
It ranges from a site built properly to a platform that runs a business, and those are not the same purchase. What we will commit to: an honest read on the call of what drives the number in your case, and a written, phased quotation after the paid diagnostic. No deposit to get either.
Because the same words describe very different builds. Publishing one number would mean quoting for a job we have not seen, and every buyer who did not fit that number would either be overcharged or scared off. We would rather tell you what drives the cost, then give you a real figure once the diagnostic has shown us what we are quoting.
Yes, with no obligation attached. You keep the written summary whether or not anything follows, and you are welcome to take it to another firm to build.
Then that is what we tell you, and it is a good outcome. The most valuable engagement we have run ended with a client writing no new software at all — they were already paying for a system that could do the job once it was configured properly.
For anything of a reasonable size, yes — quoting a build we have not investigated means padding the number to cover what we cannot see, and you pay for that padding. For a small, well-defined piece of work where the scope is genuinely obvious, we will just quote it.
You do. Code, infrastructure and data, at every phase boundary. Nothing is licensed back to you and nothing is held hostage by our hosting.