What does it cost to build an internal tool?
An internal tool usually costs SEK 200,000–800,000 to build, depending on the number of workflows, roles, and integrations. The ROI calculation is simple: hours saved per week times the internal hourly cost, weighed against the investment. A tool that saves a few hours a day for a whole team often pays for itself within one to two years.
It exists in almost every organization: the spreadsheet emailed back and forth, the list only Anna is allowed to touch, the report pieced together by hand every Monday. Internal tools are the entry point to custom software development – they’re scoped, cheaper than customer-facing systems, and unusually easy to justify financially. Here’s the pricing and the calculation.
Price levels for internal tools
| Level | Typical cost | What you get |
|---|---|---|
| Simple tool | SEK 200,000–350,000 | A register or admin panel, a few users, simple permissions |
| Standard tool | SEK 350,000–550,000 | Several workflows and roles, connection to an existing system |
| Extended tool | SEK 550,000–800,000 | Several integrations, automated steps, reporting |
What moves the price is rarely the interface but the logic behind it: number of workflows, rules, roles, and above all integrations with other systems.
The ROI calculation: hours saved times hourly cost
Internal tools are the category where the investment is easiest to justify, because the payoff can be measured in time.
A worked example. Five case handlers each spend an average of 45 minutes a day on manual work a tool would automate: compiling data, copying between systems, chasing status by email. That’s just under 80 hours a month. At an internal hourly cost of SEK 450, that’s roughly SEK 35,000 a month, just over SEK 400,000 a year. A tool for SEK 400,000 then pays for itself in about a year – and keeps saving the same amount every year after that.
Add on the gains that don’t show in the calculation: fewer errors when data isn’t copied by hand, faster onboarding of new staff, and decisions made on fresh numbers instead of last month’s compilation.
Lower UI ambition – never lower data quality
A sound principle for internal tools: they don’t need to win design awards, but they can never skimp on data quality.
Concretely, that means the interface can be simple and functional – standard components go a long way when the users are colleagues who get trained on the spot. But input validation, access control, traceability, and sensible error messages aren’t luxuries. Data from an internal tool works its way into reports, invoices, and management decisions, and bad data in the system is worse than no system at all.
That priority is also why the range starts at SEK 200,000, not SEK 50,000: a large share of the work sits in logic and data quality that doesn’t show on the surface.
Common first projects
- Replacing a shared spreadsheet for planning, staffing, or price lists
- Automating double entry between two systems that don’t talk to each other
- Consolidating cases that currently live in a shared email inbox
- Building an admin panel for what staff currently ask IT to do manually
- Compiling reports currently pieced together by hand every week
Start with what hurts the most
Choose the process where the most time leaks away, build the smallest tool that solves it, and put it into use. A tool in live use after three months beats a perfect requirements list every time – and the next phase gets better from real usage. Want to calculate a concrete workflow? Get in touch and we’ll do the ROI calculation together.
Frequently asked questions
What counts as an internal tool?
Systems used only by your own employees: admin panels, planning tools, registers, tracking, and small-scale case handling. They usually replace spreadsheets, email threads, and manual double entry – processes that work but scale poorly and create errors.
Why are internal tools cheaper than customer-facing systems?
The requirements are simpler on several fronts: fewer concurrent users, no public attack surface of the same size, and the interface can be functional rather than brand-building. The training need is also smaller – the users are in the same organization and can give feedback directly.
Couldn't we just solve this with a no-code tool instead?
Sometimes, and then it's often right to start there. No-code suits simpler forms and workflows, but hits a ceiling with complex rules, integrations, and larger data volumes. A common path is validating the need in a simple tool and building custom once the ceiling is reached.
How fast can an internal tool be in place?
A scoped tool with a couple of workflows often takes two to four months from start to live use. The fastest path is keeping the first version small: the most important workflow first, the rest in phases once the tool is already in use and delivering value.
What does it cost to run and maintain the tool?
Budget for 15–25% of the build cost per year in maintenance plus a modest cloud cost, often a few thousand kronor a month for an internal tool. The line item is worth including in the ROI calculation, but rarely changes the conclusion when the time savings are real.