Pitch the Problem, Not the Product: A Founder's Guide

Stop obsessing over your solution. A $300M founder explains why the key to fundraising is proving the problem first. Learn the framework.

Quick facts: Timothy Sheehan

Company
Greenlight
Role
Founder, Greenlight

Timothy Sheehan is profiled here for how the company was funded — the rounds raised, who backed them, and what the process looked like from the founder's side.

Veteran founder Timothy Sheehan argues that most startups fail because they get mesmerized by their solution. The key to success is to instead focus entirely on the problem: find it, test it, quantify it, and build your entire pitch around the severity and scale of the pain. This problem-first approach is what separates successful fundraisers from the rest.

Key takeaways

Stop Pitching Your Product. It’s Killing Your Startup.

According to Timothy Sheehan, who has raised over $300 million for his fintech startup Greenlight, the number one mistake founders make is getting mesmerized by their solution. You spend months building a beautiful product, polishing every feature, and crafting the perfect demo. Then you walk into a pitch meeting and lead with it.

Sheehan’s core insight, learned across a career that includes executive roles at Yahoo and multiple acquired startups, is simple but profound: You don’t raise money on your solution. You raise money on the problem. Founders who fixate on their product suffer from tunnel vision. The best founders, in contrast, throw all their focus into finding, testing, verifying, and proving the problem.

The Founder’s Tunnel Vision Trap

Why is falling in love with your solution so dangerous? It makes you deaf to feedback and blind to the market. You start to believe your elegant code or slick UI is enough to win. It isn’t.

Leading with the Demo: You jump into a product walkthrough before an investor even understands what pain you’re solving. They have no context for your features and quickly lose interest. · Ignoring Customer Discovery: You stop talking to users or only ask leading questions to validate your existing ideas, rather than seeking to be proven wrong. · Building a "Swiss Army Knife": You add feature after feature, hoping one of them will stick, instead of building a sharp spear point that solves one problem perfectly. · Misinterpreting Investor Questions: When an investor asks, "What’s your traction?" you hear "Show me more users." What they’re really asking is, "Show me evidence that people have the problem you claim they do."

The Problem-First Fundraising Framework

Instead of pitching your solution, you need to build and present an airtight case for the problem. Your goal is to make the problem feel so obvious, painful, and expensive that the investor starts wondering what the solution could be before you even mention it.

Step 1: Become an Expert on the Pain

Before you write a line of code, your first job is to become the world’s leading expert on a specific pain point. That means talking to people. Not selling, not pitching—just listening.

Sample Customer Discovery Questions (Do NOT mention your product):

"Walk me through your workflow for [process related to the problem]." · "What are the most frustrating or time-consuming parts of that process?" · "Tell me about the last time you tried to solve [problem]. What did you do?" · "What tools are you using for this now? What do you like and dislike about them?" · "If you could wave a magic wand and fix one thing about this process, what would it be?"

Your goal is to collect direct quotes and stories that illustrate the pain in human terms.

Step 2: Quantify the Problem

Once you have qualitative evidence, you need to quantify the pain. Investors need to see that the problem isn’t just annoying, but costly. This is how you build a business case.

For B2B: Calculate the cost in wasted hours, lost revenue, or compliance risk. For example: "Reps spend 5 hours a week on manual data entry. For a 100-person sales team, that’s $1.5M in wasted payroll annually." · For B2C: Quantify the cost in wasted money, time, or emotional burden. For example: "The average family overpays on credit card interest by $400/year because they lack simple planning tools."

This turns a vague "headache" into a specific, addressable market opportunity.

Step 3: Structure Your Pitch as a "Problem Deck"

Re-architect the first five slides of your pitch deck to be entirely about the problem. Your solution shouldn’t appear until you’ve fully convinced the audience that the status quo is broken.

The World Before Your Startup: Describe the target user and their world. Show them in their daily workflow. · The Problem: Introduce the specific, painful obstacle they face. Use a direct quote or story from your research. · The Cost of the Problem: Show your math. How much does this problem cost in dollars, hours, or risk? This is your market opportunity slide. · Why Existing Solutions Fail: Briefly explain why spreadsheets, competitors, or manual processes aren’t good enough. This creates a vacuum. · The Inevitable Solution: Now you introduce your product as the logical, purpose-built answer to the specific, expensive problem you just proved.

Lessons Forged in the Startup Trenches

Sheehan’s philosophy wasn’t born in a classroom. It was forged through a series of high-stakes roles that taught him the primacy of problem-solving.

At Yahoo: He learned the business fundamentals, pushing for revenue and profit. This taught him that a cool product is irrelevant if it doesn’t solve a business problem. · At Yodlee (Turnaround): Sheehan describes turning around a company as "much harder than building a business from scratch." You are forced to confront reality: redoing products, finding new revenue, and cutting costs. A turnaround is the ultimate exercise in ruthless, unbiased problem-solving.

Your Co-Founders and Your Ideas Must Serve the Problem

This problem-first mindset extends to every part of your company.

1. Choosing Co-Founders: The statistic that 67% of startups fail from co-founder conflict is well-known. The mistake is seeking a co-founder who is a mirror image of yourself. Instead, find someone who complements your weaknesses. If you’re a product visionary, you need a sales-driven operator. Map your skills and find your opposite. The tension between different perspectives, when healthy, generates better answers to the core problem.

2. Sourcing Ideas: The best ideas for solving the problem won’t always come from you. Sheehan emphasizes keeping an open mind. They often come from engineering, marketing, and especially customer service reps who are on the front lines of customer pain every single day.

Case Study: Greenlight

Sheehan applied his own advice when starting Greenlight. He didn’t start with the idea of a debit card for kids. He started by identifying a huge, unaddressed problem: parents have no effective tools to teach their children about money in a digital world. They worry about their kids’ financial literacy but are forced to use clumsy solutions like cash or giving them their own credit card.

The problem was clear, widespread, and emotionally resonant. The solution—a debit card and app managed by parents—flowed directly from that well-defined pain. This clarity of purpose is why Greenlight attracted hundreds of millions in funding.

How to Apply This a Week

Audit Your Pitch Deck: Look at your first five slides. Is it all about you and your product, or is it all about the customer and their problem? Rewrite it. · Schedule Three "Problem Interviews": Find three target customers and talk to them for 30 minutes without ever mentioning your product. Just ask about their life and their struggles. Take detailed notes. · Quantify Your Customer's Pain: Build a simple spreadsheet to calculate the cost of the problem you’re solving. Find a single, powerful number that represents the pain. · Hold a Co-Founder Audit: Honestly list your three biggest strengths and three biggest weaknesses. Ask your co-founder(s) to do the same. Are you dangerously similar, or do you balance each other out?

Frequently asked questions

What does it mean to "pitch the problem, not the solution?"
It means dedicating the first part of your investor pitch to proving a painful, expensive, and widespread problem exists. Instead of opening with your product, you open with the customer's pain point and why current solutions are inadequate.
How do I find out if a problem is big enough for a startup?
Conduct customer discovery interviews where you only ask about their workflow and challenges, without mentioning your idea. Then, quantify the pain: calculate the time wasted, money lost, or risk incurred. A big problem has a clear and significant cost.
What if investors just want to see the product demo right away?
Acknowledge their request but frame the setup. Say, "Absolutely, I'm excited to show you. To give the demo context, let me first quickly frame the specific problem we solve—it will make the demo much more powerful." This frames you as a thoughtful, problem-oriented founder.
What is the most common co-founder mistake?
The most common mistake is choosing co-founders who are too similar to you in skills and personality. The strongest teams are complementary, where one founder's strengths cover another's weaknesses in areas like tech, sales, and operations.

Related fundraising guides (24)

The decks these companies actually used (1)

Recently published pitch deck teardowns (12)

Real pitch decks, broken down slide by slide (12)

Browse by topic (2)

Fundraising library · Pitch deck examples · Investor directory · Founder database