How Much Should My Startup Raise?

Short answer: Raise the amount that funds one important company chapter, reaches a measurable milestone, and leaves enough time to handle the next financing decision. The right ask is not the largest number an investor might accept or the smallest number that keeps the lights on; it is the amount your plan can explain.

What the question is really asking

“How much should we raise?” is usually shorthand for three linked decisions: what the company needs to prove next, how long that work will take, and how much uncertainty the team can absorb. A founder who starts with a market headline—“seed rounds are usually X”—can end up choosing a number before choosing the milestone. Reverse the order. Define the work first, then price the chapter.

Start with the milestone

Write the next milestone as an observable change in the business. It might be a repeatable sales motion in one segment, a product release that unlocks usage, a defined revenue level, or a validated path to a larger round. Avoid milestones that describe activity rather than evidence. “Hire five people” is an input. “Prove that one sales pod can acquire and retain a defined customer profile” is an outcome.

Then ask what evidence would make the next investor conversation different. If the answer is unclear, the round size is premature.

Build the operating plan

List the people, product work, distribution experiments, infrastructure, professional services, and operating costs required to reach the milestone. Separate committed costs from optional bets. The plan should be understandable without a spreadsheet tour.

• What must happen in the first 90 days?

• Which hires are required, and which are conditional?

• Which costs scale with customers or usage?

• What work can be delayed without changing the milestone?

• What assumption would cause the plan to change?

Do not let the fundraise become a wish list. Every line should have a job in the company’s next chapter.

Translate the plan into runway

Runway is the number of months your cash lasts under a defined burn plan. The simple formula is cash divided by monthly net burn, but a usable fundraising model has more than one case: base, downside, and an explicit hiring or spend trigger.

Use enough runway to reach the milestone and absorb ordinary fundraising friction. Do not assume a round closes on the day your cash reaches zero. The appropriate buffer depends on the stage, process complexity, existing traction, and the risk that the milestone will take longer than expected.

Include the cost of getting to the next decision

A round is not only the product and payroll. It also buys the time needed to learn, sell, recruit, comply, and, if necessary, fundraise again. Include legal and accounting work, software, hiring costs, customer implementation, travel if relevant, and the operating slack required to avoid making every decision under emergency conditions.

At the same time, avoid padding the model with a vague “just in case” reserve. Explain the specific risks the buffer covers: slower sales, a delayed launch, a critical hire taking longer, or a financing market that requires more time.

A worked example: from milestone to ask

Imagine a company with $80,000 in monthly net burn and $600,000 in cash. The next proof point is to reach 20 retained customers in one segment, which the founders estimate will take 12 months. They expect to hire two people, add $15,000 per month of operating expense, and hold a 15 percent downside buffer.

The base monthly burn is $95,000, so 12 months requires $1.14 million. If the team adds a three-month process buffer at the same burn, that adds $285,000. A 15 percent contingency on the operating plan adds another amount that should be modeled explicitly rather than hidden. The result may point to an ask of around $1.6 million, but the final number should be checked against dilution, investor appetite, and whether all planned spending is necessary.

These numbers are illustrative, not a market benchmark. If the founders can reach the same proof point with one hire and a narrower product scope, the defensible ask changes. The model should make that tradeoff visible.

Pressure-test the ask from both directions

Ask what happens if you raise 25 percent less. Which milestone slips, and by how much? Then ask what happens if you raise 25 percent more. Does the extra capital create a real strategic advantage, or does it add dilution and expectations before the company has the operating system to use it?

A larger round can reduce financing frequency but increase dilution, execution pressure, and the size of the milestone investors expect next. A smaller round can preserve ownership and focus, but it may leave too little time to reach meaningful proof. The point is not to prefer one size; it is to show the consequence of each.

The founder decision

Your ask is becoming defensible when you can state: current cash and burn, the milestone the capital buys, the people and costs required, the runway under a downside case, the buffer you chose and why, and what evidence would change the plan. If any of those lines is missing, keep working before broad outreach.

When not to raise yet

Do not raise simply because a headline round size is available, because other founders are fundraising, or because the company has not decided what capital is meant to change. If the next milestone is still a collection of unrelated experiments, a smaller evidence-building plan—or no round yet—may create more value.

Your next step

Build a one-page raise plan with three columns: milestone, required spend, and evidence created. Add the base and downside runways, then use The Raise Memo’s Raise Calculator to compare a focused ask against larger and smaller scenarios.

Related reading: How Long Should Startup Runway Be After a Fundraise? · What Is a Defensible Fundraising Ask?

This is general education, not legal, tax, or investment advice.