Module 2, Lesson 2: Reviewing Your Market Research

Where We Are in the Course

We're on Module 2, Lesson 2. Here's the trail so far:

Module 1, Lesson 1: What You'll Need — tools, accounts, all set up
Module 1, Lesson 2: Understanding the Process — the seven-step pipeline from research to shipped code
Module 2, Lesson 1: Market Research — running Claude's Deep Research to generate your market analysis

In this lesson, I'm picking up directly from the research document Claude produced in Module 2, Lesson 1. We've got the AI's output — now I'm going to show you how I actually go through it, pressure-test it, and fill in the gaps Claude can't fill for you.

ℹ️

No corrections or updates to previous lessons. If you haven't done Module 2, Lesson 1 yet, do that first — this lesson won't make as much sense without a research document to work from.

Before We Start

Here's what I'd expect you to have in place before this lesson:

From previous lessons:

You should have your market research document from Module 2, Lesson 1 — Claude's Deep Research output, saved to Obsidian (or wherever you keep your notes)
You understand what the seven-step pipeline is — this lesson is still in Step 1, the research phase, but we're doing the human half of it

Tools / setup you'll need:

Your notes tool (Obsidian or whatever you're using) — you'll be making notes in parallel as you review
A browser — you'll be visiting competitor websites and app stores directly
Access to iOS and/or Android app stores — for reading real reviews

By the end of this lesson, you'll:

Know how to review and verify AI research output — not just accept it at face value
Have spotted things in the market that Claude didn't catch
Have confirmed (or challenged) your go/no-go signal with your own eyes
Have a research document ready to carry into the documentation phase

About This Lesson

Duration: ~17 minutes video + ~30–60 minutes for your own review pass
Skill Level: Intermediate
What You'll Build: An augmented, human-verified research document — your real foundation before we start writing product docs

The previous lesson was about using Claude to do the heavy lifting on research. This one is about not being lazy. The AI is fast and thorough, but it doesn't have your intuition. It doesn't feel the product. It doesn't know what makes you angry as a user. That's what this lesson is for.

Watch the Lesson

ℹ️

How I'd suggest going through this: Watch the video first without stopping — just get the big picture. Then come back here and work through the guide section by section. After that, this guide is your reference — you shouldn't need to rewatch to look something up.

What We're Covering

Here's what I'm walking you through in this lesson:

Why you can't just trust the AI output — what Claude gets right, what it misses, and why your own eyes matter
How to review competitor products properly — websites, app stores, and the reviews that actually tell you what's happening
Reading app store reviews like a researcher — where the real customer pain lives
Identifying your white space — the gap in the market that nobody's filling well yet
Confirming your go/no-go signal — using what you've found to make an honest call before you invest more

1. Let's Set the Scene (~0:00)

If you've done Module 2, Lesson 1, you've got a research document sitting in Obsidian. Claude produced it. It probably looks impressive — structured, comprehensive, full of data points and competitor summaries.

Here's the thing: I don't just hand that to myself and move on. The AI did the first pass, but I still have to go and confirm it with my own eyes. This is the lesson where I show you how I do that.

For my app — a co-parenting expense and communication platform — I'm reviewing what Claude found and then going to the actual competitor websites and App Store listings myself. Pulling up reviews. Reading what real customers are saying. Noticing things that aren't in the report.

This is not optional. If you're serious about building something people will pay for, you have to invest yourself into the heads of your future customers. That takes more than reading a summary.

2. The Core Idea

2.1 AI Research Is the First Draft, Not the Final Answer

Claude's Deep Research is genuinely impressive. It browses, synthesises, and structures information at a scale and speed you can't match manually. That's why we use it.

But there are things it can't do. It can't download an app and actually use it. It can't read a one-star review and feel the frustration. It can't notice that a competitor's branding inadvertently alienates the exact people they're trying to serve. Those things require a human being — which is you.

The way I think about it: Claude gives me the map. I still have to walk the territory.

ℹ️

This is the part of the process where your judgment and intuition become a real competitive advantage. Two founders can run the same Claude research prompt and get the same output. What they do with it next is where they diverge.

2.2 You're Not Reinventing the Research — You're Pressure-Testing It

This isn't about redoing what Claude already did. It's about three things:

Confirming what Claude said is actually true
Catching what Claude missed — the subtle stuff that only surfaces when you look with your own eyes
Adding your own read — what does this market feel like? What does the messaging tell you about who these products are really for?

You're not going deep on everything. You're spot-checking the important claims and then digging into the places that matter most for your specific angle.

2.3 How This Connects to Module 2, Lesson 1 - Market Research

In Module 2, Lesson 1, the output was the research document — a structured summary of the market. That document is the input to this lesson. You're not starting fresh; you're building on top of it.

By the end of this lesson, that document should have your notes on it. Things you confirmed, things you questioned, things you found that weren't in there. The more honest that document is, the better everything downstream will be — because your product docs, your specs, and your roadmap all trace back to this.

3. Let Me Show You How It Works (~1:00)

3.1 Set Up Your Review Session

Open two things side by side:

Your AI research document in Obsidian (or wherever you saved it)
A fresh note where you'll capture your own observations

💡

In Obsidian, you can drag a tab to split the view — put the Claude research on one side and your notes on the other. It makes the back-and-forth much easier during your review pass.

You're not going to read every word of the research linearly. You're looking for the key claims — particularly around competitors — and then going to verify them directly.

3.2 Start With the Biggest Player in Your Space

Claude should have told you who the dominant player in your market is. That's your first stop.

Go to their website. Look at:

What they're leading with — what's on the homepage hero? What's the main promise?
What features they're pushing — especially anything new or highlighted
How they're positioned — premium? Accessible? Court-focused? Consumer?
What they're not talking about — sometimes the most revealing thing is what a competitor isn't saying

For my app, the biggest player is OurFamilyWizard. They have nearly 80,000 ratings on iOS with a 4.5-star average. On Android it's 4.2 stars. On the surface, they look like people love them. But that's the surface.

3.3 Go Where the Real Reviews Live

App Store and Play Store ratings tell you one story. Third-party review platforms tell you another.

Claude flagged a site called Smart Customers (an app review aggregator) where OurFamilyWizard has a 1.3-star rating. That's a very different picture from their App Store 4.5. I went and confirmed it — and yes, the reviews there are brutal. Complaints about customer service, things not working, pricing, data portability.

This is gold. This is your competitors' customers telling you exactly what they hate — and what you should build differently.

💡

When you're reading reviews, you're not just looking for complaints. You're listening for the language people use. The specific words and phrases they reach for when something frustrates them — that's your future marketing copy. (We'll come back to this when we get to the GTM phase.)

3.4 Read App Store Reviews Like a Researcher

Download the apps if you can. At minimum, go through the App Store or Play Store listing and read recent reviews — especially the 1- and 2-star ones.

When I was going through the SupportPay App Store reviews, I found something Claude hadn't caught. There was a review from a user saying that the name of a competing app — CoParenter — was actually traumatising her, because the word "coparent" was tied to painful memories. That's the kind of subtle thing that never makes it into a research summary, but it's important.

It tells me: branding matters enormously in this space. The words you choose carry weight for people who are often going through one of the hardest periods of their lives.

That's not a feature — it's a product philosophy. And I wouldn't have known it if I hadn't taken the time to read reviews myself.

ℹ️

This is what I mean by "investing yourself into the heads of your future customers." These are people who will be paying you money. Read what they write. Feel what they feel. It will change how you build.

3.5 Notice What Everyone's Doing — That's Your Constraint and Your Signal

As I went through competitor after competitor, one thing became obvious: they are all mobile apps. Not websites. Mobile apps first.

Claude's research didn't call this out directly — but it's critical. It tells me that if I want to play in this market, I need to build for mobile. The market has already told me the delivery format that works.

This is one of the underrated benefits of having established competitors in your space. They've already spent the money figuring out what format works. You don't have to guess.

4. Finding Your White Space

White space is the gap in the market — the thing nobody is doing well, or at all. Your job in this review pass is to identify yours.

For my app, it became clear during the review:

Expense management is the biggest pain point in the co-parenting space
Nobody is doing it well — it's an afterthought for OurFamilyWizard, and the one app that was focused on it (UpClose) seems to have run into trouble since bumping their price
SupportPay has the deepest expense feature but has terrible UX and poor traction despite $9.4 million in funding

That's my white space. A focused, well-designed expense tracking experience for co-parents — built mobile-first, with court credibility, and better UX than anything that exists right now.

🔥

Your white space should come from the intersection of three things: (1) a real pain that customers are complaining about, (2) an area where competitors are weak or absent, and (3) something you can actually build well. If you've got all three, you're in business.

What If You Can't Find White Space?

If you've done a thorough review and you can't find a clear differentiation — stop.

Don't get emotionally attached to an idea that the market is telling you doesn't have a gap. Step back, go back to the research phase, and look at a different angle or a different market entirely. You have Claude now. Running another research pass costs you nothing except time, and it's much cheaper than building the wrong thing.

5. Confirming Your Go / No-Go Signal

At the end of your review pass, you should be able to answer these questions honestly:

Is the market real? Are there established players making money? (If nobody's making money here, why not?)
Is there a clear pain? Are customers of existing products vocally frustrated about something?
Is there a gap I can fill? Is there a specific angle nobody is executing well?
Do I have a believable path to customers? Is there a channel or community that could reach my early users?
Are the unit economics workable? If I charge X, can I acquire a customer for less than X and make the business survive?

For my app, the answers were: yes, yes, yes, yes, and yes. In fact the unit economics work out to a 5–15x return on acquisition cost — meaning if I spend $8 to get a customer, I can make $40–$120 back over their lifetime. That's a business worth building.

If your answers are mostly yes, keep going. If you're getting a lot of maybes or nos, that's important data — take it seriously.

⚠️

Don't skip the honest self-assessment. The purpose of all this research is to tell you the truth before you spend six months building something. A difficult truth now is a gift. An avoided truth now is a disaster later.

6. Watch Out For These

⚠️

Taking the AI output at face value.
Here's why this happens: the research looks comprehensive, so it feels complete.
The way I avoid it: I always go to at least the top 2–3 competitors directly, with my own eyes, before closing out the research phase.
If you've already done this: add a "manual review" section to your notes and fill it in now — it's not too late.

⚠️

Only reading the positive reviews.
Here's why this happens: it feels more encouraging.
The way I avoid it: I go straight to the 1- and 2-star reviews first. That's where the real product feedback lives.
If you've already done this: go back and read the negative reviews now. Make a note of the top 3 complaints that come up repeatedly.

⚠️

Falling in love with your idea instead of the evidence.
Here's why this happens: you've invested time, and the idea feels good.
The way I avoid it: I treat the go/no-go question as a real question with a real answer — not a formality I'm going through to confirm what I already decided.
If you're hitting this: be honest with yourself. If the evidence is thin, acknowledge that and either find better evidence or revisit the idea.

7. Practice

Exercise 1: Do Your Own Review Pass

What to do: Open your Claude research document from Module 2, Lesson 1. Create a fresh note for your own observations. Then visit each of the top 3 competitors Claude identified — their website, their App Store / Play Store listing, and at least one third-party review source. Write down what you confirm, what you question, and what Claude missed.

A nudge if you're stuck: Start with the biggest player. Just go to their website and spend 10 minutes reading it as a potential customer. What does it promise? What does it not mention? Does it feel trustworthy? Write that down.

How you'll know it's working: Your notes will have things in them that aren't in the Claude research. Observations, impressions, and at least one thing Claude didn't flag. That's the human layer added.

Exercise 2: Find Your White Space

What to do: Based on your review, write a single paragraph — in plain language — describing the gap you're going to fill. Not a mission statement, not a pitch. Just: "I noticed that no one is doing X well, and customers are clearly frustrated about it, and I think I can do it better by doing Y."

What this is practising: Clarity of positioning. If you can't write it in a paragraph, you don't understand it well enough yet. That's okay — that's what this exercise surfaces.

8. You Should Be Able to Do This Now

Here's what you can do with what we just covered:

Run a structured review of competitor products using websites, app stores, and third-party reviews
Identify the difference between what competitors claim and what their customers actually experience
Find the white space in your market — the gap nobody's filling well
Make an honest go/no-go call on your idea

Check Yourself

I've reviewed at least 2–3 competitors directly (not just via the Claude summary)
I've read real customer reviews — especially the negative ones
I've found at least one thing Claude's research didn't flag
I can describe my white space in a single paragraph
I've made an honest go/no-go call on my idea

✅

If you're ticking those boxes, you're done with the research phase. The next lesson is where we start turning everything we know into actual product documents. That's where it gets interesting.

If Something's Not Working

⚠️

I can't find clear white space in my market.
What's happening: Either the market is very well-served (possible, but rare), or you're looking at it too broadly.
How to fix it: Narrow your lens. Instead of "project management for teams," look at "project management for solo freelancers" or "for design agencies." The white space often lives in a niche, not the whole market. Go back to Claude and ask it to help you find an under-served segment.

The Short Version

Here's what I want you to walk away with:

Claude's research is the first draft, not the final answer: It's thorough and fast, but it needs a human pass to be complete.
The real customer insight is in the reviews: Not the star ratings — the actual written reviews, especially the negative ones. That's where you find what to build.
White space is your competitive advantage: Find the thing nobody's doing well and make that your focus. That's the game plan.
Make an honest go/no-go call: The whole point of the research phase is to tell you the truth before you commit. Don't skip it.

Resources

Tools Used

Obsidian — note-taking and knowledge management, used for storing and reviewing the research output
OurFamilyWizard — co-parenting app (competitor reference used in the lesson)
SupportPay — child support and expense tracking app (competitor reference used in the lesson)
Apple App Store — for reviewing app ratings and reading customer reviews
Google Play Store — same

Questions I Get Asked

Q: Do I really need to download competitor apps, or is reading their website enough?

If it's a mobile app and your app is also going to be mobile, yes — you should download it and actually use it. Even 10 minutes of hands-on time tells you things a website never will. You'll notice the UX friction, the onboarding flow, where it feels clunky. That's exactly what you want to know before you design your own.

Q: What if Claude's research and my review say different things?

Trust your own eyes. You went to the actual source — Claude synthesised from whatever it could access. If there's a conflict, note it in your research document and go with what you confirmed directly. The manual review exists precisely to catch these gaps.

Q: How long should I spend on the review pass?

Roughly 30–60 minutes for most markets. Don't let it become a week of analysis paralysis. You're looking for confirmation on the key claims and your white space — not an academic dissertation. Set a timer, go through your top 3 competitors, read the reviews, write your notes, and move on.

Q: How do I know I'm ready for the next lesson?

If you've ticked the checklist above and you can write your white space in a single paragraph — you're ready. Module 2, Lesson 3 is where we start writing the actual product documents. Everything you've gathered in the last two lessons feeds directly into that.

💬 Stuck? Come Talk to Us

💡

If something's not clicking or you want to share what you've built — come find us in Discord.
Build What Ships community → https://discord.gg/RFXRf9yg
Drop your question in the right channel. The community's active and I check in there too.

Glossary

White space: The gap in a market that nobody is filling well — or at all. Your white space is where you have a credible advantage over existing players. (introduced this lesson — Module 2, Lesson 2)

Go/no-go signal: The honest verdict at the end of your research phase — is this market worth investing in, given everything you've found? (introduced in Module 2, Lesson 1, confirmed this lesson)

MVP (Minimum Viable Product): The smallest version of your product that delivers real value to real customers. Not everything you want to build — the least you can build that still works. (introduced this lesson — Module 2, Lesson 2)

Unit economics: The math of your business at the individual customer level — what it costs to acquire one customer, and what that customer is worth to you over time. If you spend $8 to acquire a customer and they pay you $15/month for a year, your unit economics are very healthy. (introduced this lesson — Module 2, Lesson 2)

Third-party review platforms: Sites like Smart Customers, Trustpilot, or G2 where users leave reviews independently of the product's own App Store listing. Often more candid and critical than official store reviews. (introduced this lesson — Module 2, Lesson 2)