The pitch: presenting and defending your strategy

Strategies don't fail in the document. They fail in the meeting.

Somewhere ahead of you is a conversation with the person who can fund this strategy or bury it: a boss, a bank, a co-founder — or yourself. Do not smile at that last one. If you are the owner, the decision-maker is the version of you in four months who is tired, behind on the numbers, and one bad week from quietly abandoning the plan. That person needs convincing now, in writing, while you still believe.

Whoever it is, the shape of the meeting is the same. They have ten minutes, three objections, and a default answer of "not now". Everything in this lesson is about surviving that shape.

The one page, and what it opens with

The executive summary is one page, written last, read first. Its anatomy:

1. The goal — the one from Module 0. The metric, the number, the date you wrote in your Project Brief, and where you stand against it today. This is the first sentence, not the tenth.
2. The situation, in two or three sentences, from your funnel baseline.
3. The strategy in one sentence — audience, channel focus, objective.
4. The 4–6 kept initiatives, each with its cost.
5. The ask — one specific, grantable request.
6. The risk you're most worried about, named by you before anyone else can name it.

Lena's opening, to her managing director:

"Fourteen new firms a month by 1 June, from nine today. Every customer we acquire costs €67 and returns about €1,020 — a fifteen-to-one ratio when three-to-one is the working convention. We are not failing at marketing; we are underspending on it. I'm asking to raise the budget from €600 to €1,100 a month now, and to €1,800 only if the day-60 numbers earn it. Here is the plan."

Five sentences. The goal with its baseline, the economics, the diagnosis, the ask with its own safety catch. Notice what it is not: it is not "let me walk you through my research process from Module 2 onwards". Decision-makers listen top-down — conclusion first, evidence available on demand. Students present bottom-up, reliving the Program in order, and lose the room by minute four. You did the work chronologically. You present it backwards.

The five standard challenges

Every strategy meeting contains the same five questions wearing different clothes. You built the answer to each one months ago:

Before the meeting, steelman each one: write the strongest version of the objection yourself, not the convenient version. A weakness you name and answer is credibility. The same weakness found by the other side of the table is fatal.

"Why not just run ads?"

This one deserves its own drill, because you will hear it in every marketing conversation for the rest of your career. It is usually sincere — ads are the only marketing most decision-makers can picture buying. The answer has three parts, and none of them is a sigh:

1. The economics, theirs and yours. What a click costs, what a customer is worth, what that makes a conversion cost.
2. What ads can and can't do at your scale.
3. The pre-committed condition under which you would scale them.

Lena's version, when her MD asks why the extra €500 doesn't simply double the Google Ads:

"At our €13 clicks, a trial through the landing page costs about €382 against a €340 target. The page has to sustain 3.8% before a scaled euro pays back — it's at 3.4% on too few conversions to trust. So the ads keep running at €400, the day-60 checkpoint tests the gate, and if it passes, scaling is already approved in this plan. Meanwhile the €500 goes where our constraint actually is: production support, because my six hours are the bottleneck, not the ideas."

That last move matters: the extra money buys contractor hours, converting budget into the capacity the roadmap said she didn't have. And note the posture throughout — no defensiveness. If ads genuinely were the best next euro, her plan would already say so. The question only stings when your plan is hiding from it. Yours isn't, because your Module 9 arithmetic and your Not-Doing List answered it before the meeting existed.

Presenting uncertainty without losing the room

You know things a spreadsheet doesn't: which numbers are measured, which are modelled, which are guesses. The temptation is to smooth them into one confident surface. Resist it — mixed claims destroy trust the moment one is caught, and one is always caught.

The discipline is calibration. Say "the research shows" only where it does, and cite the artefact. Say "this is my judgement call" where it is. Lena's best moment in her pitch is not a strength but a flagged weakness:

"Two of our numbers disagree: reported churn implies customers stay about 42 months, our records show 14. I haven't resolved it, so the whole plan is built on the worse number. If the truth is better, everything here pays back faster."

Uncertainty presented with a decision rule attached reads as competence. Uncertainty presented as a shrug reads as risk. The difference is not confidence — it is whether you have already decided what you'll do when the fog clears either way.

The ask

End with one specific, grantable request: euros, hours, or a decision, with a date. Not "support", not "alignment" — those cannot be granted, so they won't be. A meeting without an ask produces "interesting, let's revisit", which is a no wearing a scarf.

Staging the ask, as Lena does — €1,100 now, €1,800 gated behind day 60 — is often what turns a maybe into a yes. It lets the decision-maker buy the checkpoint instead of the whole risk. Her MD's actual decision: approved at €1,100, the €1,800 conditional on the gate, and the day-60 review adopted as a standing meeting. Twenty-five minutes. The pitch worked because every answer pointed at a page that already existed.

When the answer is no

Sometimes it is no anyway — the money isn't there, the timing is wrong, the trust isn't built yet. A no is not the end of the strategy. It is data, and there are four moves that turn it into something:

1. Get the reason stated. "Not now" is not a reason. "January is our cash trough" is — and it tells you when to return.
2. Shrink the ask to a pilot. Find the smallest slice that tests the same thesis.
3. Keep the free baseline running. Nothing in a no forbids the work that costs hours instead of euros.
4. Set a revisit date tied to evidence, not to mood. "When the tagged-link data covers the peak season" beats "in a few months".

Mateus lives this one. He pitches Ana the full plan — commit the €500 a month, one creator collaboration per quarter — and adds €200 a month on top for a monthly collaboration cadence. Ana says no to the €200, and says why: January's cash trough, the one nobody plans for, is three months away. Mateus doesn't argue. He keeps the €500, drops to one collaboration a quarter inside it, and books the revisit for after peak season, when the tagged-link numbers will speak for themselves. A documented no with a reason and a revisit date is a strategy artefact. A vague no is just a stall — and if you accept it vaguely, you helped.

And if you are pitching yourself? The no still happens — it just sounds like drift. The same four moves apply, which is why the summary and the checkpoints go on paper even when the only signature required is yours.

Now write the page.

---