The Startup Executive Summary Template: A Founder's

The Startup Executive Summary Template: A Founder's Block-by-Block Guide

The executive summary is the single most-read and least-written-well document in a fundraise. Investors open it before the deck. Bankers screen with it before the model. Corporate development teams forward it before scheduling the intro call. It is one page — occasionally two — that has to do the work of thirty. Most founders treat it as an afterthought, either dumping the pitch deck into paragraphs or hiring an MBA to rewrite what they already have. Both mistakes are visible in the first sentence.

This guide walks the standard executive summary template — the one used inside YC's SAFE-round deliverables, most accelerator application packets, and the Alejandro Cremades template that ships with this article — one block at a time. Every block on that template exists because a specific reader in a specific meeting asked for it. When you understand which reader asked for which block, the summary writes itself.

Who reads the executive summary, and why the reader determines the draft

Before writing a single word, decide which of three readers you are writing for. The block order stays the same; the emphasis inside each block shifts.

The warm intro reader. A partner at a fund receives your summary from a portfolio founder. They will read it in ninety seconds between meetings. They are answering one question: does this belong in the next partner meeting or does it die in the inbox? Optimize the Who We Are, Traction, and Fundraising blocks. Everything else is background.

The cold outbound reader. An associate at a fund receives your summary from an outbound email or a demo day PDF. They will read it in thirty seconds while triaging a hundred others. They are answering a different question: is there any pattern here I recognize? Optimize the Problem, Founder's Story, and Critical Differentiators blocks. Pattern-matching lives there.

The strategic reader. A corporate development lead, a lender, or a family office receives your summary with an ask attached — pilot, credit facility, or check. They will read it in five minutes and share it internally. They are answering a third question: is this business real, and is the ask specific? Optimize the Revenue Model, Fundraising, and Team blocks.

The template has eleven blocks. Every block is present in every version. Weight shifts by reader.

The opening line is the entire summary in miniature. If a reader stops after the first sentence — and many do — this is the sentence they walked away with. Two constructions work.

The first is the "we do X for Y" construction. "We are a compliance operating system for regional banks." "We are the payroll platform for restaurant groups with more than fifty locations." Concrete verb, concrete customer, no adjectives. The second is the "we are the X of Y" analogy. "We are Stripe for physical goods." "We are the Shopify of enterprise procurement." Analogy works when the reader knows both referents; it fails badly when either is ambiguous. Use it once, in the opening line, and never again.

Three common failure modes: the mission statement opener ("Our mission is to democratize…"), the technology opener ("We use AI and blockchain to…"), and the industry opener ("The $47B logistics market is broken…"). Investors have read every version of these openings a thousand times. Skip them. Start with what the company does, for whom, and stop.

The Who We Are block is two or three sentences. It ends with a stage tag: "Founded in [year], based in [city], full-time employees." The stage tag lets the reader place the summary on a shelf before reading further.

Traction is the section investors read second and remember longest. The template asks for three numbers: revenue, customers, growth rate. Deliver those three numbers and no others in the block itself. Everything else — logo lists, contracts pending, LOIs — goes below the line as milestones.

The three numbers must be internally consistent. If ARR is $600K and customers are 40, average contract value is $15K, and readers will calculate that themselves. If you list a growth rate, it must be the growth rate of the number above it — not GMV growth reported next to revenue, not signup growth reported next to paid customers. The most common founder error in this block is mixing metric types to make the numbers look bigger. Sophisticated readers spot it in seconds and downgrade the entire summary.

For pre-revenue companies, the traction block still exists. It reports the closest proxy: waitlist size with weekly growth, LOI count with total contract value, pilot count with named counterparties, or usage on a free product with retention curves. What the block cannot say is "pre-launch, no traction yet." That is a decision to remove the block, and removing the block signals that you are not ready to raise on traction — which is a legitimate stage, but it needs to be visible somewhere else in the summary (usually the Founder's Story block).

Below the three numbers, list three dated milestones. "Q2 2025: closed first six-figure enterprise contract with [named customer]." "Q3 2025: shipped v2 with self-serve onboarding, reducing time-to-first-value from 14 days to 45 minutes." "Q4 2025: expanded to Canada with two design partners." Dated milestones do two things: they create a rhythm of execution that pattern-matches as a well-run company, and they give the reader something to ask about in the first meeting.

The Founder's Story block is where pattern-matching happens, and it is where most technical founders under-invest. Investors are not looking for a hero's journey. They are looking for evidence that you have the specific unfair advantage — domain, network, or scar tissue — that makes this company yours to build.

Insider founder. "I spent seven years running procurement at [Fortune 500]. I bought every tool in this category and none of them worked. I left to build the one that would." This construction tells the reader you know the buyer, the pain, and the failure modes of every competitor.

Repeat founder. "This is my third company. My first was acquired by [company] in 2018; my second returned capital to investors after failing to reach product-market fit." The failed second company matters more than the successful first. It signals honesty and hard-won lessons.

Technical wedge founder. "My co-founder and I met in [lab/team]. We spent four years building the algorithm that makes this product possible. Two of the three patents in this space are ours." This construction is for deep-tech only. It signals that the moat exists before the company does.

What does not work: the passion story ("I have always been fascinated by…"), the market observation story ("I noticed that…"), and the credential story ("I have an MBA from…"). Passion is table stakes. Observations are cheap. Credentials are decoration.

Two to four sentences. End with the co-founder(s). "My co-founder [name] led [relevant thing] at [relevant place]. We have worked together for years."

The Problem block is a customer moment, not a market statistic. A reader who cannot restate the problem in one sentence after reading yours has been given a market analysis, not a problem.

The template that works: name the specific customer, name the specific moment, name the specific cost. "A regional bank compliance officer opens a spreadsheet at 6 a.m. on the first of every month to reconcile transactions against BSA rules. It takes forty hours. Errors trigger regulator fines that averaged $2.3M per bank in 2024." Now the reader knows who hurts, when they hurt, and how much it costs. That is a problem.

Compare with the failure mode: "Compliance is a massive and growing challenge for financial institutions, with regulatory complexity increasing every year." A reader learns nothing about who, when, or how much. They cannot restate the problem because there is nothing concrete to restate.

If the problem is one that requires the reader to already believe a market thesis (crypto adoption, agentic AI, remote work), name the belief and defend it in one sentence. "The bet: mid-market banks will need real-time transaction monitoring by 2027 because [named regulation] takes effect January that year." A dated regulation is a defensible belief. "AI will change everything" is not.

The Solution block describes what the product does in the language the customer uses, not the language the engineer uses. If the customer calls it "reconciliation software," do not call it "a distributed ledger for financial event streams." Match the vocabulary of the buyer.

Two to three sentences. First sentence: what the product is. Second sentence: what it does that no existing tool does. Third sentence (optional): how it fits into the customer's workflow.

The rule: every claim in this block must be defensible in a demo. If the summary says "our product cuts reconciliation time from forty hours to fifteen minutes," the demo will show that reduction. If the demo shows something less impressive, the summary loses credibility and everything above it in the document loses credibility too.

Do not describe the roadmap in this block. Roadmap goes in the appendix or in the follow-up call. The Solution block describes what exists today.

This block is where market sizing lives. The template gives you two sentences. Use the first for the market size. Use the second for the shape of the landscape.

Market size the right way: bottom-up before top-down. "There are 4,200 regional banks in the U.S. with assets between $1B and $50B. Each spends between $200K and $2M per year on compliance software. That is a $2.5B addressable market today." Bottom-up numbers survive due diligence. Top-down numbers ("$47B compliance market growing 12% CAGR") die in the first partner meeting.

Landscape sentence: name the two or three real competitors and the shape of the fight. "Three incumbents own the enterprise segment (Actimize, SAS, Nice). No player has purpose-built for mid-market. Our wedge is the mid-market gap." Do not pretend competitors do not exist. Every investor has already Googled the space; the summary that omits competitors loses credibility faster than the summary that names three and explains why they lose in the mid-market.

The template asks for three bullets. Three is the correct number. One differentiator is thin; five is unfocused. Three is the number the reader can hold in memory.

Every differentiator must be a wedge, not a feature. A wedge is a reason to switch that a competitor cannot copy in the next twelve months. A feature is a checkbox that will appear on the competitor's roadmap next quarter.

Good wedges: proprietary data ("we ingest transaction data from a partnership with [named clearinghouse] that no competitor has"), network effects ("every customer we onboard improves the model's precision by 0.4% per week — competitors cannot catch up by shipping features"), regulatory relationship ("we are the only vendor with a signed no-action letter from FinCEN"), incumbent capture ("our founding customer is the compliance officer at the largest bank in [region] — she brought her network"), and speed-to-value ("we onboard in 45 minutes; competitors take six weeks").

Bad wedges dressed as good ones: "better UX," "faster performance," "cheaper price," "better team." These are outcomes of a wedge, not the wedge itself. Investors will ask "why is your UX better?" and the honest answer is either a wedge or nothing.

Two sentences. First sentence: how you charge. Second sentence: what the average deal looks like today.

"We charge a per-seat subscription of $199/user/month with a $30K annual platform minimum. Average contract value on the last ten closed deals was $52K, with a 14-month median sales cycle from first meeting to signed contract." Concrete numbers, current period, honest metrics.

Do not describe pricing you have not launched yet. Do not describe deal sizes you hope to reach. The Revenue Model block is descriptive, not aspirational. Aspirational numbers belong in the financial forecast (Block 11, appendix) where they can be defended with assumptions.

The single most credibility-destroying pattern in this block: the "we plan to charge" construction. If you have not charged anyone, say so, and describe the pricing model you plan to launch. "We are pre-revenue. Design partners pay $0 today; conversion to paid begins in Q3 with a target $30K annual contract." Honesty about pre-revenue is fundable. Vagueness about revenue is not.

The Fundraising block is two sentences and controls the meeting that follows.

Sentence one: how much and on what terms. "We are raising a $5M seed round on a SAFE, valuation cap $30M, MFN." The cap and instrument matter more than the amount. Investors have a mental model for "$5M seed at $30M cap" — it maps to a specific stage, specific ownership expectations, and specific reserve math. "$5M seed" alone leaves the model incomplete.

Sentence two: use of funds. "The round extends runway 24 months, funding two engineering hires, one enterprise AE, and the certification required to sell into the top thirty U.S. regional banks." Three uses is the correct number. Every use maps to a milestone that unlocks the next round. If you cannot describe how the money produces the next round, the fundraise is under-planned.

"We are raising to hire engineers and marketing." Vague. What does the engineer build? What does marketing test? "We are raising $10M-$15M." Ranges signal indecision. Pick a number and defend it. "We are open to different structures." Signals inexperience with venture. Pick an instrument and lead with it; if a lead investor proposes an alternative structure, negotiate then.

The Team block lists founders and, if relevant, one or two key hires. Every entry follows the same format: name, role, one sentence of the specific unfair advantage they bring to this company.

"[Founder A], CEO. Spent eight years at [company] leading the team that built [relevant thing]. Deep relationships across the top thirty regional bank compliance officers."

"[Founder B], CTO. Built and sold [previous company] to [acquirer] in 2019. Led the team that shipped [technical thing that maps to this company's differentiator]."

Do not list responsibilities ("responsible for product strategy and team leadership"). Every founder is responsible for that. List the specific reason this person is the right founder for this specific company.

If the team has a gap — no full-time technical co-founder, no domain expert, no U.S.-based commercial lead — the summary should either name the hire that closes the gap and the timeline for closing it, or accept that the gap will be surfaced in every pitch meeting and let the founder story explain why the gap does not kill the company. Silence about the gap is the worst option.

The Advisory Board block signals proximity to the right networks. Three advisors is the correct number. Every advisor is named. Every advisor gets one sentence of specific relevance to this company.

Do not list advisors who have not actually agreed to advise. Do not list advisors who are inactive. Investors call advisors during diligence, and a "surprised" advisor is a fireable offense against the summary.

Below the advisory board block, the template includes address, email, and the securities-law disclaimer required by SEC Rule 506 for private offerings. These are not decoration — the disclaimer is what makes the summary compliant when it circulates outside the founders' immediate network.

1. Writing it first. The executive summary compresses the deck and the model. It cannot be honest before those exist. Write it last. 2. Optimizing for length instead of density. A one-page summary with dense claims beats a two-page summary with padding. Every sentence must earn its place. 3. Using the pitch deck as raw material. Deck copy is designed for eight seconds of attention with a speaker. Summary copy is designed for ninety seconds of attention without one. Different mediums, different sentences. 4. Hiding the ask. The Fundraising block goes near the end for a reason — the reader has to understand the business first — but it goes on page one. If the reader has to scroll to find the ask, the summary has failed. 5. Passive voice on traction. "Revenue has been achieved" versus "We closed $600K in ARR." Every traction claim uses active voice and names the founder or the company as the actor. 6. Weasel words on differentiation. "Leading," "innovative," "cutting-edge," "next-generation." These words test badly against sophisticated readers. Replace every weasel word with a concrete claim or delete the sentence. 7. Omitting competitors. The summary that pretends no one else is in the market signals that the founder has not done the work. Name three competitors. Explain why you win. 8. No update rhythm. The summary is a working document, revised every fundraise cycle. Founders who ship the same summary quarter after quarter miss the trailing traction that is often the strongest argument for the next round.

Print the template. Highlight every block your current summary either lacks or fills badly. For each highlighted block, write the honest one-sentence version — the version you would actually say out loud to a partner across a table. Assemble the honest sentences into a full summary. Read it aloud. If a sentence sounds like a founder speaking, keep it. If it sounds like a consultant writing, cut it.

Circulate the summary to three people: a founder who has raised in your stage, an investor who is not a fit for your round (they will read honestly because they are not deciding), and a domain expert who is not on your cap table. Each of the three will surface a different failure mode. Fix all three before the summary leaves your inbox.

The executive summary is one page. It will take you two weeks to write it well. That is the correct amount of time. Every fundraise you run for the rest of the company's life starts with this document.