How to Deploy Your $5M Seed Round: A Decision Framework for Founders
Raising a $5M seed round is a remarkable achievement. The weeks after the wire lands are exhilarating. And then the question arrives — the one that keeps thoughtful founders awake at night: what exactly do I do with this money?
It sounds trivial. You have $5M. The company needs to grow. Spend the money on things that make it grow. But in practice, seed round capital allocation is one of the most consequential and most frequently botched decisions a founding team makes. The decisions about what to hire for, when to build versus buy, how much to spend on early sales, and how to sequence product development have a disproportionate impact on whether the company arrives at a Series A meeting with a compelling story or a desperate one.
At KnownWeil Capital, we have worked closely with 21 portfolio companies through their post-seed deployment phases. The patterns are clear enough that we now share a capital allocation framework with every company we back at close. This piece makes that framework public.
The Single Most Important Framing
Before we discuss specific allocation decisions, we need to establish the frame. A seed round is not operating capital for building a business. It is proof-of-concept capital for answering one specific question: can this team find evidence of product-market fit in a specific, bounded market before the money runs out?
This framing matters because it changes the calculus on every spending decision. The question is not "will this hire add value?" or "will this feature improve our product?" The question is "does this spending move us materially closer to evidence of product-market fit within our runway?" Spending that does not address that question — however defensible it might seem in a normal operating context — is consuming runway without purchasing the evidence that unlocks the next funding milestone.
We define product-market fit evidence specifically, because the term is frequently used loosely in ways that obscure rather than illuminate the underlying question. For a B2B SaaS company (the category where most of our portfolio sits), we require three indicators: first, five or more paying customers who are not personal connections of the founding team and who have renewed at least once; second, customer satisfaction scores showing 8+ NPS and unprompted referrals; and third, a sales process that has been run at least three times by someone who is not a founder, producing the same outcome. When a company can demonstrate all three, we believe they have crossed the threshold from uncertain to compelling for a Series A conversation.
Phase One: Months 1–6, Defend the Core
The first six months following a seed close should be the most conservative period in the company's capital deployment. This runs counter to the instincts of many founders, who have spent months in fundraising mode and are eager to deploy capital aggressively once the round is done. The instinct to move fast is right; the instinct to spend fast is frequently wrong.
In Phase One, the founding team should resist almost all headcount expansion. The founders, plus any hires made before the seed round, should be sufficient to build the initial product, run the first 5–10 customer conversations, and develop the first commercial relationships. Each hire made in Phase One dilutes the signal quality from the early market interactions. When a company has 12 people and sells its first 10 customers, it is genuinely unclear which variables drove the outcome. When a company has 4 people and sells its first 10 customers, the founder has a much clearer read on what is working and what is not.
The specific allocations we recommend for Phase One are: 70% on engineering and product (the founding team plus one to two senior engineers if the founding team does not include adequate technical depth); 20% on customer discovery and early sales (founder-led, with no dedicated sales headcount); and 10% on infrastructure, legal, and administrative costs. Total monthly burn in Phase One should not exceed $80,000–$100,000 for a team of four to six people.
The critical discipline in Phase One is customer discovery intensity. The founders should be having 3–5 substantive customer conversations per week — not demos, but deep discovery sessions designed to validate or refute the core assumptions about the problem they are solving. The product built in Phase One should be the minimum coherent expression of those assumptions, not a feature-complete platform. The goal of Phase One is to arrive at Month 6 with a clear hypothesis about what the product needs to be to achieve product-market fit, validated by a substantial corpus of customer evidence.
Phase Two: Months 7–14, Accelerate the Signal
If Phase One ends with the founding team having genuine conviction in a specific product direction — supported by customer evidence, not wishful thinking — Phase Two is the period to begin accelerating. The transition from Phase One to Phase Two is one of the most important judgment calls a founding team makes, and getting it wrong in either direction is costly.
Transitioning too early — before the core hypothesis has been validated — is the more common and more expensive mistake. We have seen multiple portfolio companies accelerate headcount in Month 5 or 6, based on excitement about early customer conversations, only to discover in Month 9 or 10 that the initial product direction required significant revision. The company then has to carry an inflated team through a pivot, which consumes runway and creates cultural disruption at the exact moment when clarity and focus are most needed.
Transitioning too late — remaining in a Phase One conservatism mode after the core hypothesis has been validated — is less common but equally damaging. Companies that move slowly in the presence of genuine product-market fit signals leave room for competitors, frustrate customers who want more, and arrive at their Series A conversation with traction that is less impressive than it should be given the time and capital invested.
The right transition signal is specific: a founder should be able to point to at least three customers who are using the product weekly, showing demonstrable value, and expressing strong interest in purchasing more or referring the product to peers. When that signal is present, the transition to Phase Two is warranted. When it is not, the right response is to continue Phase One discipline and revise the product direction until the signal appears.
Phase Two allocation shifts materially toward go-to-market investment. We recommend: 45% on engineering and product (maintaining development velocity while beginning to shift focus from problem exploration to feature depth and reliability); 35% on sales and customer success (the first dedicated go-to-market hire, typically a founder-quality individual contributor who can both close and manage accounts); and 20% on supporting infrastructure. Monthly burn in Phase Two typically runs $180,000–$220,000.
Phase Three: Months 15–18, Construct the Series A Narrative
The final phase of seed capital deployment is explicitly in service of a single outcome: a compelling Series A conversation. By Month 15, the company should have a clear picture of its product-market fit evidence, its unit economics at a small but meaningful scale, and the go-to-market motion that will drive growth from the Series A capital.
The mistake we most frequently see in Phase Three is confusion between the metrics that matter for operational health and the metrics that matter for a Series A conversation. These overlap but are not identical. A Series A investor is primarily evaluating whether the company can grow revenue efficiently from a larger capital base. The specific metrics they use to make this assessment vary by category, but in enterprise SaaS they typically include: ARR growth rate (minimum 3x year-over-year at the seed-to-A transition), net revenue retention (above 110% is the current threshold for a strong story), average contract value trajectory (ideally increasing as the company finds its natural buyer), and sales cycle length (shorter is better, but the trend matters as much as the absolute figure).
Phase Three capital should be deployed in ways that support the construction of this narrative. If the company's NRR is below 100%, Phase Three capital should prioritise customer success investment to reverse churn before the Series A process begins. If the ARR growth rate is strong but the sales cycle is long, Phase Three capital should test whether lighter-touch, lower-ACV products can serve as a land-and-expand motion that improves the acquisition economics. If the product is working but the team lacks the functional depth that a Series A investor expects, Phase Three is the time to make the senior hires that fill those gaps before the investor presentations begin.
"Arrive at your Series A meeting with a story, not just numbers. The story is: here is what we learned, here is what we built, here is the evidence it works, and here is why more capital will produce more of the same outcome at a larger scale."
The Hiring Framework
The single largest driver of seed round capital deployment decisions is hiring — both in terms of capital consumed and in terms of the strategic choices involved. We have developed a set of specific principles for seed-stage hiring that we share with every portfolio company.
First: hire for irreplaceable skills before nice-to-have ones. The technical co-founder who can build the core product, the first account executive who can close the type of enterprise sale you need to demonstrate, the data engineer who can instrument the product to generate the usage evidence your Series A will require — these are irreplaceable early hires. The content marketer, the HR generalist, the office manager — these can wait or be handled by the founding team until after the Series A.
Second: hire people who will be excited to work at the Series A company, not just the seed company. The best early employees are those who are willing to accept below-market compensation in exchange for equity and the experience of a fast-growth company. But they are making that trade based on a belief about what the company will become. If you hire someone who is excited about a 10-person startup but will be uncomfortable with the processes and accountability structures of a 40-person company, you will face a painful transition 18 months after the Series A close.
Third: do not hire to manage a problem. Hire to expand a capability. This distinction is more important than it sounds. Founders who are spending too much time on customer success hire a customer success manager to take those responsibilities off their plate. But a seed-stage company with 8 customers does not have a customer success management problem. It has a product-market fit question that needs the founder's direct attention. Offloading customer interactions to a hire at this stage typically reduces the quality of the feedback loop, not the burden of managing it.
The Equity Compensation Question
One dimension of seed capital deployment that receives insufficient attention is the relationship between the company's option pool and its hiring strategy. Founders who have not thought carefully about option pool management before they begin hiring often discover at the Series A that they have either over-granted equity to early employees — creating dilution pressure at the Series A that surprises the founders — or under-granted equity in ways that make it difficult to retain key people when competing offers arrive during the growth phase.
Our standard recommendation for seed-stage option pool management is to reserve 12–15% of the post-seed fully diluted capitalisation for employee equity, with a vesting schedule that requires four years of service with a one-year cliff. This is the market standard in European technology, and diverging from it in either direction creates complications at the Series A when new investors benchmark the option pool against market norms.
Within this overall pool, the allocation to individual employees should reflect the irreplaceability principle described above. The first 3–4 hires at the seed stage should receive option grants in the range of 0.5–1.5% each, depending on seniority and criticality. Subsequent hires should receive progressively smaller grants as the risk premium attached to early-stage employment declines and as the company's valuation increases.
What Not to Spend On
The framework above focuses on where to deploy capital. Equally important is clarity about where not to deploy it. The most common forms of seed capital waste we observe in our portfolio and across the broader seed ecosystem are worth naming explicitly.
Premature brand investment. A $50,000 brand identity project, a polished website redesign, or a sophisticated content marketing programme are appropriate expenditures for a company that has achieved product-market fit and is using the Series A to scale go-to-market. They are not appropriate expenditures for a pre-product-market-fit company that has not yet identified which customers it is serving or what problem it is solving. Brands are built through customer outcomes, not design projects.
Expensive office space. The trend toward remote-first working has made this less of an issue in European technology than it was five years ago, but it remains a significant source of capital waste in markets where there is cultural pressure to maintain a physical presence in premium office locations. A seed-stage company of six people does not require 2,000 square feet of class-A office space in central Paris or London. It requires a functional working environment that does not consume 15% of monthly operating expenses.
Overcapitalised infrastructure. AWS, Azure, and GCP costs can expand to fill any budget if not actively managed. We have seen seed-stage companies spending $30,000–$50,000 per month on cloud infrastructure for products with fewer than 50 paying customers. The solution is not to hire a DevOps engineer to optimise the infrastructure. The solution is for the founding team to treat infrastructure costs as a first-order metric that receives the same attention as revenue and burn rate, and to make architectural decisions that keep infrastructure costs proportional to customer count until after the Series A.