Fundraising PRD
A PRD format tailored for fundraising conversations — frames the problem, solution, and build plan in the language investors use. Covers market sizing, why now, defensibility, and the specific ask. Built for India-based founders raising pre-seed to Series A. Free to copy, download, and use. No signup required.
# Fundraising PRD **Company / Product:** [Name] **Stage:** [ ] Pre-seed [ ] Seed [ ] Pre-Series A [ ] Series A **Round size:** ₹ [Amount] / $[Amount] **PM / Founder:** [Name] **Date:** [Date] --- > **How to use this document:** > This is not a pitch deck. It is the written product narrative that goes *behind* the pitch deck — the document you send to investors before a meeting so they arrive informed, and the document they share with partners during partner review. It should be readable in 8–12 minutes. Be specific. Investors read hundreds of vague documents. Specificity signals rigour. --- ## 1. The problem **One sentence:** [The single clearest statement of the problem you solve] **Who has this problem?** [Describe the user — job title, company type, behaviour, geography. Be specific: "Product managers at Indian SaaS companies with 20–200 employees" is better than "product managers".] **How big is the pain? Evidence:** - [Data point 1 — ideally from your own customer interviews] - [Data point 2 — industry research or published data] - [Data point 3 — competitor or proxy market evidence] **What do they do today?** [The current workaround — this is your real competition. Be honest. "They use spreadsheets" is less compelling than "they spend 4 hours after each customer interview manually transferring notes into Notion, then re-read everything before writing the PRD".] **Why is the current solution inadequate?** [The specific failure mode of the workaround that your product addresses] --- ## 2. The solution **One sentence:** [What your product does — lead with outcome, not features] **The core mechanism (how it works in plain language):** [3–5 sentences. Describe the user workflow from problem to solution. No jargon. An investor who has never managed a product should understand this.] **Demo or proof:** [ ] Live product available at [URL] [ ] Recorded demo at [URL] [ ] Prototype / mockups available **The "aha moment" — when does the user first feel the value?** [Describe the specific moment in the product where value becomes undeniable. This tells investors you understand your activation metric.] --- ## 3. Market **TAM (Total Addressable Market):** [₹ / $ — the total spend on this category globally or in India] **SAM (Serviceable Addressable Market):** [₹ / $ — the portion you can realistically reach with your distribution model] **SOM (Serviceable Obtainable Market — 3-year target):** [₹ / $ — what you will capture in 3 years given your go-to-market] **Market sizing approach:** [ ] Top-down (TAM × share) [ ] Bottom-up (customers × ARPU) *Investors trust bottom-up more. If you've done both, present bottom-up first.* **Bottom-up calculation:** ``` [Target customers in India] × [% reachable via your channels] × [% who will pay] × [ARPU] = [SOM] [Number] × [%] × [%] × ₹[ARPU] = ₹[SOM] ``` --- ## 4. Why now Three conditions that make this the right time to build this product: 1. **[Enabling condition 1]:** [e.g. LLM costs dropped 90% in 18 months — the AI cost that made this category uneconomical is now viable] 2. **[Enabling condition 2]:** [e.g. India SaaS market crossed $10B ARR — enough paying customers exist to support this category] 3. **[Enabling condition 3]:** [e.g. Post-COVID, remote work normalised async documentation — the behaviour PMRead requires is now standard] *"Why now" is the question most decks skip. Investors who pass often do so because they don't believe this is the right time — not because they don't believe in the problem.* --- ## 5. Traction | Metric | Value | Period | |---|---|---| | Signups | | | | Active users (weekly) | | | | Paying customers | | | | MRR | ₹ | | | MoM growth | % | | | NPS / CSAT | | | | Notable customers | [Names if permissible] | | **Most compelling customer story (1 paragraph):** [The customer who gets the most value from your product — what they were doing before, what they do now, and what the measurable difference is] --- ## 6. Business model | Revenue stream | Description | ARPU (₹/month) | Status | |---|---|---|---| | [e.g. Pro subscription] | [Description] | ₹ | [ ] Live [ ] Planned | | [e.g. Team plan] | [Description] | ₹ | [ ] Live [ ] Planned | **Unit economics summary:** - CAC: ₹[amount] - LTV: ₹[amount] - LTV:CAC: [ratio] - Gross margin: [%] - CAC payback: [months] --- ## 7. Why we win — defensibility | Moat | Description | Strength today | Strength at scale | |---|---|---|---| | Data moat | [e.g. Proprietary training data from customer feedback] | Weak | Medium | | Network effect | [e.g. Insights are richer when more team members upload] | None | Medium | | Switching cost | [e.g. Historical insights and PRDs live in PMRead] | Medium | Strong | | Brand / distribution | [e.g. #1 for "India PRD tool" on Google] | Weak | Medium | | Regulatory | [e.g. India data localisation advantage] | N/A | N/A | **Why a well-funded competitor can't immediately replicate what you've built:** [Be honest. "We have a 6-month head start" is not a moat. "We have 18 months of insight data from 200 companies that trains our ranking model" is a moat.] --- ## 8. Team | Name | Role | Relevant background | |---|---|---| | [Name] | CEO / PM | [e.g. 5 years as PM at Razorpay, shipped X feature used by Y users] | | [Name] | CTO / Engineering | [e.g. Previously staff engineer at Swiggy, built real-time logistics at scale] | **Why this team?** [The specific experience that makes this team the right one to solve this problem — not generic "we're passionate", but domain expertise, network, or unfair access that others don't have] --- ## 9. The ask **Round size:** ₹[Amount] / $[Amount] **Instrument:** [ ] SAFE [ ] Convertible note [ ] Priced equity **Valuation cap / pre-money:** ₹[Amount] / $[Amount] **Use of funds (18-month runway):** | Category | Amount (₹) | % of round | What it buys | |---|---|---|---| | Engineering | ₹ | % | [e.g. 2 senior engineers, 18 months] | | Go-to-market | ₹ | % | [e.g. Content + SEO + 1 growth hire] | | Infrastructure | ₹ | % | [e.g. AWS + LLM inference costs at 10× current scale] | | Operations | ₹ | % | [e.g. Legal, compliance, office] | | **Total** | **₹** | **100%** | | **Milestones this round gets you to:** - [ ] [Milestone 1 — e.g. ₹X MRR by [date]] - [ ] [Milestone 2 — e.g. Series A-ready metrics: 3:1 LTV:CAC, < 5% monthly churn] - [ ] [Milestone 3 — e.g. [N] enterprise design partners signed] **What changes after this round that doesn't change without it:** [The specific bets you can take with this capital that you cannot take at the current burn rate]
How to use this Fundraising PRD template
Write the 'What do they do today?' section before anything else
The current workaround is the most important thing in this document. It defines your real competition (not Notion or Dovetail — the actual behaviour), your baseline for measuring value, and the switching cost you need to overcome. Investors who don't understand the incumbent behaviour will not understand why your product is compelling. Interview 5 customers about their current workflow before writing this section.
Use bottom-up market sizing exclusively
Top-down market sizing ('the global PM software market is $X billion, we will capture 1%') is a red flag for sophisticated investors. It signals you don't know your customer. Bottom-up sizing forces you to name a specific number of target customers, a realistic conversion rate, and a realistic ARPU. If the resulting number is smaller than the TAM-percentage number, that's the honest market size — and investors will respect the honesty.
Answer 'Why now' before the investor asks it
'Why now' is the question most founders cannot answer — which is why most investors ask it. Three structural reasons that make this the right moment (technology shift, regulatory change, behaviour change, market inflection) are more convincing than traction alone. If you can't answer why this wasn't built 5 years ago, you haven't thought through why it will survive competition from better-funded players.
Be specific about use of funds — line-item level, not categories
Vague use of funds ('product, marketing, operations') signals an early-stage team that hasn't modelled their business. Line-item specificity ('2 senior engineers at ₹30L/year = ₹60L, 18 months runway = ₹90L') shows financial rigour and makes your milestones credible. Investors who question your use of funds are really questioning whether you know how to allocate capital — answer that question before they ask it.
Want a Fundraising PRD grounded in your actual customer data?
PMRead ingests your customer interviews, feedback, and Slack threads — and generates PRDs backed by real evidence, not guesses.
Frequently asked questions
Should this be sent before or after a pitch meeting?
Send a 1-page version (problem + solution + traction + ask) before the meeting to give the investor enough context to ask good questions. Send the full Fundraising PRD after the meeting to the partner who attended, along with a note asking them to share it in the partner review. The full document is designed for the partner review stage — where your champion is presenting to colleagues who haven't met you.
How is a Fundraising PRD different from a pitch deck?
A pitch deck is a visual narrative designed for a 10-minute presentation. A Fundraising PRD is a written document designed for an 8-minute read. They cover the same ground but serve different stages: deck for the first meeting, PRD for due diligence and partner review. The PRD is longer, more specific, and includes evidence that doesn't fit on a slide (customer quotes, cohort tables, unit economics detail).
What's the right pre-money valuation for an India pre-seed / seed round?
India pre-seed (₹1–3 crore) typically closes at ₹5–15 crore pre-money valuation. Seed (₹3–8 crore) closes at ₹15–40 crore pre-money. These are ranges, not norms — traction, team pedigree, and market size all move the number. The right valuation is the one that leaves enough dilution for future rounds: avoid raising pre-seed at a valuation that makes Series A math awkward. Rule of thumb: don't give up more than 15–20% at pre-seed.
Should I include financial projections?
Include a 3-year projection as a supplement, not in the main document. State the assumptions explicitly (growth rate, churn, hiring plan) because investors will stress-test the assumptions, not the numbers. Don't anchor to a specific revenue figure — anchor to the model. 'At 5% monthly growth and 3% churn with current ARPU, we reach ₹X ARR in 24 months' is more credible than 'We will reach ₹X ARR in 24 months'.
Other free templates