Most agencies start a discovery call with a slide deck. We start with a notepad. By minute 28, we know what to build, what it will cost, and whether we are the right shop for the job. The reason is not magic. It is twelve questions, asked in order, that surface exactly the information a build team needs to scope work correctly. Here they are, in full, so you know what to expect (and so you can show up ready to get real value out of the call).
Why We Run the Call This Way
Plenty of agencies treat discovery as a sales motion. Get the prospect excited, demo something flashy, drop a number, push for close. That works fine if the goal is booking projects. It is terrible if the goal is shipping projects that actually solve the problem. Half the time the "problem" the prospect describes on the first email is a symptom, not the root cause. The questions below are designed to find the root cause before anybody talks about scope.
If we ask these and decide we are not the right team for what you actually need, we will tell you. That has happened. It is fine. Better to find out in 30 minutes than three months in.
The 12 Questions
### 1. What is the most expensive manual process in your business right now?
Not the most annoying. The most expensive. Money lost, hours burned, opportunities missed. This is almost always the right place to start a build, because the ROI math writes itself.
### 2. Where do leads die?
Every business has a leak somewhere between "person heard about us" and "person paid us." Inquiry forms that never get followed up. Quotes that take three days to send. Voicemails that pile up. We need to know where the funnel breaks.
### 3. What does a normal week look like for your top operator?
The person in your business who carries the most weight, the one you cannot afford to lose, walk us through their week hour by hour. The tasks that show up over and over are usually the right automation targets, because anything that protects your best people compounds.
### 4. What system, tool, or process do you hate but cannot get rid of?
Every business has a piece of infrastructure that everyone complains about but nobody has time to replace. Sometimes the right move is to replace it. Sometimes it is to wrap it. We need to know it exists before we can decide.
### 5. Walk us through the last 5 customer complaints. What were they about?
Complaints are free research. If three of the last five mention the same friction point, that is your next build. We want the actual complaints, not the polished version.
### 6. What does your customer hear in the first 24 hours after they buy or sign up?
Most businesses have a black hole in the first day. The handoff between sales and operations is the single highest leverage moment in the relationship, and most companies wing it. If you cannot describe the first 24 hours in detail, that is a flag.
### 7. If you doubled tomorrow, what breaks first?
This question reveals the constraint. Sometimes it is sales. Usually it is operations. Whatever breaks first when you grow is the thing that is silently capping you right now. Build for the bottleneck, not the bottle.
### 8. What are you currently paying for in software that you do not fully use?
Most growing businesses have at least three SaaS subscriptions running that they signed up for, set up partially, and never came back to. We want to see the full list. Sometimes a custom build replaces three of them. Sometimes the existing tools are fine and just need to be wired together. We will not know until we see the list.
### 9. Who on your team is the bottleneck, and do they know it?
Not a trick question. The person who is the bottleneck is usually the most senior, the most committed, and the most overworked. They are also usually the person whose buy in determines whether a project succeeds. We want to talk to them.
### 10. What have you tried before that did not work, and why?
If you have hired an agency before and the project failed, we want to know. Not to dunk on the last team, but because the reason it failed usually points at a real constraint we need to design around. Internal politics, change management, training, integration with a stubborn legacy system. These are all knowable in advance.
### 11. What does success look like 90 days after we ship?
Force the answer to be specific. "More leads" is not an answer. "Cut quote turnaround from three days to two hours" is an answer. "Recover 20 percent of abandoned carts" is an answer. "Get our GM five hours a week back" is an answer. Without a measurable outcome, we are building art, not infrastructure.
### 12. What would have to be true for you to call this the best money you ever spent?
Best closer in the book. People will tell you in 30 seconds what they actually want from the project. Half the time it is not what they led with in the inquiry. This is where the real scope reveals itself.
How to Show Up Ready
You do not have to prep for a discovery call. The questions are designed to surface what is true, not test whether you have your house in order. That said, if you want to extract maximum value from the 30 minutes, do three things. Pull a list of every SaaS subscription you are paying for. Glance at your last month of customer complaints. And block 10 quiet minutes after the call to think about what you heard. The best calls are the ones where the prospect leaves with as much clarity as we do.
Where to Start
If reading those questions sparked even one "yeah, that one" reaction, book a free 30 minute discovery call. We will run the playbook on your business and you will walk away with a written summary of what we found, whether or not you ever hire us.

