77. Pitch Deck
A pitch deck is a compression tool.
It compresses your company into a story an investor can understand, remember, discuss with partners, and test through diligence. The deck does not need to answer every question. It needs to create enough clarity and curiosity for the next meeting.
A good deck is specific, evidence-led, and easy to forward internally.
The core pitch deck question is: can the deck make the investor understand the customer, problem, proof, market, team, round, and next milestone without the founder narrating every missing piece?
What It Covers
Section titled “What It Covers”This chapter covers:
- Deck structure
- Slide principles
- Pitch mistakes
The goal is not to impress investors with design. The goal is to make belief easier.
What A Deck Must Do
Section titled “What A Deck Must Do”A deck has three jobs:
- Earn the next conversation.
- Help the investor remember and retell the company.
- Reveal that the founder thinks clearly.
This means a deck should not be a brochure. It should not be a product manual. It should not be a collection of startup buzzwords. It should be a clear argument:
This customer has a painful problem. We understand it unusually well. Our product is a strong wedge. Early evidence suggests pull. The market can become large. This team can execute. This round funds the next proof point.If the deck does not make that argument, better fonts will not help.
Core Deck Structure
Section titled “Core Deck Structure”A practical early-stage deck usually covers:
| Slide | Job of the slide |
|---|---|
| Company one-liner | Explain what you do in plain language |
| Problem | Show a painful, frequent, expensive, or urgent problem |
| Customer | Define who has the problem first |
| Current alternative | Show what customers do today and why it is broken |
| Solution | Explain your product and wedge |
| Product/demo | Show how it works through a real workflow |
| Traction | Show evidence: usage, revenue, pilots, retention, pipeline, references |
| Market | Explain first market and expansion path |
| Business model | Explain pricing, margin, sales cycle, retention, expansion |
| Go-to-market | Explain how you will reach customers repeatedly |
| Competition | Show alternatives honestly and your difference |
| Team | Explain why this team can win |
| Financials/use of funds | Show runway, hiring, spend, and milestone |
| Ask | State how much you are raising and what it unlocks |
The exact order can change. The logic should not.
Slide-By-Slide Guidance
Section titled “Slide-By-Slide Guidance”| Slide | Strong content | Common weak version |
|---|---|---|
| One-liner | ”We help [customer] solve [pain] by [product/wedge]“ | Abstract slogan |
| Problem | Specific workflow pain with evidence | Generic market complaint |
| Customer | Narrow first segment and buyer | ”Everyone” or broad industry |
| Current alternative | Spreadsheet, agency, incumbent, manual team, internal tool | Ignoring how the problem is solved today |
| Solution | Product wedge tied to pain | Feature list |
| Product/demo | Real workflow, screenshot, or before/after | Polished UI with no context |
| Traction | Stage-appropriate proof with definitions | Vanity numbers |
| Market | First market plus expansion path | Top-down TAM copied from reports |
| Business model | Pricing, margin, sales cycle, retention logic | ”Subscription model” only |
| GTM | Repeatable path to customers | ”SEO, ads, partnerships” without sequence |
| Competition | Alternatives and differentiation | ”No competitors” |
| Team | Founder-market fit and execution proof | Resume collage |
| Financials/use of funds | Runway, hiring, spend, milestone | Unsupported 5-year hockey stick |
| Ask | Amount, instrument/path, milestone | ”Raising seed” with no specifics |
Investors should be able to answer “Why this company?” after reading the deck once.
Pre-Seed vs Seed vs Series A Decks
Section titled “Pre-Seed vs Seed vs Series A Decks”The emphasis changes by stage.
| Stage | Deck should emphasize |
|---|---|
| Pre-seed | Founder-market fit, customer insight, early evidence, why now, product wedge |
| Seed | Traction quality, repeatable ICP, product usage/revenue, GTM learning, milestone plan |
| Series A | Growth, retention, sales efficiency, market expansion, team, financial discipline |
Do not pretend to be later-stage than you are. Investors can tell. A clear pre-seed deck is stronger than a fake Series A deck.
Slide Principles
Section titled “Slide Principles”One Idea Per Slide
Section titled “One Idea Per Slide”Each slide should have one headline claim. If the slide has three claims, the investor may remember none.
Weak headline:
“Market”
Stronger headline:
“Indian D2C brands lose finance time because marketplace payouts, refunds, RTO, and COD data do not reconcile cleanly.”
The stronger headline says what the investor should understand.
The headline should be a sentence, not a label. Labels force the investor to interpret. Sentence headlines tell the investor the point.
Weak:
“Traction”
Stronger:
“Twelve D2C brands are paying for reconciliation pilots, and eight use the workflow weekly.”
Evidence Over Adjectives
Section titled “Evidence Over Adjectives”Investors distrust adjectives because everyone uses them.
Replace:
- Huge market.
- Massive pain.
- Revolutionary product.
- Strong traction.
With:
- Customer count.
- Revenue.
- Retention.
- Sales cycle.
- Usage.
- Case studies.
- Customer quotes.
- Market behavior.
When evidence is early, be honest. “We have spoken to 42 target customers and 18 described this as a monthly finance bottleneck” is more believable than “massive demand.”
Clear Numbers
Section titled “Clear Numbers”Define metrics. If you say revenue, clarify whether it is booked, billed, collected, MRR, ARR, GMV, net revenue, or services revenue. If you say users, clarify active users, paying users, teams, companies, or signups.
Ambiguous metrics create diligence friction.
Good decks define numbers in footnotes or short labels:
Rs 8L collected revenue, not justRs 8L revenue.23 weekly active teams, not just23 users.14 paid pilots, not just14 customers.Rs 2.4L MRR excluding services, not blended revenue.
Clarity builds trust.
Strong Narrative
Section titled “Strong Narrative”The deck should feel like a chain:
- This customer has this painful problem.
- The old way is broken.
- We have an insight.
- Our product is the wedge.
- Early evidence suggests pull.
- This market can expand.
- This team can execute.
- This round funds the next proof point.
If the deck is just a pile of slides, rewrite the story.
Test the narrative by reading only the slide headlines. If the headlines do not tell a coherent story, the deck is not ready.
Visual Simplicity
Section titled “Visual Simplicity”Simple slides travel better. Use diagrams, screenshots, charts, and short text. Avoid dense paragraphs. The investor should understand the slide in seconds.
Useful visuals:
- Workflow before/after.
- Customer journey.
- Sales funnel.
- Cohort retention chart.
- Revenue by month with definitions.
- Market wedge and expansion diagram.
- Competitive 2x2 only when axes are meaningful.
Avoid decorative visuals that do not clarify the business.
Product Slide
Section titled “Product Slide”The product slide should answer:
- What does the user do?
- What changes compared with the current workflow?
- Why is this better?
- Which part is already built?
- Which part is roadmap?
For software, screenshots should include annotations. For AI products, show the input, output, workflow integration, and human review point. For marketplaces, show both sides and the trust/transaction flow. For hardware/deeptech, show the product, proof, and deployment context.
Traction Slide
Section titled “Traction Slide”Traction should be stage-appropriate and honest.
Examples:
| Stage | Useful traction |
|---|---|
| Idea/prototype | Customer interviews, waitlist quality, design partners, prototype usage |
| MVP | Active users, pilots, usage frequency, customer feedback |
| Early revenue | Paying customers, MRR/ARR, sales cycle, retention, expansion |
| Marketplace | Supply, demand, liquidity, repeat transactions, take rate, unit economics |
| Consumer | Retention cohorts, engagement, organic growth, CAC experiments |
Do not hide weak traction behind cumulative vanity numbers. If traction is early, explain what it proves and what remains unproven.
Market Slide
Section titled “Market Slide”A useful market slide starts with a believable wedge.
Bad:
“The global SaaS market is $300B. If we get 1 percent…”
Better:
“We start with 8,000 Indian D2C brands selling on 2+ marketplaces. At Rs X annual contract value, this first wedge is Rs Y crore. The same reconciliation workflow expands to omnichannel retail, logistics-heavy brands, and Southeast Asian marketplaces.”
Investors know large markets exist. They want to know where you can enter, why that wedge is real, and how it expands.
Competition Slide
Section titled “Competition Slide”Competition is not only companies that look like you. It includes:
- Spreadsheets.
- Manual teams.
- Agencies.
- Internal tools.
- Incumbent software.
- Doing nothing.
- Hiring another employee.
Show you understand alternatives. Then explain why your wedge wins for the first customer segment.
Team Slide
Section titled “Team Slide”A strong team slide answers “why you?”
Include:
- Domain experience.
- Customer access.
- Technical ability.
- Prior execution.
- Founder-market fit.
- Complementary skills.
- Evidence of speed or resilience.
Do not only list logos from past employers. Explain why those experiences matter for this company.
The Ask Slide
Section titled “The Ask Slide”The ask should connect money to progress:
We are raising [amount] to reach [milestone] in [time period], mainly by spending on [team/product/GTM], and success will look like [specific metrics].
Example:
We are raising Rs X crore to reach 50 paid customers and Rs Y MRR in 18 months, mainly by hiring two engineers, one founder-led sales associate, and funding onboarding. Success will be 50 paying customers, below 3 percent monthly logo churn, and a repeatable outbound motion.
Use your own numbers. The point is to connect capital to evidence.
The ask slide should include:
| Item | Example |
|---|---|
| Amount | Raising Rs X crore |
| Runway | 18 months |
| Use of funds | Product integrations, founder-led GTM support, onboarding |
| Milestone | 50 paid customers and repeatable outbound motion |
| Evidence threshold | Churn, CAC/payback, retention, gross margin, or usage metric |
| Round logic | Makes next round or profitability credible |
Avoid an ask that sounds like a shopping list. The ask should be a plan to reduce risk.
Deck Headline Test
Section titled “Deck Headline Test”Read only the slide headlines. They should tell the story without narration.
Weak headline sequence:
ProblemSolutionMarketProductTractionTeamAskStronger headline sequence:
Marketplace reconciliation is breaking month-end finance for Indian D2C brands.Finance teams still solve it with downloads, Excel, and founder escalation.Our workflow automates payout matching across marketplaces and bank credits.Twelve brands are paying for pilots and eight use the workflow weekly.We start with multi-marketplace D2C brands and expand into omnichannel retail.The round funds integrations, onboarding, and founder-led sales repeatability.Labels organize slides. Sentence headlines create belief.
Deck Diligence Notes
Section titled “Deck Diligence Notes”Every claim in the deck should have a diligence note behind it.
| Claim | Backup |
|---|---|
| Market size | Bottom-up calculation and assumptions. |
| Revenue | Booked, billed, collected, recurring, or services definition. |
| Customer count | Paid, pilot, active, signed, or design partner definition. |
| Retention | Cohort, period, denominator, and exclusions. |
| Pipeline | Stage definitions and next steps. |
| ROI | Customer data, assumption, or pilot result. |
| Competitive advantage | Evidence, not adjectives. |
The deck can be concise because the founder has the backup ready.
First Meeting Deck vs Send-Ahead Deck
Section titled “First Meeting Deck vs Send-Ahead Deck”You may need two versions:
| Version | Purpose |
|---|---|
| Send-ahead deck | Clear without narration, more context in speaker notes or short text. |
| Meeting deck | Simpler, more visual, supports conversation. |
If an investor will forward the deck internally, the send-ahead version must stand alone. A beautiful deck that requires the founder’s voice on every slide will not travel.
India Angle
Section titled “India Angle”Indian founders often need to explain context carefully.
If you are selling to Indian SMBs, investors may worry about willingness to pay, collections, support load, and market fragmentation. If you are selling globally from India, investors may worry about distribution, credibility, customer proximity, timezone support, and competition.
Address the real concern instead of pretending it does not exist.
For India-first companies, show practical operating insight: buyer behavior, pricing, support, trust, payments, language, logistics, compliance, and collections. For global companies, show proof that customers outside India trust and buy from you.
Indian fundraising deck specifics:
- If selling to Indian SMBs, show willingness to pay and collections evidence.
- If selling to enterprises, show procurement/security/implementation understanding.
- If selling to consumers, show retention and distribution quality, not only installs.
- If building fintech/health/regulated sectors, show compliance seriousness without overclaiming.
- If selling globally from India, show customer trust, references, and sales motion outside India.
- If using AI, show why the product is not a thin wrapper and how quality is controlled.
Do not assume investors understand the operating context. Explain it cleanly.
Common Pitch Deck Mistakes
Section titled “Common Pitch Deck Mistakes”- Too much text.
- Vague customer definition.
- Fake TAM built from top-down numbers.
- No customer proof.
- Ignoring competition.
- Metrics without definitions.
- Product screenshots with no explanation of value.
- Financial projections that are too precise and unsupported.
- Unclear ask.
- No milestone plan.
- Team slide that lists resumes but not unfair advantage.
- No clear first customer.
- Treating LOIs or pilots as equivalent to revenue.
- Avoiding uncomfortable metrics.
- Changing the story between deck, memo, and meeting.
- Overusing AI, platform, or ecosystem language without showing workflow value.
Deck Review Checklist
Section titled “Deck Review Checklist”Before sending, ask:
- Can a stranger understand the company in 30 seconds?
- Is the first customer narrow?
- Is the pain specific and evidenced?
- Is the product tied to a workflow?
- Are traction metrics defined?
- Is the market entry believable?
- Is the competition honest?
- Is the GTM plan sequenced?
- Does the team slide explain why this team can win?
- Does the ask fund a milestone?
- Are the risks visible somewhere in the deck or memo?
- Can the deck be forwarded without your voiceover?
If not, rewrite before designing.
Plain Text Test
Section titled “Plain Text Test”Before polishing design, write the deck as plain text. For each slide, write:
- The headline claim.
- The evidence.
- The question the investor may ask.
If a slide has a claim but no evidence, either add proof or make the claim more modest.
Use this table:
| Slide | Headline claim | Evidence | Investor question | Fix |
|---|---|---|---|---|
| Problem | ||||
| Customer | ||||
| Product | ||||
| Traction | ||||
| Market | ||||
| GTM | ||||
| Ask |
This makes weak slides obvious.
Deck Narrative Spine
Section titled “Deck Narrative Spine”A good pitch deck is not a pile of slides. It is one clear argument.
Use this narrative spine:
This customer has this painful problem now.The old way is breaking because of this market change.We have a specific insight into the workflow.Our product creates this outcome.Early evidence shows customers care.This market can become large from this wedge.We can reach customers through this believable GTM motion.This team has an unfair learning/execution advantage.This round funds the next proof point.If a slide does not support the spine, remove it or move it to appendix.
Slide Claim Discipline
Section titled “Slide Claim Discipline”Every slide should have one headline claim.
Weak headlines:
- “Market”
- “Traction”
- “Product”
- “Competition”
Stronger headlines:
- “CA firms lose 6-10 hours per client each month chasing GST documents.”
- “Our first 12 paid pilots came from founder-led outbound to mid-sized firms.”
- “The wedge is monthly compliance readiness, not full practice management.”
- “Incumbents are broad tools; our advantage is workflow depth and onboarding speed.”
Investors skim decks. Headlines should carry the argument.
The Objection Slide
Section titled “The Objection Slide”For important risks, do not hide. Address them directly in the memo or appendix, and sometimes in the deck.
Examples:
| Objection | Useful response |
|---|---|
| ”Is this a feature?” | Show workflow ownership, expansion path, and willingness to pay. |
| ”Will SMBs pay?” | Show current spend, paid pilots, or collection evidence. |
| ”Why can you win against incumbents?” | Show ignored segment, product wedge, speed, service layer, or distribution edge. |
| ”Is this too services-heavy?” | Show which parts are manual now and how they become repeatable. |
| ”Is AI reliable enough?” | Show human review, accuracy thresholds, and customer trust requirements. |
Acknowledging a real objection can increase trust if your answer is thoughtful.
Deck Appendix
Section titled “Deck Appendix”Prepare appendix slides for:
- Metrics definitions.
- Cohort or retention detail.
- Customer examples.
- Sales pipeline.
- Market sizing logic.
- Competitive landscape.
- Product roadmap.
- Use of funds.
- Cap table summary if appropriate.
- Regulatory/compliance notes if relevant.
Do not overload the main deck. Use appendix to answer diligence without derailing the story.
Reader Action
Section titled “Reader Action”Send the plain-text deck to one trusted founder or advisor. Ask them to answer:
- What does the company do?
- Who is the first customer?
- Why now?
- What proof exists?
- What does the round unlock?
If they cannot answer without your explanation, the deck is not ready.
Then do one live pitch to a founder who will be blunt. Ask them to interrupt whenever a slide feels vague. Fundraising is not the place to discover that your story only makes sense inside your own head.
Slide-By-Slide Founder Notes
Section titled “Slide-By-Slide Founder Notes”For each slide, write the speaker note you would use if the investor interrupted you after 20 seconds.
| Slide | The note should answer |
|---|---|
| Problem | Who has the pain, how often it occurs, what it costs, and what they do today. |
| Customer | The first narrow segment, why that segment now, and how you reach them. |
| Solution | The workflow outcome, not only the feature list. |
| Product | What exists today, what is manual, what is automated, and what is hard to copy. |
| Traction | Metric definitions, customer quality, repeatability, and caveats. |
| Market | First market, expansion path, and bottom-up assumptions. |
| Competition | Current alternatives, why customers switch, and where incumbents are strong. |
| GTM | Channel sequence, founder-led learning, sales cycle, and why it can repeat. |
| Business model | Pricing, margin, payback, expansion, and collection assumptions. |
| Team | Why this team has earned the right to solve this problem. |
| Ask | Amount, runway, use of funds, and milestone. |
This exercise prevents decorative decks. A good slide should survive interruption.
Deck Versions
Section titled “Deck Versions”Keep separate deck versions:
| Version | Purpose | Length |
|---|---|---|
| Teaser deck | Warm intros and quick context | 6-8 slides |
| First meeting deck | Live conversation | 10-14 slides |
| Send-after deck | Forwardable explanation | 12-18 slides |
| Diligence appendix | Details and proof | As needed |
Do not send the live meeting deck if it only works with your narration. Do not open a first meeting with a 40-slide diligence appendix. Investors should feel the founder has judgment about sequence.
For Indian founders raising from global investors, the send-after deck often needs slightly more context on local workflows, collections, trust, regulation, or buyer behavior. Explain enough for a non-Indian investor to understand the opportunity without turning the deck into a market research report.
Numbers Slide Discipline
Section titled “Numbers Slide Discipline”Every number in the deck should be able to survive three questions:
- What exactly does this number mean?
- Where did it come from?
- What caveat should I know?
Examples:
| Number | Clarify |
|---|---|
| ARR | Is it booked, contracted, invoiced, collected, or annualized MRR? |
| GMV | What is net revenue, take rate, refunds, and payment timing? |
| Customers | Paying customers, pilots, active accounts, logos, or users? |
| Retention | Logo retention, revenue retention, cohort retention, or usage retention? |
| Pipeline | Qualified opportunities, proposals, verbal commitments, pilots, or signed contracts? |
| CAC | Fully loaded or channel-only? Founder time included or excluded? |
If a metric is early or messy, say so. The founder who defines numbers clearly earns more trust than the founder with inflated metrics.
Forwardability Test
Section titled “Forwardability Test”Most investors do not decide alone from your live pitch. They forward the deck, discuss it with partners, compare it with other opportunities, and come back with questions. Your deck must travel without you.
Run a forwardability test:
- Send the deck to a trusted founder who has not heard the pitch.
- Ask them to write a 5-line summary without calling you.
- Ask what felt unclear, risky, or exaggerated.
- Ask what they would tell a partner if they had to sponsor the deal.
- Rewrite the deck where their summary differs from your intent.
If the reader cannot identify customer, pain, product, proof, market, team, and round milestone, the deck is not ready for serious investor circulation.
Partner-Retell Slide
Section titled “Partner-Retell Slide”Create one internal slide or memo paragraph that helps an investor retell the company:
[Company] helps [first customer] solve [painful workflow] by [product wedge].The timing is good because [why now].The early proof is [specific evidence].The round funds [milestone].The biggest open risk is [risk], and the company will test it by [plan].You may not include this exact paragraph in the deck, but you should be able to say it. If you cannot, the story is still too loose.
Deck QA Checklist
Section titled “Deck QA Checklist”Before sending the deck widely, check every slide:
| Check | Pass condition |
|---|---|
| Headline | The headline makes a claim, not just a label. |
| Specificity | The slide names customer, workflow, number, or decision where possible. |
| Evidence | Adjectives are backed by behavior, metrics, examples, or customer stories. |
| Sequence | The slide follows logically from the previous slide. |
| Metric clarity | Numbers have definitions and date ranges. |
| Risk honesty | Major risks are either addressed or reserved for appendix/memo. |
| Visual clarity | The slide can be understood in seconds. |
| India context | Local workflow, trust, payments, regulation, or distribution context is explained when needed. |
| Ask logic | The deck connects capital to a milestone, not just spend. |
Do not ask whether the deck is “nice.” Ask whether it makes belief easier.
Red-Team Questions
Section titled “Red-Team Questions”Before investor outreach, ask someone sharp to attack the deck.
Questions:
- Which slide feels like hand-waving?
- Which metric would you distrust?
- Which customer segment still feels too broad?
- Which claim would a competitor challenge?
- Which assumption, if false, breaks the company?
- Which slide creates more questions than clarity?
- Which slide would you remove if the investor had only five minutes?
Do not defend while receiving feedback. Write down the pattern. The goal is not to win the red-team conversation. The goal is to avoid losing the investor conversation.
Investor Objection Bank
Section titled “Investor Objection Bank”Every serious fundraising process produces objections. Do not treat them as random criticism. Build an objection bank and use it to improve the deck, memo, data room, and company plan.
Track each objection:
| Field | What to capture |
|---|---|
| Objection | The exact concern in the investor’s words. |
| Investor type | Angel, micro-VC, seed fund, sector specialist, growth fund, strategic, or accelerator. |
| Pattern | One-off comment or repeated by multiple investors. |
| Category | Market, customer, product, GTM, team, metrics, valuation, competition, regulation, cap table, timing. |
| Current answer | How you answer today. |
| Evidence needed | Customer proof, metric, case study, contract, model, product demo, expert reference, legal note. |
| Materiality | Deal-killer, serious concern, clarification, or low-priority issue. |
| Action | Change deck, change memo, add appendix, improve data room, collect evidence, change strategy, or ignore. |
Use the bank weekly. If the same objection appears three times, assume the market is telling you something. Either strengthen the answer with evidence or change the fundraising strategy.
Good founders do not answer every objection by adding another slide. Sometimes the correct response is to narrow the customer segment, reduce the ask, delay the raise, change investor target, improve metrics, or admit that the round is ahead of proof.
The Partner Retell System
Section titled “The Partner Retell System”Most founders think the deck’s job is to impress the investor in the room. That is only half the job. The deck must also help that investor retell the company to partners, analysts, advisors, and investment committee members when the founder is not present.
After reading the deck, a high-fit investor should be able to say:
This company serves [customer].They solve [pain] that matters because [impact].The wedge is [first use case].They have evidence through [traction/proof].The market can expand from [wedge] to [larger opportunity].This team has an advantage because [founder-market fit/distribution/technical insight].The round funds [milestone].The main risk is [risk], and the team is addressing it through [plan].If a partner cannot retell that in two minutes, the deck is not clear enough.
Retell Slide Requirements
Section titled “Retell Slide Requirements”Every important slide should make one retellable claim:
| Slide | Retellable claim |
|---|---|
| Problem | A specific customer has a painful, costly, repeated problem. |
| Customer | The first ICP is narrow and reachable. |
| Product | The product solves a visible workflow, not a vague category. |
| Traction | Evidence shows real customer behavior, not only interest. |
| Market | The wedge can expand into a large enough opportunity. |
| GTM | The company has a believable path to customers. |
| Business model | The pricing and margin logic can produce a good business. |
| Competition | The founder understands alternatives and the wedge. |
| Team | The team has a specific right to win or learn fast. |
| Ask | The round converts money into milestones. |
If a slide cannot be retold, either simplify it or move the detail to the appendix.
Five-Minute Deck Drill
Section titled “Five-Minute Deck Drill”Before investor meetings, run a five-minute drill with a friendly founder or advisor:
- Give them the deck for five minutes.
- Take it away.
- Ask them to explain the company back to you.
- Write down what they remembered, missed, distorted, or questioned.
- Fix the deck where the retell failed.
This drill is uncomfortable because it exposes ambiguity. Good. Investors will do the same thing silently.
The Slide Evidence Tag
Section titled “The Slide Evidence Tag”Internally, tag each slide:
- Proven: supported by customer behavior, revenue, retention, contracts, or repeated usage.
- Emerging: supported by pilots, discovery, pipeline, or early metrics.
- Hypothesis: plausible but not yet proven.
- Plan: what the round will fund or test.
The final deck does not need visible tags, but the founder should know the status of every claim. This prevents overclaiming and helps answer diligence questions calmly.
Round Milestone Slide
Section titled “Round Milestone Slide”Many decks say how much money the company is raising but not what belief the money will create. Add a round milestone slide or make the ask slide answer this clearly.
| Question | Good answer |
|---|---|
| What will this round prove? | A specific customer, revenue, product, retention, distribution, or regulatory milestone |
| Why does that milestone matter? | It reduces the next investor/customer/team risk |
| What work unlocks it? | Named product, hiring, GTM, operations, or compliance work |
| How will progress be measured? | Metrics with definitions and time window |
| What happens if the plan is slower? | Burn control, narrower plan, bridge, profitability, or shutdown option |
Example:
This round funds 18 months to prove that mid-market logistics companies can be acquired through founder-led outbound and converted into repeatable annual contracts. The milestone is 25 paying customers, 70 percent activation within 30 days, gross margin above 70 percent after onboarding, and at least 3 expansion references.This kind of slide helps investors understand the company as a risk-reduction plan, not just a spend plan.
Deck-Memo Alignment
Section titled “Deck-Memo Alignment”The deck is for fast understanding. The memo is for deeper conviction. They should tell the same story.
| Topic | Deck role | Memo role |
|---|---|---|
| Problem | Make pain obvious | Show customer evidence and workflow detail |
| Market | Show scale and wedge | Explain segment logic and expansion path |
| Product | Show what exists and why it matters | Explain roadmap, tradeoffs, and technical/product risks |
| Traction | Show proof clearly | Define metrics, cohorts, caveats, and sales quality |
| GTM | Show repeatable path | Explain funnel, pipeline, channels, CAC assumptions |
| Team | Show right to win | Explain founder-market fit and hiring gaps |
| Ask | Show amount and milestone | Explain use of funds, scenarios, and runway |
If the memo contradicts the deck, investors will notice. If the deck is exciting but the memo is vague, diligence will slow down. If the memo is thoughtful but the deck is unclear, meetings may not happen.
India-To-Global Story Check
Section titled “India-To-Global Story Check”For Indian startups, the deck must be explicit about whether the company is India-first, India-only, India-to-global, or global-from-day-one.
| Story | Investor question |
|---|---|
| India-first | Is the Indian market large, reachable, and monetizable enough? |
| India-only | Can the business become durable and profitable without global expansion? |
| India-to-global | What proof in India transfers to the next geography, and what does not? |
| Global-from-day-one | How will the team sell, support, price, and build trust internationally? |
Do not hide this choice. It affects pricing, sales cycles, product expectations, hiring, compliance, support, and investor fit.
Add one clear sentence:
Our initial wedge is [India/customer segment] because [access/proof], and expansion to [geography/segment] depends on proving [transferable advantage].If nothing transfers, the global story may be premature. If the India market alone supports the ambition, say that confidently and show the economics.
Investor Retell Test
Section titled “Investor Retell Test”A deck is working when an investor can retell the company clearly to a partner, associate, angel friend, or internal committee.
After reviewing the deck, a smart outsider should be able to say:
This company serves:The painful problem is:The insight is:The product does:The evidence so far is:The market can expand by:The team has an advantage because:The round will fund:The next milestone is:The main risk is:If the outsider cannot retell the story, the deck may be too clever, too dense, or too founder-inside. Fix the narrative before adding more slides.
Retell Failure Modes
Section titled “Retell Failure Modes”| Failure | What to fix |
|---|---|
| Investor remembers the product but not the customer. | Make the customer and use case sharper. |
| Investor remembers market size but not wedge. | Add bottom-up entry segment. |
| Investor remembers traction but not quality. | Explain revenue type, retention, pipeline quality, and cohort. |
| Investor remembers AI but not workflow. | Show where AI changes cost, speed, quality, or trust. |
| Investor remembers ambition but not milestones. | Make the use of funds and next round proof concrete. |
The deck should make the story travel without you in the room.
Traction Slide Integrity Rules
Section titled “Traction Slide Integrity Rules”Traction is the slide most likely to build or destroy trust. Show strength, but do not blur the truth.
Rules:
| Rule | Why it matters |
|---|---|
| Define every metric. | Investors need to know what counts. |
| Separate paid, unpaid, pilot, services, and recurring revenue. | Blended revenue can mislead. |
| Show time period. | Monthly, quarterly, annualized, and cumulative numbers mean different things. |
| Do not hide churn or failed pilots if material. | Serious investors will ask. |
| Show quality, not only quantity. | Logo count is weaker than usage, retention, expansion, or collected cash. |
| Use cohorts where helpful. | Averages can hide weak retention. |
| Tie traction to next milestone. | The slide should answer why now and why this round. |
For Indian founders, collection quality matters. Booked revenue, invoiced revenue, and collected cash can tell different stories. Be explicit where it matters.