Growth Academy · Section 4 · Finding the money
If your next prospect could only remember one thing about the call, would it be your pitch, or the question you asked them?
This section covers what happens between the moment you meet a prospective client and the moment they'd call you again without being asked. It is one section because it is one habit of mind, but it plays out in two arcs, and it helps to know which one you're standing in.
Arc A, winning the conversation, covers everything before money moves: how you open a first meeting, the questions you ask before you say anything about what you'd do, and how you earn the bigger mandateThe formal go-ahead and scope a client gives you for a piece of work. by proving something small first. Arc B, delivering like a partner, covers what happens after the engagementA defined stretch of paid work between you and a client. starts: how you hold the relationship so the client experiences you as embedded team rather than outside vendor, and how you hand off work so it strengthens them instead of creating dependency on you.
The two arcs share one root move: withhold your own agenda until you understand theirs. In Arc A that means diagnosing before prescribing. In Arc B it means teaching instead of hiding the work. Same discipline, aimed at two different moments in the same relationship.
The standard opening move with a new consulting client is to propose nothing. First come weeks of analyzing how the business actually runs: who is doing what, what software touches what, and where the real problems sit. Only after that diagnosis comes the change plan, and only then does the team execute. The reasoning is blunt: a business owner deep inside daily operations cannot reliably diagnose their own systemic problems. A physician wrestling with insurance-billing chaos in her own practice is too close to it to see which failures are software limitations, which are people limitations, and which are simply broken process.
"We don't know what we don't know until we actually analyze your business. So there is no chance that your work will not become better."
Diagnosis has a second, quieter rule inside it: ask what's already been tried and what it cost, before you suggest anything. Skipping this means walking back in with a "fix" the client already ran and watched fail, which spends their patience and your credibility in the same sentence. When a client hands over a prior agency's history, the right response is plain: "This is who we worked with. This is the extent. This is what challenges they faced." Get the history before you get to the pitch.
DiscoveryThe structured questions you ask a prospect before proposing anything, to learn how their business actually works., the set of questions you ask before you propose anything, is not a free-form conversation. It runs in the same sequence every time, because asking budget first, or ownership last, risks scoping work against assets you can't actually touch, or proposing spend nobody in the room is authorized to approve.
Two questions open the substance of that discoveryThe structured questions you ask a prospect before proposing anything, to learn how their business actually works., and both do the same job: they get the other person to state what they actually want before you've proposed a single fix. The first is the magic-wand question: "If you had a magic wand and a dream team that could do anything, what would be the order of the things you'd want handled first, just the outcome, not the how?" One team asked it of a platform lead twenty minutes into a demo of her product, which had a low conversionWhen someone takes the next step you wanted, like signing up or paying. rate, deliberately pausing before suggesting anything. The second question is shorter and just as load-bearing: "What does success look like?" It is normally the first move, because it keeps a team with real capability from drifting into pitching everything it could possibly do instead of the one thing the client is actually asking for.
One diagnostic trap: asking a prospect directly whether something matters to them. "Is data important to you?" gets a reflexive yes every time, because admitting it isn't important makes the prospect sound careless, so the answer is always yes, and the signal is worthless. The fix is force rankingMaking someone put options in order instead of letting them call everything important. instead of a verdict: instead of asking about each priority alone, make the prospect choose between two real trade-offs, or sort a list into high, medium, low. As one advisor put it when applying the technique to farmer priorities: "This element of force ranking can be really helpful when talking with prioritization of things that are important... the grower is likely to say, well, I need both of those." Force the choice, and the truth falls out.
When a buyer has been over-promised to and under-delivered for, the correct move is not a better pitch. It is proof, at small scale, before you ask for anything. A founder in a skeptical, previously-burned market named the dynamic directly: "They're not going to switch until they see the business case... That show-me is important... It's hard for them to go by faith, and they shouldn't, because there's an awful lot with things being told to them that don't necessarily prove out on the ground." The same logic drives a simpler move: bring a working prototypeA rough working version built to show an idea in action before the real product exists., not a deck of ideas. One team built a functioning booking platform for nurses and clickable brand-direction files before a single pitch call, rather than presenting concepts. "We wanted to show you rather than tell you we can do that."
Proving it small has a repeatable shape. Watch it work across three different rooms:
When everyone in the room is a deep expert, the failure mode is never saying too little. It's saying too much. A proposal written by experts defaults toward comprehensiveness, because each person wants their full domain in it, and that comprehensiveness is exactly what stops a buyer from saying yes. The buyer gets overwhelmed instead of convinced. That fear surfaced before drafting a single line of a real proposal: "it's very easy for us to kind of overshoot and overwhelm [him] with a long proposal that explains everything." The discipline that fixes it is a single question, asked before the draft begins: "If he gave us three minutes to explain what do we want, then what do you say?" Answer that first. Everything that can't survive the three-minute cut moves to an appendix, or gets cut outright.
Two more moves round out how the room gets run. Sequence a multi-topic call so substance comes before money: protocol, then process, then data protection, then the investment conversation, in that order, using early agreement to build momentum before the harder ask. And when the market itself is insular or skeptical of outsiders, route the pitch through a credible insider who has personally felt the pain, rather than pitching the institution cold. That championAn insider at the buyer's organization who personally wants your product and pushes for it from within. becomes the plan for winning that first customer, the go-to-marketThe plan for how a product reaches and wins its first customers., not a formality in front of it.
The deal closing is not the finish line. It's where the second arc starts, and it opens with the same move that won the conversation: reject the vendor frame before the client can assume it. A first working call, right after introductions, can open like this: "So you can be as frank as you can, as you need to be, and as you want with us. So you can tell us the real challenge because we're kind of, think of us as internal... We're not an agency. We don't operate like one." That same frame, reused across three separate engagementsA defined stretch of paid work between you and a client., surfaced churnThe rate at which existing customers cancel or stop buying. numbers, technology complaints, and internal dysfunction a client would have softened for an outside vendor: "Our intention is we don't look at anything that comes from [the client] as a client. We look at them as a member of our team."
Where the trust required goes deeper, a regulated industry, a protective internal team, sensitive disclosures, the internal frame can become a literal internal role. When the ideal execution lead already has the client's personal trust, the move is to have the client formally hire that person into an internal title, not engage the firm purely as an outside consultancy: "The most important thing is we need unfettered access to everything so that we can analyze the business... within a couple of weeks, to meet with everyone, and they need to be comfortable talking to us." The title changes what people are willing to say.
"We're not treating him like a client where the company needs to show up in a certain way. We've always showed up with him very honest — this is where we are, here's what we're dealing with, here's what we are contending or contemplating. And we'd love your input."
Under-promise and over-deliver is not a practice you demonstrate quietly over time and hope the client notices. Say it, as a stated value, in the first conversation, so the other side can hold you to it later: "if you work on success and work directly with the clients, last thing you want is to over-promise and under-deliver. You want to actually always under-promise and over-deliver."
The work itself has to stay visible, not hidden behind a "trust us, here's the result" delivery. The client should not feel the work is happening to them; they should feel like they're working alongside you and retain control even while delegating execution: "You learn what we're doing. It's not hidden. You get to know all of that so that you have control as well... we work alongside you, not just take the work from you." The same instinct governs how drafts get handed over, not as a finished answer to approve, but as raw material to argue with: "Feel free to ignore all of that. Think of it as raw material." A client who owns customer-journey knowledge you don't have will tear a draft apart fast and honestly. A client asked to approve a "finished" deliverableThe concrete thing you hand a client at the end: the report, the build, the campaign. will hedge instead.
When you propose taking over a messy function, structure it as three distinct layers, not one bundled ask:
Last, a rule about pacing a partner who has less time than you do: take what they can give you now, and ask for more only if a real gap remains. Partial input on time beats complete input that never arrives. And where a partner is time-constrained, absorb the integration burden yourself. Take the whole unsorted export and do the segmenting on your own side, rather than asking a busy partner to pre-filter what they think you need. Every hour you save them is trust banked for later.
Everything above is a set of moves you can rehearse before you ever need them live. The drill below builds the actual script you'll open your next first meeting with, then pressure-tests it against a skeptical counterpart.
Format: scripted role-play, run with a cofounder, a peer, or an AI playing the prospect.
You did it right if in the role-play transcript, the prospect spoke more than you did, and you proposed nothing in the first ten minutes.
Next: Section 5 picks up once the money question is settled and moves to what you build with it, starting with the interrogation you run on any tool or vendor before it enters your workflow.