What Custom Software Development Costs and Where the Money Goes
Most custom software quotes are hard to read because they price hours, not artefacts. Here is what each delivery stage produces, and which of those artefacts you should refuse to pay for twice.
Custom software development costs are driven by how many decisions must be made and documented before code is written, not by the number of screens you ask for. Judge any quote by three things: whether each stage names a deliverable you can inspect, whether the requirements document states what happens when a field is wrong, and whether the handover package lets another team take over without your original vendor. A quote that fails those three tests will cost more later, whatever the headline figure.
How much does custom software development cost, and what sets the figure?
A custom software cost estimate is only meaningful when it is tied to a defined scope, because the same feature can take three times longer if the approval rules behind it are unclear. The figure moves with four factors: how many roles touch each record, how many external systems must be integrated, how much existing data must be migrated and cleaned, and how strictly the software must log who changed what.
Two projects with identical screen counts can differ in price by a wide margin for one reason: one has a purchase order approval step with three exception paths, the other has a single approver. The delivery team controls estimation accuracy and engineering quality; the client controls how quickly decisions are made and how available the people who know the rules are.
That is why we quote stage by stage rather than as one lump. If you want to see how we structure that on the custom software development side, the stage list is public. If a vendor will not break the price down by stage, you cannot tell which stage is absorbing the risk.
What does the software development process actually produce at each stage?
Each stage of a software development process should end with an artefact the client can read, question and sign, because an unsigned artefact is where rework starts. The table below is the sequence we run, and the thing you should receive before the next stage begins.
| Stage | Artefact you receive | What it decides |
|---|---|---|
| Discovery | Process map with named roles and exception paths | Which steps the software replaces and which stay manual |
| Requirements | Software requirements document, field by field | What each field accepts, who may change it, what happens on error |
| Design | Screen flows and data model | Where a user lands after each action, and how records relate |
| Build | Working environment refreshed on a fixed rhythm | Whether progress is visible before the invoice arrives |
| Testing | Test log mapped back to the requirements document | Which requirement was proven, by whom, on what date |
| Handover | Software handover checklist plus source code and credentials | Whether another team could take over without you |
The requirements document is the stage that most often gets skipped, and it is the one that decides cost. A requirement that does not say what happens when a field is empty, duplicated or wrong will be rebuilt at least once. That rebuild is not a change of mind; it is a gap that was priced as if it did not exist.
Testing deserves the same treatment. A test log that says "invoice module tested" tells you nothing. A test log that lists each requirement, the person who checked it and the date tells you what was actually proven, and it is the document you rely on when a dispute arises six months later.
When should a business stop using spreadsheets?
A business should replace spreadsheets when more than one person edits the same file and the correct value depends on who edited last. That is the threshold, not company size. Below it, a spreadsheet is the cheapest tool you have; above it, every copy becomes a separate version of the truth.
Watch for these signals, in rough order of cost:
- Two people keep their own copy of the same customer or order list and reconcile them by email.
- A figure on a report cannot be traced back to the transaction that produced it.
- Someone rebuilds the same monthly summary by hand because the formulas break when rows are inserted.
- Access control is a shared password or a folder permission, and you cannot say who changed a price.
- An auditor, bank or customer asks for a history of changes and the answer takes days.
The last signal matters more in Madrid than in many markets. Spanish clients and auditors routinely ask for a traceable record of who changed an invoice or a price and when, and a spreadsheet cannot answer that question. If a wrong answer in the file would cost money or fail an audit, the decision to replace it is already overdue.
How long does it take to build a custom business system?
Duration depends on how many decisions the client can settle per week, not on how many developers are assigned. Adding people to a project whose requirements are still moving makes it slower, because each new person needs the context that has not been written down yet.
The delivery team controls the build rhythm and how quickly work is shown. The client controls two things that dominate the calendar: who has authority to approve a rule, and how fast existing data can be cleaned. Data migration is the stage most often underestimated, because legacy records usually contain duplicates and free-text fields that must be mapped to a fixed list before anything can import.
For a legacy system replacement, expect the old system to run in parallel for a period you choose, with both systems live. That overlap is a cost, and it is a deliberate one: plan the parallel run before the build starts, because it sets the real go-live date. Bespoke business software that goes live on a date nobody tested against is the most expensive kind.
What should be included in a software handover?
A software handover checklist should let a development team you have never met rebuild and redeploy the system from what you were given. If it cannot, you do not own the software; you rent access to the people who built it.
The checklist should include, at minimum:
- Source code in a repository you control, with commit history intact.
- Build and deployment instructions that someone else has followed successfully.
- Database schema and a description of each table's purpose.
- Credentials and third-party accounts transferred into your name, not the vendor's.
- The requirements document and test log, kept as the record of what was agreed.
- A named contact period for defect questions, with the end date written down.
The credential item is the one that causes real damage. If a domain, cloud account or payment integration sits in the vendor's name, your leverage ends when the contract does. We transfer those accounts into the client's name before go-live rather than after, because the transfer is easier while both teams are still working together. Businesses working across language boundaries should also confirm that documentation is written in a language their own staff can maintain; our Chinese-speaking developers handle that as a delivery requirement, not an add-on.
Where does the money actually go?
Most of the budget goes into the stages that produce no visible screens: requirements, testing and data migration. That is not overhead. A screen is cheap once the rule behind it is settled, and expensive when it is not.
When you read a quote, map each line to an artefact in the table above. Lines that map to a document you will receive are defensible. Lines that map to nothing you can inspect are where you should ask questions. If a line item cannot be tied to a deliverable, treat it as unverified until the vendor names one.
Our own practice is to keep the requirements document and the test log in the client's repository from the first week, so the record exists regardless of who continues the work. We deliver custom software, business systems, mobile apps, websites, IoT systems and AI applications from Chengdu, and the stage list stays the same across all of them. If your operations span both China and Spain, the Madrid page covers how we handle the working-hours overlap.
Frequently asked questions
How much does custom software development cost?
There is no universal figure, because custom software development cost depends on how many roles touch each record, how many systems must be integrated, how much legacy data needs cleaning and how strictly changes must be logged. A quote is only comparable to another when both are tied to the same requirements document. Ask for the price broken down by stage so you can see which stage carries the risk.
How long does it take to build a custom business system?
Duration is set mainly by how fast the client can approve rules and clean existing data, not by team size. Projects with unclear approval paths run longer regardless of how many developers are assigned. Plan a parallel run with the old system before the build starts, because that overlap sets the real go-live date.
When should a business stop using spreadsheets?
Stop when more than one person edits the same file and the correct value depends on who edited last. Other signals include reports that cannot be traced to a source transaction, manual monthly rebuilds and shared passwords instead of access control. If a wrong answer in the file would cost money or fail an audit, the replacement is already overdue.
What should be included in a software handover?
A handover should include source code in a repository you control, build and deployment instructions that someone else has followed, the database schema, the requirements document and test log, and all credentials transferred into your name. It should also name a defect-support period with a written end date. If another team cannot rebuild and redeploy from the package, you do not own the software.
What is the difference between custom software and off-the-shelf tools?
Off-the-shelf tools encode someone else's process, so you adapt your approvals and reports to fit them. Bespoke business software encodes your process, which costs more at the requirements stage and less at the workaround stage. The trade is worth making when your process is a source of advantage or when a regulator or auditor needs a traceable record.
Questions we are asked
How much does custom software development cost?
There is no universal figure, because custom software development cost depends on how many roles touch each record, how many systems must be integrated, how much legacy data needs cleaning and how strictly changes must be logged. A quote is only comparable to another when both are tied to the same requirements document. Ask for the price broken down by stage so you can see which stage carries the risk.
How long does it take to build a custom business system?
Duration is set mainly by how fast the client can approve rules and clean existing data, not by team size. Projects with unclear approval paths run longer regardless of how many developers are assigned. Plan a parallel run with the old system before the build starts, because that overlap sets the real go-live date.
When should a business stop using spreadsheets?
Stop when more than one person edits the same file and the correct value depends on who edited last. Other signals include reports that cannot be traced to a source transaction, manual monthly rebuilds and shared passwords instead of access control. If a wrong answer in the file would cost money or fail an audit, the replacement is already overdue.
What should be included in a software handover?
A handover should include source code in a repository you control, build and deployment instructions that someone else has followed, the database schema, the requirements document and test log, and all credentials transferred into your name. It should also name a defect-support period with a written end date. If another team cannot rebuild and redeploy from the package, you do not own the software.
What is the difference between custom software and off-the-shelf tools?
Off-the-shelf tools encode someone else's process, so you adapt your approvals and reports to fit them. Bespoke business software encodes your process, which costs more at the requirements stage and less at the workaround stage. The trade is worth making when your process is a source of advantage or when a regulator or auditor needs a traceable record.
