Retool

Retool is a low-code platform for building internal tools: the admin panels, dashboards, and operational apps that every company needs but no engineer wants to build from scratch. It began in 2017 as a near-dead pivot and grew into a company valued at $3.2 billion, and its playbook is a textbook wedge strategy: own the unglamorous, universal problem of internal software, embed deeply, then expand outward. Every story below traces back to founder David Hsu's insight that almost all internal tools are the same tables, buttons, and forms rebuilt over and over.

Beachhead: The pivot that found a universal, ignored problem

The problem. In early 2017, Hsu's Y Combinator (Winter 2017) startup was Cashew, a UK Venmo competitor burning roughly $1,000 a day and losing money on every payment, with fewer than 60 days of runway left. He needed a new idea that was real, urgent, and provable in weeks, not a speculative bet.

The approach. Scouring the custom software they had built to keep the fintech running, the team noticed that all of it looked the same: "When you build enough internal tools as an engineer, you realize that all internal tools basically look the same," Hsu said, just tables, buttons, dropdowns, and forms rebuilt from scratch. They picked that single narrow wedge, internal tools, and built a drag-and-drop prototype in a few days.

How it solved it. The beachhead was validated almost immediately: a few weeks later at YC Demo Day 2017, Retool announced it had already signed an enterprise pilot worth $1.5 million. The problem was universal and painful enough that a rough prototype closed a seven-figure deal, confirming the wedge before the product was even built.

Land and Expand: One overnight feature, then dozens of apps per account

The problem. A single support dashboard is a small foothold. To build a durable business, Retool needed each customer to go from one tool to many, and needed the product to keep pulling accounts deeper rather than topping out after the first use case.

The approach. Retool ran a tight land-and-expand loop: land on one internal tool, then say yes fast to whatever unlocked the next. When Retool's second customer couldn't adopt it without API connections, the team built that capability overnight. Hsu's rule was to build only generalizable "building blocks" usable by 30%+ of customers, so every expansion compounded across the base.

How it solved it. Audit logs requested by DoorDash ended up used by 50 to 60 percent of customers, turning one account's need into platform-wide value. That motion scaled outward too: Retool grew from an internal-tools builder into Workflows, a managed database, mobile, and AI, and more than 500,000 apps have now been built on the platform by customers like Amazon, Brex, and Mercedes-Benz.

Switching Costs: Business-critical apps welded into daily operations

The problem. Low-code tools risk being disposable. If Retool were just a faster way to prototype, customers could rebuild elsewhere or churn the moment a cheaper option appeared, especially the operationally heavy companies Retool targeted.

The approach. Retool let teams wire apps directly to any database or API, layer in permissions, and self-host, so the tools became load-bearing infrastructure for support, ops, and finance rather than throwaway UIs. Once dozens of daily-use apps, their data connections, and their access controls live inside a company's operations, unwinding them means rebuilding working software that people depend on every day.

How it solved it. The embedding shows up in usage: over 500,000 apps built and billions of queries run through the platform, with companies like DoorDash and Brex running core operational workflows on Retool. Early on, Hsu credits internal alerting tools ("Big Fish Swimming," "Big Fish Errors") with preventing an estimated 80% of potential customer loss, catching problems before an embedded account could sour.

Category Creation: Naming "internal tools"

The problem. The pain Retool solved was real but nameless. Engineers everywhere hand-rolled admin panels, but there was no recognized category to search for, budget for, or buy. Retool's earliest messaging reflected the confusion: pitches like "Excel, with higher order primitives" and outreach to legacy FileMaker developers drew sub-2% response rates and hostile replies.

The approach. Retool reframed everything around two plain words: "internal tools." Instead of an abstract spreadsheet metaphor, the pitch became "build internal tools faster," aimed at engineering leaders at operationally heavy startups.

How it solved it. The renamed category landed instantly: a cold email to Rappi's CTO got a reply within 15 minutes ("let's get on a call"), and outbound campaigns began hitting roughly 8% response rates. By naming and productizing internal tools, Retool turned diffuse engineering pain into a market it now defines and leads, reaching an estimated $93.5M ARR by 2023.

Differentiation: Betting on engineers who hate drag-and-drop

The problem. Low-code was crowded with tools aimed at "citizen developers," non-technical business users. Targeting engineers looked like a mistake: as Hsu put it, "developers are allergic to drag and drop. They hate drag and drop." But engineers were exactly the people who otherwise hand-built internal tools.

The approach. Retool differentiated by building for developers, not around them. It gave engineers building blocks rather than finished templates: connect to any database or API, drop into raw SQL and JavaScript when needed, use version control, and self-host. The drag-and-drop canvas was a shortcut for undifferentiated work, not a replacement for real code.

How it solved it. That credibility with technical buyers won the accounts generic low-code tools couldn't. Retool's first customers were fellow YC companies followed by Brex and DoorDash, engineering-heavy teams that adopted it precisely because it respected how developers work, reaching an estimated $1 to $2 million ARR from around 40 outbound-sold customers before its public Hacker News launch on August 9, 2018.