Four dev-tool ideas this week. Four dead, all from the same cause, and it took me embarrassingly long to see the pattern instead of just the individual rejections.
I'm a solo dev, no team, no funding, building in public-ish. The move I keep reaching for is the classic one: ship something free (a CLI, a GitHub Action, a linter) that devs adopt for free, then sell a paid backend on top: history, dashboards, team alerts, whatever the free tool can't do alone. It's the Sentry/Vercel playbook, scaled down. It's also, as of 2026, mostly a trap if you're doing it alone with no existing audience. Here's the check I wish I'd been running from idea one instead of idea four.
The idea that looked good on paper
The one I actually got excited about: flaky-test analytics. Real, universal pain (every CI setup eventually has a test that fails 1 time in 20 for no reason), and unlike most of my other ideas, there's an actual company charging real money for it. BuildPulse has been selling this since around 2019, three tiers, $99/$249/$499 a month, same structure on the pricing page for years. That's rare. Most "obvious" dev-tool ideas don't have anyone visibly paying for them at all.
So I went looking for the wedge: free CLI/Action reads your JUnit XML, no write access needed, dead simple to adopt. Then I checked who else is standing in that spot.
