Mine the boring pain at work
Camille Fournier (author of The Manager's Pathand a long-time distributed-systems engineer) has consistently argued that the most reliable startup ideas for technical founders sit hidden in plain sight. They're the internal tools, ops workflows, and platform pain you already build by hand at every company.
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.
If a tool lives in a Slack pin or a private repo for two years and people quietly rely on it, that's a productizable business waiting for someone to take it outside the company.
Productizing manual friction
How manual corporate workarounds translate into enterprise scale platforms:
The internal-tools inventory
Filter your past experiences to find viable corporate opportunities:
List the tools at your last three jobs
Look for anything that lived in a Slack pin, a wiki page, or a private repository for years. Tools that people quietly relied on daily.
Filter by genericity
Ask: would a company without an engineer of your caliber have built this? If not, productizing it solves a real skill gap.
Validate the budget exists
Search job boards for roles owning the pain. If companies are hiring people to solve it manually, they will pay for software to automate it.
Talk to the buyer, not the user
The engineer using the tool is rarely the one signing the check. Validate with a manager or director who controls the budget slots.
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 actually understand it. Everyone else asks those two people to make changes.
The Feature Flag Wedge Pipeline
CLI-only flag manager built internally. Only 2 developers understand it, creating constant bottlenecking.
→Director of Engineering who sees release velocities dropping and wants to re-deploy dev resources.
→Existing SaaS options like LaunchDarkly are already line items in budgets, validating WTP.
→Self-serve UI targetting mid-market teams too small for LaunchDarkly but too big to fly blindly.
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+ angles against it (Customer Segments, Competitive Wedge, Defensibility, Distribution Edge, 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.
Find My Best Startup OpportunityFAQ
What is Camille Fournier's framework for finding startup ideas?
+
Camille Fournier (author of The Manager's Path and a long-time distributed-systems engineer) has consistently argued in talks and essays that the most reliable ideas for technical founders come from internal tools, ops workflows, and platform pain that working engineers and managers already build by hand at every company.
Why does "boring" matter in this framework?
+
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. Boring categories don't trend on Twitter, but they pay invoices on net-30.
What kind of companies has this framework produced?
+
Productized internal tools have become quietly enormous businesses. Think HashiCorp (configuration), PagerDuty (incident response), Sentry (error monitoring), Linear (engineering project management), Plaid (financial data plumbing). Every one of them solved a problem that working engineers were already gluing together by hand inside their companies.
Is this framework only for technical founders?
+
It's most natural for technical founders because they've lived the pain. But the same logic applies to any operator. A finance lead who built spreadsheet templates that her whole team relies on is sitting on the same kind of opportunity. The question is: what did you build at work that other companies would also need?
What's the biggest risk with this framework?
+
B2B internal-tool ideas usually need an enterprise sales motion. If you're a solo founder who hates sales calls, this framework will frustrate you. The ideas reward founders who can sell a five-figure annual contract from day one. If you want self-serve and small-ticket, pair this framework with Pieter Levels.