What are you actually asking a supplier to price?
Custom software development cost depends on the work included and the uncertainty still unresolved. A request for a customer portal could mean a simple document area or a complex service with several organisations, approval rules and integrations. A headline figure is difficult to compare until those differences are visible.
This guide does not give a universal UK price range or a Project Hero quotation. Instead, it provides a way to prepare a useful brief and compare estimates on the same basis. Ask suppliers to show their assumptions rather than treating an early estimate as a commitment to deliver every possible interpretation.
Describe one complete journey first. Include who uses it, what starts it, which systems provide information and what must be true when it finishes. Note the situations that could make the journey fail. That gives the estimator something more concrete than a list of screen names.
Separate discovery from delivery
Unknown requirements need investigation. Ask which questions can be resolved through a workshop, prototype, data sample or integration test, and what each activity will produce. Agree a stopping point so discovery ends with a decision rather than an expanding document.
The GOV.UK Service Manual describes discovery as understanding the problem, users and constraints before committing to a build. Its public-sector process is not a mandatory commercial project format, but the underlying distinction is useful: learning what to build is different work from delivering it.
Request an estimate that identifies known work, assumptions and unresolved dependencies. For example, access to a test environment may be required before an integration can be priced with confidence. Give the dependency an owner and explain what happens if it is unavailable.
Look at the drivers behind the estimate
User roles affect more than the number of login screens. Different permissions may require different views, approval rules and tests. Ask for a role list with the records each role can read or change. This can expose requirements that would otherwise appear late in development.
Integrations require clear boundaries. Record the systems involved, available interfaces, access arrangements and failure behaviour. Data migration also needs its own scope: what moves, how inconsistent records are handled and who confirms that the result is correct.
Quality requirements deserve explicit space in the budget. Agree the important accessibility, security, performance and recovery checks, with evidence expected at handover. Avoid accepting a quote that names testing but leaves everyone with a different idea of what it includes.
Compare quotations using the same worksheet
For each proposal, record the discovery deliverables, design work, included journeys, integrations, migration, testing, deployment and training. Add an exclusions column. Mark anything unclear as a question rather than assuming it is covered by the total.
Record the payment model and how changes are authorised. With a fixed scope, understand the acceptance criteria and exclusions. With time-based work, understand rates, reporting, budget controls and the decision points for stopping or changing direction. Neither format removes the need for clear communication.
Ask whether VAT and third-party charges are included. Record currency, quotation validity and payment milestones as stated by the supplier. Compare the commitment you would actually make, not a headline amount stripped of the services needed to operate the product.
Custom software development cost: comparison worksheet
Copy this worksheet once per supplier, using the same requirements for each. Write included, excluded or unclear beside each scope item. Ask for clarification wherever a blank could change the total commitment.
Proposal: [supplier, reference and date]. Currency: [currency]. Quote valid until: [date]. Payment model: [fixed scope / time-based / other]. Quoted amount or estimate: [amount and basis]. VAT: [included / excluded / clarification needed]. Payment milestones: [amounts and triggers].
Discovery: [deliverables and price treatment]. Design: [included work]. Core journeys: [list]. Roles and permissions: [list]. Integrations: [systems and boundaries]. Migration: [records, cleaning and verification]. Exclusions: [list].
Quality and handover: [testing, accessibility and security evidence]. Deployment: [responsibility]. Training and documentation: [deliverables]. Acceptance criteria: [location]. Repository, accounts and usage rights: [terms to confirm].
Running costs: [hosting, storage, paid services, monitoring and support]. For each charge record: [amount or rate, billing period, usage assumption, included allowance and overage basis]. Maintenance scope: [included work]. Support availability and response expectations: [terms].
Uncertainty: [assumption or dependency]. Owner: [name]. Evidence needed: [test or answer]. Cost effect if wrong: [supplier explanation]. Change approval: [who authorises work and how spend is controlled].
Comparison conclusion: [which proposal covers the agreed requirement]. Unpriced essentials: [items]. Clarifications required before commitment: [questions]. Do not calculate a comparable total until the scope, tax treatment and recurring-cost assumptions are clear.
First-year planning total = one-off quoted work + (12 × fixed monthly costs) + annual fees + estimated usage-dependent charges + any separately agreed contingency allowance. One-off work: [discovery + design/build + migration + other agreed setup]. Fixed monthly costs: [hosting + support + other recurring items]. Annual fees: [items]. Usage charges: [expected billable units × applicable rates]. Contingency: [amount or calculation basis, purpose and approval owner].
Calculation assumptions: [which 12-month period this covers]. Monthly services active for fewer than 12 months: [items and actual charged months; replace 12 for those items]. Usage scenario: [volume, included allowances, overage rates and billing rules]. Tax basis: [all amounts inclusive or all exclusive of applicable VAT, stated consistently]. Currency: [currency].
Check that bundled items appear only once: do not add discovery again if the build quote includes it, or annual fees already covered by monthly charges. Payment instalments are the timing of an existing cost, not extra costs. Keep an unspent contingency separate from the supplier quotation. Calculate a higher-usage scenario using stated assumptions; neither scenario is a guaranteed final bill.
Budget for the period after launch
Create a separate running-cost list covering hosting, storage, monitoring, paid services, maintenance and support. Ask which charges vary with users, messages, transactions or data volume. Use your expected activity and a higher-use scenario, with assumptions clearly labelled, rather than treating future growth as certain.
Clarify ownership and practical access to the repository, deployment accounts and documentation. Identify any third-party licences and the process for moving to another supplier. GOV.UK's technology guidance includes total ownership cost and avoiding unwanted lock-in among its decision considerations.
Do not assume a warranty, maintenance agreement and feature-development budget are interchangeable. Ask how the proposal distinguishes a defect, an operational incident and a requested change. Record support availability and response expectations rather than interpreting the word support as unlimited cover.
Reduce scope without weakening essential safeguards
A smaller first release can defer a secondary journey or manual convenience. It should still complete the agreed core task and handle its important failure cases. Review each proposed omission against the effect on users and the team operating the service.
Finish the budget with a decision log: what is included, what is postponed, what remains unknown and who can approve further spend. Revisit custom software development cost as assumptions become evidence. A useful budget is a controlled plan that can be updated, not an apparently precise number built on unanswered questions.