Startup Problem Statement Examples (With a Template)

A startup problem statement is one to three sentences that name a specific group of people, the problem they hit, what it costs them and why today’s options fall short, all written before you mention your product. Below you get a fill-in template, startup problem statement examples for 12 industries, the way Airbnb, Dropbox, Canva and Rent the Runway described their problem before they were worth billions, business problem statement examples for established companies, and an interview script to test yours with real customers.

I’m Violetta Bonenkamp, also known as Mean CEO, founder of Fe/male Switch (a startup game for women founders) and CADChain. Here is why this page exists: in its March 2026 analysis of 431 VC-backed startups that shut down since 2023, CB Insights found poor product-market fit in 43% of the failures with a known cause, and two thirds of those were early-stage companies that never found a market. A sharp problem statement is the cheapest insurance against joining that list.

A startup problem statement is a short, evidence-backed description of a problem worth solving: who has it, when it shows up, what it costs and what people do about it today. It leaves the solution out on purpose, so you, your team and your customers can judge the problem on its own.

Investors, accelerators, hackathon juries and teachers ask for it first because everything else in a pitch (market size, product, pricing, go-to-market) hangs on it. When the problem is vague, the rest of the deck is guesswork with nice fonts.

The 5 parts of a problem statement for a startup

• Who: a customer group narrow enough that you could find 20 of them this week.
• What: the task or goal they struggle with, described in their words.
• When: the situation or trigger that makes the problem show up.
• Workaround: what they do today (a spreadsheet, a freelancer, a competitor, or nothing at all).
• Cost and proof: the time, money, stress or risk it creates, and how you know.

Problem statement, mission statement and pitch line: what is the difference?

These statements get mixed up in pitch decks and school assignments all the time. Here is how they differ, using one imaginary allergy startup plus one in-company sample:

The figures in these samples are invented to show the format. Your real statement uses numbers you collected yourself.

Copy this fill-in template, replace every bracket, and you have a first draft in ten minutes:

[Specific customer group] struggles to [task or goal] when [situation or trigger]. Today they [current workaround], which costs them [time, money, risk or stress]. We know this because [evidence: interviews, data, reviews].

For a slide or a hackathon form, use the short version that Google’s design-thinking guide for developers recommends: USER_GROUP needs NEED because REASON. The same Google for Developers page warns against writing the need as a solution: “needs an app to order food” is a product idea, while “needs to access nutritious meals quickly” is the actual need.

How to fill in each slot

Put together: Freelance bookkeepers with 10 to 30 small-business clients struggle to collect receipts before each quarterly VAT deadline. In the last week of every quarter they chase clients by email and WhatsApp and retype photos into spreadsheets, which eats their evenings and exposes clients to late-filing fines. The evidence goes in bullets under the statement on your slide, or in the appendix of your plan.

If you think better in boxes than in sentences, fill in the problem statement canvas first and turn each box into one clause of the template.

4 rules that keep the template honest

• Leave the solution out. If the statement contains “app”, “platform” or your product name, rewrite it.
• One customer group per statement. Two groups means two statements, so a marketplace writes one for buyers and one for sellers.
• Use their words. Customers say “I lose my Sundays to scheduling”, and that line beats any jargon you could write.
• Add a number as soon as you have one. “9 of 14 bookkeepers we interviewed” is stronger than “many bookkeepers”.

Here are 12 startup problem statement examples you can adapt. Each one is a hypothesis, so the last column tells you which evidence turns it from a hunch into a fact before you show it to an investor.

Problem statement for startup ideas you haven’t built yet

When all you have is an idea, write the problem statement before you name the idea. Start from your concept, ask “what has to be true for someone to pay for this?”, and turn the answer into a sentence about a person. Say your idea is an app that plans dinners from whatever is in the fridge. The problem statement behind it: working parents throw away food they bought with good intentions, because by 7 pm nobody has the energy to plan a meal around it. Now you can test the problem without writing a line of code.

Problem statements for student projects and hackathons

Teachers and hackathon juries look for three things: one specific group, no solution hidden in the sentence, and at least one cited data point. If you still need a topic, pick one from our list of business project ideas and run it through the template above.

Unicorn startups wrote problem statements that named a real group of people, a workaround those people already used and the reason existing options failed. The word “unicorn” comes from investor Aileen Lee, who used it in a 2013 TechCrunch article for US software startups founded since 2003 and valued at $1 billion or more. Here are four whose early problem framing you can check in the founders’ own documents or interviews.

Airbnb: hotels cost too much and keep you away from the city (2008 pitch deck)

The first Airbnb deck, from when the company was still called AirBed&Breakfast, opened with three short problem lines, as Business Insider reported:

• Price is an important concern for customers booking travel online.
• Hotels leave you disconnected from the city and its culture.
• No easy way exists to book a room with a local or become a host.

Why it works: one line covers price, one covers the experience and one covers the missing marketplace, for guests and hosts at once. The deck also pointed to people already living with a workaround: Couchsurfing.com had 630,000 users at the time, yet there was no easy, central platform that worked around the world. Business Insider put Airbnb’s later private valuation at $31 billion.

Dropbox: “no good integrated solution” (2007 Y Combinator application)

Drew Houston’s original Y Combinator application lists what small teams need: their files wherever they are, everyone working on the latest version, and data protected from disaster. Then it names the substitutes people used (separate sync tools, backup tools and web upload tools) and concludes there was “no good integrated solution”. He adds a human proof point: his little sister used the beta for her high school papers and no longer burned CDs or carried USB sticks.

What to copy: name the workarounds. Investors trust a problem more when they can see what people do today and why it is clumsy. Dropbox reached a $10 billion valuation in 2014, TechCrunch reported.

Canva: a whole semester to learn where the buttons are (Melanie Perkins)

Melanie Perkins was 19 and teaching other university students in Perth to use design programs in 2006 when she spotted the problem, she told CNBC Make It. Students found the software “crazy hard”, and people spent “an entire semester learning where the buttons were”. She and Cliff Obrecht first tested the idea in a narrow niche, an online school yearbook design business called Fusion Books, and started Canva in 2013. CNBC reported a $3.2 billion valuation after an October 2019 funding round.

The takeaway: the cost was time to learn, measured in semesters. A clear unit of pain (hours, semesters, euros) makes a problem statement stick in an investor’s head.

Rent the Runway: a closet full of clothes and nothing to wear

In 2008, Jennifer Hyman watched her younger sister Becky buy a $1,600 Marchesa dress for a wedding, even though her closet was full. Becky had already been photographed in every dress she owned and couldn’t stand repeating an outfit. Fortune’s account of the founding sums up the problem as “a closetful of dresses, but nothing to wear”. When Hyman asked why she picked such an expensive dress, Becky said she wanted to feel beautiful. Hyman took the story to Jennifer Fleiss, they founded Rent the Runway, and the company reached a $1 billion valuation in March 2019, Fortune reported.

Steal this: dig under the purchase. Becky’s real need was feeling confident in photos, and the new dress was her expensive workaround.

What these four problem statements have in common

All four start with a person in a specific moment, and the billion-dollar valuations arrived years after those first sentences were written. For more company stories with the lessons spelled out, read our startup business examples.

A business problem statement describes the gap between how a process performs today and how it should perform, plus what that gap costs the company. Teams use it to kick off an improvement project, a business case or a consulting brief, and like a startup problem statement, it leaves the fix for later.

Fill-in format: Over [time period], [process or metric] moved from [X] to [Y], against a target of [Z]. This costs us [money, customers, hours or risk] every [month or quarter].

The numbers in brackets below are placeholders that show the format. Swap in the figures from your own systems.

Business plan problem statement examples

In a business plan or business proposal, the problem section answers three questions in about half a page: who has the problem, how big it is in money or numbers, and why current options fail. Here is a sample with placeholders: Independent physiotherapy clinics in [region] ([number] clinics, source: [registry]) lose [X] hours a week to missed appointments. Reminder tools built for hospitals cost [€X] per month and need IT support these clinics don’t have.

Size claims belong in this section, so back them with a bottom-up estimate. Our guide on how to calculate TAM SAM SOM for a startup walks you through it.

Business research problem statement example

Academic and market research projects phrase the problem as a gap in knowledge: Small grocery stores in [city] that added self-checkout report mixed results, and nobody has measured which store traits predict whether the investment pays back. The research question follows from it: which store traits predict a payback within [24] months?

A weak problem statement describes a market, a trend or a product. A strong one describes a person, a moment and a cost you can check. Seven rewrites (the strong versions are sample hypotheses that show the shape, so test them before you borrow one):

5 mistakes that weaken a startup problem statement

• The solution in disguise. “There’s no app for X” describes your product idea, and customers never describe their lives that way.
• Everyone as the customer. If you can’t name where to find the first 20 people, the group is too wide.
• Trends instead of behavior. “Gen Z cares about the planet” tells you nothing about what a 22-year-old does on a Tuesday, and Tuesday behavior is where problems live.
• Symptoms instead of causes. Customers say “it’s slow”. Ask why until you reach the cause you could fix.
• No evidence. Swap “everyone says so” for counts like “9 of 14 interviewees described this in the last month”.

Test a problem statement by talking to 10 to 20 people from your customer group about the last time they had the problem, without pitching your idea, and by checking whether they already spend time or money on a workaround. If most of them can’t recall a recent, specific moment, rewrite the statement before you build anything.

Step 1: Turn the statement into 3 assumptions

• The group exists and you can reach it. You know where they gather, online and offline.
• The problem comes back regularly. Weekly or monthly beats once a year.
• They care enough to act. They already pay, hack or complain about it.

Step 2: Interview without pitching

At Y Combinator’s Startup School, Pebble founder Eric Migicovsky recommended five interview questions, summarized on the YC blog. Adapted to your problem statement:

1. What is the hardest part about [the task in your statement]?
2. Tell me about the last time you ran into this problem.
3. Why was that hard?
4. What, if anything, have you done to solve it?
5. What don’t you love about the solutions you’ve already tried?

The same talk names three mistakes: pitching your idea, asking hypothetical questions and talking too much. Rob Fitzpatrick’s book The Mom Test builds on the same idea, and its three rules, as Unusual Ventures summarizes them, are: talk about the customer’s life instead of your idea, ask about specifics from the past, and talk less while listening more.

Step 3: Rate what you hear

Step 4: Rewrite, then retest

Put your counts into the evidence line (“11 of 16 bookkeepers retype receipts by hand every quarter”) and sharpen the “who” around the people who reacted most. List every alternative interviewees mention, then use our AI competitive market analysis tool to plan how you will size up those competitors. Once the problem holds up, move it into the customer segment box using these business model canvas ideas.

Elona Musk, our AI co-founder, will happily draft ten versions of your statement in a minute. Only your customers can tell you which one is true. If you want to practice this whole loop with deadlines and a community of women founders around you, the Fe/male Switch startup game takes you from idea to first customer through practical quests.

What is a good problem statement for a startup?

A good startup problem statement names a specific customer group, the situation where the problem shows up, what it costs them and what they do today, in one to three sentences. It has evidence behind it and no solution inside it.

How long should a startup problem statement be?

One to three sentences, about 50 words at most, so it fits on one pitch deck slide. Put the supporting evidence in bullets below it or in the appendix of your business plan.

Should a problem statement include the solution?

No. Keep your product out of it so you can test the problem on its own, and so readers judge the problem before they judge your idea.

What is a unicorn problem statement?

People use the phrase for the problem statements of unicorn startups, meaning young companies valued at $1 billion or more. The documented ones above (Airbnb, Dropbox, Canva, Rent the Runway) each name a real group, a workaround and a cost.

What is the difference between a business problem statement and a startup problem statement?

A business problem statement describes a gap inside an existing company, between current and target performance of a known process. A startup problem statement describes a customer group’s problem in a market you haven’t proven yet, so it needs customer evidence first.

How do I write a problem statement for an entrepreneurship assignment?

Use the template above, pick one customer group, add two or three data points from sources you cite (government statistics, industry reports, your own interviews), and save your solution for the next section of the assignment.

Where do I find data for a problem statement?

National statistics offices, industry associations, academic papers on Google Scholar, annual reports of public companies, app store and product reviews (for the customer’s own words) and, most convincing of all, your own interviews and time logs.

What is a challenge statement?

In design thinking workshops and idea competitions, a challenge statement turns the problem into an open question that starts with “How can we…”. Problem: night-shift nurses lose details at handover. Challenge statement: how can we make sure no patient detail gets lost between shifts?

Can ChatGPT write my startup problem statement?

An AI assistant can draft and tighten the wording, but it can’t supply evidence. Write the draft with AI if you like, then test it in customer interviews and replace every guess with something you heard or measured.

• Problem statement canvas: map who has the problem and why before you write a word.
• How to calculate TAM SAM SOM: size the market behind your problem.
• Startup business examples: successful startups and what they teach.
• Startup stories: how founders got through the first hard years.
• Business project ideas: topics for students and teams that need a problem to solve.
• First startup checklist on the Fe/male Switch blog: plan the next steps once your problem statement holds up.
• Fe/male Switch startup game: build your startup from idea to first customer.