The Architecture Pitch
Overview
Section titled “Overview”The justification pack is the document. The pitch is the twenty minutes in a room with people who will not read it.
Both are necessary and they are different artifacts. A pitch that is the pack read aloud fails, for reasons this topic is about.
Much of what follows is persuasion mechanics rather than architecture, and the useful source is Cialdini’s Influence — particularly on why a commitment made in advance of a meeting holds, which is what the pre-socialising in Section 1 was exploiting.
Lead with the problem
Section titled “Lead with the problem”The single most common failure: opening with the solution.
An architect opens with the architecture — the design, the components, the technology — because that is what they have been working on and it is genuinely interesting. The room hears a proposal to spend money on something technical, with no established reason, and spends the rest of the presentation trying to work out why.
Lead with the business problem, in the business’s own units. Not “we propose a retrieval system” but “forty per cent of support volume is questions our documentation already answers, at a cost of X per ticket, and the team is at capacity.” Everybody in the room can evaluate that sentence, and it establishes the reason before anything is proposed.
The test, and the rubric makes it explicit: no technology named on the first slide. If a technology appears there, the pitch is about the solution and the problem has not been established.
A structure that works
Section titled “A structure that works”graph TD A["<b>1 · The problem</b><br/>business units,<br/>no technology"] --> B["<b>2 · What it costs<br/>to do nothing</b>"] B --> C["<b>3 · The prior failure</b><br/><i>before anyone raises it</i>"] C --> D["<b>4 · The decision</b><br/>one sentence"] D --> E["<b>5 · Why not the<br/>alternatives</b>"] E --> F["<b>6 · What it costs<br/>and what gives</b>"] F --> G["<b>7 · The ask</b><br/>specific, decidable"] classDef prob fill:#5B8FB9,stroke:#4A7A9E,stroke-width:2px,color:#ffffff classDef scar fill:#D9695B,stroke:#B4483A,stroke-width:2px,color:#ffffff classDef dec fill:#E8A33D,stroke:#C4832A,stroke-width:2px,color:#ffffff classDef ask fill:#7D9A4E,stroke:#5F7A38,stroke-width:2px,color:#ffffff class A,B prob class C scar class D,E,F dec class G ask
Seven movements. The terracotta one is third — early, before the decision — which is the placement that distinguishes a prepared pitch from a defended one.
What it costs to do nothing is the slide most architects omit and the one that makes the rest decidable. A proposal without a baseline asks the room to compare your plan against an unstated alternative, and the unstated alternative always looks free.
The prior failure comes third. Before the decision, not in the question-and-answer. This is the pre-handling move: raised by you, it is evidence of preparation; raised by someone else forty minutes later, it is a challenge you are answering under pressure in front of people who have watched you be surprised.
The decision is one sentence. If it takes a paragraph, it is not yet a decision.
The ask is specific and decidable. Not “we would like support” but “we are asking for one engineering slot in Q1, with the billing extraction slipping to Q3, and for the compliance review to be scheduled this month.” A room can say yes to that. It cannot say yes to enthusiasm.
Pre-answering the strongest objection
Section titled “Pre-answering the strongest objection”The general technique, of which the prior failure is the main instance.
Before the pitch, write down the three strongest objections and who would raise each. Then put the strongest one in the pitch itself, in your own framing, with your answer attached.
Two reasons this works. It is disarming — an objection you raised yourself cannot be used against you. And your framing is better than theirs: you choose the version of the objection you answer, which is a legitimate advantage because you have thought about it longer.
The pre-socialising from Section 1 is the complement: the people most likely to object have already seen your answer privately, so the objection does not arrive cold.
Reading the room
Section titled “Reading the room”Three signals worth watching, with their responses:
Silence from someone with influence. Not agreement. Address them directly — “this touches your area; what am I missing?” — because an unspoken objection becomes a decision after the meeting.
Detail questions arriving early. Usually a sign the problem framing did not land; the room is testing competence instead of evaluating the proposal. Return to the problem rather than answering at depth.
A question you cannot answer. The second topic in this module supplied the sentence: I do not know; I will find out by Thursday. Guessing in a room is the single most expensive thing available in this module.
Keep the deck short and the pack available
Section titled “Keep the deck short and the pack available”The pitch is short because attention is scarce. The pack exists for the people who will read it — and knowing that the depth exists changes how the summary is received, because a claim is more credible when its backing is visibly available.
Ten slides is enough for the seven movements above. The pack can be forty pages.
Feeds the workbook
Section titled “Feeds the workbook”This is the ten-slide pitch artifact. Two rubric items land here: no technology on the first slide, and the prior-failure objection answered before it is asked.
→ Sometimes the preparation is excellent and the room still decides against you. — When the decision goes against you