Menu

What actually decides the cost of an internal tool
📰

What actually decides the cost of an internal tool

DEV Community: productivity·Harjot Rana·4 days ago
#hoXxZF3l
#devtoproductivity#devto#dev#team#first
Long article (507 words) — no AI summary yet.
Reading 0:00
15s threshold

"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.…

Continue reading — create a free account

Join HashtagPLUS to read full articles, follow hashtags, vote, and join the conversation.