Investor ask slide that states amount, runway, and milestones

An investor ask slide states how much you are raising, what runway it buys, how funds are allocated, and which milestones make the next conversation non-embarrassing. Vague asks that say raising to grow force partners to invent your plan. Specific asks invite diligence on the plan you actually have.

This guide is built for founders closing a narrative arc in a partner meeting or async forward, seed through Series A, who can already name amount and primary use of funds. Skip it if you have not decided instrument, amount, or what the round must prove; or you want the ask to stay fuzzy until the partner names a number first. Pair it with pitch deck structure, seed vs Series A, and pre-seed checklist. Every section below either teaches a decision rule or shows a worked failure, no synonym padding, no “in today’s world” throat-clearing, no keyword soup.

Who the ask slide is for, and the honest not-for

Read this if you are among founders closing a narrative arc in a partner meeting or async forward, seed through Series A, who can already name amount and primary use of funds You will get leverage here if you already have a decision to force and a short list of proof you can defend in Q&A. The fastest way to waste a week is polishing slides before the decision job is named.

Not for you if you have not decided instrument, amount, or what the round must prove; or you want the ask to stay fuzzy until the partner names a number first In that case, fix the upstream artifact first, whiteboard, memo, or metric glossary, then return. Gamma amplifies clarity and confusion at the same speed. We would rather you delay generation than ship a confident fiction that collapses in the first associate question.

Decision rule: if you cannot state the audience, the decision, and the proof inventory in four sentences, you are not ready for slides. Write those four sentences in a doc, then open a generator. If your four sentences disagree with each other, resolve the disagreement before you touch typography.

The four-line ask stack

Use The four-line ask stack as the operating checklist. It is intentionally rigid. Investors, executives, and operators parse familiar structure as a trust signal; novelty belongs in the wedge and the proof, not in reinvented sequencing that forces the room to decode your originality.

1. Amount + instrument, $3.5M seed on SAFE or priced terms you can defend. 2. Runway, months of operating plan the raise funds at stated burn. 3. Use of funds, three buckets max with percentages or dollar bands. 4. Milestones, two to four outcomes that make the next round or default alive a clean story.

Bend the framework only when a stronger asset earns an earlier slot, for example, putting traction before market when traction is undeniable and the meeting is twelve minutes. Do not bend it because a template looked prettier in another order. When you bend, say why in a speaker note so collaborators do not “fix” it back to generic order by accident.

Proof inventory before pixels

Build a one-screen proof inventory before generation: decision wanted; audience titles; five to twelve metrics with time windows; two customer or operational outcomes; constraints you will not claim; ask or next step terms. That inventory is the only numeric source of truth. Missing numbers become TBD, never model guesses.

Category titles are a failure mode across every deck job. Overview, Solution, Traction, and Next Steps force the room to dig. Claim titles carry skim: name the cost, the wedge, the metric, or the decision. Run a title-only pass before you debate colors. The interactive on this page exists to force that rewrite into something you can paste into Gamma.

One home per metric. If ARR appears on title, traction, and ask, the windows and definitions must match. Associates compare slides side by side; inconsistency reads as spin even when it was only sloppy editing.

Slide budget, density, and the skim test

Meeting length and stakes set slide count; design fills the budget. A twelve-minute partner intro cannot carry eighteen narrative slides without becoming a speed-read disaster. Live rooms stay on the sparse end of the density spectrum; leave-behinds can densify without changing the spine. Use the calculator when this page includes one, then lock the number in your prompt so the model does not invent a tour.

Run the title-only skim: export titles, read them aloud in under ninety seconds, and ask a stranger in your sector to restate the story. If titles are categories, you do not have a narrative yet. Claim titles carry skim; body copy is for the curious. Rehearse with a timer before you change design, founders who practice the spine aloud fix title weakness faster than founders who tweak fonts.

Live versus leave-behind is a structure choice. Live decks can be thinner because you are in the room. Leave-behinds need self-sufficient claims. Do not email a live skeleton as a cold attachment unless you enjoy follow-up confusion.

Worked example with specifics

RelayAuth seed ask rebuild before a Tuesday partner meeting at a multi-stage fund.

Before title: The Ask. Body: Raising to accelerate growth and hire. No runway, no buckets, no milestones. Associate follow-up email asked four clarifying questions the slide should have answered.

After title: Raising $3.5M seed · 20 months · path to $1.4M ARR. Buckets: 45% GTM hires, 35% payer integrations/engineering, 20% runway buffer. Milestones: 40 clinics, $1.4M ARR, CAC payback under nine months on outbound cohort.

Decision rule from this example: if an associate must email to learn amount, runway, or milestones, the ask slide failed before the meeting ended. If you cannot map your own proof into the after state, you are missing inventory, not design talent. Steal the transformation pattern, not the fictional company’s numbers.

Deep dive, the ask slide

The ask is where trust compounds or collapses. Partners forgive a rough product slide if the wedge is clear; they do not forgive an ask that hides the plan. Write the ask in a sentence you can say aloud without looking at the slide: we are raising X for Y months to hit Z milestones via these three spends.

Bridge rounds need even more specificity. Say bridge, name the single milestone that unlocks the next proper round, and avoid raising for optionality language. If you cannot name the milestone, you are not ready to put a number on a slide.

Reconcile the ask with traction homes before you send. If traction shows $420K ARR, the ask path must not imply you already crossed $1M. Path language is allowed; inconsistent present-tense claims are not.

Failure modes, what to cut

Cut these without ceremony:

• Amount without runway months. • Use of funds as a pie with Other 40%. • Milestones that are activities without outcomes. • Ask buried in appendix or only spoken, never written. • Ask that conflicts with traction metrics on earlier slides. • Raising for optionality with no default-alive story.

Cutting is a structure skill. Partners and operators rarely complain that a deck was too short when every remaining slide earns its minute. They do complain, silently, when they cannot find the ask or the decision. If a slide does not change a belief about problem, wedge, proof, or next step, demote it to appendix or delete it. Empty slides kept “because the template had them” are still empty.

Interactive practice, then regenerate surgically

Use the interactive on this page to produce an output you can paste into Gamma, a slide budget, a constrained prompt, or a claim rewrite. Do not treat toggles as decoration. The output should name audience, length, and proof constraints. If the interactive output is vague, your inputs were vague, tighten them before generating slides.

When a section is weak, regenerate that section only. Full-deck rerolls reshuffle metaphors and sometimes invent metrics. Keep a frozen outline document beside Gamma so you can diff titles between versions. Version when claims change, not when a theme color changes. Two to four surgical regenerations beat one magical reroll.

Honesty rule for AI assists: if a number does not appear in your proof inventory, delete it even when it sounds helpful. Helpful fiction is still fiction. Flag unknowns as TBD rather than letting a model guess. Search the deck for digits you did not type before any external forward.

Stage, artifact, and export choices

Stage changes proof weight, not the right to invent. Pre-seed can overweight insight and design-partner signal. Seed needs a clearer wedge and early revenue or strong usage. Series A must show repeatable acquisition and unit economics that survive associate models. Board packs and investor updates are different jobs from pitches, do not paste the raise narrative into a board meeting and call it stewardship.

Present-link when you control the room and metrics will move this week. Export PPTX when a firm process demands markup in a file. Structure survives export only when hierarchy was real in the outline. See export to PPTX and Method when you need fidelity and evaluation language.

Appendix and data room hold density: cohort charts, legal, security, deep competition grids. Label jumps so associates can find methodology. Never open a live meeting in the appendix. Never confuse a persuasive deck with a diligence room, see data room vs deck when the boundary blurs.

Collaboration, Q&A, and revision hygiene

Decks fail in collaboration as often as they fail in content. Name an owner for the spine, an owner for metrics, and a freeze time before the meeting. Late drive-by edits that change ARR windows without updating the ask create diligence traps. Put the metric glossary in speaker notes so a co-founder can update a number without rewriting the narrative voice.

Prepare Q&A from the slides you almost cut. The appendix exists so you can jump when challenged without stuffing the live arc. If a question requires a new slide you do not have, write the answer in a follow-up memo, do not invent a chart mid-call. For AI-assisted decks, keep the prompt and inventory beside the file so revisions regenerate from truth, not from the previous hallucination.

Revision hygiene: change one variable per pass when possible, titles, then proof, then density, then visual theme. Mixing all four in one frantic hour is how teams lose the plot. If stakeholders disagree on story, resolve the disagreement in a one-page memo before regenerating slides again.

Pre-send checklist

• Amount and instrument visible in title or first line. • Runway months match burn assumptions you will defend. • Three use-of-funds buckets max. • Milestones are outcomes with dates or thresholds. • Ask metrics reconcile with traction home slide. • Optional title-slide tease does not replace the full ask.

After the checklist, send titles only to a peer outside your company. If they can pitch the story back, you are ready for design polish. If they ask what you sell or what you want, return to the claim clinic before any external forward. Good structure reduces cognitive load so the room spends time on your wedge, not decoding order. Version the file when structure changes and note what moved, associates running parallel processes deserve a changelog, not a surprise.

Operating notes for the ask slide

Operating note for the ask slide: write the decision sentence before you open any generator. If two stakeholders write different decision sentences, stop and reconcile. Tools cannot merge political disagreement into a clean skim path. Once the decision sentence is shared, lock it at the top of the outline and refuse slides that do not advance it.

Operating note for the ask slide: keep a living metric glossary with definition, window, inclusion rules, and owner. When AI regenerates a section, paste the glossary entries that section may use. If a regenerated slide introduces a synonym metric with a new window, treat it as a defect even if the number looks flattering.

Operating note for the ask slide: schedule a peer skim with someone outside the building of the deck. Give them titles only for ninety seconds. If they cannot restate audience, wedge or core tension, and ask or next step, you are not ready for visual polish. Peer skims catch category titles faster than internal reviews.

Gamma bridge, concrete next step

In Gamma, regenerate only the ask section with amount, runway, buckets, and milestones pasted verbatim from your plan. Do not reroll the whole deck. Keep the ask as the narrative close even if a one-line tease sits on the title slide.

Concrete next step in Gamma: open Gamma, paste the constrained prompt from this page’s interactive output, freeze section order, generate outline first, run a title clinic, regenerate at most three weak sections, rehearse on a present link, then export only if a process demands a file. Score the result on Method before you send. Browse examples for shape, never copy someone else’s metrics. If you need fundraising-specific artifacts after the pitch, continue through the fundraising hub rather than overloading one deck with every job.

If you are comparing tools after the draft, use compare pages with Method language, structure, honesty, editability, export, instead of feature bingo. Billing and plan limits live on billing; product CTAs still route through login until create entry is public. The teaching goal of this page is judgment; the product goal is a faster honest draft.