Most clients walk into a first call expecting to talk about pages, features, and timelines. Most agencies are happy to let them, because it's an easy conversation to have and it gets to a number fast. It's also the wrong conversation — and it's usually the first sign that the agency is going to build you a solution to the wrong problem.
A real discovery call is a diagnosis, not a pitch. Here's what should actually happen in one, on both sides of the table.
What a Good Agency Asks First
Before anyone mentions a feature, a good agency is trying to understand who the software is for and what it's replacing. That means questions like these, roughly in this order:
"Who's actually going to use this, day to day?"
Not "the business" — the specific people. A dispatcher with fifteen years on paper forms needs a different tool than a tech-comfortable office manager, even if the end feature list looks identical.
"What systems does this need to talk to?"
Your accounting software, your calendar, your payment processor, the spreadsheet everyone still secretly uses. If the agency doesn't ask this before scoping, they're scoping blind.
"What's actually broken about how you do this today?"
The request is rarely the real problem. "We need a booking app" often means "we lose track of who confirmed and who didn't," which is a much narrower — and sometimes much simpler — thing to fix.
"What happens if this doesn't get built?"
This tells the agency what's urgent versus what's nice to have, and it should shape what gets built first — not everything gets equal priority just because it's on the wish list.
The Red Flag: Jumping Straight to "How Many Pages Do You Want?"
If the first substantive question on a call is about page count, screen count, or a feature checklist, treat that as a signal, not a formality. It usually means the agency prices by inventory — count the pieces, multiply by a rate — instead of by outcome. That approach produces software that technically matches a list but doesn't fix the actual workflow problem, because nobody asked what the workflow problem was.
It also tends to produce scope fights later. When "page count" was the unit of the original conversation, every misunderstanding turns into an argument about whether something counts as a new page instead of a conversation about whether the software is actually working for the people using it.
What You Should Bring to the Call
The clients who get the most out of a discovery call come prepared with specifics, not adjectives. Concretely, that means:
- A real example of your current process — the actual spreadsheet, the actual paper form, a screen recording of the tool you use now. "We want something modern" tells an agency nothing; a messy Excel sheet with seventeen columns tells them everything.
- A specific moment where the current process failed. A missed appointment, a double-booked truck, an invoice that went out twice. These are the moments the new software actually needs to prevent.
- A list of every existing tool or account it has to connect to — even the ones you're embarrassed about, like the shared inbox everyone logs into.
How to Know, After the Call, If They Actually Understood
You won't know from confidence or polish. Confidence is cheap. Look for these instead:
- They repeat your problem back correctly, in their own words. Not your request — the actual problem underneath it. If their summary sounds like a rephrased version of your first sentence, they weren't listening past it.
- They ask a follow-up about something you didn't flag as important. That's the sign they're building a mental model of your business instead of filling in a template.
- They describe a workflow, not a stack. "Here's what your dispatcher will see on Monday morning" is worth more than a list of technologies you've never heard of.
- They push back on something. A good agency questions at least one assumption in your original request — because your first instinct about the solution is often shaped by whatever tool you've already seen, not by what would actually solve the problem.
If none of that happened and the call moved straight to "so, how many screens are we thinking," you already have your answer — even before the proposal shows up.
Want a Call Like This?
Bring us your actual process — spreadsheet, paper form, or the tool you're outgrowing. We'll ask about the problem before we talk about the build.
Book a Discovery Call