· 5 min read

Retool at 20 Users: The Per-Seat Math Nobody Runs Before Subscribing

Retool's Team plan looks cheap at $10/builder — but run the real math at 20 users: role-based seats, metered workflow runs, and the developer you still need. Numbers inside.

TL;DR

Team sizeRealistic Retool tierMonthlyPer year
10 users (1 builder + 9 internal)Team$55$660
20 users (1 builder + 19 internal)Business$335$4,020
40 users (1 builder + 39 internal)Business$635$7,620

Retool is an excellent tool — for teams that already have developers. The pricing page leads with “$10 per builder,” and that number is true, and irrelevant: at 20 users on the tier you’ll actually need, you’re paying $12,000+ over three years to rent the right to build your own internal tools — and you still need someone technical to do the building. This is the math to run before you subscribe, not after.

The pricing, stated plainly

Retool prices by role, per month (pricing, August 2026, annual billing):

TierPer builderPer internal userWhat’s gated in
Free$0$0500 workflow runs/mo, exploration only
Team$10$55,000 workflow runs/mo, staging environments
Business$50$15Audit logging, rich permissions, portals, custom branding
EnterprisecustomcustomSSO, self-hosting, air-gapped deployment

Two definitions from Retool’s own fine print that decide your bill:

  • A builder is anyone who built or edited an app or workflow during the billing cycle. Your “one developer” silently becomes three builders the moment a colleague helps with a screen.
  • Internal users pay even if they only view. Twenty staff logging in a few times a week is 19 internal seats.

The math at 20 users

The tier you’ll realistically land on is Business, because that’s where the features separating “tool” from “system” live: audit logging (who changed this record?), granular permission controls, and portals if customers ever touch the data. At 20 users — one builder, nineteen internal:

  • Business: $50 + (19 × $15) = $335/month → $4,020/year → $12,060 over three years.
  • Even the cheaper Team tier runs $105/month at the same headcount — $3,780 over three years — without audit logging or fine-grained permissions.

And on top of the seats, two meters are running: workflow runs (5,000/month on Team — every automation step counts) and AI credits, with overage packs sold separately. A busy operations app with nightly syncs and alerting can push past both.

For comparison, a purpose-built internal tool on a modest VPS — the kind I build for exactly this profile — carries hosting on the order of single-digit dollars per month and no per-seat meter at all. The $12k isn’t buying capability Retool lacks; it’s buying the rental shape of capability you could own.

The cost the pricing page can’t show: the builder

Retool markets to developers, honestly — it’s a developer tool with a GUI. What that means for a non-technical SMB:

  1. Someone still designs and builds. Data model, queries, permissions, edge cases. Retool accelerates that person; it doesn’t replace them.
  2. Someone maintains. Retool apps drift like any software: sources change, queries break, permissions need review. On Business at 20 users, you’re paying $4k/year and holding a dependency on whoever built it.
  3. If nobody internal fits, the realistic path is hiring Retool freelancers — whose hourly rates eat the “cheaper than custom” argument quickly.

This is the pattern across the whole internal-tools class: the platform is the cheap part; the human who assembles, migrates, and owns the result is the scarce part. Subscriptions don’t sell you that human. Nobody does, as a subscription.

”But Budibase/Appsmith self-host on my own VPS”

Fair — and worth addressing directly, because it’s the objection I get most often: open-source builders (Budibase, Appsmith, ToolJet) run on your own infrastructure, so “your data, your VPS, custom UI” alone is not a reason to hire anyone, including me. Those are solid tools.

But notice what they share with Retool: they’re builders, not results. Someone still has to model the data, migrate the spreadsheets, wire the integrations, define the roles, test the edge cases, and answer for it when it breaks at 9am on a Monday. Self-hosting the tool solves hosting; it doesn’t solve delivery. For a technical team, that someone is on staff. For everyone else, that’s the actual purchase — and it’s the part I sell: the finished system, the migration, and one accountable person, on infrastructure you control.

When Retool is genuinely the right choice

  • You already employ developers who’ll own the tools (then per-builder pricing is honest and cheap).
  • You need internal panels over an existing production database quickly.
  • Headcount is small (<10) and stays flat.

Retool is a good product that beats building CRUD screens by hand — for the team it’s designed for. The failure mode isn’t the product; it’s a non-technical business buying a developer tool and discovering the developer isn’t included.

The exit math

If you’re at 20 users on Business Retool, the comparison isn’t “Retool vs free.” It’s ~$12,000 / 3 years of rental + builder dependency vs a one-time build of a system you own, deployed on a VPS you control, sized to your actual load (which, for an internal ops tool, is almost always modest), maintained by the person who built it. If you’re going to spend four figures a year forever, it’s worth a conversation about what that buys as an asset instead.

Sources & further reading