Skip to main content
Redergo
Software development

Custom software development: when it pays off, what it costs and how it works

8 minutes read
Custom software development: when it pays off, what it costs and how it works

Custom software development pays off when a company's processes differ from those an off-the-shelf product expects, when it needs integrations a package does not offer, or when licences and workarounds cost more than a system built for the job. A first useful release usually takes 2-3 months, a complete platform 4-8 months.

What custom software development is

Custom software development means building an application around the processes of a specific company, instead of adapting the company to a product designed for everyone. The result can be an internal platform that replaces spreadsheets and email, a portal for customers and suppliers, a management system with your own rules, or a product to offer to others, such as the debt recovery platform Rekupero.

The difference from off-the-shelf software, a licensed management package or a subscription service, is not the technology. It is who decides what the software does. With an off-the-shelf product the vendor decides, for thousands of customers. With custom software you decide, for yours.

Custom software or off-the-shelf: the comparison

  • Time to start. Off-the-shelf: 2-6 weeks. Custom: 2-3 months for a first release.
  • Cost model. Off-the-shelf: recurring licence plus configuration. Custom: initial investment plus maintenance.
  • Processes. With off-the-shelf you adapt to the product; with custom software the software follows your processes.
  • Integrations. Off-the-shelf: the ones the vendor provides. Custom: the ones you need, via API.
  • Evolution. Off-the-shelf follows the vendor's roadmap; with custom you set it.
  • Ownership. Off-the-shelf: a licence to use. Custom: your code and your data.
  • Main risk. Off-the-shelf: dependence on the vendor and costs that grow with users. Custom: a project poorly defined at the start.

Neither path is better in absolute terms. For accounting, payroll and tax compliance an off-the-shelf product is almost always the right choice: the rules are the same for everyone and someone else updates them every year. Custom software is for where your company works differently from the others.

When custom software pays off

There are usually four signs, and they tend to show up together.

  1. Exceptions are the rule. Every job is different, price lists vary by customer, warehouse flows are unusual. An off-the-shelf product handles them with free-text fields, parallel Excel sheets and manual work.
  2. The same data is entered more than once. An order that moves from email to spreadsheet to delivery note is a cost paid every day, in time and in errors.
  3. Systems don't talk to each other. E-commerce, ERP, CRM and accounting live apart and someone bridges them by hand.
  4. The process is your advantage. If the way you work is what sets you apart from competitors, using the same tool they use flattens it.

It does not pay off if the process is standard, if configuring an existing product well is enough, or if the budget does not also cover maintenance in the following years: custom software left untouched ages like any other.

Often the right answer is a mix: the package for accounting and compliance, custom modules where the package falls short, connected via API. For management systems, what we build and how it connects to what is already there is on the page for custom management software.

How to decide in practice

The quickest way is to map your current processes with the people who use them every day, not only with management, and split them into those common to your sector and those specific to your company. If around 70% are common, start from an off-the-shelf product; if 70% are specific, from custom software. How often they change matters too: processes that change every year pay back custom software sooner, processes that stay stable for years sit well in a ready-made product.

The mixed route only holds if the product you start from has stable, documented APIs. If the vendor changes them without notice or charges for access to the data, the modules built on top become fragile. We run this mapping in two or three meetings before proposing anything, and sometimes the conclusion is that the off-the-shelf product was already the right choice.

How much custom software development costs

There is no figure that fits everyone: an internal application with a few screens and a management system covering orders, warehouse and jobs sit on different orders of magnitude. The price comes down to three factors.

  • Features. How many and how complex. A searchable customer register costs little; an engine that calculates prices with different rules for each customer costs much more.
  • Integrations. Every external system, whether ERP, e-commerce, courier or accounting, adds work, especially if it exposes no API.
  • Infrastructure and users. An internal application for ten people and a public platform for thousands of users have different needs for security, performance and hosting.

That is why a serious quote comes after analysing workflows, data and systems, not before. Two things can be said in advance, though.

  • Maintenance is a recurring cost. Each year it is typically 15-25% of the initial cost and covers security updates, small improvements and support. Budget for it from day one.
  • Compare with off-the-shelf over five years, not on the first-year price: per-user licences, add-on modules, paid customisations and hours lost to manual work. In complex scenarios the break-even point usually comes between the third and fourth year. We wrote about the costs old software hides in a separate article.

To keep the initial investment down, start with a first release containing only the essential features, and add the rest once that first piece has proven itself.

How long it takes

A first useful release, meaning a version with only the essential features, typically takes 2-3 months. A complete platform takes 4-8 months. For a management system, a first module in production takes 2-3 months and a system covering orders, warehouse and jobs six months or more.

You don't have to wait for the end: with incremental releases the first piece delivers value while the rest is still being built.

How a project works, step by step

  1. Analysis. Workflows, data and existing systems are studied together with the people who use them every day. The output is a map of what to build and in what order, and a detailed quote. To prepare the starting material: how to write a brief for a software house.
  2. Design. Interfaces and architecture, validated before writing code.
  3. Development in sprints. Two-week cycles in which you plan, build and test together. Initial estimates change along the way, and that is normal: sprints exist precisely to correct course early.
  4. Data migration. The longest part is usually not the technical one but the clean-up: duplicate records, codes used differently by different departments, free-text fields where everyone writes their own way.
  5. Release and support. The system goes into production one module at a time, without stopping work, and from there maintenance and improvements continue.

Two real examples

An internal platform for a manufacturing company. Daily work ran through spreadsheets and email threads. We built a single web tool from scratch to replace both: manual work down 90%, zero data entry errors, a return of three times the investment in the first year.

B2B orders for A Tavola. The same order was retyped across email, spreadsheet and delivery note. By connecting the ordering channel to internal management, the order is entered once and flows through to preparation: manual re-entry down 66%, zero transcription errors. The A Tavola project.

How to choose a supplier

Five questions to ask before signing.

  • Will the code and data be mine? They should be, with documentation and exports in open formats. Otherwise you have swapped dependence on a product for dependence on a supplier: more on this in how to avoid vendor lock-in.
  • Who actually writes the code? Talking from the start with the people who will write it keeps requirements from getting lost between sales and development.
  • How does it integrate with what I already have? A serious answer talks about APIs, about what to do when a system does not expose them, and about the limits that brings.
  • How do we work during the project? Frequent releases and the chance to see and try the software every two weeks, not only at final delivery.
  • What happens after release? Maintenance, response times and annual costs should be put in writing before starting.

Before you decide

Custom software makes sense where the way you work differs from everyone else's and an off-the-shelf product forces you to compensate by hand. Before deciding, compare the cost over five years, not just the first quote, and choose a supplier who leaves you the code.

If you are evaluating a project, the first consultation is free: tell us about the process you want to digitalise and we will tell you whether custom really pays off. See our custom software development or get in touch.

Frequently asked questions

Is custom software better than customising the management system I already have?

If your current system exposes APIs and covers most of your processes well, keep it and build only the missing part as custom software, connected via API. Replace it entirely only when the existing system makes the data unusable in any way.

Can you start with an off-the-shelf product and move to custom later?

Yes, and it is a pragmatic middle ground. Start with a product that has open APIs, build custom modules for the processes that make the difference and, when it is justified, migrate fully. It works if the vendor does not block integrations.

How much does custom software maintenance cost?

Typically 15-25% of the initial cost every year. It covers security updates, changes needed when external systems evolve, small improvements and support.

How much does custom software cost?

It depends on features, integrations and number of users: an internal application with a few screens and a complete management system sit on different orders of magnitude. The quote comes after analysing workflows, data and the systems to integrate, and the first consultation is free.

What do you need to ask for a quote?

A description of the process you want to digitalise, who will use the software and how many people, which systems it must connect to and the volumes involved (orders, documents, users). You do not need a technical specification: it is built together during the analysis phase.

Related questions

  • When does custom software pay off compared with an off-the-shelf product?
  • How much does custom software development cost?
  • How long does it take to develop custom software?
  • How do you choose a software house for a custom project?

Do You Have a New Project?