No mockups, no quotes. This is what the first real conversation looks like: what we ask, and what should come out of it with clarity.
This blog has talked a fair amount, in the abstract, about why a diagnosis should come before a quote. This time, in concrete terms: what actually happens in those 45 minutes, what we ask, and what should be clear by the end.
We don't start by asking what you want built
The first question is almost never "what do you need us to build?" It's closer to: "walk me through a normal day of operations — from when a request or a new client comes in, to when that matter gets resolved." That open question, without steering toward any solution, is what lets us actually see where the work lives, not where someone assumes it lives.
The areas we cover
Where time is being lost. Which tasks repeat almost identically every day or every week, and how much of that time is spent by someone doing something they already know by heart, instead of deciding something new.
Where the critical knowledge lives. If there's a task, a calculation, or a decision that only one person on the team knows how to do well — that's a silent risk, and almost always a sign that something needs to be systematized, not that the person is irreplaceable.
Where clients or money are being lost without it being noticed at the time. Follow-ups that don't happen, quotes answered late, errors discovered after they already cost something. These are the hardest to see from the inside, because each instance feels like an isolated case.
What tools already exist and aren't being used well. Often the business already pays for a CRM, a shared spreadsheet, or software that could do more than it currently does — the problem isn't always a missing tool, sometimes it's a missing process around the tool that's already there.
What we do NOT do in this conversation
We don't show mockups. We don't give a price. We don't promise a solution before understanding the problem. A diagnosis that ends with "here's what we should build" on the same call wasn't a diagnosis — it was a sales pitch dressed up as a conversation.
What should be clear by the end
By the close of the 45 minutes, the minimum that should be on the table is: what the real bottleneck is (not the most visible symptom, but the cause), how urgent it is to solve compared to the business's other priorities, and an honest sense of whether the next step is a system, a process adjustment that needs no new software, or — sometimes — nothing yet, because the business has a different problem to solve first.
Why it's worth doing even if nothing gets hired afterward
An honest diagnosis leaves value even if the conclusion is that it isn't yet the moment to build a system. Naming precisely where the bottleneck is is already information the business can use, with or without us. That's the difference between a real diagnosis and a sales call: one is designed to leave you clearer, the other to leave you ready to sign.
If you'd like to book yours, reach out to us.
Conversation