What custom software really costs a small business — and what drives the price
How custom software is scoped and priced, which features drive cost, and how to get a build that pays for itself instead of an expensive prototype.
Custom software quotes vary wildly because the word covers everything from a booking form to a multi-branch inventory system. Understanding the four cost drivers lets you compare quotes properly and, more usefully, shape the project so the first version costs less and ships sooner.
The four things that actually drive cost
- Number of distinct user roles — each role means its own screens, permissions and testing
- Integrations — payments, SMS, accounting or courier APIs each add real work and ongoing maintenance
- Data complexity — a flat list of records is cheap; stock movement across branches with audit history is not
- Reliability requirements — a tool used by five staff differs enormously from one customers rely on 24/7
Typical shapes of project
A single-purpose internal tool — job logging, a booking queue, a simple stock register — is generally a two to four week build with one role and no external integrations.
A customer-facing platform with accounts, payments and notifications is a multi-month project because every path needs securing, testing and a support plan.
The most expensive mistake is starting at the second shape when the business only needed the first. Almost every successful system began as a narrow tool that earned its expansion.
How to scope a first version that pays for itself
- 1Write down the single most expensive manual process in the business, with its weekly hours.
- 2Describe the smallest software change that removes most of those hours.
- 3List everything else as version two and refuse to negotiate it back in.
- 4Agree what 'done' means in writing — screens, data, and who can use them.
- 5Budget separately for hosting, support and changes after launch; software is never finished on delivery day.
Build, buy or adapt
Off-the-shelf software wins when your process is standard — accounting, email, basic e-commerce. Custom software wins when the process is your competitive advantage or when the off-the-shelf option forces you to work backwards.
A common middle path is adapting an existing platform with custom integrations and a small purpose-built layer on top. It is often the fastest route to value.
What a good quote includes
- A written scope with named screens and user roles
- The technology stack and where the system will be hosted
- Who owns the source code — the answer should be you
- A support and change process after launch
- A realistic timeline with milestones, not one delivery date
Frequently asked
Do I own the code you write for me?+
Yes. Clients own the source code for work delivered, with a copy handed over at completion along with deployment documentation.
Can we start small and expand later?+
That is the recommended approach. A tightly scoped first version proves the value quickly and funds the next stage from real savings.
What ongoing costs should I expect?+
Hosting, domain and any third-party service fees, plus an optional support arrangement for updates and changes. These are quoted separately and clearly.
Need this done for you?
Have a manual process eating your week? Book a consultation and get a scoped, written estimate.