After ~15 products built with the same landing page, auth, payments and support setup, he spent about a week gathering that code with basic docs and released it as ShipFast.
When it applies: developers who have shipped many similar products
When a big account tweets about a widespread problem (founders faking revenue), build the small tool that settles it (a board of Stripe-verified revenues), then let it grow into a bigger product.
When it applies: you follow large accounts in your niche
He noticed he checked Plausible for traffic and Stripe for payments; DataFast = traffic analytics + revenue, with revenue-per-source as the main metric. His MVP was a Plausible-style dashboard with Stripe revenue bolted on, built in a few weeks.
When it applies: Finding SaaS ideas from your own workflow
Choose must-have problems over nice-to-haves; he explicitly says to avoid note-taking apps and habit trackers unless you already have an audience.
When it applies: Idea selection, no existing audience
He says how launchable a product is is his entire focus; he ships a one-feature version of an idea rather than a full startup, so he doesn't spend a year building something nobody wants.
When it applies: solo makers shipping many small products
He used AI to help analyze and craft tweets for his agency's X marketing, noticed tools like Tweet Hunter hadn't integrated AI, and built that, treating existing paid competitors as validation.
When it applies: idea stage
He used early GPT-3 to cluster and categorize viral tweets into a startup-tweet library viewed in a CLI, used it to post, then launched a single search-bar feature on Twitter and Reddit.
When it applies: you're a heavy user of a channel
Per the article, ByeDispute came from his own Stripe ban over a chargeback, and ZenVoice from spending over $2,000 on Stripe PDF invoices: each product fixes a pain he personally paid for.
When it applies: solo makers
Either use deep industry experience to spot broken processes insiders accept as normal (Loom, SpaceX examples) or run a repeatable generate-and-test process; don't build what you saw trending.
When it applies: idea selection
He thought creator-brand matching was saturated back in 2015, then noticed a newer player (Passionfruit) doing well with ready-to-book sponsorship packages for creators; he suggests flipping it into a sponsorship page for brands.
When it applies: idea stage
Go through your own subscriptions, pick one, and build a narrower version that fits your specific situation; others likely share your odd use case.
When it applies: idea stage
Keep a running list of ideas sourced from places people voice unmet needs: Reddit questions, feature-request boards for Shopify/Webflow, the Chrome extension store, 3-star reviews of popular Amazon products, and app store complaints.
When it applies: pre-idea, solo builders without deep industry knowledge
Match the idea to your skills, interests, long-term staying power and natural marketing style (SEO, content, ads or 1-1 sales); a product that depends on writing or SEO will drain you if you hate those.
When it applies: idea selection
Being the 10th-100th AI profile picture generator or scheduler gets ignored by both algorithms and people. Take what worked and make it weird or different so it has novelty.
When it applies: Choosing what to build next