He Built It in 9 Days and Got Zero Signups. Here's What the Canvas Would Have Found.
Jack is a consultant in Denmark. Late 2025, he noticed he was spending 45 minutes after every client call formatting his notes into something he could actually send. So he built a tool. Nine days, $200 in Bolt credits, a React frontend, Stripe for payments.
December 22nd, he posted to Hacker News: "ClearNoteLab - Turn meeting notes into client-ready PDFs in 30 seconds."
Results after four hours: 1 point (his own upvote). 0 comments. 0 signups.
He wrote a post-mortem on Indie Hackers. His diagnosis: bad timing (three days before Christmas), no social proof (landing page trust score 4/10), no audience (zero Twitter followers, zero email subscribers).
He's not wrong about any of that. But he's doing autopsy on the wrong body.
The diagnosis that stops too early
When a launch fails, founders reach for the obvious explanations. Timing. Marketing. Distribution. These feel like the problem because they're visible. The silence comes right after launch, so launch must be where things went wrong.
The silence was decided weeks earlier. Maybe months.
Jack's three launch mistakes were real. Fix all three and he might get 20 signups instead of zero. But here's the question none of that addresses: would any of those 20 have paid $12 a month?
That's a different problem. It's the one that actually kills products.
What the Canvas finds in the customer segment cell
The Pre-Validation Canvas has a cell called Customer Segment. Not "who has the problem" - that's too easy. It asks: who feels the problem acutely enough to pay to make it go away, and what does that person look like specifically?
Jack's answer was "consultants." There are several million consultants in the world. That's not a segment, that's a census category.
Consultants who routinely create formal documentation for clients. Solo operators, not big firms with ops teams. People whose client relationships require polished deliverables. Consultants who already trust AI tools with client-facing work. That's starting to get somewhere.
How many of those people are there? Where do they gather online? Do they already have a workflow for this, even if it's clunky? Would they switch to a $12/month subscription, or would their billing process make that impossible?
Jack never asked these questions. He validated the problem on himself, which is the most common mistake in indie products. Your own pain is real. It doesn't tell you whether the market exists.
The trigger cell that would have caught this earlier
There's another cell: Trigger. It asks what makes someone decide, specifically today, that they need to solve this problem.
This matters more than whether the problem exists. Problems exist everywhere. Triggers are rare.
For ClearNoteLab, the trigger question is: what moment makes a consultant think "I need to fix my documentation workflow right now"? Is it landing a big new client? Getting negative feedback on deliverables? Starting a new engagement? Preparing for a quarterly review?
If you can't name the trigger, you can't find the customer. They're not searching for your product because they're not in the moment when they'd need it. They have the problem every week, but it's low enough grade that they live with it. That's not a buying trigger. That's background noise.
This is why Jack had zero signups even from people who saw his HN post and had the exact problem he described. They recognized it, maybe nodded, and scrolled past. They weren't in the moment. They'd fix it someday.
The channel question he skipped
Jack's right that he had no audience. But framing this as a marketing problem he could have solved with more Twitter followers misses something.
The Canvas has a Channel cell. It asks: how does the customer currently find solutions to this problem, and can you meet them there?
Consultants with documentation problems aren't searching for "meeting notes to PDF tool." They're searching for a ChatGPT prompt to clean up client notes. They're asking in Slack communities for freelancers. They're checking the apps they already use - Notion, Otter, Fireflies - to see if there's a formatting feature.
That means the channel isn't Hacker News. It's those Slack communities. It's direct messages to consultants in his own network, one at a time. It's cold outreach to twenty people who fit the exact profile with a free offer in exchange for a conversation.
He never did any of that pre-launch. He built, then tried to market. The Canvas makes you do this in the opposite order: find the channel first, because if you can't find five people who will talk to you before you build, you definitely won't find a hundred who will pay after.
The 9-day build is the trap, not the solution
Jack's post-mortem includes this line: "Building is easy now. Distribution is the real work."
Mostly right. But the framing still misses something. Distribution is how you reach customers. Validation is how you confirm they exist before you spend nine days building for them.
The tools that made it possible to build ClearNoteLab in nine days are genuinely impressive. Using them isn't the mistake. But they've made a specific trap worse. When building takes nine days instead of nine months, skipping validation feels nearly costless. You'll just build it and see.
The problem is that nine days of building still costs something. Not just the $200 in Bolt credits. It costs you your framing. Once the product exists, you stop asking "should I build this?" and start asking "how do I market this?" The build-first sequence closes off the question you should have been asking all along.
Jack's real mistake wasn't December 22nd. It was October, when he decided that his own pain was proof enough that others had it too.
What a 20-minute Canvas session would have surfaced
This isn't speculation. The Pre-Validation Canvas is a structured set of questions that catches exactly these gaps before you commit to building.
Run Jack's idea through the Canvas: the customer segment narrows from "consultants" to a specific profile you can actually find. The trigger question reveals the problem is low-urgency for most people in that group. The channel question forces a reckoning: he had no existing access to this audience. The willingness-to-pay question never gets answered, because you can't answer it without finding a real customer first.
Twenty minutes. Not after nine days of building. Before.
That's the difference between launching into silence and having a real shot at knowing before you ship.
Jack's story isn't unusual. It's almost standard. The honesty in his post-mortem is rarer than the failure. Most people in his position either never write it, or blame something external.
He built something real. He just built it before he confirmed anyone was waiting for it.
The Pre-Validation Canvas walks you through the questions Jack didn't ask, before you write a single line of code. Built on 250+ real startup validations. Start here for $9.