How to know a micro product will sell before you build it

A $27 template, built over a weekend, can earn more in its first week than a lot of people make from a "real" launch that took them four months. The gap isn't talent. It's that most people spend their limited creation time building the wrong thing, because they skipped the one step that would have told them which thing to build.

The instinct to skip that step is understandable. Validation feels like the thing standing between you and actually making something, and a micro product is small enough that "just build it and see" feels like a reasonable shortcut. It's the shortcut that produces most of the templates and mini-courses nobody buys.

Create Micro Products is upfront about why this happens: 42% of startups fail primarily because they built something nobody wanted, according to the CB Insights figure it cites. For a $500 product built in a weekend, that failure rate is a bad Saturday. For a micro product line meant to fund your bigger offers, it's a habit worth breaking early.

The three-filter test, and the 7-day validation sequence

The book's ideation process starts with mining what it calls the voice-of-customer spreadsheet: exact phrases pulled from support tickets, community threads, and consultation questions, rather than problems you assume people have. Frequency matters (the same complaint showing up across multiple channels), but so does intensity: the book flags language like "I'm desperate for" or "this keeps me up at night" as the tell that someone will actually pay to make a problem go away, as opposed to merely being mildly annoyed by it.

Once you have a shortlist of pain points, the book runs each through a three-filter test before anyone touches a design tool:

1. Urgency: how soon does this need solving? Problems on a deadline convert faster than problems people plan to get to eventually.
2. Impact: how much does solving it matter? Higher-impact problems support higher prices and stronger motivation to act.
3. Solvability: can you actually build a focused fix quickly? The best micro product ideas are narrow enough to finish in days, not months.

From there, the companion checklist, Micro Product Validation, lays out a 7-day sequence that escalates commitment at each step: pain-point research and scoring on days 1-2, trend and competitor checks on days 3-4, a single-question poll and a "coming soon" landing page on day 5, and (the step most people skip) actual pre-selling with a founder's discount on days 6-7. The book's own bar for proceeding is a 30% waitlist-to-sale conversion rate; below that, it treats the result as a signal to pivot the concept rather than push forward on hope.

The book makes the case with a specific number. A freelance copywriter validated and launched a $19 "High-Converting Email Subject Line Swipe File," sold 500 copies in three weeks for $9,500, then later launched a $499 course to that same list: 75 of those micro product buyers upgraded, adding another $37,425. The small product didn't just make money on its own; it built a list of people who'd already paid once and were more likely to pay again.

Where people go wrong

The most common mistake is building first and validating never: sinking a weekend into a template or workshop based on a hunch, then discovering the audience was lukewarm all along. The 7-day sequence exists precisely to catch this before the time is spent, not after.

A second mistake is stopping at the landing page. A "coming soon" page with an email signup measures curiosity, not willingness to pay, and the book is specific that only actual pre-sales, real money changing hands before the product exists, count as validation. Interest and payment are different signals, and treating the first as proof of the second is how people end up building for an audience that admires the idea but doesn't buy it.

The third is picking a vague, generally-annoying problem instead of one that scores high on both frequency and intensity. "Email overwhelm" sounds like a real pain point until you dig in and find the actual complaint is narrower (a prioritization problem, not an inbox problem), which is exactly the kind of distinction the Business Foundations guide treats as the difference between a product that sells and one that doesn't.