The Database Tool That Started Acting Like a Product Studio
Airtable built its reputation as a spreadsheet that didn’t make you feel stupid. Colorful rows, drag-and-drop fields, a friendly learning curve – it was the tool non-technical teams used to manage projects without bothering engineering. But over the past 18 months, the company has been quietly building something else entirely: a no-code interface layer that lets users construct fully functional internal apps directly on top of their Airtable bases. The feature is called Interfaces, and it is starting to look a lot like Retool’s core product.
Retool made its name by giving engineers a faster way to build internal tools – dashboards, admin panels, customer-facing portals – without writing full-stack applications from scratch. The pitch was speed: connect to a database or API, drop in some components, ship something useful by the end of the day. That pitch still works. But Airtable is now offering a version of the same outcome to a completely different buyer, and some of those buyers are agencies that previously ran entire Retool practices.
What Interfaces Actually Does That Retool Does Too
Airtable Interfaces lets users build form-based workflows, detail views, dashboard components, and filtered data displays without writing a single line of code. A user can create a client-facing portal showing only specific records, a team dashboard pulling live data from multiple tables, or an intake form that routes submissions directly into a structured base. For operations teams, this covers a lot of ground – the same ground Retool covers, just with a different ceiling and a lower floor.
The key difference has always been depth. Retool connects to virtually anything: PostgreSQL, REST APIs, GraphQL, Stripe, custom endpoints. It lets developers write JavaScript inline, build conditional logic, and construct genuinely complex tools. Airtable Interfaces can’t do most of that. The data source is always Airtable itself, and the logic stays shallow. But for agencies building client deliverables around structured data – editorial calendars, campaign trackers, vendor management portals – that constraint barely registers. The client doesn’t need a custom API integration. They need a clean interface on top of a spreadsheet they’re already managing.
Agencies are particularly sensitive to where the time goes. A Retool project requires someone who can write JavaScript and understands how to connect data sources. That person costs more, takes longer, and sometimes doesn’t exist on smaller teams. An Airtable Interface project can be handed to a junior ops hire or a project manager who took a weekend course. The skill floor drops, and the margin improves. For agencies billing on time and materials, that math is hard to ignore.
Airtable has also been expanding the Interface component library steadily – adding charts, timelines, gallery views, and form branching logic that didn’t exist two years ago. Each addition quietly closes the gap with what agencies were previously outsourcing to Retool. No single update is dramatic enough to generate headlines, but the cumulative effect is a product that now handles a meaningful slice of the use cases that drove agency adoption of Retool in the first place.
Why Retool’s Agency Customers Are the Vulnerable Ones
Retool’s strongest customer segment has always been in-house engineering teams at mid-size and growth-stage companies. Internal tools built by people who understand databases and want to move faster than writing React from scratch – that’s the core. The agency segment is secondary, but it exists and it has been growing as more consulting firms and boutique digital shops started packaging Retool implementations as service offerings.
Those agency clients are now the most exposed to Airtable’s move. They typically work with clients who are not engineering-led, who already use Airtable for operational data, and who don’t need the tool to connect to a custom backend. When a client is already paying for Airtable and already managing data there, the argument for spinning up a separate Retool workspace – and paying a developer to maintain it – gets harder to make. Airtable just needs to be good enough, and for a growing number of use cases, it already is.
The Pricing Dynamic That Makes This Uncomfortable for Retool
Retool’s pricing is structured around editors and end users, and for internal tools with a defined user base, it works cleanly. But agencies building client portals often face a different math: the end users are the client’s own customers or staff, and seat counts can scale unpredictably. Retool’s external user pricing has historically been a friction point for agency-built client-facing tools. Airtable’s Interface pricing, embedded within its existing base plans, sidesteps that friction almost entirely for smaller deployments.
Airtable also benefits from being the system of record. When the data already lives in Airtable, the interface sits on top of something the client is already paying for and already understands. There’s no migration, no new data pipeline, no onboarding lift. The sale is “you can make this look like a real product” rather than “let us rebuild your data layer in a new tool.” That’s a much shorter conversation, and it closes faster.
Retool isn’t sitting still – it has expanded its own no-code capabilities and recently pushed harder on its workflow automation features. But the product remains fundamentally aimed at the developer buyer, which is the right call for its core market and a structural limit on how far down it can go. Airtable has no such constraint. Its entire product history is about making structured data accessible to people who aren’t developers, and Interfaces is just that instinct applied to the output layer rather than the input layer.
The agencies most at risk are probably the ones that built Retool expertise as a differentiator for clients who didn’t have in-house engineering. If those clients are now realizing they can get 80% of the outcome inside a tool they’re already using, the agency’s core value proposition needs to evolve – or find clients with more complex requirements. Whether Retool moves to compete more aggressively on the low end, or decides that market isn’t worth defending, is the tension that will define both companies’ positioning over the next two years.
