Before the deck: build a one-page proof brief

What the minimum asset is

Before sending a pitch deck to a warm investor or buyer, prepare a one-page proof brief. It is not a shorter deck. It is the smallest document that lets the recipient inspect four things without a live explanation: the problem, your proposed change, one credible piece of evidence, and the next decision you want.

The brief can become the first three slides of the deck, but it should work on its own. A practical layout is:

1. Context: who has the problem, what happens today, and why the issue matters now.
2. Claim: what your company changes and for whom, in one plain sentence.
3. Evidence: one inspectable result, artifact or observation that supports the claim.
4. Ask: the single next decision, such as a diligence call, a technical workshop or a pilot review.

This four-part format is an editorial recommendation, not an industry standard. It compresses the questions in Y Combinator's pitch guidance and Sequoia Capital's business plan guide into a pre-deck check. If any part is vague, adding slides will usually hide the gap rather than resolve it.

Why a warm introduction still needs proof

A warm introduction improves access. It does not make a claim more credible. The recipient may trust the person who introduced you while still knowing little about your company, the problem or the requested commitment.

Y Combinator recommends a pitch that is clear, concise and explicit about what the company does, its progress and what the founder wants. Sequoia's guide similarly asks founders to cover purpose, problem, solution, timing, market, competition, model, team, financials and vision. The useful common principle is clarity of thinking before visual polish.

The one-page brief is therefore a gate. Send the full deck only when a reader can identify the claim, inspect the evidence and understand the ask. If the evidence is not ready, send a smaller request that matches reality, such as feedback on an experiment or permission to share a pilot result later.

What counts as evidence

Evidence must be connected to the specific claim. A product screenshot can show that a workflow exists, but not that customers will pay for it. A signed pilot can show commitment, but not long-term retention. Usage data can show activity, but its meaning depends on the period, population and definition.

Useful proof may include:

• a working demo with the relevant workflow visible;
• a measured experiment with the method and period stated;
• a customer quotation used with permission and tied to a precise outcome;
• a signed pilot, purchase order or letter whose status is described accurately;
• cohort, revenue or usage data with definitions and a reproducible source;
• a technical artifact that answers a known feasibility concern.

Choose one strong item rather than several weak signals. State what it proves and what it does not prove. Do not turn a conversation into a customer, a pipeline value into revenue, or an internal projection into market evidence.

Investor versus buyer

The structure remains stable, but the proof and ask change with the audience. The comparison table above separates the central question, useful proof, minimum context, appropriate ask and main red flag for each recipient.

This is not a claim that every investor or buyer follows the same checklist. It is a practical adaptation of the audience-specific framing described on the official Deck Studio page. The recipient's actual role and decision process take priority over the labels in the comparison.

Build the brief in 30 minutes

Use a fixed sequence so the deadline does not produce invented certainty.

Minutes 0 to 5: write the recipient's name, role and likely decision. If you cannot name the decision, stop and clarify the introduction.

Minutes 5 to 10: write one sentence describing what the company does. Remove jargon and ask someone unfamiliar with the project to restate it.

Minutes 10 to 20: select one evidence item. Add its source, date, population and limitation. If it is a demo, link to the exact workflow. If it is a metric, define the numerator, denominator and period.

Minutes 20 to 25: write one direct ask. Avoid “What do you think?” Choose a next step the recipient can accept, decline or redirect.

Minutes 25 to 30: run the four-part reading test. A colleague should be able to repeat the context, claim, evidence and ask without additional explanation.

Thirty minutes is a practical preparation window, not a promise that every company can complete the work that quickly. When evidence must be collected or approved, prepare the brief only after that work is complete.

Concrete example

Imagine an early-stage founder selling software that reduces the time required to prepare a weekly operations report. The weak version says the product “transforms operational intelligence” and claims broad productivity gains.

The stronger proof brief names the audience and boundary: “Operations managers currently combine three exports every Friday. In a two-week pilot with one team, the product produced the same report from the same inputs. The team lead confirmed the output matched the existing checklist. We are asking for a 30-minute technical review to define a second pilot.”

This example contains a limited claim, a period, a comparison point and a next step. It does not claim adoption, revenue, retention or savings that the pilot did not measure. An investor version could use the same underlying evidence but connect it to execution progress and the company's insight. A buyer version would emphasise workflow fit and validation conditions.

Decision criteria

The brief is ready to become a deck when all six answers are yes:

1. Can a new reader state what the company does in one sentence?
2. Is the evidence traceable to a source, date and defined scope?
3. Does the evidence support the central claim rather than an adjacent claim?
4. Is the audience named as an investor or buyer with a specific role?
5. Is the ask one decision rather than a list of possible outcomes?
6. Are important limitations visible before the recipient asks?

If the first, second or third answer is no, do not solve the problem with design. Return to the claim or evidence. If only sequence and emphasis are weak, a presentation workflow can help organise the material.

How Deck Studio fits

Deck Studio is relevant after the proof brief exists. Its official product page describes a workflow that starts from the presentation intention, connects the narrative to business foundations, adapts the content to the audience and supports rehearsal. That helps turn the four-part brief into a coherent investor or client story.

The workflow can help sequence the problem, evidence, implications and ask. It can also surface narrative gaps before slides are final. It cannot create genuine traction, validate a customer quotation, qualify the introduction or guarantee a decision. Those inputs remain the founder's responsibility.

Use Deck Studio to test whether every slide advances the audience's understanding. Keep the evidence accessible behind the summary, and verify every generated statement against the original record before export.

Limits

A one-page brief is not sufficient for every regulated, technical or high-value decision. Some recipients need a security review, financial model, legal evidence, references or a full diligence package before they can proceed. The brief should point to those materials without pretending to replace them.

The framework also does not rank evidence universally. A prototype may be decisive before product launch and weak after commercial claims have been made. A signed pilot may matter to one investor and reveal little to a buyer who needs integration proof. Match the artifact to the claim and the decision stage.

Finally, do not send confidential customer data, personal information or restricted documents merely to make the proof feel stronger. Redact, aggregate or obtain permission, and use a secure channel when the material requires it.

Sources and updates

The pitch criteria are based on Y Combinator's guide to pitching a company and Sequoia Capital's guide to writing a business plan. Deck Studio capabilities and audience frames are limited to Ember's current official product page.

The one-page proof brief, four-part test and 30-minute sequence are Ember editorial recommendations derived from those sources. They are not presented as investor consensus or a guaranteed route to a meeting. Recheck the live product page before relying on a specific capability.