The ask slide is an allocation of proof

The slide that says nothing

The last slide of most decks says some version of this: "Raising $2M. 50% engineering, 30% sales and marketing, 20% G&A. 18 months of runway." Sometimes there is a pie chart. The colors are nice.

An investor reads that and learns almost nothing they can act on. They already assumed you would spend most of it on people. They have no idea what those people will produce, what will be true about the company in 18 months that is not true today, or why $2M is the right number instead of $1.2M or $3.5M. The slide answers "where will the money go" when the question in the partner's head is "what does this money buy, and will it be enough to get you to a round I'd want to lead next."

A pie chart by department is an accounting view of your own company. It treats the round as a budget to allocate. But the investor is not funding your budget. They are funding the removal of the specific risks that are keeping your valuation where it is. The money is a means. The milestones are the product. A use-of-funds slide that leads with departments has buried the only thing the investor came to see.

Why the department pie chart fails

The breakdown-by-function slide fails for three reasons, and all of them are about what the investor cannot infer from it.

It hides the milestones. "50% to engineering" could mean you ship the enterprise version that wins six-figure contracts, or it could mean you refactor the backend. One de-risks the business. One does not. The percentage tells the investor nothing about which.

It makes the amount look arbitrary. When the ask is a budget, $2M and $2.5M look equally defensible, which means neither is defensible. The investor has no anchor to judge whether you are raising the right amount. Raise too little and you stall before the milestone that earns the next round. Raise too much and you dilute for proof you didn't need yet. The department split gives them no way to check either failure.

It disconnects the raise from the next raise. Seed money exists to buy the metrics that make the Series A fundable. If the slide doesn't name those metrics, the investor has to reverse-engineer your plan to figure out whether this round even sets up the next one. Most won't. They'll just register the slide as generic and move on to the parts of the deck that tell them something.

The underlying mistake is framing. Founders build the slide by asking "how will I spend this." Investors read it by asking "what will be true when this is spent." Those are different slides.

Use of funds as an allocation of proof

Reframe the slide around one idea: every dollar in the round is buying down a specific risk by hitting a specific milestone. Your job is to show the allocation of proof, not the allocation of cash.

Start from the milestone, not the money. Before you touch the budget, write down the two to four things that must become true for your next round to be easy to raise. Not vanity goals. The specific risks an investor at the next stage will care about. For most companies these cluster into a few categories:

Market risk: can you find and reach customers who pay. Product risk: can you build the thing that makes them stay. Revenue risk: does the unit economics work at the price you charge. Team risk: can you hire the people who get you to the next stage. Each milestone you fund should remove one of these, and you should be able to name which.

Then attach money and time to each milestone, not to each department. The question for every line is: what does removing this risk cost, in dollars and in months, and what is the proof point that shows it's removed. "Reach $50k MRR" is a milestone. "Spend $600k on sales" is a budget line. The first tells the investor what they're buying. The second tells them you have a sales team.

Finally, connect the milestones to the next event. The bottom of the slide should make one thing obvious: when these milestones are hit, the company is positioned for [the next round, profitability, or the metric a Series A investor needs]. That sentence is what turns a spending plan into an investment case. It tells the partner that funding you now is a step on a path they can see the rest of, not a bet into fog.

The reframe is not cosmetic. It changes what you raise. When you size the round from the milestones up, the amount stops being a round number and becomes the cost of buying the proof you need plus a runway buffer to raise the next round from a position of strength. That is a number you can defend line by line.

Before and after

Here is the same company, same plan, two ways of presenting the ask.

Before (department pie):

Raising $2M. Allocation: Engineering 50%, Sales & Marketing 30%, G&A 20%. 18 months runway. Use of funds: grow the team and accelerate growth.

After (allocation of proof):

Raising $2M to remove the three risks standing between us and a Series A. By month 16 we will have: (1) closed the product gap that loses us enterprise deals, proven by 5 paying enterprise logos; (2) shown the sales motion repeats, proven by a rep other than the founder hitting quota; (3) reached $1.5M ARR at 110% net retention. That gets us to Series A metrics with 4 months of buffer to run the raise. The $2M is the cost of those three milestones plus that buffer.

The "before" is true. The "after" is true and fundable. Same company, same spend, but the second version hands the investor the exact thing they were trying to extract from the first: what this money makes true, and why it's enough.

The use-of-funds milestone table

This is the artifact. Build the table first, on a working slide or a doc, then compress it into the deck slide. One row per milestone, not per department. The department spend falls out of the rows; it is an output, not the input.

Three rules make the table work. First, every milestone names the risk it removes in plain language, because that is what the investor is buying. Second, every milestone has a proof point a stranger could verify, not a goal only you can score. "Sales is repeatable" is a goal; "one non-founder rep at quota for two quarters" is a proof point. Third, the bottom row reconciles to the ask to the dollar, so the amount is the sum of named milestones plus a stated buffer, never a round number you backed into.

When a cell is genuinely unknown, write the assumption instead of faking precision. "[assumes 1 enterprise deal closes per quarter from month 6]" is honest and a partner can argue with it. A made-up number that collapses in the first diligence call costs you the round.

How the table shifts by stage

The structure holds across stages. What changes is which risks dominate and how hard the proof points are.

At pre-seed, you are buying the right to exist. The milestones are mostly product and first-signal: ship the thing, get the first handful of users or design partners who would be sad if it disappeared, show one loop works. Proof points are qualitative and small-n, and investors know it. Sizing the round to "12–18 months to a seed-worthy signal" is the move; precision theater hurts you here.

At seed, you are buying repeatability. The risks shift to "does this go to market" and "do the economics work." Proof points get quantitative: a revenue number, a retention number, a channel that returns more than it costs. The table should tie the round to specific traction metrics a Series A investor will ask for by name.

At Series A, you are buying scale efficiency. The risks are "does this get more efficient as it grows" and "can the org execute a step-change." Proof points are about ratios and systems, not existence: payback period, magic number, a sales org that runs without the founder in every deal. The buffer line matters most here, because A-to-B rounds are sized on demonstrated efficiency, and running out of room mid-proof is fatal.

Across all three, the discipline is identical: name the risk, attach the proof, size the money to the proof, reconcile to the ask. Only the content of the rows moves.

Why this matters for the round

The ask slide is the last thing an investor sees and the first thing they bring to their partners. When it is a department pie chart, the partner who liked your deck has nothing concrete to repeat in the Monday meeting except "they're raising $2M, seems early." When it is an allocation of proof, that same partner can say "they're raising $2M to hit three milestones that set up a clean A, and the math reconciles." The second version arms your champion to sell you when you are not in the room. That is most of what the slide is for.

It also pre-answers the question that kills momentum: "why this amount." Founders dread that question because the honest answer to a budget-based ask is "it felt right." With a milestone table, the answer is already on the slide. The amount is the cost of the named proof plus the buffer to raise from strength. You stop defending a number and start defending a plan, which is a conversation you can win.

Where RoundOS fits

The milestone table is the easy part. The hard part is that the round is a moving target: a partner pushes back on your ARR assumption, a milestone slips a quarter, a new comp resets what "Series A ready" means, and the plan you put on the slide drifts from the plan you are running day to day. Most founders keep the plan in the deck and the round reality in their inbox and notes, and the two slowly diverge.

RoundOS pulls the sources where the round already lives, your notes, emails, the deck, and the tracker, and keeps the round plan connected to the conversations happening against it. When an investor questions a milestone or an assumption, that objection attaches to the plan instead of getting lost, and the next move it implies (revise the buffer, line up a customer reference, update the ARR slide) shows up in your decision queue as a follow-up to make, not a thing to remember. The use-of-funds table is the input. A round plan that stays current as investors react to it is the output.