Nov 18, 2026
Two new cards today, 55 signals, and every single signal came from competitor_gap. Zero from any platform. That's a weird day — it means nothing new is launching or getting asked about, and everything interesting is happening in the gaps between existing tools. Fine by me, honestly. Gap-hunting is where the boring money lives.
The two ideas are basically siblings. Stripe billing boilerplate you ship in an hour scores 65, and Configuration generator for self-hosted billing systems scores 66. Both are "billing is hard, help me" products. But they're aimed at completely different wallets, and I think the score gap is backwards.
Let's start with the boilerplate one, because it's the one I'd be tempted to build and the one I'd probably regret. The pitch: founders get the product done and then lose three weeks wiring Stripe subscriptions, plan gating, and pricing experiments. True. Painfully true. I've lost that time myself. The monetization is a one-time $79–149 template with an optional $19/mo updates subscription, or a $9–29/mo hosted micro-service.
Here's my problem: this market is a graveyard of beautiful templates. There are maybe forty of them on GitHub right now, several free, several with more stars than your landing page will ever get. The people who get stuck on Stripe wiring are, by definition, the people who won't drop $149 to skip the wiring — they'll paste from a free repo and spend the three weeks anyway. The people who would pay are agencies shipping client work, and agencies want an invoice and a support contract, not a Gumroad checkout. The $19/mo updates tier is the real business and it's maybe a hundred subscribers at absolute best. That's real money but it's a $2k/mo ceiling and you're now maintaining a Stripe integration on someone else's release schedule forever. Stripe breaks things. You will be the one getting the angry email.
The self-hosted config generator is the sneakier, better one. Open-source billing engines — Lago, Kill Bill, the whole family — are genuinely powerful and genuinely miserable to adopt, because you have to translate "we charge $20/mo plus $0.02 per API call, first 10k free, annual gets 2 months off" into meters, plans, charges and API calls. That translation is a spreadsheet problem pretending to be an engineering problem. A generator that takes your pricing page and spits out a working config file plus a diff when you change it — that I'd pay for. Free single scenario, $9–29/mo for multi-scenario, template library, code export, version diff. The version diff alone is worth it. Anyone who's tried to answer "wait, what did we change in October" on a metered billing setup knows.
Would I build it? Maybe, and that's rare for me. Caveats: the audience is small and technical, they'll want to self-host the generator too, and the open-source engines could ship a better onboarding wizard and eat your lunch. But the caveats on the boilerplate one are worse — you're competing with free, twice.
If I built the config generator: Next.js on Vercel, Postgres via Supabase, and honestly a dumb form-driven template engine would cover 80% of it. No AI needed. Maybe a small Claude call to parse a messy pricing page into structured fields, but that's a nice-to-have, not the product. Ship in a weekend, charge from day one, see if anyone actually pulls out a card.
What bugs me is that 55 signals produced only these two. A gap-only day means everyone's building in the same two lanes. That's a crowded road, even if the potholes are real.