Readiness report

ShipCheck

ALMOST

Strong product thinking with a few gaps. Fix the RED items - you are close.

Overall insight

The product thinking on user definition and problem clarity is strong and specific. The critical gap is distribution - the current plan names channels but not sequences, people, or messages. A product about product thinking needs a distribution plan that demonstrates product thinking. Fix that section and this is ready.

Question 15

Who are the first 10 users, and how exactly will you reach each of them?

RED

Post to Mind the Product Slack #building channel. Tweet to Build in Public community. Share in Lenny's Newsletter Slack. DM 5 PM friends who are actively building side projects with a personal ask.

This names four channels but does not specify sequence, message, or named contacts. Post to MTP Slack and tweet to Build in Public are intentions, not a plan. For a developer tool at MVP stage, distribution needs to start with direct personal outreach before public posting.

Next step: Write the exact DM message you will send to 5 specific people this week.

Question 18

What is your Day 7 retention plan - what brings a user back after their first session?

RED

ShipCheck is deliberately one-shot per project. Users return when they start a new project. There is no artificial retention mechanic - return visits reflect genuine new building activity.

Accepting that a tool is one-shot is honest, but users return when they start a new project is not a retention plan. For a developer tool, the lack of any re-engagement mechanism means growth relies entirely on word of mouth from first-time users.

Next step: Identify one concrete touchpoint that brings a user back for their second project.

Question 9

On a scale of 1-10, how urgent is this problem for your user - where 10 means they are actively searching for a solution right now?

AMBER

6. They are not searching for this product by name. But when shown it, the recognition is instant and the use is immediate. The urgency is latent - it becomes acute the moment they try it.

The honesty of latent urgency is right. But for a developer tool targeting builders, a 6 is a positioning problem: if users are not searching for this, distribution must create demand rather than capture it.

Question 19

What is the single metric that tells you, unambiguously, whether your product is working?

AMBER

Wizard completion rate: the percentage of users who start question 1 and submit all 20. Below 60% means the friction is too high somewhere. Novus drop-off data tells us exactly where.

Completion rate is the right north star for a wizard-based product. The 60% threshold is a reasonable hypothesis. What is missing is a secondary metric for whether completing the wizard led to behavior change.

Question 1

Describe your target user in one sentence - job title, context, and the one thing they care most about.

GREEN

A solo builder or PM who has an idea or MVP and is about to ship - and has not yet been forced to articulate the uncomfortable basics: who it is for, whether the problem is real, and whether anyone will find it.

Specific role, specific moment, specific psychological state: has not yet been forced. This user definition would survive a research interview. The framing makes the product value proposition self-evident without needing an explanation.

Question 3

What does your user do today instead of using your product?

GREEN

They ship anyway. They move from idea to build without the middle step. The alternative to ShipCheck is not another tool - it is nothing, and shipping with nothing is the default behavior of 90% of builders.

Naming nothing as the real alternative is the most insightful answer in this section. It correctly identifies that the competitive threat is default behavior, not another app. That framing has direct implications for messaging and distribution.

Question 11

Can a complete stranger land on your URL right now and get value without reading any documentation?

GREEN

Yes. One headline, one button: Check your product. No signup. No documentation. You are answering question 1 within 30 seconds of landing.

This answer demonstrates product maturity because it says what a stranger can do without documentation. The specific 30 seconds to question 1 detail shows the first-use path has been measured.

Question 20

What does your Novus / analytics data show about how users actually behave vs. how you expected them to behave?

GREEN

Novus showed 43% of users dropped off at question 12 - what would a user have to believe is true to find your product valuable? The subtext was too abstract. We rewrote it with a concrete example. Drop-off at that question fell from 43% to 21%.

This is the strongest answer in the report. It names a specific metric, a specific question, a specific intervention, and a specific result. This is what product thinking with behavioral data looks like.