Scope you refuse to cut
Every feature adds design, build and test time. Ten finished features beat thirty half-started ones.
COST GUIDE
Custom software development cost is set by the workflow you are replacing, not by a rate card. The bands below are the same indicative ranges this guide already published. The rest of the page shows how to read them and how to keep a first release inside one band.
Get a project estimateMost requests fall into one of these three bands. Find the closest, then use the drivers to see which end of the band you are nearer.
A dashboard, approval workflow, or report generator that replaces a spreadsheet process.
A customer portal, booking system, or CRM with user roles, integrations, and reporting.
Several connected modules, multiple user types, APIs, and ongoing releases. Often delivered in stages.
These are indicative ranges for projects built by a small, senior team. They are a planning guide, not a quote. A real estimate depends on your scope, integrations, and how much of the design is already decided.
Six factors explain most of the gap between a small tool and a platform.
Every feature adds design, build and test time. Ten finished features beat thirty half-started ones.
One team sharing a tool is simple. Admins, staff, customers and partners each need screens and checks.
Payments, accounting, an ERP or a third-party API need a connection, a failure plan and upkeep when that service changes.
A conventional interface costs less than a full design system with many unique screens.
Audit trails and stricter access add planning and tests. Cheaper quotes often leave them out.
Moving records out of an old tool, or fitting the new one beside it, can match the cost of the new screens.
How the work is bought changes who carries the risk of a vague brief.
| Model | Choose it when | What you direct | What to watch |
|---|---|---|---|
| Fixed scope | The first release is described in plain language | You accept that release against written criteria | Later ideas are estimated on their own |
| Staged milestones | You want to learn from the first users before committing the rest | You release budget stage by stage | Each stage needs a review, not a status email only |
| Dedicated team | The work will continue and the order will change | You prioritise a roadmap | Idle weeks still cost money if nobody is deciding |
The build is not the whole budget. Hosting, security updates, bug fixes and small improvements continue for as long as people rely on the software. This guide’s existing planning guideline is to set aside roughly 15 to 20 percent of the original build cost each year, adjusted for how fast the product changes.
Also ask what handover includes: documentation, a session with the people who will operate it, and a defined support period. Those are worth more than a slightly lower build price if they decide whether the next team can continue the work.
Cut work that does not change the first outcome.
Illustration only, not a client and not a quote. An operations team tracks approvals in a spreadsheet: a request arrives by email, a manager types a yes or no, and someone copies the result into another sheet. The first release is a form, two roles (requester and approver), a status, and a simple list. No customer login, no mobile app, no accounting sync.
That is the internal-tool band ($5k to $15k). It becomes a business system ($15k to $50k) if customers submit the request themselves, if finance must see a matching record, or if the old spreadsheet’s history has to be imported and cleaned. It becomes a platform only when several departments each need their own module and the modules must share one record.
Write the version you mean. Otherwise one supplier prices the spreadsheet replacement and another prices the platform.
Narrower ranges sit on the web application development cost, CRM software development cost and MVP development cost pages. A Laravel delivery team is described under offshore Laravel development.
THE FIRST STEP
A short description of who does the work today is enough to start. We will separate a first release from the later list and say which band that release sits in.
Start a project conversationThe useful number is a range with its assumptions written down. We split what the first release must do from what can wait, then show which decisions would move the range. That is easier to compare than three totals with three silent scopes.
The indicative bands here are $5,000 to $15,000 for an internal tool, $15,000 to $50,000 for a business system, and $50,000 to $150,000 or more for a multi-module platform. They are planning ranges for a small senior team, not a quote.
The first invoice usually is. Over several years the comparison also includes licences, workarounds and how badly a packaged tool fits. Custom tends to fit when the workflow is specific or the subscription still needs constant manual glue.
They include different design depth, testing, migration, training and support. A low price that leaves those out often costs more once the software is in use. Compare the included list first.
Yes. Milestones release budget as each stage is delivered and reviewed. That also lets you change the later list after the first release is in use.
You pay for capacity on your roadmap instead of a single fixed scope. It fits when priorities move often and someone on your side can order the work. The monthly amount is in the proposal, not on this page.
A common planning guideline already used in this guide is roughly 15 to 20 percent of the original build cost each year for hosting, fixes and small improvements. The right figure depends on how fast the product changes and how many people rely on it.