How to budget a digital project realistically
A digital budget is a set of choices over time, not just a build price. A credible plan separates initial work, recurring operations and uncertainty, then connects each cost to a useful outcome and a named responsibility.
What to remember.
- Budget for discovery and content, not only production.
- Separate launch costs from recurring ownership.
- Protect a contingency for evidence-based changes.
Price the result, not a feature list
Begin with the business and user outcomes that justify investment. Features should earn their place by supporting those outcomes. Removing a low-value integration can free budget for content, accessibility or testing that improves the whole service.
Separate the work into phases
Distinguish discovery, design, content, implementation, migration, quality assurance and launch. This reveals dependencies and makes it possible to stop, learn or adjust before committing the entire amount.
Include internal effort
Reviews, content preparation, legal validation, data cleaning and stakeholder workshops consume real time even when they do not appear on a supplier invoice. Assign owners and estimate availability before agreeing to a schedule.
Calculate recurring costs
Hosting, licences, support, security updates, analytics, translations and content governance continue after launch. Record renewal dates, price assumptions and the person responsible for each service.
Make uncertainty explicit
Use a contingency for unknown legacy systems, data quality or approval delays. A short paid discovery phase may reduce uncertainty more effectively than asking suppliers to hide risk inside a fixed price.
Link trade-offs to priorities
When the budget is constrained, reduce scope deliberately: fewer journeys, a smaller catalogue or one language at launch. Avoid cutting invisible essentials such as testing, backups or accessibility without documenting the risk.