How Much Does a Custom Internal Tool Cost? A Transparent Breakdown

The first thing every small business owner asks about a custom internal tool is the same thing they ask about a custom website: how much. The honest answer is the same too: it depends, but there are tiers, and the tiers are narrower than you would expect. This is the version with the real numbers attached.

The short answer

For a small business in Europe, a custom internal tool from a serious freelance developer costs €500 to €5,000 depending on shape. Below that you are looking at a one-off macro or a Zapier zap. Above that you are no longer building "a tool", you are building a small custom application. I broke that out separately in How Much Does a Custom Website Cost, which covers the application end of the spectrum.

Here is the breakdown for the tool category.

Tier 1: €500 to €1,500, the single-purpose script

This is one job, done well, shipped as a button somebody on the team double-clicks.

What it looks like:

• An Excel-in, Excel-out sorter, transformer, or summariser.
• A batch renamer or PDF generator that takes a folder of files and produces a folder of files.
• A small scheduled job that pulls one report from one system every morning and emails it.
• A targeted scraper that produces a refreshed CSV from a public source on a schedule.

What is included:

• Discovery call to write down the rules in plain English.
• Code, in Python or Node, with the rules versioned.
• A handover: a runnable folder, a one-page README, a 15-minute walkthrough.
• 30 days of small revision support.

Timeline: 1 to 3 weeks. This tier covers the long tail of "I keep doing this same boring thing every week". Most of these jobs are smaller than people think.

Tier 2: €1,500 to €3,000, the admin panel or scheduled tool

The next tier up adds a UI, a small database, or a scheduling layer. This is the shape that most small businesses with a website should also have underneath the website.

What it looks like:

• An admin panel where the owner manages products, prices, content, customers, or inquiries without calling a developer.
• A scheduled job with a small database that tracks state across runs, so it can email you only the things that changed.
• A small private dashboard that joins data from two systems and shows a single view.

What is included on top of the previous tier:

• Authentication (single user or small team).
• A small database (usually Supabase Postgres or SQLite).
• A simple but consistent UI that matches the rest of the business's tools.
• Hosting setup on a free or near-free tier.
• 60 days of small revision support.

Timeline: 3 to 5 weeks. The admin panels behind White Sail Split and Urban Design sit roughly here.

Tier 3: €3,000 to €5,000, the multi-piece tool

This tier covers tools that integrate with at least one external system, or that have multiple roles, or that need real reliability because the business runs on them.

What it looks like:

• A dashboard that pulls from a payment processor, a booking platform, and an inventory file, and reconciles them daily.
• A small workflow engine: when a customer submits an inquiry, run X, then Y, then send Z to the team.
• A multi-role internal tool: the owner sees one view, the staff sees another, the accountant exports a third.
• An integration glue layer that replaces a Zapier-plus-three-zaps stack.

What is included on top of the previous tier:

• API integrations (usually 1 to 3 external systems).
• More careful error handling and retry logic, because failures are visible to customers.
• Logging and a small debugging surface so the owner can see what ran and what failed.
• 90 days of small revision support.

Timeline: 5 to 8 weeks. The Start-List Generator on the portfolio is a small example of this tier, with the federation rulebook acting as the "external system".

Tier 4: €5,000+, custom application

At this point the tool is no longer a tool, it is a small custom application that the business runs on. Multiple users, real auth, complex permissions, integrations with payment systems, customer-facing components. These are scoped individually and overlap heavily with the higher tiers in the website cost breakdown.

Where the money actually goes

Just like custom websites, the build itself is a smaller share of the time than people imagine. For a typical internal tool:

• Discovery and rule extraction (~25%). This is where the value lives. Most internal tools encode rules that exist only in someone's head, and getting them onto the page in a form a computer can apply is the actual work. The code is downstream of this.
• Build (~35%). Writing the code, including the parsing, the transformation, the output formatting, the handover script.
• Edge case handling and QA (~20%). Real input data is messier than a sample. Half empty rows, currency formatting drift, encoding issues, the one customer whose record breaks every rule. Catching these before launch is what separates a tool that runs from a tool that breaks on the fifth invoice.
• Handover and documentation (~10%). The README, the one-pager on how to run it, the call where the team learns where the button is.
• Post-launch support buffer (~10%). A reasonable padding for the small things that come up in the first 30 to 60 days.

How this compares to renting

For a like-for-like SaaS, monthly cost typically runs €30 to €150 depending on the category. Compounded over three years, that is €1,080 to €5,400 with no asset at the end of it. The custom build sits at €500 to €5,000 once, and the asset is yours.

The math does not always favour custom. For genuinely universal needs (email, calendar, accounting), the SaaS is doing more for you than €5,000 of a developer's time would. I worked through the case-by-case version in Why Internal Tools Beat Another SaaS Subscription.

The hidden cost of NOT having one

The cost most owners forget to count is the manual workaround. If a junior staffer spends two hours a week at €20/hour producing a report by hand because the SaaS does not quite cut it, that is €2,080/year, paid out of the labour budget. A €1,500 custom version pays that back in nine months and disappears it from the team's calendar forever.

The same logic applies to errors. A single mis-sorted heat at a tournament means rerunning the event, embarrassed apologies, and a refund. A correct heat list, generated by code, costs nothing additional after build.

What the price tells you

If the quote you are getting is far below this range, the work is being treated as a freelance hourly script with no QA, no handover, no real support. It will run once.

If the quote is far above, you are paying agency overhead for a tool that does not need it, or the developer is misreading the scope as a custom application.

A quote inside the right tier, with a clear deliverable list and a fixed timeline, is what a serious freelance build of this kind looks like.

Work with me

I quote internal tools the same way I quote websites: free 30-minute discovery call, written quote with scope and timeline, fixed price, no surprises. Email info@tonibarisic.com or use the contact form. For the umbrella overview of the category, see Internal Tools for Small Businesses, A Practical Guide. For the build-vs-rent calculation, see Why Internal Tools Beat Another SaaS Subscription.