The scope memo is the product.

The deck was always a performance. A 60-slide artefact produced to justify the fee that paid for it. A two-page scope memo does the job better: it is faster to write, harder to hide behind, and both sides sign the same thing.

The deck is theatre.

Consulting decks are a genre. They have tropes — the appendix of sources nobody will read, the executive summary that repeats itself three times in slightly different fonts, the "implementation roadmap" that is really a Gantt chart of meetings. The deck exists because the deck is the only tangible artefact that justifies the invoice. Nobody rereads it after week three. It sits on a SharePoint until someone's laptop is replaced.

The market still expects them. Buyers often ask, unprompted, "will we get the final deck?", as though the deck, not the shipped work, were the point.

The alternative.

Most founders don't want the deck. They want to know what will change, by when, for how much, and what's out of scope. That fits on two pages. They can read it before dinner and sign it the next morning.

Anatomy of a scope memo.

Every scope memo I write has the same shape. It is two pages. It fits in an email. A founder can read it in the time it takes to drink an espresso. Here is the spine:

• 01
  Outcome. One sentence. Not a goal — a measurable result, for example "activation on new cohorts from X% to Y% within 10 weeks." If you can't commit to that, you don't have the memo yet.
• 02
  Timeline. Calendar dates, not weeks. "Start: 12 May. Memo review: 26 May. Halfway check: 16 June. Close-out: 14 July." Weeks drift. Dates don't.
• 03
  Inputs. What the client provides: access, data, a named decision-maker, and the first hour of their Monday. If they can't provide these, the engagement is a fantasy.
• 04
  Outputs. What is shipped, in the client's system of record. A live funnel. A hired operator. An agent workflow running in their own accounts. Not a document.
• 05
  Price. Flat fee. Paid in two tranches. No hourly billing, no retainer escalator, no "change orders". If the work is bigger than scoped, that's the vendor's cost to eat.
• 06
  What I will not do. The most important section. "I will not write a board deck. I will not run the all-hands. I will not represent the company externally." Explicit boundaries prevent the engagement from shape-shifting.

Why it works.

The memo is not a lighter version of the deck. It is a different instrument. A deck is a performance of expertise; the memo is an act of commitment. A deck is asymmetric — you present, they receive. The memo is symmetric — both sides sign the same two pages. When the memo is the product, the deliverable is decisions, not documents.

There is a second-order effect. Because the memo is short, it has to be true. You cannot hide behind a 60-slide architecture when the whole argument fits on two pages. If you can't justify the outcome, timeline, and price in three paragraphs, you haven't scoped the work yet.

What you lose, what you gain.

You lose the theatre: the handover meeting with twenty people in it, the closing presentation, the ceremony around a pricey engagement. Some senior buyers will miss it at first.

You gain speed. A memo takes a day to write, not a fortnight. Work can start in week one. Scope is unambiguous. And the final artefact is the thing that got built, running in production, not a file nobody opens again.

How to try this.

If you are on the client side of a consulting relationship: next time someone sends you a deck, ask them for two pages. Outcomes, timeline, a fixed quote, what they will not do. Most consultancies cannot write it. The ones who can are the ones worth hiring.

If you are on the vendor side: try replacing your next proposal with a memo. It is a strange feeling: fewer slides, a smaller file, a clearer yes or no. You may miss the theatre for a while. Then you won't.