Mine the boring pain at work

Why boring wins

Most internal tools never escape the company they were built in. A few of them, productized for the broader market, become quietly enormous businesses. HashiCorp, PagerDuty, Sentry, Linear, Plaid. Every one of them solved a problem that engineers were already gluing together with shell scripts and Slack pings.

The key insight is that boring here means has a buyer. CTOs already have line items in their budget for incident response, observability, developer productivity, and security tooling. You don't have to invent demand. You have to displace a worse incumbent or fill a workflow gap.

The internal-tools inventory

1. 01List the tools at your last three jobs that someone built and others quietly relied on. Anything that lived in a Slack pin, a wiki page, or a private repo for years.
2. 02Filter by genericity.For each, ask whether a company without an engineer of your caliber would have built it. If not, productizing it has a real market because the median company can't replicate what you did.
3. 03Validate the budget exists. Search job postings for the role that owns the pain. If dozens of companies are hiring for it, the spend is real. The first-time founders page covers how to do this validation without quitting your job.
4. 04Talk to the buyer, not the user. The engineer using the tool is rarely the buyer signing the contract. Validate with a manager or director who controls the budget. Their language reveals what slot in the budget your product has to fit into.

Worked example

An infra engineer notices that at three companies in a row, someone has built an internal tool to manage feature flags rolled out by experimentation. The tool has no UI, just a CLI, and only two people at each company actually understand it. Everyone else asks those two people to make changes for them.

The buyer is a Director of Engineering who sees experiment velocity slowing because of the bottleneck. The budget exists because LaunchDarkly and Optimizely already get paid to solve a related problem badly. The wedge is a self-serve UI for the cohort of companies too small to afford LaunchDarkly but too large to fly without flag governance. Boring problem, named buyer, validated budget, clean wedge.

When this framework fails

B2B internal-tool ideas often need an enterprise sales motion. If you're a solo founder who hates sales calls, this framework will frustrate you. Pick something self-serve from Pieter Levels' framing instead. Fournier's ideas reward founders who can sell a five-figure annual contract from day one.

Run all five frameworks at once

The boring-pain method is excellent at sourcing candidates. It's less helpful at ranking them or finding the cleanest commercial wedge inside a candidate. IdeaTwister takes your boring-pain seed and runs 15 lenses against it (Customer Segments, Competitive Wedge, Defensibility, Solo Executable, GTM Channels, and 10 more) so the shortlist is ranked by commercial signal, not just by which pain felt the worst on a given Tuesday.

FAQ