You liked each other, the conversation flowed, and you said you would send something over. Three weeks later you were writing a proposal from memory for somebody who turned out not to be able to sign it. That is not a charisma failure. It is what happens when nobody decided, before dialling, what the call had to produce.
This lesson makes the case for treating a discovery call as a document you are collecting rather than a conversation you are having. You will learn the six outputs, why the problem they lead with is almost never the one worth fixing, and how to establish what they can spend without ever asking about budget.
In this lesson
• See why a call that went well and a call that produced something are different things
• Learn the six outputs, and which one you missed when a proposal goes silent
• Find the real problem underneath the one they opened with
• Establish what they can spend by asking what they were about to spend on instead
You finish with: The framework and the argument behind it. Nothing to run yet.
Twenty minutes of preparation the day before changes what the call produces. Not a script — those make you sound like a bank — but three ranked priorities so you know what to sacrifice when it overruns, the questions in your head rather than on your screen, and a named list of what they will challenge.
You will run the first three prompts and meet the demo: Apex AI calling Pebble & Co, the same prospect the Cold Outreach course wrote the strongest opener to. She replied, and this is the call that reply produced.
In this lesson
• Run prompt 01 and read the assumption it flags before anything else
• Learn the three questions you ask no matter how short the call runs
• Avoid the three questions that get an answer which is not true
• Run prompt 03 and fix your weakest objection answer, or accept it is coming
You finish with: A call plan, fifteen questions, and the objection you cannot yet answer.
Run this half within a few hours of the call ending, while you can still tell the difference between what was said and what was implied. Three days later an interpretation you made on Tuesday reads exactly like something the client said, and you will price against it with total confidence.
The lesson ends on the step most people skip: asking whether to propose at all. The prompt is forbidden from hedging and returns one of three verdicts. On the demo call it returns go back with questions, because a second decision-maker was named once and the cost of the problem was a shrug rather than a number.
In this lesson
• Turn a messy transcript into nine structured headings, gaps named rather than filled
• Keep their words and your interpretation separable a week later
• Send a recap under 150 words today, with exactly one question in it
• Take the verdict seriously, including when it says walk away
You finish with: Discovery notes, a sent recap email, and a decision you can defend.
No new teaching. The whole chain run start to finish on screen, using Apex AI and the Pebble & Co call from the demo pack — so you can watch what each prompt actually returns before you spend a call finding out.
It includes one output that comes back too tidy, and the follow-up instruction that fixes it. That is deliberate. A confident set of notes containing three things nobody said is the most expensive failure in this course, and it is much easier to recognise once you have seen it happen to somebody else.
In this lesson
• Watch prompt 01 name an assumption that turns out to be wrong
• See nine lines of shorthand become structured discovery notes
• See the notes come back too confident, and the instruction that corrects them
• Follow the verdict to go back with questions rather than propose
You finish with: A clear picture of what good looks like at every step, before you run your own.