Guide for companies
Custom business software
Updated July 2026
Almost every company reaches the point where spreadsheets stop coping: data lives in three places, someone retypes numbers by hand, and nobody is sure which version is current. The question is always the same: buy something off the shelf, or have it built? There is no universal answer — it depends on how much your way of working resembles everyone else’s.
When it pays off, and when it does not
Custom makes sense
- The process you want to digitise is your competitive advantage: doing it the way everyone else does would cost you exactly that.
- You have tried ready-made products and the real work always falls outside them, handled by hand.
- You need systems that do not talk to each other to do so: machines, accounting, stock, e-commerce.
- You pay several subscriptions that together exceed the cost of owning the solution.
- The constraint is regulatory or industry-specific and generalist products do not cover it.
Off-the-shelf is better
- An existing product covers 80% of what you need: adapting how you work costs less than writing software.
- The process is standard: routine accounting, e-invoicing, payroll.
- Nobody internally can follow the project: without an internal owner, even the best supplier stalls.
- You need it working in two weeks: custom is not realistic.
- The budget covers development but not maintenance: unmaintained business software becomes a problem within a year.
What it can cover
Custom software does not have to do everything: it has to cover the points where you lose time or accuracy today.
Orders and jobs
From quote to delivery, with progress visible to everyone instead of living in one person’s head.
Stock and materials
Real stock levels, reorder points, batch traceability and links to purchasing and production.
Job sheets and hours
Technicians record the work on site from a phone: no sheets to retype back at the office.
Production and machines
Shop-floor progress, data collected from the machines, stoppages and their causes — without manual entry.
Customers and suppliers
Full history of communications, documents and terms, available to those who need it and only to them.
Dashboards and control
The few numbers that matter, updating themselves: margins, delays, workload.
How to start without a false step
The reliable way is not to define everything upfront: it is to start small on something measurable.
1. Pick a single process
The one costing you the most time today. Software that starts by covering one process well is worth more than one covering five badly.
2. Measure where you are
How many hours a month are lost, how many errors, how many manual steps. You need it to judge afterwards whether the software actually helped.
3. Have a first useful version built
A few features that go into real use immediately. It is the only way to discover what was actually needed: no document says it as precisely as daily use.
4. Grow on what gets used
Every addition starts from an observed problem, not a list written a year earlier. That way the budget follows the value.
What it costs
Custom business software covering a single process typically starts around €8,000. Once it spans several departments, handles per-role permissions and integrates with systems already in use, it passes €50,000 quickly. The number of processes and integrations weighs far more than the visual design. On top of the build, budget maintenance at roughly 15–20% a year.
Frequently asked questions
What does custom business software cost?
It starts around €8,000 to cover a single process well, and passes €50,000 once it spans several departments and integrates with existing systems. The heaviest variable is not the number of screens but how many integrations are needed and how clear the process is.
How long does it take?
A first useful version on a single process typically takes 2-4 months; a system spanning several departments 6 to 8 months. Timelines usually stretch for non-technical reasons: waiting on data, access to existing systems, and internal decisions.
Does my company own the software?
It should, and it belongs in writing before you start, not after. Check that the contract assigns you ownership of the source code and that it is handed over: that is what lets you change supplier without starting again.
Can it talk to our machines?
Yes, and it is one of the most common uses: production data is taken from the machines over protocols such as OPC UA or Modbus and delivered into the system. The demanding part is almost always integration with the systems already in use, not the collection itself.
Freelancer or software house?
For software covering one or two processes, a good freelancer is often the more efficient choice: lower cost and direct communication. For systems spanning the whole company and expected to run for years, the continuity of an organisation is worth the higher price.
How do I avoid depending on one person?
Put three conditions in the contract: the code is yours and is handed over, the software is documented enough for someone else to work on it, and it uses widespread technology rather than the supplier’s proprietary solution.
See also: how to find freelance developers · industrial automation and PLC.
Is a process costing you time?
Describe it anonymously on Araknet: receive offers from freelance developers with price and timeline, and choose at your own pace. No commission on the work.
Post your project