Limited Time

24-Hour Flash Sale: 70% OFF "NO BS STARTUP GUIDE" — USE CODE: NOBSPATRON

00 Hrs
00 Min
00 Sec
Claim Discount

Problem Validation: Are You Solving a Real Problem?

Farzad Khosravi

By

3x founder · Coach to 300+ founders

July 20, 2026 8 MIN READ Updated November 2026
Problem Validation: Are You Solving a Real Problem?

A friend of mine built a tool that let you control an Android phone from a PC. He thought it was a toy, never showed it to anyone, and left it sitting on his laptop for months while he worked on things he considered more serious.

I wrote one plain description of it and posted it in an Android developer forum. Nothing to sign up for.

Within minutes, people were asking how to get it. One stranger offered to pay on the spot.

I spent an afternoon on that post. Those replies gave me a place to start. I could ask people what they already did when they needed to control a phone from a PC.

Most founders get the reverse. They spend six months building, launch, hear nothing back, and only then start asking the questions that would have saved them the six months. The product works perfectly. Nobody visits the signup page. The most expensive thing a founder builds is a solution to a problem nobody has.

Problem validation is the step most founders skip

Most founders validate the solution and never touch the problem. They ask a friend if they’d use it. The friend says yes, so they start building. “Would you use this” is the most useless question in startups. People say yes to be kind, and a kind yes has killed more startups than any competitor.

Problem validation means checking whether a specific group of people keeps running into a problem with consequences they can show you. Ask what happened the last time and what they did about it. Once you understand the cost, you can test whether they’ll pay for the solution you have in mind.

What a real problem actually looks like

A real problem leaves marks. It shows up often. It costs the person something they can measure. And they’re already doing something clumsy about it: a messy spreadsheet, a WhatsApp thread, a $5-an-hour VA, a competitor’s half-broken tool.

A problem with none of those marks is a vitamin. Nice to have, easy to skip. You want a painkiller, the thing someone with their hair on fire types into Google at 11pm.

The No BS name for the opposite is the “nobody gives a shit” problem. You build something clean and launch it. Almost nobody comes. Nothing about the product is broken. The pain you solved was so small that people had already stopped noticing it, and no marketing budget fixes that, because the pain was never big enough to make anyone move.

Follow the workaround until the job is done

When someone tells you they use a spreadsheet, ask them to walk you through the last row they closed. A tool name tells you where the work lives. You still need to see what happened between opening the row and being able to forget about it.

With their permission, use a redacted example. A verbal walkthrough works too. Pick one recent case that went smoothly and one that got stuck. For each, write down what started the work, then follow it to the end.

The handoff. Who did the next thing after the software finished?

The wait. Who noticed that a response was late, and where did they keep track of it?

The exception. What went wrong, and who had to fix it?

The finish. What told them it was really done?

Keep two times in your notes. Record how long the case stayed open and how many minutes people spent working on it. Days of waiting can tie up cash or delay somebody else’s work. Staff minutes tell you how much work the team could get back.

Say you’re thinking of building automatic payment reminders. In this hypothetical, you look at two invoices. The first was paid and reconciled four days after it went out. The finance team spent three minutes on it, all to match the payment to the invoice. The customer’s accounts-payable team rejected the second because it was missing a purchase order number. Someone had to find the number, reissue the invoice and check that payment came through. It was paid and reconciled eleven days after it went out, and the team spent thirty-five minutes on it. Another reminder would have left the same work on their desk.

Before building, I’d ask how often invoices get rejected for that reason and what happened the last time the team tried to fix it. If their invoicing tool can already require a purchase order number, find out why they aren’t using that setting. If the same exception keeps coming up, offer to help one team catch missing numbers on a small batch before the invoices go out. Compare rejections and staff time with a similar recent batch. Ask whoever owns collections what result would make a paid trial worth approving.

Before the next round of calls, decide what would change your mind. If several teams can show recent rejections with the same costly fix, test that fix. If the delay keeps happening to teams that get the purchase order number late, narrow your search to those teams. If all you can find is one bad invoice from months ago, put the idea down and look for a problem people are dealing with now.

Why founders skip the problem

Building is comfortable. You control the code. You can work all weekend and point at something you built.

Calling twenty strangers to ask about their week is uncomfortable, and it might tell you the thing you’ve been building for months is a vitamin.

I call this the Ape Brain. It’s the part of you wired to look busy and dodge the scary question. Shipping one more feature looks like progress on the calendar. The call that might end the whole project keeps getting pushed to next week, and then the week after that.

How to validate a problem before you build

The three checks below run on conversations and a little honesty. No product needed. Run them before you write another line of code.

Look for the workaround they already pay for

Ask what they use today and what it costs them in money or staff time. If they say they live with it, ask what happened the last time they did. A delay they accept every week and a problem they barely notice can sound the same until you ask for an example. Treat existing alternatives as your real competition, because that duct tape is what you have to beat.

Score it on frequency and pain

Write down how often the problem comes up and what it costs each time. A daily annoyance can still be cheap to ignore. A quarterly deadline can cause a serious loss if it slips. Ask about a specific incident so you have something better than a severity score to work with.

Hear the problem in their words, before you pitch

The strongest signal is a stranger describing the problem to you, unprompted, before you’ve said what you’re building. Ask what they did last week. Skip the hypothetical about someday. Write down the exact words they use for the pain, then hold your product up against them. The customer discovery interview questions that get receipts give you the script. If the problem only comes up after you describe your product, ask for a recent example before you count it as evidence.

In college I ran eighteen calls on a marketplace I was building for farmers, and seventeen of those calls were polite enough to keep me building. The eighteenth told me farmers close deals face to face. The premise died right there. I’d already built half the product.

What counts as a validated problem

I’d keep testing when several people in the same customer group can show me recent instances of the same problem and explain what it cost them. In B2B, find out who owns that cost and what they can approve. An introduction to that person shows the team is willing to spend some effort. A paid trial gives you evidence about whether someone will buy your solution.

Where problem validation breaks

Problem validation isn’t a rule for every case. Three honest exceptions.

New categories can lack an obvious workaround because the pain is real and people have quietly given up. Listen for a resigned “I just deal with it.” That sounds different from “what problem?”

In B2B, the person with the pain is often not the person with the budget. Validate both, or you’ll build something a user loves and a buyer never approves.

Your own pain counts as one data point, and a single user isn’t a market. Being your first customer is a fine place to start. Go find ten more.

Validate the problem before you build the answer

I turned the No BS validation process into a free worksheet. It walks you through pressure-testing the problem and the person paying for it before you write a line of code.

Get the No BS Validation Worksheet, free.

Run your idea through it. If the problem holds up, move on to validating the solution itself. If you want a second set of eyes on what you’re building, book a call and bring your riskiest assumption. The No BS startup guide maps the stages on either side of this one.

Before your next build session, ask someone to walk you through the last time they dealt with the problem. Stay with the example until you know what it took to finish.

Related Startup Guides

All articles
Farzad Khosravi, No BS Startup Coach

Farzad Khosravi

No BS Startup Coach · 300+ Founders Coached

I help early-stage founders launch, grow, and lead with clarity. I cut through the noise to the few tactics that actually change your numbers. I've coached 300+ founders across validation, growth, leadership, and fundraising.

Join The Sauce.

Weekly tactics to grow, lead, and build your startup without the fluff.

Get The Sauce, my weekly newsletter for founders. Unsubscribe anytime.

Confirm your email to start receiving The Sauce. Unsubscribe at any time.

One useful founder lesson each week.

Built something worth Scaling?

Book Your Free Strategy Call