Anticipate and rebut common investor objections
advancedClaude OpusFounders & StartupFundraisingfundraisinginvestor-objectionspitch-prepq-and-aseed
Use case
Use this 1-2 weeks before a fundraise kickoff. Founders are usually blindsided in pitch meetings not by random questions but by the 5-10 predictable concerns about their specific business that they haven't rehearsed answers to. This prompt forces you to face those objections privately first, with rebuttals that don't sound rehearsed.
The prompt
You are a skeptical, experienced seed/Series A investor on a partner Monday. You've passed on 95% of pitches. You're going to read this company and surface the objections you'd actually raise — not generic ones, the specific ones for THIS business. Then help me rebut them. Company:{{company_name}}One-line description:{{description}}Stage and round:{{stage_and_round}}Traction:{{traction}}Team:{{team}}Wedge / ICP:{{wedge}}Market:{{market}}Why now:{{why_now}}Pricing model:{{pricing}}Known weaknesses I'm aware of:{{known_weaknesses}}Do this: 1. Generate the 8-10 most specific, sharp objections an investor would have about THIS company. Not generic objections. Not "is the market big enough" — say WHY they'd doubt the market for this specific company. 2. For each objection: - State it the way an investor would actually say it (with the slight skepticism, not in formal language) - Rate it: high concern / medium concern / weak concern - Provide a rebuttal under 60 seconds spoken (~120 words) - Note whether the rebuttal fully resolves the concern, partially resolves it, or just acknowledges it 3. Identify the top 3 objections that are actually fair — i.e., where the rebuttal is "yes, that's a real risk and here's our plan." Don't fake confidence on these. 4. Identify which objections are likely to come from which type of investor (e.g., "the technical risk question will come from the partner who looks at infra; the market sizing will come from the consumer/SMB-focused partner"). 5. End with one objection you should preemptively raise yourself in the pitch — because doing so signals self-awareness and disarms the room. Be sharp. The point is not to make me feel good — it's to make me bulletproof.
Variables
{{{{company_name}}}}Replace with your {{company name}}{{{{description}}}}Replace with your {{description}}{{{{stage_and_round}}}}Replace with your {{stage and round}}{{{{traction}}}}Replace with your {{traction}}{{{{team}}}}Replace with your {{team}}{{{{wedge}}}}Replace with your {{wedge}}{{{{market}}}}Replace with your {{market}}{{{{why_now}}}}Replace with your {{why now}}{{{{pricing}}}}Replace with your {{pricing}}{{{{known_weaknesses}}}}Replace with your {{known weaknesses}}
Example
Input
company_name: Linework description: Mobile-first ops platform for mid-market apparel and logistics — replaces shift handoff, incident logs, and floor visibility for ops managers stage_and_round: pre-seed, raising $2M seed traction: $32k MRR, 14 customers, NPS 58, Patagonia signed last month, 4 expansions in 60 days team: Maya (CTO, ex-Stripe eng), Jordan (CEO, ex-HubSpot sales/PM, prior ops manager) wedge: morning shift handoff at apparel/logistics ops teams (200-500 employees) market: $40B+ mid-market ops software, dominated by legacy ERPs and internal tools why_now: AI summarization of messy ops data became reliable 18 months ago; post-2020 ops managers expect consumer-grade UX pricing: $24k average ACV, per-site, monthly known_weaknesses: - No SOC2 - Founder-led sales - Mid-market segment historically hard to sell into profitably - Vertical wedge (apparel) might cap upside
Output
EIGHT SHARP OBJECTIONS — and rebuttals 1. "Mid-market is a graveyard. Companies that try to sell to 200-500 person companies usually end up either pulled down to SMB or up to enterprise. What makes you different?" (HIGH CONCERN) Rebuttal: "Fair concern, and you're right about the historical pattern. Two things make our case different. First, our ACV is already $24k average — that's enterprise-tier ACV being earned in mid-market because we're attached to a critical workflow, not a nice-to-have. Second, our buyer is the ops manager, not IT or finance — that's a more decisive buyer in mid-market than the typical 'committee' that drags deals. We're aware of the gravity in both directions and we're tracking ACV trend monthly. If it drifts down, we'll know within 60 days." Resolves: partially. The risk is real; what we've done is offered evidence we're not in the typical mid-market trap yet. 2. "Apparel is a tiny piece of the $40B you cited. Why should I believe you can expand into manufacturing? That's a different sale, different buyer, different stack." (HIGH CONCERN) Rebuttal: "We started in apparel because the ops workflow is highly portable — the shift handoff at a Patagonia distribution center looks 80% like the one at a mid-size manufacturer. We've already had inbound from a mid-size manufacturer through a Patagonia exec referral. The expansion path is workflow first, vertical second. We're not promising we win manufacturing in year one — we're saying the wedge is portable and we'll prove it before raising the next round." Resolves: partially. The cross-vertical claim is unproven, and we're naming it as the next milestone, not the current state. 3. "Founder-led sales at 14 customers is fine. But your case for $200k MRR depends on hiring an AE who can sell this without you. First sales hires almost always miss." (MEDIUM CONCERN) Rebuttal: "Agreed — first sales hires miss 50% of the time. We've budgeted for it. The plan: hire one strong AE in month 2-3, evaluate against specific milestones at day 75 (5 closed deals from inbound), and if they miss, replace fast. The 24-month runway in this round explicitly accounts for one mis-hire. We'd rather raise the right amount and hire carefully than raise more and hire faster." Resolves: partially. We're not promising the AE works; we're promising we won't be surprised if they don't. 4. "How do you compete with a Notion or a Coda once they decide to go vertical?" (MEDIUM CONCERN) Rebuttal: "We don't compete with horizontal docs tools because the buyer doesn't want a flexible canvas — they want a workflow that lives on a phone in a noisy warehouse with patchy connectivity. Notion's product surface is the wrong shape for this user. The defensibility isn't a feature; it's the workflow ownership and the customer relationship at the ops manager level. Notion isn't going to staff field sales for ops managers." Resolves: mostly. 5. "$32k MRR in 8 months is fine. But what's your ACV trend? If you're discounting to land logos like Patagonia, your unit economics are worse than they look." (HIGH CONCERN) Rebuttal: "Patagonia is at our standard ACV — we did not discount to land them. Of the last 14 customers, 12 are at list price; 2 took a 15% multi-year discount. We can share the cohort by ACV in the data room. The honest read of our numbers is that mid-market ops managers buy at price when the workflow value is clear." Resolves: fully — assuming the data backs you up. Make sure it does. 6. "Why now is interesting but I've heard 'AI changed it' a lot this year. What's actually different in your product because of AI versus marketing copy?" (MEDIUM CONCERN) Rebuttal: "Specifically: the auto-summarization of shift handoff notes. The handoff used to require 30 minutes of an outgoing manager typing; we get it down to 90 seconds because the model summarizes from voice + photo + structured fields. Without that, we're just a better Notion. With it, we're a different product. We can show this in the demo." Resolves: fully — if the demo lands. 7. "Two cofounders, neither has done this before. Who's the operator if it scales?" (WEAK CONCERN — but they'll ask) Rebuttal: "Maya operated 60-person eng orgs at Stripe; that's the operator depth on the team. I [Jordan] managed PMs and sales teams at HubSpot. We're aware that scaling a company is different from scaling a function, and we've already engaged two operating advisors who've done it. We're not pretending we have all the answers; we're naming the gap and surrounding it." Resolves: mostly. 8. "Pricing per-site at $24k — what happens when a customer wants to roll out to 30 sites? Do you have an enterprise SKU?" (MEDIUM CONCERN) Rebuttal: "Yes — at 5+ sites we move customers to a multi-site agreement with volume pricing. Patagonia is the first multi-site deal. We're testing pricing actively and we'll have a real enterprise SKU defined in the next 90 days, before this round closes. Open to your input on pricing strategy." Resolves: partially. The fact that you don't have a real enterprise SKU yet is a small flag. ACTUALLY FAIR (top 3 — don't fake these) - Mid-market gravity (1) — real risk, plan is monitor and react. - Vertical-to-cross-vertical expansion (2) — unproven, named as a milestone. - First AE hire (3) — high failure rate, runway accounts for it. WHO ASKS WHAT - Generalist consumer/SMB partner: 1 (mid-market gravity), 5 (ACV trend). - Vertical SaaS specialist: 2 (cross-vertical), 4 (horizontal competition). - Technical / infra-leaning partner: 6 (AI is real?), 7 (operator depth). - Enterprise-focused partner: 8 (enterprise SKU). RAISE YOURSELF IN THE PITCH Bring up the mid-market gravity concern unprompted. "Here's a fair pushback you might have — mid-market is historically a graveyard. We're aware. Here's what we're tracking and what would tell us we're in the trap." Doing this in the pitch raises your credibility instantly and disarms the harshest version of the question.
Tips for best results
- 1If you can't answer an objection in 60 seconds, the answer isn't ready. Keep tightening.
- 2The objections labeled 'fair' should be the ones you most want to address head-on. Investors trust founders who name real risks more than ones who deflect.
- 3Run this prompt 2 weeks before pitching, not 2 days before. You need time to actually fix some of the issues, not just rehearse rebuttals.
- 4After 5-10 actual investor meetings, re-run this prompt with their actual questions as input. The questions you actually got are signal — the ones nobody asks were never real concerns.
- 5Practice rebuttals out loud, with someone who'll push back. Reading them off a page is not preparation.
Related prompts
Draft the narrative arc for a seed pitch
advancedBuild a tight seed pitch narrative — problem, wedge, market, traction, ask — that survives 10 minutes of investor questions instead of falling apart in 3.
Founders & Startupfundraisingpitchnarrative
Build a data room checklist tailored to round size and stage
intermediateGenerate the right-sized data room for your specific round — not the kitchen-sink version that takes 3 weeks to build, and not so light that diligence stalls.
Founders & Startupfundraisingdata-roomdiligence
Generate a structured fundraise status tracker update
intermediateBuild a clear weekly fundraise tracker that shows where every investor sits in the process, what's stalled, and what to do next — so you stop guessing how the round is actually going.
Founders & Startupfundraisingpipelinetracker
Need help implementing this prompt in your workflow?
Book a call