For agenciesScope My Project

Cost guide

What shapes the cost of custom software development?

There’s no honest single price for custom software. Investment depends on scope, complexity, integrations and delivery choices. This guide explains what drives it — and how to get a quote that reflects your project.

Request a Tailored QuoteAssess Your Scope

Scopeivo editorial · Updated October 9, 2026

Why this guide has no price list

Two custom software projects with the same label can differ several times over in effort. Published price ranges hide that difference and anchor conversations on the wrong question. A useful quote starts from your scope: the capabilities, users, integrations and quality bar your first release needs.

The biggest cost drivers

  • Business rules and workflow complexity

    High impact

    Undocumented rules and exceptions are the biggest source of unplanned effort.

  • Legacy systems and data migration

    High impact

    Replacing or connecting older systems requires discovery, mapping and parallel running.

  • Integrations

    High impact

    Each connected system needs agreed contracts, test environments and monitoring.

  • Roles, approvals and audit

    Medium impact

    Approval chains and audit history add design, permissions and testing work.

  • Reporting and automation

    Medium impact

    Automated steps and management reporting depend on a clean, well-defined data model.

  • Hosting, security and support model

    Medium impact

    Availability targets, security reviews and long-term support shape the delivery plan.

How complexity changes the work

Scopeivo classifies projects into four published levels. More complexity means more design, engineering, testing and coordination — not a fixed amount.

  1. Simple

    A focused internal tool that replaces one spreadsheet-driven process.

  2. Moderate

    A multi-step workflow with roles, notifications and a few integrations.

  3. Advanced

    Department-wide systems with complex rules, data migration and several integrations.

  4. Enterprise-level

    Core business platforms with high availability, audit, single sign-on and many connected systems.

Team and delivery considerations

Most projects need a product lead, a designer, engineers and quality assurance, though not always full time. Elapsed time also depends on review cycles, content and data readiness, and how quickly decisions are made on your side.

How to get an accurate quote

Partners can only price what they understand. Share these details and ask each partner to state inclusions, exclusions and assumptions.

  • The outcome the first release must achieve, and what is out of scope.
  • Who will use the product and what each group needs to do.
  • Existing systems, data sources and integrations.
  • Your preferred launch window and any fixed business dates.
  • Who reviews and approves decisions on your side.
  • Optionally, a confidential investment range to frame the proposal.

Your brief does most of this for you. The Project Scoper captures each item in about ten minutes.

Scope My Software Project

Fixed price or time and materials?

A fixed price limits some uncertainty only when scope and acceptance criteria are clear. Time and materials offers flexibility, but needs a spending cap, a reporting cadence and a clear process for changing priorities.

Common mistakes

Comparing a fixed price with a time-and-materials proposal without checking scope; forgetting content and data work; treating a preferred launch date as a validated plan; and leaving accessibility and security until late in the build.

Methodology

This guide is editorial and qualitative. Impact levels describe typical effort, not prices, and Scopeivo does not present estimates as market data. How Scopeivo assesses projects. For an independent process reference, see the GOV.UK discovery guide.

Custom software guideHow to compare proposals