Budget for the whole project, not only the build invoice. Staff time, content, data, training, subscriptions, support, and ongoing running costs all matter.
01
Budget from scope drivers
Cost changes with the number of users, pages, workflows, integrations, data to move, access levels, tests, accessibility needs, reviews, and support requirements.
02
Include internal effort
You may need subject experts, content owners, technical contacts, approvers, testers, trainers, and a project lead. Set aside their time in the project plan.
03
Separate build and operation
List ongoing costs for hosting, software, domains, messaging, storage, maintenance, analytics, support, content, and campaigns. The project must remain affordable after launch.
04
Use phases when uncertainty is high
Pay for discovery first when requirements, integrations, content, or data are unclear. A smaller first phase is safer than pricing a large project based on assumptions.

