Skip to main content
Retoolretoolpricinginternal tools

How Much Does Retool Cost? Pricing for Australian SMEs

Retool lists at USD $10 to $50 per builder plus $5 to $15 per internal user. Here is what that adds up to in AUD, and what the licence fee leaves out.

· Founder & AI Consultant, IOTAI9 min read

Retool's list price is one of the more legible numbers in the internal-tools market: a per-builder fee, a per-internal-user fee, and four tiers you can read off a page in under a minute. For an Australian buyer that legibility is the useful part, because it lets you work out the licence line exactly and then spend your attention on the number that actually moves — what it costs to design, build and keep the app running.

Here is the pricing as listed in August 2026, converted to AUD, with worked scenarios at 5, 20 and 60 users.

The model: builders plus internal users

Retool splits your people into two categories. Builders create and edit apps, workflows and queries. Internal users log in and use what the builders made — approving credit applications, updating a job record, running a refund. Retool bills both, at very different rates, and you pay per month per head in each bucket.

That split is the whole story. Most organisations end up with a handful of builders and a long tail of users, so the per-user rate compounds while the per-builder rate barely moves.

The four tiers, August 2026

Taken from Retool's pricing page and cross-checked against independent pricing trackers in mid-to-late August 2026. All figures are USD.

PlanPer builder / monthPer internal user / monthAI credits per builder / monthNotable inclusions
Free$0$0250Around 5 users, limited workflow runs
Team$10$51,000 (750 base + 250 bonus)Add-on credit packs available
Business$50$153,000 (1,500 base + 1,500 bonus)Audit logging, external user access
EnterpriseCustomCustom10,000 (5,000 base + 5,000 bonus)Negotiated

One thing worth knowing before you renew: a 2025–2026 total-cost analysis notes that effective Business pricing has landed at $65 per builder plus $18 per user on some older contracts, while the list price as at 14 August 2026 is $50 plus $15. If you signed a while ago, check what you are actually being charged against the current list.

What that means in AUD

Retool bills in US dollars, so your real cost carries an FX line and moves with the exchange rate. The figures below use an assumed rate of AUD 1.55 to the US dollar and exclude any GST treatment. Use them as shape, not as a quote — re-run them at the rate on the day you sign.

Five people: one builder, four users

PlanUSD / monthAUD / monthAUD / year
Team$30~$47~$558
Business$110~$171~$2,046

At this size the Free plan is genuinely viable for a first app — around five users and 250 AI credits a month is enough to prove a concept. Team at roughly $47 a month is cheaper than most SaaS point solutions you would otherwise buy to solve the same problem.

Twenty people: two builders, eighteen users

PlanUSD / monthAUD / monthAUD / year
Team$110~$171~$2,046
Business$370~$574~$6,882

The builder line is now $20 of the $110 on Team, and $100 of the $370 on Business. Everything else is people logging in.

Sixty people: three builders, fifty-seven users

PlanUSD / monthAUD / monthAUD / year
Team$315~$488~$5,859
Business$1,005~$1,558~$18,693

At sixty seats on Business, builders are 15 per cent of the bill. The other 85 per cent is the tail of people who open the app twice a week.

The per-user line dominates long before the builder line does

Run the ratio on Business: one extra builder costs $50, which is the same as 3.3 extra internal users. That inverts the instinct most teams bring to seat-based pricing. Rationing builder access to save money is close to pointless — you will spend more per month on the six warehouse staff who need read access than on a second developer who can halve your delivery time.

The lever that matters is who actually needs to log in. Every seat you can serve with a scheduled email, a Slack message, a PDF, a read-only dashboard or a public form is a seat you do not pay $15 a month for. On a sixty-person rollout, moving twenty occasional viewers to a push-based notification instead of a login saves around AUD $5,580 a year on the Business plan, and usually makes the process better because nobody has to remember to go and check something.

Two design decisions follow from that:

  • Build the app for the people who take action, not the people who want to know. Notifications and reports serve the second group more cheaply.
  • If external parties — clients, subcontractors, suppliers — need access, that sits on Business, which is where external user access appears. Price the tier around that requirement rather than discovering it after you have built.

AI credits are attached to builders, not users

Retool's credit allowances scale per builder: 250 a month on Free, 1,000 on Team, 3,000 on Business, 10,000 on Enterprise, with add-on packs available. That means your AI capacity is a function of how many builder seats you hold, not how heavily your users hammer the app. A two-builder Business account carries 6,000 credits a month between them.

For an app that does light AI work — summarising a case note, classifying an inbound email, drafting a response for a human to approve — the bundled allowance behaves as a predictable ceiling rather than a metered bill, which is the main argument for using in-platform credits over calling an LLM API directly and metering it yourself. For anything genuinely LLM-heavy, model the credit burn per transaction before you commit, because that is where the tidy monthly number stops being tidy.

The licence is the small, predictable number

Take the twenty-person Business scenario: roughly AUD $6,882 a year. That is real money, but it is not the number that decides whether the project succeeds. The spend that determines the outcome sits in four places the price list says nothing about:

Design. Deciding what the app is for, what happens on the screen, and what it deliberately does not do. Internal tools fail far more often from being wrong than from being slow.

Data modelling. Retool is a front end over your systems. If your job records live in three places with inconsistent identifiers, Retool will faithfully surface that mess to sixty people at once. Reconciling the underlying data is frequently the largest single piece of work, and it is work you would face on any platform.

Permissions. Who can see costs, who can approve above a threshold, what gets audit-logged, what happens when someone leaves. This is where the Business tier earns its price and where most builds get revised after the first security conversation.

Maintenance. Rotated API keys, an upstream schema change, a new field in your accounting system, a process that shifts because the business shifted. Internal tools are living things. Budget for someone owning them, whether that is your ops lead with capacity carved out or an external partner on retainer.

Because those four items exist regardless of platform, the comparison SMEs should be running is not Retool versus doing nothing. It is Retool plus build effort versus a bespoke application plus build effort. What the licence buys you in that comparison is auth, role-based access control, audit logging, a component library, hosting, deployment and a database connector layer that already works. On the bespoke side, all of that is yours to write and yours to patch. That is the trade being made, and at AUD $6,882 a year for twenty people it is usually not close — which is why the sensible way to evaluate the platform is to price a scoped build of your first real internal application rather than to compare seat rates. It is also why building internal tools on Retool tends to be judged on delivery speed and on who maintains the thing afterwards, not on the monthly line item.

The exception is the app that becomes a product — something you sell, or something a large external user base touches. At that point the per-user model stops flattering you and a bespoke build starts making sense. Retool is at its best for internal operations run by a known, countable set of staff.

Before you commit

Sit down with a headcount and split it into three columns: people who will build, people who will act inside the app, and people who only need to be told something happened. Multiply the first two columns by the Team and Business rates above, convert at today's rate, and you have a defensible annual licence figure to take to whoever signs.

From there the question is whether the first app is worth building at all, and that needs a number on the other side of the ledger. We will scope a specific internal tool — the data sources it touches, the permissions model, what it replaces, and what a typical two-to-four week build looks like — and put an honest figure against the hours it gives back. Run your own numbers first with the automation ROI calculator, and if the payback looks marginal we will say so rather than sell you a licence you do not need.

Share on

Founder & AI Consultant, IOTAI

IOTAI is Australia's leading AI consultancy and Managed Intelligence Provider, specialising in Retool, n8n, and AI agent development for SMEs.

Want this built rather than researched?

We scope the work, tell you what it costs, and say plainly if it is not worth automating yet. Most builds ship in two to four weeks.

Or read more about internal tools and business apps.