How much custom business software costs, and what it depends on

Custom business software has no list price: the cost depends on how many processes it has to handle, how many programs it has to connect, how many people will use it and from where. On top of development come costs that recur every year, such as servers, backups and maintenance. To get the budget right, start from a written analysis and a first working piece, and pay in phases.

What does the price of custom business software depend on?

The price depends mostly on how much work the software has to cover and how many systems it has to get talking to each other. These are the items that really make up the cost:

Take a 12-person business that sells spare parts over the counter and online. The heart of the software is orders, stock and customers. The cost goes up if it also has to read orders from the online shop, issue e-invoices, match incoming payments to bank transactions and give the two sales agents an app on their phones. Each of these pieces makes sense, but not necessarily all of them in the first phase.

You know the price before we start: a written quote after the assessment, in approved phases. A figure only means something once these items have been laid out for your case: that is what we do in the initial assessment, which is free.

Why do integrations count for so much?

Because every connection also depends on systems you do not control. An integration often goes through an API, the channel two programs use to exchange data: it has to be designed, tested on real cases and updated when the other system changes.

• E-invoicing. Since 1 January 2019, invoices between parties resident or established in Italy can only be electronic, and they go through the Italian Revenue Agency’s exchange system, the SdI (Sistema di Interscambio): if they do not go through it, they count as not issued. They must also be stored in a legally compliant way, with the Agency’s free service or a private provider. The software can send them to SdI itself or pass them to the invoicing program you already use: two options with different costs. For incoming invoices, see the guide on how to automate invoices and documents.
• E-commerce. Orders, stock levels and prices must stay in sync both ways, so you do not sell parts you do not have.
• Bank. Reading transactions and matching them to invoices often needs an external service linked to the account, which has its own cost.
• Accounting. It usually makes sense not to rebuild it from scratch, but to pass the data cleanly to the program your accountant uses.

Which costs do you pay once, and which every year?

You pay once for the work to build the software; every year you pay for what it takes to keep it running, secure and up to date. When you compare two proposals, look at the total cost over three years, not just the first invoice.

One-off costs

• analysis and design;
• development of the modules and integrations;
• data migration and clean-up;
• initial training and support alongside your team in the first days.

Recurring costs

• hosting, meaning the servers the software runs on, and backups;
• maintenance: bug fixes, security updates, and changes when the rules (for example the technical specifications of the e-invoice) or the connected programs change;
• pay-as-you-go external services: sending to SdI, storage, the bank connection, any AI models;
• new developments: the new features you will ask for after a few months of use.

Business software without maintenance does not stand still: it ages. The yearly fee to maintain it is part of the price, not an extra.

Custom, off-the-shelf or something in between?

Off-the-shelf software makes sense when it covers almost everything without forcing you to change the way you work; custom software makes sense when the way you work is what sets you apart. In between there is the hybrid option, often the most sensible one for an SME. According to ISTAT, Italy’s national statistics institute, 48.8% of Italian small and medium-sized businesses with at least 10 employees used an ERP in 2025. An ERP is the software that moves information between accounting, planning, production and marketing, and ISTAT itself notes that it can be standard, customised or built in-house.

An example of a hybrid: an 8-person engineering practice keeps its accounting and invoicing program and has only the missing piece built: job management with hours, expenses and progress, connected to the rest. When we design custom software, this is exactly the comparison we make in the initial assessment, and sometimes the answer is that you do not need custom software.

How do you read a quote for business software?

A readable quote is divided into phases, each with its own cost, its own timing and a result you can try out. Beyond the total, check:

• What is included and what is not. Data migration, training, testing, documentation and integrations are the items most often missing, and they turn up again later.
• How changes are handled. What happens if you ask for an extra feature halfway through: who estimates it and who approves it, before it is built.
• Who owns the code. Italian copyright law gives the business, unless agreed otherwise, the economic rights to software written by its own employees as part of their job (Article 12-bis of Law 633/1941). For an outside supplier there is no such clear-cut rule: the transfer of rights and the handover of the source code must be written into the contract.
• Data and access. Servers, domain and the accounts of connected services should be in your name. If the supplier processes personal data on your behalf, you need the data processing agreement required by Article 28 of the GDPR.
• Exit costs. How you will get your data back, in what format, how quickly and at what price if you change supplier. For standard cloud services, the EU Data Act (Regulation (EU) 2023/2854, applicable since 12 September 2025) requires the conditions for switching to another provider to be written into the contract, and any exit costs to be explained to you before you sign. A European Commission proposal of 19 November 2025, the “Digital Omnibus” package, aims to adjust these rules too: as of September 2026 it is still under discussion.

What makes the price go up?

The price goes up mostly because of decisions made at the start, not because of the technology. The most common mistakes:

1. Wanting everything in the first phase. The bigger the project, the harder it is to estimate and the later you see something working.
2. Copying the old system. Rebuilding today’s Excel sheet carries its flaws into the software too.
3. Changing the rules once work has started. New requests are normal, but without an estimate and a written approval they turn into surprise costs.
4. Underestimating the data. Duplicate customers, mismatched product codes, incomplete records: cleaning them up costs money, and it has to be done first.
5. Involving the people who will use the software too late. If the warehouse and the office only see it at the end, corrections come when they cost the most.
6. Choosing on the lowest total alone. A light quote is sometimes light because it leaves out items you will pay for anyway.

What should you ask the supplier?

The right questions tell you in half an hour whether a quote holds up. Take them to the first meeting:

1. What phases do you plan, and what will I be able to use at the end of the first one?
2. What is excluded from this quote?
3. Can I see a first working piece before committing to the whole thing?
4. Will the source code and documentation be mine? Where is that written?
5. Where will the data be, and in whose name will the servers and access be?
6. How much does it cost each year to keep the software running and up to date?
7. Who provides support, at what hours and with what response times?
8. If one day I wanted to change supplier, what would you hand over, and at what cost?

To assess the people in front of you as well, see the guide on how to choose who to trust with digitalising your business.

Where to start tomorrow

Before you ask for a quote, prepare three sheets: they take you a few hours and make the proposals more precise and easier to compare.

1. The process map. For each activity (order, shipping, invoice, payment received), write down who does it, with which program and where it gets stuck.
2. Today’s numbers. How many hours a week go on copying data, how many mistakes a month, how many orders. If you do not have them, the guide on the numbers to track in a small business will help.
3. The list of systems. Programs, files and services the software will need to read from or feed, with their suppliers.

With these three sheets, any supplier can give you a serious estimate. If you like, we can go through them together: here is how we work, in approved phases and with code that stays yours.