The standard advice on customer research assumes you have customers. You don't. You have an idea, ten browser tabs of half-written notes, and a Stripe account waiting for the first dollar. The frameworks built for product teams at funded SaaS companies don't work in this state. They are too slow, too dependent on access to users you haven't earned yet, and too willing to mistake politeness for signal.
This is the playbook I wish someone had handed me two startups ago.
Stop running surveys before you have a hypothesis
Surveys feel productive. They produce numbers. The numbers are mostly meaningless. Three reasons.
First, recall bias. Ask "how do you currently solve X" and you get the polished story your respondent thinks makes them sound competent. Ask "what did you do last Tuesday at 4pm when you hit X" and you get reality. Surveys default to the first form because it's easier to write.
Second, courtesy bias. People answering a founder's survey want to be helpful. They will rate your idea higher than they actually feel because they don't want to crush your dreams. Their wallet is honest. Their survey response isn't.
Third, n. Five responses can't tell you anything about a market. Fifty responses still can't tell you whether the people answering are the people who would pay. Surveys feel like data and aren't.
Use surveys after you have a hypothesis to test, not before. The hypothesis comes from listening.
The listening pass
Before you talk to anyone, read what they already wrote.
The phrase someone in your audience types into Reddit at 2am, the comment they leave under a competitor's YouTube review, the TikTok caption asking "how do I solve X". Those are voice-of-customer data with no courtesy bias and no recall bias. They wrote it because they had the problem at the moment of writing.
For one product idea, 30 minutes of structured reading produces more useful customer research than three weeks of survey design. The catch is that it's structured. Random Reddit scrolling teaches nothing. The structure has three steps.
Step 1: pick the phrasing your audience would type
Most founders skip this step and start searching their own product description. Wrong direction. Your audience doesn't search "AI-powered productivity tool." They search "I keep dropping commitments" or "every week I lose track of my todos."
To find the right phrasing, write down five sentences that describe the problem from your audience's perspective, in their own words. Strip out your product. Strip out category language. Just the problem.
Example. If you're building a calendar app for solo founders, the problem phrases are "I forget to follow up", "my schedule is a mess this week", "I keep double-booking myself", "I can't remember when I told someone I'd do something." Search those phrases on Reddit, X and YouTube. The results are your audience in the moment.
Step 2: capture 25 examples in their own words
For each search, save the exact phrase the person used, plus the platform, the date, and one constraint they mentioned (time, money, alternative they tried). After 25 records you have enough to see patterns.
What you're looking for: repeating language, repeating constraints, repeating workarounds. If 18 of 25 people say "I tried X and it didn't work because Y" then "Y" is the wedge for your positioning. If 22 of 25 people describe the problem in financial terms, you sell to a CFO not an end user. The patterns rarely match the persona doc you would have written from your desk.
Step 3: turn patterns into copy
The output of customer research isn't a 40-slide persona deck. It's three things you do differently next week.
One: the headline on your landing page. Use the exact phrasing your audience used. Not your version. Theirs.
Two: the audience for your first ad campaign. Not "founders 25-45." The subreddit, the keyword, the YouTube channel where you saw the highest concentration of the problem.
Three: the question you'll ask the first 5 customer interviews. Not "what features would you want?" That's the worst question in product research. Better: "tell me about the last time the problem hit." Then shut up and let them describe it.
How to do customer research for a SaaS startup specifically
SaaS founders have one advantage and one disadvantage. The advantage: your audience is online and posting about their work. The disadvantage: every other SaaS founder is reading the same Reddit threads, and the obvious subs are saturated.
Two adjustments. First, go narrower than the obvious subs. r/SaaS is too crowded. r/microsaas, r/EntrepreneurRideAlong, r/buildinpublic and the niche-specific subs (r/Entrepreneur for the broad pool, r/devops for technical audiences, r/marketing for marketers) have less competition and more honest posts.
Second, follow the platform mix. The same person who posts "is anyone using X" on Reddit might post "X just doesn't fit my workflow" on X. The combined picture is sharper than either platform alone. This is the mistake most customer research playbooks make: they pick one platform and miss 60 percent of the signal.
The interview, after listening
Once you have 25 records and a hypothesis, then run interviews. Not before. The interviews aren't for discovery; they're for validation.
The Mom Test rules apply. Ask about past behavior, not future intent. Talk less than the interviewee. Don't pitch. Don't validate your idea. Validate the problem. If the interviewee can't describe a recent moment when the problem hurt, the problem isn't real for them. Move on.
Five interviews structured this way teach you more than 50 unstructured ones. The pattern of "yes the problem is real, here's how I worked around it, here's why my workaround sucks" repeats fast when the problem is real. When it doesn't repeat, you don't have a problem worth solving.
Tools that help
Most of this is reading and writing. The bottleneck is the listening pass: searching across Reddit, X, Bluesky, LinkedIn, and YouTube manually takes a Saturday. Gorilla automates the search side: paste the problem, get 20+ phrasings, hit five platforms in parallel, ranked by intent. The output is the 25 records you'd otherwise spend a weekend collecting. From there it's still on you to read carefully and write down the patterns.
For interviews, dovetail.com or read.ai handle transcripts. Don't pay for those until you've listened first.
What to do this week
- Pick one product hypothesis. One.
- Write five audience-language phrases for the problem.
- Run those phrases through one search round (manual or via a tool).
- Save 25 records with phrase + platform + constraint.
- Look at the records together. Write down the three patterns that repeat most.
- Rewrite your landing-page hero using one of those exact phrases.
Six steps, two hours of work, one real piece of customer research. More useful than a quarter of survey theater.
Related reads: