Budget guide
What belongs in a software implementation budget
Separate the work needed to create your version from the cost of running it.
Initial adaptation
This covers the engineering and acceptance work that turns a starting workflow into your agreed edition. Custom integrations and unusual operating rules can change this cost considerably. It needs a scoped quote.
Standard setup and migration
Branding, configuration and training can form a standard setup package. Historical data is different: mapping, cleaning, trial imports, access review and reconciliation can require separate work. Do not assume a setup fee includes every migration.
Recurring service
Identify hosting, backups, monitoring, maintenance and support responsibilities. Ask how changes are requested and priced. A subscription label is not a substitute for knowing what the supplier is responsible for.
Provider usage and regional amounts
Payment processing, email, SMS and other services may have separate charges. Confirm the currency, tax treatment, billing unit and any user minimum. A GBP proposal and a USD proposal are separate prices unless an exchange mechanism is expressly agreed.
Use a partial subtotal carefully
A one-time licence and setup package, or standard setup plus one year of managed service, is a useful planning subtotal. It is not the full implementation cost while adaptation, migration and third-party charges remain unknown.