Every week, founders send me pitch decks hoping I’ll write a check. Most of them make the same mistakes—not because they’re bad people or bad ideas, but because they don’t understand what actually moves the needle for investors. I’ve sat on both sides of the table: as a founder who raised $12 million across three companies, and now as an angel investor who’s looked at over 400 decks in the past two years. What I’ve learned is that reading a pitch deck is a specific skill, and most investors—even experienced ones—don’t do it systematically enough.
This guide gives you the framework I use every time a founder slides into my DMs with their deck. It’s not about finding the perfect company; it’s about understanding what questions to ask, what signals matter, and where most people get fooled. I’ll walk through each slide, explain what actually matters versus what’s just theater, and show you how to dig deeper in your follow-up conversations.
The problem statement seems straightforward—you’d think any founder can articulate what problem they’re solving. But here’s what I’ve noticed: roughly 70% of decks I review conflate a symptom for the root cause. They say something like “small businesses struggle with inventory management” when the real problem is “retailers can’t predict demand during seasonal shifts because their POS systems don’t integrate with forecasting tools.”
The solution slide is where things get interesting. A strong solution slide doesn’t just describe what the product does—it demonstrates a unique insight. The best founders I’ve backed didn’t just build something new; they saw something others missed. When I look at a solution, I’m asking: does this feel like a feature that could be added to an existing product, or is it a fundamentally different approach to the problem?
One exercise I use: read the problem and solution slides together, then ask “so what?” three times. If the founder can’t explain why this particular solution is the only one that works, that’s a signal. Slack didn’t just build a better chat tool—they understood that enterprise communication was broken in ways email couldn’t fix. The problem-solution fit should feel almost annoyingly obvious once you see it.
Investors’ obsession over market size is both justified and frequently misused. The classic mistake is pulling a number from a Gartner report that says the total addressable market for “enterprise productivity software” is $50 billion, then claiming that’s their market. That’s not how it works.
When I evaluate market size, I start with the serviceable addressable market—the portion the startup can realistically reach given their go-to-market strategy. A B2B SaaS company selling to mid-market manufacturing companies doesn’t have access to the entire enterprise software market. Then I look at serviceable obtainable market—the revenue they can actually capture in a realistic timeframe.
Here’s what most articles get wrong: market size matters less than market timing. A $500 million market that nobody is serving is far more interesting than a $50 billion market with three well-funded incumbents. Look for markets that are either newly created (AI coding assistants didn’t exist five years ago) or undergoing structural shifts (remote work changed everything about B2B office equipment).
The honest admission most guides won’t make: I rarely spend more than 90 seconds on the market size slide. If the numbers are obviously inflated, that’s a data point about the founder’s integrity. If they’re reasonable but not spectacular, that’s fine—great companies often start in smaller markets. What I’m really looking for is whether the founder has done the homework to understand their specific corner of the market.
Traction is where the conversation gets real. A pitch deck can hide behind words, but numbers don’t lie—except when they do. I’ve seen founders celebrate 300% year-over-year growth when they’re comparing $10,000 in revenue to $40,000. Context changes everything.
The metrics I care about most depend on the stage. For pre-seed companies, I’m not looking for revenue—I’m looking for evidence of demand: waitlist signups, LOIs (letters of intent), pilot participants, or even just strong engagement metrics if it’s a consumer product. For Series A and beyond, I want to see cohort retention. Can the company acquire customers profitably, and do those customers stick around?
One framework I use: calculate the ratio between customer acquisition cost and customer lifetime value. If you can’t tell me what LTV is, that’s a problem. If you tell me LTV is $50,000 and CAC is $5,000 but you’ve only been acquiring customers for three months, I need to see that play out over longer periods before I believe it.
Growth rate matters, but not in the way people think. A company growing from $100K to $500K ARR (500% growth) is more interesting than one going from $5M to $10M (100% growth) if the earlier company has found a repeatable sales motion. The question isn’t just “are they growing?” but “can they keep growing at this rate while maintaining or improving unit economics?”
Every investor will tell you “the team is the most important factor.” That’s true, but it’s also the most exploited. Founders know investors say this, so they load their deck with advisors who have famous names and executives who left prestigious companies two years ago after a disagreement.
Here’s what actually matters in a team assessment: domain expertise and execution credibility. Did the founders live the problem they’re solving? Have they personally experienced the pain point, or have they spent years working in this specific industry? The best founders I’ve backed didn’t just identify an opportunity—they had stories about why this problem kept them up at night.
The co-founder question is underrated. Single founders raise money, but I always ask why they don’t have a co-founder. Building a company is hard enough with two committed people; doing it alone signals either difficulty collaborating or inability to convince someone else to bet on the idea. That’s a data point, not a dealbreaker, but it’s worth understanding.
Reference checks matter more than bios. I don’t care that your CTO worked at Google—I care what they actually built there and whether the people who worked with them would work with them again. Cold calling a reference is uncomfortable, but it’s the only way to get real signal. I’ve passed on deals where the reference call revealed a pattern of blaming others for failures.
The competition slide is where founders either underestimate or overestimate their competitors, rarely landing in between. The “we have no competition” answer is an automatic red flag—no market exists in a vacuum. The 50-page competitive analysis that compares every feature against 15 competitors usually indicates the founder is more focused on competitors than customers.
What I actually want to see: honest acknowledgment of what already exists, combined with a clear articulation of why this approach is defensible. A feature advantage isn’t a moat—features can be copied in weeks. A network effect takes years to build. A brand takes decades. Proprietary data is valuable if it’s actually proprietary and hard to replicate.
The moat question I always ask: “What prevents a well-funded competitor from building this in six months?” If the answer is “our technology” or “our team,” that’s not enough. If the answer involves compounding advantages—more users generating more data leading to better products leading to more users—now we’re talking.
I’ll be direct: I don’t believe financial projections. Nobody projects revenue accurately beyond 12 months, and even that’s generous. What I do look for is whether the projections are internally consistent and whether the founder understands the key assumptions driving their business.
Unit economics should be visible on the financials slide or in the appendix. How much does it cost to acquire a customer? What’s the gross margin? What’s the payback period on acquisition spend? If these numbers aren’t in the deck, that’s a signal—the founder either doesn’t know them or is hiding them.
Gross margin is particularly important for SaaS companies. A software company with 80% gross margins can survive a lot of mistakes; a 40% margin business needs to execute perfectly. The difference between those two models is fundamental to how I think about risk and return.
The projection exercise I use: ask the founder what has to be true for the numbers to work. What conversion rate, what deal size, what sales cycle length? Then ask how realistic those assumptions are based on their current metrics. Founders who can walk through this exercise thoughtfully demonstrate operational understanding that distinguishes them from people who’ve just extrapolated a curve.
The ask slide seems simple—how much money do they want and what will they do with it? Yet I’ve seen founders ask for $2 million without being able to explain what happens at month 18 if they only raise $1.5 million. That kind of thinking reveals a lack of planning.
Strong decks break down the use of funds by category: engineering, sales and marketing, operations, and runway. They also explain the milestones this raise will enable. The question I want answered: what does the company look like 18 months from now that it can’t look like today without this capital?
Runway math matters more than people admit. If you’re raising $2 million at $500K monthly burn, that’s four months of runway—way too tight. A quality deck shows at least 18 months of runway, with a clear path to the next financing round or profitability. The best founders I’ve backed have conservatively estimated burn and optimistically estimated growth.
The “why now” question applies to funding as much as to the business itself. Why raise now versus six months ago or six months from now? The answer should connect to market timing, team readiness, or a specific competitive window. If they can’t articulate why this particular moment requires outside capital, I wonder whether they need it at all.
Beyond the basics, there are quieter warning signs that experienced investors notice but rarely articulate. One of them: founders who can’t explain what their customer says about them. Not metrics, not NPS scores—actual words from actual customers. If the founder hasn’t had conversations with users that changed how they think about the product, that’s a problem.
Another red flag: the deck is polished but the product is half-baked. Visual design matters for fundraising, but not at the expense of substance. I’ve seen decks that looked like they came from a professional design agency attached to products that still had significant bugs. The founder’s energy went to the wrong place.
The advisor list deserves scrutiny. If every advisor is a famous name who hasn’t responded to an email in six months, that’s decorative. Strong decks have advisors who are actually involved—advisors the founder can describe specific conversations with about specific decisions.
Watch for the “asymmetric upside” claim. Every pitch promises 10x returns with “limited downside.” But if the business model requires everything to go perfectly, that’s not limited downside—that’s high risk. The best investments have some margin of error built in.
The deck gets you to the meeting. The conversation gets you to the investment. After reviewing a deck, I come with specific questions that the deck couldn’t answer.
For traction: walk me through your last ten customers. What was the sales cycle? Who was the decision maker? What almost made them say no? This reveals whether the sales process is repeatable or whether it was a few lucky closes.
For product: show me the product, not as a demo, but as you actually use it. Where are the rough edges? What do users complain about most? Founders who can’t identify weaknesses haven’t talked to users enough.
For the market: what’s the hardest part of selling to this customer? What’s the most common objection you hear? If they say “no objections,” they haven’t actually tried to sell anything yet.
For the team: what’s the biggest mistake you’ve made in the last six months, and what did you learn from it? Failure to reflect on mistakes—or worse, inability to identify any—indicates a lack of self-awareness that will compound over time.
Reading a pitch deck isn’t about finding the perfect company. It’s about developing a systematic way to separate signal from noise, then having the conviction to act when others hesitate. The frameworks in this guide will help you evaluate decks more consistently, but the actual skill comes from looking at hundreds of them and developing an intuition for what feels right.
The thing nobody tells you: you’ll still miss things. Every investor has passed on companies they should have backed, and funded ones that failed. The goal isn’t perfection—it’s building a process that captures the factors that actually correlate with outcomes. Start with these questions, add your own as you go, and remember that the best investors are always learning from the decks that got away.
Most founders obsess over user acquisition. They celebrate every new signup, crow about growth metrics…
The startup funding landscape has changed a lot over the past decade. One of the…
Startup accelerators have become one of the most influential institutions in the technology world over…
The startup world is littered with products nobody wanted. Millions of dollars burned on features…
Most investors and operators treat go-to-market strategy as an afterthought. They obsess over product features,…
Most startups fail because they build something nobody wants—not because they run out of money.…