You needed an internal tool. A dashboard for the operations team. An admin panel for support staff. A data viewer the business could actually use without asking a developer for a query. Building it from scratch would take weeks. Retool promised a faster path.
You connected the database. You dragged in components. You wrote a few queries. A working tool appeared in a day or two.
Then someone needed a new column. Then a filter. Then a second table. Every request went back through the developer who built it. The tool works. But it never left the developer's domain. The business is still dependent on whoever built it to keep it running.
What Retool Actually Requires
Retool is a developer tool. It is fast for developers. The query editor, the JavaScript blocks, the component library: these are all things a developer works with. A non-technical staff member does not open Retool and make changes. They open a ticket and wait for a developer.
For engineering teams at growth-stage companies building dozens of internal tools, that is fine. There is a dedicated internal tooling function. Retool fits that context well.
For a smaller team that built one tool and needs it to keep running, Retool becomes a permanent dependency. The developer who built it needs to stay available. If they leave, someone new has to learn how the app was constructed before they can change anything.
- A developer to build and maintain the tool
- Per-user billing for every ops person with access
- Ongoing dependency on whoever built it
- Query editor and JavaScript for custom logic
- Version control and environment management
- Retool account tied to your database credentials
- An internal tool that works
- Staff who can open and use it without touching the code
- Changes scoped and priced when they are needed
- No per-seat cost as the team grows
Who Retool Is Actually Built For
Retool is built for engineering teams. Companies with a dedicated internal tooling function. Developers who want to build fast without writing frontend code. Organisations building dozens of internal tools across multiple teams, with a development culture that treats tooling as ongoing product work.
If your business built one tool and needs it to keep working without a developer keeping watch over it, Retool is solving for a different problem. You are paying for a platform designed for a different kind of customer.
The Per-User Problem
Retool charges per user. On the Team plan, that runs around A$12 to A$15 per standard user per month. For a tool the whole operations team needs to access, every person who uses it adds to the monthly cost. The tool does not change. The bill does.
Consider a team of five people using a Retool-built tool every day. That is A$60 to A$75 a month. Over three years, that is A$2,160 to A$2,700, before any developer time for the changes that come up along the way. And that assumes the team stays at five. Add two more people and the bill goes up immediately.
The tool was built to do one job. The cost of accessing it should not scale with headcount.
What a Custom Internal Tool Looks Like Instead
A Merebase internal tool is built for the specific job your business has. You describe the data, the workflow, the fields your team uses, and how results need to be displayed. The app is built to do exactly that.
When it is delivered, your team opens it and uses it. There is no query editor to maintain. No component library to learn. No developer dependency. The app does the job the business described.
What Merebase builds:
CRM and contact managers. Job and task trackers. Invoice and proposal tools. Staff records and leave tracking. Inventory and stock management. Support ticket queues. Merebase reporting dashboards. One app. One job. A$499 once. You bring your own hosting. A basic plan runs A$5 to A$20 a month.
Changes are handled as separate builds. You describe what needs to change. It is scoped and priced in writing. No payment until the scope is agreed. No retainer. No ongoing fee for the privilege of updating something your business already paid for.
The Maintenance That Was Supposed to Go Away
Retool was meant to make building faster. It does. A working tool appears in a day. What it does not change is who is responsible for keeping it working. That person is still a developer. They are still needed every time the business wants something different.
A tool that requires a developer to change is not a tool the business owns. It is a tool the business rents access to, with a developer as the ongoing condition of that access.
A Merebase build is handed off. The scope is agreed in writing before any payment. When it is delivered, it belongs to the business. Changes are separate builds, scoped separately, paid separately. There is no ongoing dependency and no subscription fee.
CRM and contact managers. Job and task trackers. Invoice and proposal tools. Staff records and leave tracking. Inventory and stock management. Support ticket queues. Merebase reporting dashboards. One app. One job. A$499 once. You bring your own hosting. A basic plan runs A$5 to A$20 a month.