Internal tools are the screens your staff use to run the business: job boards, approval queues, stock lists, admin panels over your database. You can build them in a low-code builder such as Retool, Appsmith or Microsoft Power Apps, which mostly charge per user per month, or have them built as custom software you own, which costs more up front but has no per-user fee.
Which suits you comes down to how many people use the tool, how long you will use it, and who will maintain it. A disclosure: CentriWeb builds custom software, including internal tools, so weigh our view with that in mind. Every price below comes from each vendor’s own pricing page as at November 2026. Check their pages for current prices.
Common internal tools in a service business include:
- a job or work order board that shows what is booked, who is on it and what is waiting on parts
- an approval screen for quotes, refunds or timesheets
- a customer lookup that pulls the CRM, invoices and past jobs into one view
- an admin panel for updating prices, stock or staff rosters without touching the database
Internal tools options compared
| Retool | Appsmith | Power Apps | Custom build | |
|---|---|---|---|---|
| What it is | A low-code builder for screens over your data, hosted by Retool | A low-code builder with an open-source edition you can host | Microsoft’s app builder, tied into Microsoft 365 | Software written for your process |
| How it charges | Per builder and per user, monthly | Per user, monthly, or a flat Enterprise rate | Per user, monthly, paid yearly | A project price, then hosting and upkeep |
| Who maintains it | Your builders, on Retool’s platform | Your builders, on Appsmith’s cloud or your server | Your builders, inside Microsoft’s platform | The developer or studio under an agreement, or your own team |
| Who it suits | Teams with someone technical and a database already | Teams that want a self-hosted option | Businesses already on Microsoft 365 | Tools used daily by many people, or that customers see |
How Retool, Appsmith and Power Apps charge
Retool
Retool’s pricing page separates builders, who make the apps, from internal users, who only use them. It showed:
- Free: up to 5 users, 500 workflow runs a month, up to 5 modules, a production environment only.
- Team: $10 per builder and $5 per internal user a month billed annually, or $12 and $7 billed monthly.
- Business: $50 per builder and $15 per internal user a month billed annually, or $65 and $18 monthly. External users are free up to 50, then priced in tiers starting at $8 a month each billed annually.
- Enterprise: custom pricing, and the only plan that lists self-hosting.
The page shows a $ sign without naming a currency.
Appsmith
Appsmith’s pricing page showed a free plan for up to 5 users on its cloud, Business at $15 per user a month for up to 99 users, and Enterprise at $2,500 a month for 100 users. A user is anyone added to a workspace, and anyone present during a month is billed for that month. There is also a free open-source Community edition you host yourself. Prices are shown in $ with no currency named.
Microsoft Power Apps
Microsoft’s Power Apps pricing page (United States version) showed a free Developer Plan for building and testing, and Premium at $20 per user a month, paid yearly. It says users of production apps need a paid plan, and that your actual price shows at checkout. Prices differ by country, so open the page for your region.
What each option does well
- Retool is quick for someone technical to put screens over an existing database or API, and the split between builders and users keeps the cost down when most staff only view and update records.
- Appsmith offers a self-hosted open-source edition, which suits a business that wants its data on its own server and has someone to run it.
- Power Apps fits a business already on Microsoft 365, with staff signing in on accounts they already have.
- A custom build fits the process exactly, has no per-user fee, and can be opened to customers or contractors without a licence for each.
The per-user maths over three years
Low-code pricing is easiest to judge with your own numbers. Take a business with 3 people building tools and 25 staff using them, at the prices listed above:
- Retool Team, annual: 3 x $10 plus 25 x $5 is $155 a month, or $5,580 over three years.
- Retool Business, annual: 3 x $50 plus 25 x $15 is $525 a month, or $18,900 over three years.
- Appsmith Business: 28 users x $15 is $420 a month, or $15,120 over three years.
- Power Apps Premium: 28 users x $20 is $560 a month, or $20,160 over three years.
Those are licence costs only. You still pay someone to build and change the tools, whether that is a staff member’s time or a contractor. Double the staff and the licence bill roughly doubles. A custom build has the opposite shape: most of the cost is up front, then hosting and maintenance that do not rise much as staff numbers grow.
Run the same sum with your own headcount and the plan whose features you need. If the three-year licence total is small next to what a custom build would cost, low-code is usually the sensible choice.
What owning it means, and what you take on
A custom internal tool belongs to you, if your contract says so. Our guide to who owns the code covers the copyright rules. You are not tied to one vendor’s prices or roadmap, and you can open the tool to customers, subcontractors or suppliers without paying per head.
Ownership also means responsibility. Someone has to host it, keep it secure, back it up, and update it when the systems it connects to change. Budget for that from the start, as our guide to software maintenance cost explains. With a low-code builder, the vendor carries much of that platform work for you, which is a big part of what the per-user fee pays for.
Signs you have outgrown the builder, or the spreadsheet
- Licence fees keep rising as you add staff, and most of them only need one or two screens.
- You want customers or contractors to log in, and each would need a seat.
- The tool needs logic the builder handles awkwardly, such as complex pricing, scheduling or multi-step approvals.
- Only one person understands how the tool works, and they are busy.
If your internal tool today is still a shared spreadsheet, start with our guide to replacing the spreadsheet the business runs on, and the comparison of no-code against custom development.
Where a built and looked-after tool fits better, and who it does not suit
A custom internal tool built and maintained for the business fits when many people use it every day, when customers or contractors need access, or when the process is what sets the business apart and does not fit a builder’s components. CentriWeb’s custom software work covers that: we build the tool around how your team works, connect it to the CRM and accounting software you keep, and look after it afterwards.
It does not suit:
- Small teams. With five users or fewer, the free plans above may cover you entirely.
- Businesses with a capable builder in-house who enjoys the work and has time for it.
- Short-lived tools. If you need it for a project that ends in six months, a monthly licence is cheaper than a build.
- Budgets where a standard plan already does the job, which is often the case for simple admin screens.
Where to start
- List the internal tools you need and who uses each one.
- Count builders and users separately.
- Price the plan you would really need on each vendor’s page, over three years.
- Get a quote for a custom build of the most-used tool, including three years of hosting and maintenance.
- Compare the totals, then weigh who will maintain each option.