The unfiltered FAQ continues. After the intense 'Why are you building this?' session last week, the most urgent questions I heard from early-stage teams revolved around the next critical step: Validation.
Founders, we’re wired to build. We see a problem and immediately want to ship the solution. But the biggest killer of early-stage startups isn't competition or a lack of funding; it's wasted time building a product nobody needs.
Here are five real questions every early-stage founder faces (but might hesitate to ask out loud) from the past week:
Q: Should I build an MVP or validate first?
A: Validate first. Always.
I've burned months building features nobody asked for because I thought I knew better than the market. (Spoiler: I didn't.) Your MVP isn't code. Your MVP is a conversation.
Here's what validation looks like in week one:
10 customer interviews (more on this below).
1 landing page describing the solution.
1 Google Form collecting early interest.
If 50+ people sign up for a waitlist without you having built anything? Build. If 5 people sign up and 3 of them are your college friends being polite? Keep validating.
The brutal truth: if you can't get people excited about a description of your solution, you definitely can't get them excited about the actual solution. Save yourself the pain. Talk to humans before you talk to code.
Q: How do I find my first 10 customers to interview?
A: Start with your network. Yes, even if your network "isn't in your target market."
Your network knows people. And those people know people.
However, Do the homework first. Then ask. Many founders jump straight to "can you intro me?" That's why people ghost.
Instead, go deep on one person: research their company's recent news, their role evolution, and the obvious pain in their world. Then, reach out with specificity:
"Hey [Name], I was reading about [Company]'s recent pivot into [X]. I noticed you're now leading [function]. I'm exploring how teams are tackling [specific challenge related to their new focus] and would love 20 mins of your first-hand perspective. No pitch—just genuine curiosity about your experience."
You're not asking them to find the connection—you found it. You're asking for help on a challenge they've experienced. Most people are willing to share a bit of their time if it isn't a sales pitch.
If your network genuinely has zero overlap? Join the communities where your customers hang out: LinkedIn groups, Slack communities, or industry forums. Post a thoughtful question. Build rapport. Then DM: "Mind if I pick your brain on this?" You're not selling. You're learning. That shifts everything.
Q: What questions should I ask in customer interviews?
A: Don't ask what they want. Ask what they do.
People are terrible at predicting their own behavior. They'll tell you they'd pay $100/month for your tool, then ghost you when you send the invoice.
Instead, ask about past behavior and current pain:
"Walk me through the last time you faced [problem]."
"What did you try? Why didn't it work?"
"How much time did that cost you?"
"Who else needs to sign off on a solution?"
You're mining for pain intensity, current workarounds, and willingness to pay.
The golden question: "If I built this, would you be my first customer?" If they hesitate, you haven't found product-market fit yet.
Q: How do I know when to stop validating and start building?
A: When the same problem shows up in 10 different conversations, and you can describe the solution in one sentence.
Validation isn't infinite. At some point, you're just procrastinating.
Here's my rule: If you've talked to 30 people and you still can't clearly articulate:
The specific problem
Who has it
How you'll solve it
Why they'll pay
...you're not ready to build.
But if you can answer those four, and you've got 10+ people saying "I'd buy this today," stop talking and start shipping.
Think of it like a racer in the pit lane: you don't want to wait forever or you'll lose the race. But you also don't want to leave too early without your tires on—that’s the surest way to get dragged back in. It's about finding when you have just enough signals to GO. The real validation happens when someone hands you money. Everything before that is just theory.
Q: I'm a solo founder. Is that a red flag?
A: Only if you treat it like one.
I've worked with both solo founders and co-founder teams. The solo founders who struggled weren't struggling because they were alone—they were struggling because they tried to do everything themselves.
Solo doesn't mean isolated.
Here's what worked for me:
Advisor network: 2-3 people I could text at 11 PM when I hit a wall.
Fractional help: Contractors for design, dev, or operations—whatever wasn't my zone of genius.
Founder communities: Regular check-ins with other solo founders who got it.
Yes, co-founders can split the load. But they also split equity, decision-making speed, and sometimes, the company itself. The question isn't "Should I find a co-founder?" It's "Can I build the support structure I need to win?" If yes, you're fine.
Stuck on something? Let's chat.
I offer 30-minute, no-BS sessions for early-stage founders needing clarity or fresh perspective. Bring your biggest blocker — leave with practical next steps. Happy to help find synergies in my network too.
Book a slot: https://lnkd.in/gVU35F77