What The 30-Minute Scoping Call Actually Covers

Most discovery calls are sales calls in disguise. Ours is not. This is what actually happens in the thirty minutes, in the order it happens.

The frame, in one sentence

You leave the call knowing whether the workshop is the right fit, what the first measurable win would be, and what we would have to see to walk away. We leave the call knowing whether we can publish a falsifier next to the work without flinching. If either side cannot say yes to those, we say so on the call, not after.

Minutes 0–3. The two intake questions

We open with two questions and then we shut up:

• What is the task that has been quietly costing you the most this quarter? Not the headline initiative. The thing that the team keeps redoing.
• How would you know, six weeks from now, that something actually changed? If the answer is "we'd feel better about it," we say so and push for a number.

We are listening for whether the task has an operator surface — a place where a human currently does the work and could mark whether an output was used. No operator surface, no override rate, no receipts. (Class C — every engagement we have had to course-correct started with a task that had no clear "kept vs. rewrote" boundary.)

Minutes 3–10. The current-state walk

We ask you to walk us through the workflow as it exists today. Not the diagram on the deck. The actual click path, the actual handoffs, the actual file that gets copy-pasted into the actual email.

What we are listening for:

• Where the rewrites happen. Every workflow has a step where someone silently fixes the previous step. That step is almost always where the first receipt belongs.
• Where the dark dependencies are. A vendor in the chain whose behavior nobody can predict, an API key one person has, a model version nobody pinned. (Class C.)
• What the team has stopped trying. The tasks people gave up on are usually the tasks where a small, measured win lands hardest.

We do not interrupt with solutions in this segment. If a solution is obvious, we write it down and bring it back at minute 22.

Minutes 10–17. The honesty pass

This is the section most clients tell us they were not expecting. We ask:

• What would have to be true for you to fire us in week four? If you cannot name it on the call, the engagement does not have a falsifier and we will build one with you before signing.
• Who internally is going to argue against this project? Not the generic skeptic. The named person, in the named meeting, with the named objection. We want to address that objection in writing before kickoff, not after week one.
• What is the failure mode the last vendor caused? We are listening for retainer-treadmill patterns, opaque pipelines, seat-license traps — the shapes we have seen before. (Class E — these patterns are documented across the field, not unique to us.)

If you do not have answers to these, that is fine. The call is partly where you build the answers out loud.

Minutes 17–22. The first-receipt sketch

We pick one task class from the current-state walk and sketch, on the call, what the first receipt would measure. Out loud, with you correcting us. Concretely:

• The task class boundary ("emails responding to inbound qualified leads, excluding the support inbox").
• The operator surface ("the rep marks kept, edited, rewrote, or discarded in the existing CRM stage").
• The falsifier ("if override rate is not lower than the four-week baseline by week four, we have not improved the workflow and you are free to end the engagement").

This is the section where it stops being a sales call. You can feel the shape of the work. (Class C.)

Minutes 22–28. The disqualifiers, said out loud

We tell you, on the call, the things that would make us decline the engagement. Examples we have actually said:

• The task has no operator surface and the client is not willing to build one.
• The internal stakeholder who would argue against the project has veto power and is not in the room before kickoff.
• The win the client wants requires an extraction posture we will not take — for example, locking the team into a tool they cannot inspect.

If none of the disqualifiers fire, we say that too, on the call.

Minutes 28–30. What you walk away with

Before we hang up you have three things in writing in the follow-up email, sent within two hours:

• The one-line task class we would scope first.
• The one-line falsifier that would end the engagement.
• The one-line "what would have to be true" that would make us decline.

No deck. No proposal. No "we'll get back to you next week."

If you want the longer companion piece on how to prepare for the call, see the workshop-readiness buyer's guide. If you want the self-check before booking, see are you ready for the workshop. When you are ready to book the call itself, the entry point is the workshop.