fundraising: the pm's role
The founder tells the story. The PM brings the receipts. Every number in that pitch deck, every claim about retention, every product roadmap slide — someone built that evidence. That someone is you.
You are not the person raising money. The founder is. But in every fundraising round I have been part of — as a founder, as an operator, and as someone who has trained thousands of PMs at startups going through this — the PM is the person who makes or breaks the product story in the deck.
Investors do not invest in products. They invest in markets, teams, and trajectories. But the product is the proof that the team can execute, the market is real, and the trajectory is not a fantasy. When that proof is weak, the round falls apart. When it is strong, the PM is the reason it held together.
This page is about the PM’s specific role in fundraising: what investors ask, what metrics matter at each stage, how to handle product demos, and what Indian VCs look for that differs from the Valley playbook you read on Twitter.
You are not raising. You are arming.
The first mistake startup PMs make during fundraising is thinking it is not their problem. “The CEO handles investor meetings. I just build the product.”
Wrong. The CEO handles the relationship. The PM builds the ammunition.
Every fundraising deck has a product section. That section needs:
- Metrics that prove traction, not just activity
- A roadmap that shows strategic thinking, not a feature list
- A competitive narrative that holds up under questioning
- A demo that demonstrates value, not features
The founder cannot build this alone. They know the vision. You know the numbers — or you should. If the founder is pulling metrics from dashboards at 2am before a pitch meeting because the PM never prepared a clean metrics brief, that startup has a PM problem.
Your job during fundraising is to make the founder dangerous in every product conversation. Arm them with the right numbers, the right framing, and the right answers to the questions investors will ask.
What investors actually ask about product
After sitting through dozens of investor meetings across seed, Series A, and Series B — and debriefing with PMs who have been through many more — the product questions cluster into five categories. Investors rotate the phrasing, but they are always asking the same things.
1. Is this product solving a real problem?
They will not ask it this directly. They will say: “Walk me through how a user discovers and starts using your product.” Or: “Tell me about your last five customers — why did they buy?” What they are testing: did you build something people want, or something you think people should want?
2. Do users stay?
Retention is the question behind every growth question. They will ask about DAU/MAU, cohort retention, churn rate, NRR. What they are testing: is your growth real, or are you filling a bucket with a hole in it?
3. Can this scale without breaking?
They will ask about your tech stack, your architecture decisions, your team size relative to your user base. What they are testing: if we give you 10x more users tomorrow, does the product survive?
4. What is your moat?
This is the question PMs dread most, because for most early-stage startups, the honest answer is “not much yet.” They will phrase it as: “What happens when [large company] copies this?” or “What stops a well-funded competitor from doing exactly what you do?” We will come back to how to handle this.
5. Where does the product go from here?
They want to see that the roadmap is a strategic argument, not a wishlist. They will ask: “What are you building in the next 12 months and why?” What they are testing: does the PM think in terms of market position, or just features?
A Series A pitch meeting at a VC office in Koramangala, Bangalore. The founder and PM are presenting to two partners.
VC Partner: “Your growth looks good. 3x in six months. But walk me through your cohort retention — what does month-3 look like for users who joined in January?”
Founder: “Our retention is strong. Users love the product. We see great engagement across the board.”
The founder glances at the PM. The PM has the cohort data on their laptop but it was not in the deck.
PM: “January cohort month-3 retention is 34% on a weekly active basis. That is up from 22% for our October cohort. The improvement tracks to a change we made in onboarding — we moved the core action from step 4 to step 1.”
VC Partner: “34% monthly or weekly?”
PM: “Weekly. Monthly active retention for the same cohort is 58%.”
VC Partner: “That's a meaningful improvement. What's driving the remaining 42% churn at month 3?”
PM: “Two things. 30% of churned users never completed their first project — that's an activation problem we're addressing this quarter. The other 12% completed projects but didn't return. We're interviewing that segment now to understand the drop-off.”
The VC nodded. The PM had not just shown the number — they had shown they understood what was behind it and had a plan.
The founder had the relationship. The PM had the answer. Without the PM's preparation, that retention question would have ended the meeting.
Product metrics that matter at each stage
Investors look for different things depending on which round you are raising. PMs who prepare the wrong metrics for the wrong stage waste the founder’s credibility.
Seed: prove the problem is real
At seed, investors are betting on the team and the market. Product metrics are thin — and that is expected. What they want to see:
- Engagement intensity in a small cohort. Not how many users you have. How intensely the users you have are using the product. If you have 50 users and 40 of them use it daily, that is a stronger signal than 5,000 signups with 2% DAU.
- Qualitative evidence of pull. Actual user quotes. Screenshots of inbound messages asking for features. Evidence that users sought you out rather than being dragged in through paid acquisition.
- Speed of iteration. How fast are you shipping? Seed investors want to see a team that can build and learn quickly. Show your release cadence. Show how user feedback changed the product in the last 60 days.
- Willingness to pay (even if small). If even 10 users are paying anything — even Rs 99/month — that is a stronger signal than 10,000 free users. Payment proves intent.
Series A: prove retention and early growth
Series A is the PMF round. The product section of a Series A deck must answer one question: do users stay?
- Cohort retention curves. Not a single retention number — a chart showing retention by cohort over time. Investors want to see the curve flattening, meaning a stable base of retained users. If every cohort trends to zero, your growth is a mirage.
- Activation rate. What percentage of signups complete the core action that predicts retention? If you do not know what that action is, you are not ready for Series A.
- Growth rate and source. Month-over-month growth, broken down by channel. Organic vs paid. Referral rate. The question behind the question: is your growth sustainable without increasing spend proportionally?
- Unit economics (early signal). You do not need perfect LTV:CAC at Series A, but you need to show the direction. Is CAC decreasing as you learn? Is revenue per user stable or growing?
Series B: prove the economics work
Series B is the efficiency round. Investors want to see that the engine works and more fuel will produce proportional results.
- LTV:CAC by segment and channel. Not a blended number — segmented. Which customer segments are profitable? Which channels are efficient? A blended 3:1 LTV:CAC that hides a 10:1 segment and a 0.5:1 segment is a trap.
- Net Revenue Retention (NRR). For B2B: are existing customers spending more over time? NRR above 110% means your product grows within accounts. Below 100% means you are on a treadmill.
- Payback period. How many months until a customer pays back their acquisition cost? Indian VCs care about this more than Valley VCs at Series B. Capital is more expensive in India, so payback period discipline matters earlier.
- Product-led growth metrics. Viral coefficient, time-to-value, self-serve conversion rate. Evidence that the product itself drives acquisition, not just the sales team.
Series C and beyond: prove market leadership
At this stage, product metrics are about market position and defensibility.
- Market share in your category (or evidence you are defining a new one)
- Platform metrics: API usage, integrations, ecosystem indicators
- Switching cost indicators: how deeply embedded is your product in the customer’s workflow?
- Expansion revenue as a percentage of total revenue
Product demos in investor meetings
Most product demos in investor meetings are disasters. The PM spends 15 minutes clicking through every screen while the investor checks their phone. Here is what actually works.
Show the core value in 90 seconds. Not the onboarding. Not the settings page. Not the admin panel. The one thing that makes the product valuable. If you cannot demo the core value in 90 seconds, you do not understand what your core value is.
Demo with real data, not dummy data. Investors have seen a thousand perfect demo environments. Show real customer data (with permission and anonymization where needed). Real data has messy edges — and that is actually more convincing than a pristine demo dataset.
Anticipate the “can you build X?” question. Every investor will ask if you can build something adjacent to your product. The wrong answer is “yes, we can build that.” The right answer is: “Here is what we are building and why. That feature is interesting — here is how it fits (or does not fit) our current thesis.”
Stop before they ask you to stop. A 3-minute demo that leaves the investor wanting more is better than a 10-minute demo that leaves them exhausted. End with: “I can go deeper on any part of this — what would you like to see?” Now they are driving, and you learn what they care about.
Never demo bugs live. If there is a flow that is unstable, do not demo it. If the investor asks about it, say “we are rebuilding that flow right now — here is a screenshot of the new version” or “that is shipping next week.” Investors understand that products have bugs. They do not understand PMs who demo broken flows without acknowledging them.
Building the product narrative for the deck
The product section of a fundraising deck is not a feature list. It is an argument. The structure that works:
Slide 1: The problem (with evidence). Not a generic problem statement. A specific, quantified problem that your specific users have. “Enterprise procurement teams in India spend 14 hours per week on manual vendor comparisons” — not “procurement is inefficient.”
Slide 2: Your solution (with a screenshot). One screenshot. The core screen. Annotated if necessary. The investor should understand what the product does in five seconds of looking at this slide.
Slide 3: Traction (metrics). The stage-appropriate metrics from the section above. Charts, not tables. Trends, not snapshots. Label the axes. Annotate inflection points.
Slide 4: Product roadmap (strategic framing). Three horizons: what you built (proven), what you are building (in progress), what you will build with this funding (planned). Each item should connect to a market insight or a customer signal — not “we want to add AI” but “our top 20 customers all asked for automated categorization, which reduces their processing time from 14 hours to 3.”
Slide 5 (optional): Competitive positioning. Only include this if you have a genuine differentiation to show. A 2x2 matrix where you are conveniently in the top-right corner convinces nobody. Show what you do that others cannot, and why.
What Indian VCs specifically look for
The Valley fundraising playbook is all over Twitter. Indian fundraising is different in ways that matter for how you prepare the product story.
Indian VCs are more metrics-focused at early stages than US VCs.
At Peak XV (formerly Sequoia India), Accel, Z47 (formerly Matrix Partners India), and Elevation Capital — the firms that write the largest early-stage checks in India — partners will interrogate your metrics with more specificity at seed and pre-Series A than their US counterparts typically do. This is partly because Indian startups have lower margins and Indian markets have higher price sensitivity, so the metrics need to be stronger earlier to justify the bet.
Prepare for questions like: “What is your CAC by channel?” at seed stage. In the US, this question comes at Series A. In India, it comes earlier because capital efficiency is a survival question, not just a preference.
Revenue per user matters more than total users.
Indian VCs have seen too many startups with millions of users and zero monetization. The GMV-obsessed era of 2015-2019 burned a generation of investors. Now they want to see revenue per user early. If you are pre-revenue, show willingness-to-pay data. If you are post-revenue, show ARPU trends by cohort.
India market depth is a question, not an assumption.
When you pitch to an Indian VC, they will ask about your TAM with skepticism. “The Indian market for X is $Y billion” is the opening of every Indian startup deck, and VCs have learned to discount it aggressively. They want to see bottom-up TAM: how many specific customers exist, what they pay today, and what share you can realistically capture.
The PM’s job is to build this bottom-up estimate. Not from a market research report — from your actual data. “We have 200 paying customers from a total addressable base of 8,000 similar companies in Tier 1 and Tier 2 cities. Our penetration is 2.5%. Based on our current growth rate and win rate, we project reaching 12% penetration in 18 months.” That is a PM talking, not a consultant.
Runway discipline is product-adjacent.
Indian VCs will ask how long your current runway is and what you will achieve with the money they give you. The PM’s role here is to connect product milestones to fundraising milestones. “With this round, we will reach 500 paying customers and 65% month-3 retention — which are the benchmarks for our Series B.” That is a product milestone framed as a fundraising milestone. It shows the PM thinks in terms of what the company needs to prove, not just what to build next.
Comparable exits matter.
Indian VCs need to see a plausible exit path. In the US, there are hundreds of acquirers for any category. In India, the acquirer pool is smaller. The PM can help by framing the product in terms of strategic value to potential acquirers: “Our data layer becomes critical infrastructure for any company serving Indian SMEs — which is why Razorpay, Zoho, and Tally are all potential acquirers if we reach 5,000 paying accounts.”
Handling the moat question
This deserves its own section because it is the question that trips up the most startup PMs.
“What is your competitive moat?”
For most early-stage startups, the honest answer is some combination of: we execute faster, we understand the customer better, and we have a small data advantage. None of these sound like moats. A moat is a network effect, a patent, a regulatory advantage, or massive switching costs. Most startups do not have these at Series A.
The mistake is either pretending you have a moat you do not have, or wilting under the question and saying “we just move fast.” Both are bad.
The framing that works: describe your moat as a trajectory, not a state.
“Today, our advantage is execution speed and customer intimacy — we ship weekly based on direct customer feedback, and our NPS is 62 compared to 28 for the nearest competitor. By the time we reach 500 customers, our advantage becomes data: we will have the largest dataset of [domain-specific data] in India, which feeds our recommendation engine. By 1,000 customers, it becomes switching costs: our product will be embedded in their daily workflow with integrations to their existing tools. The moat is building. It is not built yet — and anyone who tells you they have a moat at this stage with this revenue is not being honest.”
That answer shows strategic thinking, self-awareness, and a plan. It is infinitely better than a vague claim about “our team is our moat.”
Test yourself
You are the PM at a B2B SaaS startup in Bangalore. You have 120 paying customers, Rs 18L MRR, and 11 months of runway. Your product is a compliance automation tool for Indian SMEs — it tracks GST filings, TDS deadlines, and audit preparation. You are in a Series A pitch meeting. The VC partner leans forward and asks: 'Tally and Zoho are both building compliance features. What stops them from killing your product?'
The founder looks at you. This is a product question, and you prepared for this meeting. What do you say?
your path
Common mistakes PMs make during fundraising
Preparing metrics only when asked. If the founder has to request a metrics brief before each investor meeting, you are reactive. Build a standing fundraising metrics document that updates weekly during the fundraising period. Include: retention by cohort, growth rate by channel, activation rate, unit economics, and NPS/Sean Ellis score. Keep it current. The founder should be able to pull it up in any meeting without warning.
Showing every feature in the demo. Investors do not care about your settings page, your notification preferences, or your admin panel. They care about the core loop: the thing that makes a user come back. Demo that. Everything else is noise.
Using vanity metrics in the deck. Total signups, total page views, total downloads — these are vanity metrics. They go up and to the right by default. Investors want engagement metrics, retention metrics, and revenue metrics. If the only numbers in your product section are vanity metrics, the investor will assume the real numbers are bad.
Not knowing your numbers cold. In the pitch meeting, the founder should not be looking at you every time a metric question comes up. Prepare the founder. Run mock pitch sessions. Drill the numbers until the founder can answer cohort retention, CAC by channel, and activation rate without looking at a slide.
Building the roadmap for the investor, not for the business. Do not add “AI features” to your roadmap because you think VCs want to hear it. Build the roadmap based on what your customers need and what your data tells you. Investors can smell a roadmap designed for fundraising. They want to see a roadmap designed for customers.
Create a one-page metrics brief that your founder could use in any investor meeting this week. Include:
- Traction snapshot: Total customers (paying vs free), MRR/ARR, month-over-month growth rate for the last 6 months
- Retention chart: Cohort retention by month for your last 4-6 cohorts. Plot the curves. Note any inflection points and what caused them.
- Activation funnel: Define the 3-5 steps from signup to core action. What is the conversion rate at each step? Where is the biggest drop-off?
- Unit economics: CAC by top 3 channels. ARPU. Estimated LTV (even if rough). Payback period.
- Competitive positioning: One sentence on your top 3 alternatives (include “do nothing / spreadsheet” if relevant). One number for each that shows why you win.
If you cannot fill in any section, that gap is your highest priority research task this week — not another feature.
Now rehearse: have someone ask you “walk me through your retention” and “what’s your CAC?” Practice answering without looking at the document. The founder needs to do this from memory in the room.
When the round does not close
Not every fundraising process succeeds. When a round stalls or fails, the PM’s reaction matters.
Do not blame the investors for “not getting the product.” If multiple investors pass, the product story is not compelling enough. That is a PM problem. Go back to the metrics: is retention actually strong? Is activation actually working? Is the growth real or inflated by a single channel?
The most useful thing a PM can do after a failed fundraising attempt is run a postmortem on the product questions that went badly. Which questions made the founder stumble? Which metrics were missing or unconvincing? What did the investor ask about that you had no answer for?
That postmortem becomes your product roadmap for the next three months. Fix the gaps. Build the evidence. Then go back.
A startup's CEO asks the PM to prepare a product slide for the Series A pitch deck. The CEO wants the slide to show the product roadmap for the next 18 months with specific feature commitments. The PM thinks committing to specific features 18 months out is a mistake.
The call: What does the PM put on the slide?
A startup's CEO asks the PM to prepare a product slide for the Series A pitch deck. The CEO wants the slide to show the product roadmap for the next 18 months with specific feature commitments. The PM thinks committing to specific features 18 months out is a mistake.
The call: What does the PM put on the slide?
Where to go next
- Strengthen your PMF story before fundraising: Product-Market Fit
- Build the metrics foundation investors will interrogate: Metrics and KPIs
- Prepare for the presentation itself: Presenting to Leadership
- Understand the founder-PM dynamic during fundraising: PM at a Startup