On this page
Your seed deck may earn the first meeting, but the investor FAQ for Indian seed rounds decides whether that meeting becomes a second call. The FAQ is where an investor tests whether your numbers, customer learning, ownership, and fundraising plan hold together under pressure. Build it before outreach, not after a difficult diligence email exposes the gaps.
What an investor FAQ for Indian seed rounds does
An investor FAQ is a working document that gives direct, evidence-backed answers to the questions investors ask after your pitch. It is not a longer pitch deck, and it is not a script to memorise. Your deck creates interest; the FAQ reduces doubt.
At seed stage, most investors know you will have open questions. They are judging whether you know what is unknown, whether you can explain your assumptions, and whether you have a method for learning faster. A vague answer is usually more damaging than an honest answer that states the current evidence and the next test.
Use the FAQ to create one source of truth across founders. If your CEO gives one version of customer traction, your product lead gives another version of roadmap priorities, and your finance model tells a third story, diligence slows down. A good FAQ forces those stories into one operating view.
- Deck: the investment case in a short narrative.
- FAQ: the detailed proof, assumptions, and trade-offs behind that narrative.
- Data room: the underlying documents that support the FAQ.
- Founder conversation: the judgment that explains why you made each decision.
We see founders treat fundraising as a deck-writing task. It is a company-building task. The answers in your FAQ should reflect the same decisions you use to run validation, product, and go-to-market work through our three-phase process.
Build the question map before writing answers
Start with the questions, not polished prose. Pull questions from prior investor calls, customer interviews, co-founder debates, and the places where your deck makes a large claim in a small amount of space. Every major deck slide should produce at least three follow-up questions.
Group the questions by decision area so you can find weak spots quickly. Your aim is not to predict every question an investor may ask. Your aim is to cover the questions that determine whether the business is fundable at your current stage.
| Decision area | Questions to prepare | Evidence to attach |
|---|---|---|
| Problem and customer | Who has the pain? How often does it occur? Why does it matter now? | Interview notes, user quotes, buyer profile |
| Market | Who pays? What is the initial wedge? How does demand expand? | Segment logic, pipeline, customer categories |
| Product | What works today? What is manual? What must be built next? | Product demo, roadmap, usage data |
| Business model | How do you make money? What changes as you scale? | Pricing, margin assumptions, cohort data |
| Fundraise | How much are you raising? What milestones will it fund? | Use-of-funds plan, hiring plan, runway model |
Keep a separate question log during fundraising. When an investor asks something new, record the exact wording, your answer, and the document needed to support it. If three investors ask a question, it belongs in the core FAQ. If one asks it, it may still reveal a blind spot worth examining.
Write answers that can survive diligence
Each answer should start with the direct answer, then show the evidence, then state the implication. Do not bury the point under background. Investors often scan an FAQ between meetings, so the first two lines must stand on their own.
For example, do not write: “We have received good feedback from many potential users and believe there is strong market interest.” Write: “We spoke with 24 target users in our initial segment. Seventeen described the same workflow delay, and six agreed to test our product. Our next validation step is converting those tests into paid usage.” The second version states the evidence and admits what remains unproven.
Use a three-part answer structure: answer the question directly, name the evidence you have, and state the action that will reduce the remaining risk. This keeps founders from presenting assumptions as facts.
Separate facts from estimates throughout the document. Label actual revenue, signed contracts, active usage, and cash in bank as current facts. Label pipeline, conversion assumptions, future pricing, and hiring outcomes as estimates. Investors can work with uncertainty. They lose confidence when they discover that a founder has blurred it.
Keep the tone calm and specific. Avoid defensive language when a metric is weak. If retention is early, say it is early. If the product is still partly manual, explain why that manual process exists and what you will automate after you have enough repeat demand. Seed capital exists to fund learning and execution, not to reward perfect certainty.
If your answers reveal that the business case is not yet clear, fix the work before you expand outreach. Nebula 1.0 is our current live 2-week fundraising sprint for founders who need to turn company evidence into an investor-ready raise. Apply for Nebula 1.0.
Answer the numbers without performing certainty
Indian seed investors will examine the relationship between your raise amount, burn plan, milestones, and next financing position. The FAQ should make that relationship easy to follow. A founder who asks for INR 1 crore without explaining what it buys is asking an investor to supply the reasoning.
Build one answer for each financial area: current cash position, monthly burn, expected burn after hiring, revenue or pricing model, gross-margin logic, planned raise, and use of funds. The numbers in these answers must match your deck, cap table, financial model, and founder conversation. Check them on the same day before sending materials.
- Raise amount: State the amount and the instrument you intend to use, if decided.
- Runway: Explain the operating period your plan supports under stated assumptions.
- Milestones: Name the product, customer, revenue, or distribution outcomes the capital funds.
- Hiring: Specify which roles are required, when they are needed, and what work they will own.
- Next round logic: Explain what evidence should exist before you raise again.
Do not treat valuation as a standalone answer. Investors will ask why the valuation fits the stage, the quality of evidence, the round structure, and the ownership available. Your response should show your reasoning, not a claim that comparable startups command a certain number. If you do not have a settled position, state the range or structure you are considering and the basis for it.
Include downside cases. What happens if sales take twice as long? What work pauses if the round closes below target? Founders who have thought through these cases appear more prepared than founders who insist the base case is inevitable.
Prepare the questions behind traction
Traction is rarely one number. At seed stage, investors want to know what your traction means, whether it can repeat, and what part of it comes from founder effort. Your FAQ must explain the operating mechanics behind every traction claim in the deck.
For a B2B company, be ready to explain who the buyer is, who uses the product, how a deal moves from first conversation to payment, and why a customer renews. For a consumer company, explain acquisition source, activation behaviour, repeat behaviour, retention window, and the cost or effort required to bring the next user. Do not use aggregate numbers where a trend tells the clearer story.
Ask “what would make this metric false?” If a spike came from one campaign, one enterprise pilot, founder-led sales, or a temporary discount, say so. Then explain what you are doing to test repeatability.
Your answers should also identify the narrow customer segment you are pursuing first. “Everyone with this problem” is not a market entry plan. A specific segment gives investors a way to judge your customer learning, distribution approach, pricing, and product focus.
Attach raw evidence where it helps: anonymised pipeline views, cohort exports, customer interview summaries, pilot terms, invoices, or screenshots from your product. Do not send every file to every investor at the first interaction. Maintain the material so you can provide it quickly when a serious conversation reaches diligence.
Our portfolio work reinforces a simple rule: evidence gets more useful when a founder can explain its limits. Your FAQ should make that explanation easy, consistent, and fast.
Cover team, ownership, and risk directly
Investors are funding a company and the people responsible for its decisions. Prepare clear answers on founder roles, time commitment, relevant experience, team gaps, hiring priorities, and decision rights. If one founder owns product and another owns sales, state where those responsibilities begin and end.
Have your ownership information ready before an investor asks. Your FAQ should explain the current cap table, founder ownership, existing investor rights, employee pool status if applicable, and any promised equity that is not yet documented. Do not wait until term-sheet discussions to discover that old verbal commitments create confusion.
- What does each founder own day to day?
- Is every founder working full time? If not, what is the transition plan?
- Which role is the most urgent hire after the round?
- Who owns key intellectual property and customer contracts?
- What are the three largest execution risks in the next 12 months?
- What evidence would show that your current plan is wrong?
Risk answers should never be theatre. State the risk, the early warning signal, the owner, and the planned response. For example, if your sales cycle may be longer than expected, define the pipeline stage that will reveal the issue and the lower-burn operating plan you would use.
This section often separates prepared founders from polished presenters. Strong founders do not claim they have no risks. They show that they can see risks early and make decisions before the company runs out of time or cash.
Use the FAQ throughout the raise
Your FAQ is a live operating document during the raise. Review it after every meaningful investor conversation, but do not rewrite it to fit one person’s preference. Update it when you have new evidence, a corrected number, a repeated question, or a decision that changes the company plan.
Set one founder as the document owner, even when several people contribute. That person checks version control, confirms that linked documents are current, and makes sure the deck, model, cap table, and FAQ agree. Use dated internal versions so your team can see what changed and why.
| Fundraising moment | How to use the FAQ |
|---|---|
| Before outreach | Find unsupported claims, missing documents, and founder disagreements. |
| After first meetings | Record recurring objections and improve weak answers with evidence. |
| During diligence | Respond consistently and direct investors to supporting material. |
| Before term-sheet discussions | Confirm round structure, ownership, milestones, and use of funds. |
Do not email the full FAQ automatically to every investor. Use it as your internal control document first. Share relevant sections when they answer a specific follow-up, and provide the complete version when the investor has shown real diligence intent.
The goal is simple: every serious question should receive the same clear answer from every founder, backed by material you can produce. That discipline makes fundraising more efficient because it makes the company easier to understand.
Build the investor FAQ for Indian seed rounds before your next investor meeting, then test it against your deck, model, cap table, and customer evidence. If you need embedded support across fundraising, product, validation, and go-to-market, Apply for Nebula 1.0.
Enjoyed this? Get the next one in your inbox.
Fundraising guides and validation frameworks, every two weeks. No spam.
Frequently asked questions
What should an investor FAQ include for an Indian seed round?
Include direct answers on the problem, customer, market entry, product status, traction, pricing, financial plan, use of funds, team, cap table, and execution risks, with supporting evidence for each major claim.
When should founders share an investor FAQ?
Use it internally before outreach, then share relevant sections after specific investor follow-ups or during serious diligence. Do not send it automatically with every first outreach email.
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 conversationTalk to the founder directly. We reply within two working days.
Applying to Nebula 1.0? Apply here →