On this page
At seed, a ₹2 crore raise can disappear faster than founders expect: a few senior hires, product rebuilds, cloud bills, customer acquisition experiments, and a delayed collection cycle can consume most of the runway. A seed round use of funds plan India is how you show investors that every rupee has a job, a timeline, and a measurable result.
What a seed round use of funds plan in India must answer
A use of funds plan is not a pie chart added to the final slide of your deck. It is an operating plan that explains what the company will do after capital lands, what evidence each spend category will create, and what milestone makes the next round possible. Investors use it to test whether your raise amount matches the business you are building.
Indian founders often begin with a number they believe sounds reasonable, then reverse-engineer categories to fill it. Start the other way around. Define the milestone you need to reach, identify the work required to get there, calculate the team and operating costs, then determine how much capital that plan requires.
The core question: If we fund this company for the planned runway, what will be materially true at the end that is not true today? Your answer should cover product, customer proof, revenue quality, team capability, and financing readiness.
A good plan also separates “needed to operate” from “needed to learn.” Building a feature may be an operating expense. Running a narrow pilot to find whether that feature drives repeat usage is a learning expense. Both can be valid, but investors need to see the logic connecting the spend to a decision.
At Nebula, we treat fundraising as one stage in a wider build process, not an isolated event. Our venture process moves from idea and market work through product, validation, funding, and scale because a credible raise depends on work completed before the pitch and execution planned after it.
Start with the next fundable milestone
Your seed round should buy a defined transition in the company. For a SaaS business, that could mean moving from founder-led pilots to repeatable paid deployments. For a consumer company, it may mean proving repeat purchase behaviour in a focused customer segment. For a marketplace, it may mean demonstrating that demand, supply, fulfilment, and unit economics can work together in one narrow operating zone.
Do not describe the milestone using vague language such as “scale the business” or “grow awareness.” Those phrases do not establish what the company will know at the end of the round. State the evidence you plan to produce and the operating capability required to produce it.
| Weak milestone | Fundable milestone | What the use of funds must support |
|---|---|---|
| Increase sales | Establish a repeatable sales motion for a defined customer segment | Sales capacity, customer research, onboarding, pipeline tracking |
| Build the app | Release the smallest product needed to validate a paid user behaviour | Product team, design, engineering, testing, support |
| Expand across India | Prove one geographic or customer segment playbook before replication | Focused GTM tests, local operations, measurement systems |
The milestone also sets the raise amount. If your plan needs 12 months to build, test, sell, and learn, calculate the cash required for that period rather than selecting a round size based on another founder’s announcement. A seed round is useful only if it gets you far enough to tell a stronger financing story later.
Write the milestone as a sentence at the top of your internal plan. Every budget line should connect to it. If a line cannot be linked to a milestone, defer it, reduce it, or remove it.
Turn the plan into operating buckets
Most seed budgets fall into five working buckets: people, product and technology, go-to-market, operations, and contingency. The categories are familiar. The quality of your plan comes from the detail underneath them. “Team” is not enough; investors need to know which roles you will hire, when they enter, what work they own, and why founders cannot cover that work yet.
Use hiring timing instead of assuming every role starts on day one. A senior sales hire may make sense only after founders have closed enough early customers to understand the sales process. A finance hire may be premature if outsourced support can handle the current workload. Early hiring must remove a proven bottleneck, not create a larger monthly burn.
- People: founders, planned hires, contract specialists, statutory and payroll costs.
- Product and technology: engineering, design, infrastructure, software tools, security work, testing, and integrations.
- Go-to-market: customer acquisition experiments, sales travel, pilot delivery, partnerships, customer success, and marketing production.
- Operations: legal, accounting, compliance, workspace, equipment, insurance, and business administration.
- Contingency: a deliberate reserve for delays, failed experiments, collections pressure, or costs you cannot yet predict precisely.
Keep each bucket tied to an owner. Product spending needs a product owner. GTM spending needs a founder or operator responsible for the experiment. Operating costs need a clear approval process. Without ownership, a budget becomes a retrospective explanation rather than a management tool.
We see stronger fundraising preparation when founders make the budget part of their weekly operating rhythm. Nebula 1.0, our current two-week fundraising sprint, helps founders turn scattered assumptions into a fundraise case that can stand up to investor questions.
Apply for Nebula 1.0 if you need to pressure-test your raise narrative, use of funds logic, and investor materials before starting outreach.
Tie every rupee to a measurable output
Investors do not expect you to predict the future with precision. They do expect you to know what each major spend is meant to produce. This is where founders move from expense categories to operating logic. A product hire should produce a release, a learning cycle, or a reliability improvement. A GTM budget should produce qualified conversations, activated users, pilots, paid conversions, or a clearer channel decision.
For each major budget item, document four things: the cost, the start month, the owner, and the expected output. Then add the metric that tells you whether the spend is working. That metric should be close to the activity. Do not measure a new customer-success hire only through annual revenue if the first evidence should be onboarding completion or early retention.
There is a difference between a metric and a target that exists only to impress. Use targets based on your current operating data, customer conversations, pilot results, or known delivery capacity. When evidence is thin, present the assumption plainly and explain how you will test it. Sophisticated investors can accept uncertainty; they are less patient with false certainty.
A practical plan also names the decision point. If a channel has not produced the expected result after a defined period and spend level, what changes? Will you stop, revise the offer, narrow the segment, or move funds to a channel already showing better quality demand? Capital discipline is partly about knowing when to stop funding a weak assumption.
Your deck can show this in one clean slide, but your internal model must go deeper. Keep a monthly view of expenses, cash balance, hiring dates, expected receipts, and milestone progress. The investor version should be simple because the underlying work is not.
Build runway around cash, not revenue hope
Revenue forecasts can make a use of funds plan look attractive while hiding a cash problem. A signed customer may pay late. A pilot may take longer to convert. A large contract may require implementation work before collections begin. Your runway plan must survive those timing differences.
Start with opening cash, then map monthly outflows and expected inflows. Include salaries, contractor payments, software, compliance, customer delivery, travel where relevant, and tax obligations. If you have receivables, model when cash is expected to arrive rather than treating booked revenue as money already available to spend.
| Planning layer | What to include | Why it matters |
|---|---|---|
| Base case | Current conversion assumptions and planned hiring | Shows the primary operating plan |
| Downside case | Slower sales, delayed collections, higher delivery effort | Shows where cash pressure appears first |
| Response plan | Hiring pauses, reduced experiments, revised spend sequence | Shows how founders retain control when assumptions fail |
Do not use contingency as an excuse for loose budgeting. It exists because early-stage work contains uncertainty. State what it protects: a delayed launch, an extended enterprise sales cycle, a replacement hire, or an unplanned compliance need. If you cannot explain the reserve, investors may read it as evidence that the rest of the model lacks rigour.
Runway is also a fundraising variable. Begin preparing for the next round before cash forces the conversation. A company that raises while it still has choices can negotiate from evidence and momentum. A company that waits until cash is nearly exhausted must often accept terms under pressure.
Present the plan in your seed deck
Your deck needs one use of funds slide, not a finance department report. The slide should show the raise amount, the major allocation buckets, the expected runway, and the milestone the capital is designed to reach. Put the detailed monthly model in your data room or share it when an investor asks for it.
Use percentages only when they help the reader understand the shape of the plan. In most conversations, absolute INR amounts are more useful because they force clarity. A founder who says “40% for product” may still have no answer on which roles, vendor costs, or delivery outcomes sit inside that category.
Prepare for direct investor questions. Why this amount rather than less? Why hire now? What happens if revenue arrives later? Which expenditure can be delayed? What will prove that customer acquisition is repeatable? What is the next financing event designed to fund? Your answers should match the budget, the product roadmap, and the GTM plan.
Keep the story consistent across your materials. If your deck says the round is for customer acquisition but your budget is dominated by product rebuilding, investors will spot the mismatch. If you claim a product is ready but need most of the round for core development, explain what remains and why it matters.
Our work as a venture builder covers validation, product, fundraising, and go-to-market alongside founders. You can review the kinds of companies we have worked with through our portfolio, or see how our engagement models support companies from prototype through scale-up.
Treat the plan as a founder operating contract
The strongest seed round use of funds plan India founders can present is one they already use to run the company. It sets priorities between co-founders, gives hiring decisions a standard, and prevents attractive but unrelated opportunities from pulling the team away from the funded milestone. Once money enters the account, this plan becomes a commitment to the company and to the investors who backed it.
Review it monthly, but do not rewrite it every time the market becomes noisy. Compare actual spending against plan, inspect the output from each major investment, and decide whether the original assumptions still hold. When evidence changes, revise the model and record why. That discipline helps you build a cleaner board update and a more credible story for the next raise.
Seed capital should create proof, not merely extend survival. Spend first on work that reduces the largest risk in the business: whether customers want the product, whether you can deliver it reliably, whether the unit economics can work, or whether a repeatable route to market exists. The order will differ by company, but the rule holds.
Your plan does not need to look perfect. It needs to show that you understand the trade-offs, have chosen a sequence, and will measure whether the capital is producing the intended result. That is how you shift the investor discussion from “How much are you raising?” to “What does this company become after this round?”
Build a raise plan that can survive investor diligence and real operating pressure. Apply for Nebula 1.0 to work through your fundraising case before you enter the market.
Enjoyed this? Get the next one in your inbox.
Fundraising guides and validation frameworks, every two weeks. No spam.
Frequently asked questions
What should a seed round use of funds plan include?
Include the raise amount, planned runway, people costs, product and technology costs, go-to-market spending, operating expenses, contingency, and the milestone each category is meant to achieve.
How detailed should the use of funds slide be in a seed deck?
Keep the deck slide high level: show major INR allocation buckets, runway, and the milestone the round will fund. Maintain a monthly cash and hiring model for diligence conversations.
How should Indian founders calculate a seed round amount?
Start with the next fundable milestone, map the work and team needed to reach it, create a monthly cash plan, test a downside scenario, and calculate the capital required for that sequence.
Ready to build your startup?
We work with a small number of founders each year — mentorship, fundraising support, and a co-founder network included.
Start a conversation
Talk to the founder directly. We reply within two working days.
Applying to Nebula 1.0? Apply here →