On this page
A pre-seed pitch deck for Indian VCs has one job: make an investor believe that this team has found a real, urgent problem and can turn early evidence into a fundable company. At pre-seed, you are rarely selling scale. You are selling clarity, speed of learning, and a credible plan for what the capital will prove.
What Indian VCs Need to See at Pre-Seed
Indian VCs know that early-stage companies are incomplete. Your product may still be rough, revenue may be small, and your customer base may be narrow. None of this is automatically a problem. The problem is when the deck hides those gaps behind large market claims, vague product screenshots, or a funding ask with no operating logic.
A strong pre-seed deck answers five questions in sequence. What painful problem exists? Who feels it often enough to pay for a solution? Why is your approach better than the current workaround? What evidence shows that you can execute? What will this round allow you to prove before the next raise?
Do not treat your deck as a company brochure. It is an investment memo in presentation form. Every slide should reduce one uncertainty in an investor’s mind: market risk, customer risk, product risk, distribution risk, team risk, or financing risk.
| Investor question | What your deck must show |
|---|---|
| Is the problem real? | A specific customer, recurring workflow, and existing pain. |
| Can this become a business? | A clear buyer, pricing logic, and route to repeatable demand. |
| Why this team? | Relevant insight, execution ability, and evidence of learning speed. |
| Why fund now? | A defined milestone plan tied to the capital you are raising. |
We see founders lose investor attention when they start with their product. Start with the customer’s broken reality. Your product only matters after the investor agrees that the problem deserves solving.
Build Your Pre-Seed Pitch Deck for Indian VCs Around One Story
The best pre-seed pitch deck for Indian VCs has a single argument running through every slide. It should be possible to state that argument in one sentence: a defined customer has a costly problem, current options fail, your team has a better way to solve it, and early signals justify funding the next stage.
Most weak decks are collections of slides. They have a problem slide, a market slide, a product slide, and a team slide, but the slides do not build on one another. The result is confusion. An investor should never need to infer how your customer interview connects to your product, or how your product connects to your revenue model.
- Problem: Name the customer and the expensive or repeated pain.
- Insight: Explain what you learned that others have missed.
- Solution: Show how your product changes the customer’s current behaviour.
- Proof: Present customer, product, or revenue evidence without exaggeration.
- Plan: State what the round funds and the milestone it delivers.
Keep the deck to a pace that supports a real conversation. The slide count matters less than whether each slide earns its place. If you need three slides to explain the problem, you probably have not defined it sharply enough. If you need four slides to explain the product, you may be describing features instead of customer value.
Your verbal pitch should add context, not rescue the deck. Send a version that can stand on its own because investors may review it before, after, or without a meeting.
Make the Problem and Customer Specific
Your opening problem slide should avoid broad statements such as “small businesses struggle with digitalisation” or “students need better career access.” These are categories, not investment cases. Specify whose workflow is broken, when the problem occurs, what it costs them, and what they do today instead.
For example, a stronger statement names the user, the trigger, and the failed workaround: “Independent retailers reorder fast-moving inventory through calls and spreadsheets, leading to stock-outs during weekly demand spikes.” That statement gives an investor something to test. It also points naturally to the product, buyer, and sales motion.
Customer evidence matters more than customer adjectives. Do not call a problem “massive” or “urgent” without showing why it is urgent. Use direct findings from interviews, pilots, waitlists, signed letters of intent, repeat usage, or paid orders. State the sample plainly. Ten interviews are ten interviews; do not present them as market validation.
Use this test: If your customer can postpone solving the problem for six months without consequence, your pitch must explain why they would buy now. Urgency drives early adoption.
In India, customer segments often differ by city tier, language, trust channel, payment behaviour, and buying authority. Do not assume that one customer profile represents the whole country. Start with the narrowest segment where you can reach users repeatedly and learn quickly.
A useful problem slide gives an investor confidence that you know exactly whom to call for diligence. A vague slide tells them that you are still searching for the customer.
Show the Product as a Better Workflow
Pre-seed investors do not need a polished product tour. They need to understand the core workflow and why a customer would change behaviour. Show the moment where your product removes delay, error, cost, or effort. One annotated screen, process diagram, or short before-and-after flow often does more work than a gallery of screenshots.
Describe the product in customer terms. “AI-powered platform” is not a product explanation. Say what the user inputs, what the system does, what decision or task improves, and what result the user gets. If there is a human operation behind the product today, state that too. Investors are more likely to trust an honest operating model than a false impression of automation.
- Show the customer’s current workflow first.
- Show the specific point where your product enters.
- Explain the measurable outcome you expect to improve.
- State what is live, what is in development, and what the round will build.
Be careful with product roadmaps. A long feature list signals weak prioritisation. Tie each planned product release to a customer outcome or a business constraint: faster onboarding, stronger retention, lower service cost, or access to a new buyer segment.
Our venture-building process separates validation from product development for a reason. A working product cannot compensate for an untested buying decision. Make sure the deck proves both: that people want the outcome and that your product can deliver it.
Use Traction Without Overclaiming
Traction at pre-seed is evidence that reduces uncertainty. It does not need to be revenue alone. A founder with a narrow pilot, repeat product usage, customer deposits, successful onboarding, or a clear conversion pattern may have a stronger case than a founder presenting a large but inactive waitlist.
Present the evidence in its real form. Separate paid customers from free users. Separate signed agreements from informal interest. Separate recurring revenue from one-time project income. If a pilot is unpaid, explain what it is designed to prove and what conversion event comes next.
| Evidence | What it can prove | What it does not prove alone |
|---|---|---|
| Customer interviews | Problem relevance and language | Willingness to pay |
| Paid pilot | Initial buying intent | Repeatable sales motion |
| Repeat usage | Product value for active users | Large market demand |
| Revenue growth | Commercial momentum | Healthy unit economics |
Use a chart only when the trend matters. A chart with three data points can look artificial. In that case, write the evidence clearly and explain the context. Investors will ask how customers came in, why they stayed, what they paid, and what it cost to serve them. Prepare answers before the meeting.
If your evidence exists but the story is still scattered, our current Nebula 1.0 is a 2-week fundraising sprint built to help founders prepare for investor conversations. Apply for Nebula 1.0.
Make Market, Business Model, and Competition Credible
Market slides fail when they start with a giant global category and end with a tiny percentage of it. Indian VCs can recognise top-down arithmetic immediately. Begin with the customer segment you can actually reach in the next 12 to 18 months, then show how that segment can expand through adjacent customers, geographies, or use cases.
You do not need to claim that every customer in India is a potential buyer. You need to show why your initial wedge is focused enough to win and large enough to support the company you intend to build. Explain how many customers fit the initial profile, how they buy, who owns the budget, and what a realistic annual contract or transaction value could look like.
Avoid false precision: Do not create a market-size number from assumptions that have not been tested. If you use your own estimates, label them as assumptions and explain the calculation in the appendix.
Your competition slide should include the alternatives customers already use. These may be spreadsheets, WhatsApp groups, local agents, internal staff, or established software. Saying “no competitors” usually means you have not studied customer behaviour closely enough.
Then explain your edge with evidence. It may come from distribution access, a hard-to-copy operating process, a data advantage that improves over time, or a founder insight earned through direct exposure. A feature comparison rarely makes the case on its own. Features change; customer access and execution discipline are harder to copy.
Turn the Fundraising Ask Into a Plan
Your final slides should answer the investor’s practical question: what changes after this capital enters the company? State the amount you are raising in INR, the expected runway, the main uses of funds, and the measurable milestones you expect to reach. A round is not a reward for effort. It is capital for a defined set of experiments and operating outcomes.
A clear pre-seed use-of-funds plan usually focuses on three areas: product work required for the core use case, customer acquisition or sales experiments, and the minimum team needed to execute. Avoid allocating money across too many functions. Early capital spread across product, hiring, branding, partnerships, expansion, and operations usually produces weak learning everywhere.
- Product milestone: What must work reliably for the initial customer?
- Commercial milestone: What validates repeatable demand or conversion?
- Team milestone: Which capability must become full-time?
- Next-round milestone: What proof will make the next raise credible?
Include the founder and team slide before the ask or immediately after it. Explain why this team has access to the problem, the ability to build, and the commitment to stay close to customers. If there is a gap, name how you will fill it. Investors can accept an incomplete team; they struggle to accept a team that does not recognise what it lacks.
We co-build with founders across validation, product, fundraising, and go-to-market because the deck is only useful when the operating plan behind it is real. Apply for Nebula 1.0 when you are ready to turn your fundraising narrative into an investor-ready process.
Enjoyed this? Get the next one in your inbox.
Fundraising guides and validation frameworks, every two weeks. No spam.
Frequently asked questions
How many slides should a pre-seed pitch deck have?
Use only the slides needed to explain the problem, customer, solution, evidence, market, team, and fundraising plan. Each slide should answer a distinct investor question.
Do Indian VCs expect revenue at pre-seed?
Revenue can strengthen a pre-seed case, but early evidence may also include paid pilots, repeat usage, customer deposits, or clear conversion signals. Present the evidence accurately.
What should founders include in a pre-seed funding ask?
State the amount in INR, runway, main uses of funds, and the product, commercial, and team milestones the round is intended to achieve.
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 →