The Challenge
Every company needs internal tools: admin dashboards, customer support panels, approval workflows, data management interfaces. But these tools are "boring" — they're not the product, they're not customer-facing, and they never get prioritized.
The result: developers spend an estimated 30-40% of their time building and maintaining internal tools. This represents billions of dollars of engineering time spent on non-differentiating work.
The Approach — Tools in Action
- External products: Custom (and should be — this is the company's differentiation)
- Internal tools: Custom but shouldn't be — most internal tools are variants of the same patterns (tables, forms, charts, buttons that trigger APIs)
- Databases and APIs: Product/commodity
Internal tools were stuck in the "custom-built" phase despite being highly standardizable. This was the classic Wardley Mapping opportunity.
First Principles: "What is an internal tool, fundamentally?" → A UI that connects to a database or API and lets users read/write data. 90% of internal tools are variations of: a table, a form, a chart, and buttons. If you can assemble these from pre-built components, you can build any internal tool in minutes. Impact-Effort Matrix prioritized the approach:- Quick wins: Drag-and-drop UI builder connecting to databases
- Major projects: Custom JavaScript for complex logic, version control
- Eliminated: Mobile apps, consumer-facing features, marketing websites
The Outcome
Retool turned "boring" into a massive market:
- Valued at $3.2B
- Used by 27,000+ organizations including Amazon, DoorDash, and NBC
- Saves companies an estimated 30-40% of engineering time on internal tools
- Proved that the most valuable software often solves the problem no one wants to talk about
- Inspired a category of "internal tools" startups
Key Takeaway
The "boring" problems that every company has are often the most valuable to solve at scale. Use Wardley Mapping to find components that are custom-built everywhere but could be productized.
Tools Used in This Story
Wardley Mapping
Systems ThinkingVisualize your strategic landscape and anticipate market evolution
First Principles
Problem SolvingBreak down complex problems into basic elements and create innovative solutions from there
Impact Effort Matrix
Decision MakingPrioritize by weighing impact against the effort required