"Internal tool" covers two very different builds. One replaces a spreadsheet for one team. The other plugs into systems you already run. They can look the same on screen. They are not the same amount of work.
Here is how I break it down when I scope one.
The two versions
1. One team, one workflow. A web app your own team signs in to. It replaces a spreadsheet or a manual process. Sign-in, a database, data entered in the tool. No outside integrations.
2. Connected to your systems. The same tool, but it reads from or writes to one or two tools you already use, like a database or a chat app.
In my scope estimator, the first one lands at $3,500 to $5,500 over about 3 to 4 weeks. The second lands at $6,500 to $9,000 over about 4 to 5 weeks. Those are estimates from fixed rules, not quotes. They assume one user type, no AI, standard business data, a private launch to your team first, and hosting on your own accounts.
Why connecting costs more
The screens can be identical. The difference is what happens behind them.
Every connection to another system brings the same chores:
- getting access to it in the first place
- handling errors when the other system is down
- testing against real data, not just a sample
In the estimator, one or two integrations move the work up a tier on their own. That is usually the line between "a better spreadsheet" and "part of your infrastructure".
What pushes the cost up
- Pulling data from several existing systems
- A custom or poorly documented internal API
- Approval chains across several departments
- Regulated data such as health or payroll
- Large imports, scheduled jobs, or live sync
- Rolling it out to customers, not just staff
Past a point (several or custom integrations, regulated data, high volume from day one) I stop giving a range at all and scope it sprint by sprint, with a fixed price for each.
What you can cut for a first version
- One team and the one process that hurts most
- Data entered in the tool, or one CSV import
- One login type before roles and permissions
- Your team as the only users at first
- The current spreadsheet as the spec
- Reports and exports left for the next sprint
Check this before paying anyone
For internal tools, check whether a low-code admin builder over your existing database is enough before you commission a custom app. If it covers your workflow, it will cost less than any custom build, mine included.
Growing it later
A first version does not have to be the whole thing. The next workflow can be its own sprint with its own fixed price. If you own the code in a repository in your name, anyone can extend it later.
The full breakdown for internal tools, with FAQs, is here: harjotrana.com/cost/internal-tool. If you want a number for your own idea, the free scope estimator uses the same rules.
Happy to answer questions in the comments.
Top comments (0)