Cost is often the first question, but it is rarely the most useful one to start with. The right question is: compared to what? A custom internal tool is not just a line-item expense — it is a comparison against the ongoing cost of the alternative, whether that is SaaS subscriptions, manual labour, or a combination of both.
That said, real numbers are useful. Here is a straightforward breakdown of what custom internal tools actually cost, what drives those costs, and how to think about the comparison honestly.
What determines the cost
The cost of a custom internal tool comes down to four factors: scope (how much functionality), complexity (how many edge cases and rules the system needs to enforce), integrations (how many external systems it connects to), and how much polish the user interface requires for non-technical users.
Simpler tools with a limited feature set and a small number of user roles cost less. Systems covering multiple workflows, multiple data sources, and complex permission structures cost more — not because custom development is inefficient, but because there is genuinely more to build and test.
- Number of distinct features and workflows covered
- Number of user roles and permission levels
- Volume and complexity of third-party integrations (each API adds scope)
- Data migration requirements from existing spreadsheets or systems
- Reporting and dashboard complexity
- Required level of UI polish for end users
Typical cost ranges by project type
These ranges reflect real-world costs for SME-scale internal tools. They cover design, development, testing, deployment, and initial configuration — not just code.
- Simple dashboard or data viewer: €4,000–€9,000
- CRM replacement or scheduling system: €9,000–€20,000
- Multi-module operations platform: €18,000–€40,000
- Multi-tenant SaaS platform: €28,000–€58,000+
These are initial build costs. Hosting and maintenance run separately — typically €100–€450 per month depending on infrastructure requirements — covering uptime monitoring, security updates, and bug fixes. We quote this as a fixed monthly figure before anything goes live.
How custom compares to SaaS over time
The most common mistake in this comparison is treating a SaaS subscription as if it were free, or low-cost. Per-seat pricing compounds quickly.
A fifteen-person team on a €50 per-seat-per-month tool costs €750/month, €9,000/year, €27,000 over three years — for software that may not fit your process, may not integrate with your stack, and can change its pricing at any point.
A custom tool in the €12,000–€18,000 range — paid once — fits your exact workflow, carries no recurring seat fees, is owned permanently, and gets maintained and updated as your operation changes. The three-year total cost of ownership is frequently lower than the equivalent SaaS, and the tool actually works the way your process works.
The break-even for most SME-scale internal tools is in the 18–30 month range. After that, every month the system runs is pure savings compared to the subscription alternative.
Thinking through the build vs buy decision more broadly? We cover the full framework, including the hidden cost of workaround labour.
Build vs buy software: how to make the right decision →What ongoing costs look like
Beyond the initial build, a maintained custom system involves:
- Hosting and infrastructure: €100–€400/month depending on usage and architecture
- Maintenance: monitoring, security patches, bug fixes, and minor updates — included or quoted as a fixed monthly figure
- Feature additions: scoped and quoted individually as your business needs change
The maintenance cost is what keeps the system running well over time. It is also what distinguishes a system that works reliably in year three from one that degrades. We quote hosting and maintenance as a clear figure at the start of every project.
Getting an accurate estimate
Vague requirements produce vague quotes. The only way to get a realistic number is to describe what the tool actually needs to do. What to prepare before a scoping conversation:
- The core workflow the tool needs to support — written out step by step if possible
- The number of people who will use it and what they each need to do
- The existing systems the tool needs to connect to
- Whether you have existing data that needs to be migrated across
- Any hard requirements: compliance, data residency, hosting location
We build custom internal tools for SMEs across Europe — and take responsibility for hosting and maintaining everything we ship.
Custom internal tools overview →