Three-year ownership
Keep this out of the build total. Each year gets its own lines for hosting and maintenance.
The research on lifetime cost is consistent even when the figures differ. Published estimates of maintenance as a share of total lifecycle cost run from 67% (Schach) to over 90% (Erlikh), with annual maintenance for actively developed systems commonly set at 15 to 25% of the original build. Treat that as a starting anchor and refine it against your own integration count and compliance obligations. For deeper planning on this, work through our dedicated maintenance budget guidance.
Compare two fictional scopes
The two figures below are invented illustrations built to show how effort moves. They are not Evolved Ideas prices, and they are not benchmarks for your system. Both exclude tax and ongoing operation.
One approval workflow
A single approval workflow, estimated at 160 hours and priced at £75 an hour, gives £12,000 of labour. Add £2,000 of non-labour costs for environments and a licence, and the base is £14,000.
Apply 20% contingency once, against that stated base, and you get £16,800. That's the software development cost. Value added tax at the standard rate of 20% sits outside the figure, as does everything you'll pay from the day it goes live.
Expanded workflow
Now add one integration with your finance system and a reporting requirement for the people who approve. Effort rises to 240 hours, so labour is £18,000, and non-labour costs rise to £3,000 because the integration needs its own environment and test data. The base becomes £21,000, and £25,200 with the same 20% contingency.
Eighty extra hours for what sounds like two small additions. The integration brings mapping and error handling. The reporting brings decisions about what gets stored and who can see it, which is design work before it's development work.
Test every assumption
Every number above rests on an assumption that needs to be argued with before money moves. Evolved Ideas starts with in-depth consultation sessions to understand your processes and goals, then a structured workshop. The software development cost estimate comes after that work.
Three questions do most of the damage when left unasked. Who owns each interface, and what happens when the other side changes it? What is deliberately excluded from this scope? And who inside your organisation is accountable for the decisions that unblock delivery?
After launch, the questions change but don't stop. Tier 3 development support covers security patching and new features, which is the maintenance line in your three-year view made concrete. An early estimate is a position to be tested, not a quotation to be banked.
Compare proposals consistently
Suppliers will structure proposals differently, and the differences are where comparison breaks. Send the same checklist to everyone and ask them to answer in your format.
-
Scope statement in business outcomes, with exclusions written out explicitly
-
Hours by role, with the rate for each role shown separately rather than blended
-
Integrations listed individually, naming the system on the other side of each one
-
Data migration effort, including profiling and reconciliation
-
Environments and hosting as their own lines
-
Third-party licences, with who holds the contract
-
Client effort expected from your team, expressed in days by role
-
Contingency as a percentage, with the base it applies to and the rationale
-
Tax treatment stated, so net and gross are never confused
-
Three-year recurring costs by year, separated from the build
If your system includes a mobile element, estimate that against our mobile development guidance. The same applies to scoring the responses themselves, where a weighted model beats a side-by-side glance at totals. Both sit in their own guides.
Discuss your system
Bring us the workflow as it runs today and the interfaces you depend on. Evolved Ideas has built bespoke business systems since 2007 from our Leicester head office, and we test your scope assumptions with you. Book a 30-minute call through our contact page and let's examine the software development cost together before a proposal is written.