You know that feeling when you’re sitting in a coffee shop at 6 AM, nursing your second espresso, and you realize your entire business model might be built on a faulty assumption? Yeah, that’s the moment most founders either pivot hard or double down on denial. The difference between the ones who survive and the ones who become cautionary tales often comes down to one thing: they actually understood their market before they started spending money.
Here’s the uncomfortable truth nobody wants to hear: most business failures aren’t because the idea was bad. They fail because founders skipped the foundational work of truly understanding who they’re selling to, what problems those people actually have, and whether they’re willing to pay to solve them. It’s not sexy. It doesn’t make for good startup mythology. But it’s the difference between building something real and building something that looks good in a pitch deck.
Let me walk you through how to do this right.
Start With Your Assumptions, Not Your Solution
Every founder walks into this with a list of beliefs about their market. Maybe you think small business owners are desperate for workflow automation. Maybe you believe Gen Z will pay premium prices for sustainable fashion. Maybe you’re convinced that remote teams need better async communication tools.
Here’s what I learned the hard way: your assumptions are usually wrong. Not completely wrong—but wrong enough to cost you serious money if you don’t interrogate them first.
Write down every assumption your business depends on. And I mean every one. Who’s your customer? What problem do they have? How much does that problem cost them? How do they currently solve it? Would they actually switch to your solution? How much would they pay? How would they find out about you?
Once you’ve written them down, rank them by risk. Which assumptions, if they’re wrong, would completely sink your business? Those go to the top of your investigation list. Because here’s the thing: you’re going to test these assumptions against reality, and reality is a lot cheaper than learning through a failed launch.
This connects directly to how you’ll approach talking to real people—because that’s where the rubber meets the road. Your assumptions are just stories you’re telling yourself until you validate them against actual human behavior.
Talk to Real People (Not Your Mom)
I’m going to be blunt: your mom thinks your idea is great. So does your best friend. Your co-founder definitely thinks it’s great, or they wouldn’t be working on it. But none of them are your customer, and their validation means approximately nothing.
You need to talk to actual people in your target market. Strangers. People who have no reason to be nice to you. Ideally, people who have a problem that needs solving right now, whether you exist or not.
Here’s how to do this without it feeling like a sales call (because it’s not—you’re researching):
- Find people with the problem: Cold email, LinkedIn messages, relevant Slack communities, Reddit, industry forums. Go where your potential customers actually hang out. If you’re building for SaaS founders, you’re not finding them at the golf course—you’re finding them on Indie Hackers or in startup Slack groups.
- Lead with curiosity, not a pitch: “Hey, I’m researching how marketing teams currently manage campaign workflows. I noticed you’re in that space—would you have 20 minutes for a quick conversation?” You’re asking for their knowledge, not their money.
- Ask about their current situation: How do they currently solve this problem? What’s frustrating about their current solution? What would an ideal solution look like? How much are they currently paying? How much would they be willing to pay if something significantly better existed?
- Listen more than you talk: The goal is to understand their world, not to convince them that your solution is brilliant. If you find yourself pitching, you’re doing it wrong.
- Talk to at least 20 people: You need enough conversations to spot patterns, not just anecdotes. One person saying something is interesting. Five people saying the same thing is a signal. Ten people saying it is validation.
According to the Small Business Administration, one of the leading reasons startups fail is lack of market research. And this is the market research. Not fancy reports from consulting firms. Just conversations with real humans who either do or don’t have the problem you think you’re solving.
Map Your Customer Journey Like You’re Planning a Heist
Once you understand who your customer is and what problem they have, you need to map out their entire journey. From the moment they realize they have a problem, all the way through to becoming a loyal customer (or not).
This isn’t theoretical. Sit down with your research notes and trace the path:
- Awareness: How do they discover they have a problem? Is it a sudden pain point or a slow realization? What triggers that awareness?
- Consideration: Once they know they have a problem, how do they start looking for solutions? Do they Google it? Ask their network? Check industry publications? This is where you figure out where you need to be visible.
- Evaluation: How do they evaluate different options? What criteria matter most to them? Price? Ease of use? Integration with existing tools? Social proof?
- Decision: What pushes them to actually buy? Is it a free trial? A conversation with a sales person? Watching a demo? Reviews from peers?
- Retention: After they buy, what determines whether they stick around or churn? What’s their onboarding experience like? Do they see value immediately?
Understanding this journey changes how you think about your entire business. You realize that a beautiful product doesn’t matter if nobody can find you during the consideration phase. You realize that a low price doesn’t matter if the onboarding is so bad that people give up before they see value. You realize that your positioning strategy needs to speak directly to how they think about their problem, not how you think about your solution.
This is also where you start thinking about your actual go-to-market strategy. Not as a theoretical exercise, but as a direct response to how your customers actually make decisions.
Validate the Money Part Early
Here’s where a lot of founders get squeamish: you need to know, before you build anything substantial, whether people will actually pay for this.
Not whether they like the idea. Whether they’ll exchange actual money for it.
There are a few ways to test this without building a full product:
- The presale approach: Create a landing page describing your solution. Drive traffic to it. Ask people to sign up for early access or put down a deposit. If nobody’s willing to pay anything, that’s valuable information.
- The concierge test: Manually solve the problem for a few customers. Charge them for it. Does the unit economics work? Are they happy enough to keep paying? This gives you real revenue and real feedback before you build software.
- The survey approach: Ask directly: “If a product like this existed and cost $X per month, would you buy it?” People will lie here sometimes, but combined with other signals, it’s useful.
- The waitlist with commitment: Some founders ask early users to commit to a specific price point when the product launches. This is stronger than a generic “I’m interested” email.
The key insight is this: if you can’t get people to pay for a solution to their problem before you’ve built a polished product, you probably shouldn’t build that product. The market is telling you something.
Y Combinator founder advice consistently emphasizes this point—the founders who make it are the ones who validate demand before they commit to a specific technical solution. They’re willing to pivot the solution if the market wants something different, but they don’t pivot the customer or the problem.
Identify Your Competitive Landscape
“We don’t really have competitors” is something I hear from founders about once a week, and it’s always wrong. If you’re solving a real problem, there are already solutions out there. Maybe they’re not perfect solutions. Maybe they’re more expensive or harder to use. But they exist.
Your job is to understand them deeply:
- Direct competitors: Who else is building exactly what you’re building? What are they doing well? Where are they falling short?
- Indirect competitors: How are customers currently solving this problem? Maybe it’s a competing product. Maybe it’s a manual process. Maybe it’s spreadsheets and email. Understanding the current state matters.
- Substitute solutions: Are there other ways to achieve the same outcome? Someone might solve their workflow problem with a different tool entirely. You need to understand why they might choose that instead of your solution.
When you talk to potential customers, ask them specifically: “How are you currently solving this? What products or approaches have you tried?” Their answer tells you what you’re really competing against. It’s usually not the obvious competitor you found on Google—it’s the status quo, or a half-decent existing solution that’s “good enough.”
Understanding your competition isn’t about copying them or matching them feature-for-feature. It’s about understanding why customers would choose them over you, so you can either differentiate meaningfully or pick a different market where you have a real advantage.
Build Your Positioning Strategy
Once you’ve done all this research, you can actually build a positioning strategy that resonates with real customers instead of sounding like generic marketing copy.
Positioning is about answering these questions clearly:
- For whom: Specifically, who is this for? “Small business owners” is too broad. “E-commerce businesses doing $500K–$5M in annual revenue, managing inventory across multiple channels” is positioning.
- What problem: What specific problem are you solving? Not “making work easier.” What actual pain point are you addressing?
- Why you: Why should they trust you to solve this? What’s your unfair advantage? Is it the team’s background? A novel approach? Deep industry knowledge?
- Against what: What are the alternatives, and why is your approach better for your specific customer?
Your positioning statement doesn’t need to be public. It’s internal clarity. It’s the filter you use to make every decision about your product, marketing, and sales. It’s why you say yes to certain customer requests and no to others. It’s why you don’t build features that don’t serve your specific customer.
This flows directly from your customer journey map and your competitive analysis. It’s the synthesis of all the research you’ve done.
Harvard Business Review has written extensively about how positioning is the single most important strategic decision a company makes—and yet most founders skip it entirely, jumping straight to building.
Test Before You Scale
This is where most of the learning happens. You’ve validated your assumptions. You’ve talked to customers. You have a positioning strategy. Now you test everything at a small scale before you bet the farm.
This might mean:
- Running a small beta with 20–50 customers before a full launch
- Testing different messaging on small cohorts before your big marketing push
- Selling to early customers with a manual process before you automate it
- Trying different channels to reach customers (cold email, content marketing, partnerships, ads) and seeing which actually works
- Measuring retention and satisfaction obsessively—if customers are churning quickly or complaining about the same things, that’s data you need to act on
The goal isn’t perfection. The goal is learning. Every test that fails is information that saves you from a bigger failure later. Every test that works is a signal that you’re on to something real.
And here’s the thing: your market understanding isn’t static. It evolves. Customers’ needs change. Competitors emerge. Your product gets better and attracts different customers. You keep talking to customers, keep testing, keep adjusting your strategy based on what you’re learning.
The founders who win are the ones who understand that market research isn’t a box you check before you start building. It’s something you do continuously, throughout the life of your business. It’s how you stay relevant. It’s how you avoid becoming obsolete. It’s how you build something people actually want.
FAQ
How many customer conversations do I need before I start building?
There’s no magic number, but I’d say 15–20 conversations where you’re asking good questions and actually listening. You should start seeing patterns emerge—the same problems, the same frustrations, the same desires. If you’re only hearing one unique take per conversation, keep going. If three conversations in a row are saying similar things, you’ve probably got a signal.
What if my research shows the market doesn’t want what I’m building?
That’s the whole point. Better to learn that before you’ve spent six months and $100K building it. You pivot. You talk to a different customer segment. You solve a different problem. Or you decide this isn’t the right market for you and you move on to something else. All of these are wins because you’re not wasting resources on something that won’t work.
Should I do market research if I’m bootstrapping with limited time?
Absolutely yes. This is actually where bootstrappers have an advantage—you can’t afford to waste time and money on something nobody wants. Your constraints force you to do the research properly. A few hours of conversations will save you hundreds of hours of wasted building.
How do I know if my positioning is actually working?
Your customers will tell you. If your messaging resonates, they’ll repeat it back to you. They’ll say “Oh, you’re the tool for [specific problem] for [specific customer type].” If your messaging is off, they’ll either be confused or they’ll explain what you actually do in different terms. Listen to how they describe your solution—that’s often closer to the truth than how you’re describing it.
Can I do this research while I’m already running a business?
Yes, and you should. Even if you’ve already launched, the principles apply. Keep talking to customers. Keep testing new positioning. Keep looking at your competitive landscape. Keep validating assumptions. The businesses that stay relevant are the ones that never stop doing this work.
