THE CENTRAL IDEA
Compare what will be delivered and what must be operated after handover. The lowest build price is not always the lowest ownership cost.
Separate three types of cost
There is setup cost: discovery, design, implementation, content and testing. There is operating cost: hosting, domain, external services and usage. And there is continuity cost: updates, monitoring, backup, recovery and improvements. State who pays and manages each item and what is included or excluded. This guide does not invent estimates without requirements or usage information.
Scope matters more than screen count
One approval screen can hide roles, states, audit requirements and integrations. Ask for journeys and exceptions, content readiness, languages, migration needs and acceptance criteria. Do not compare two proposals before checking that they address the same need and that testing, documentation and handover are not missing from one.
Ownership needs to be written down
Specify custom source, design rights, content and accounts separately from licensed components. Clarify when and how handover occurs and what modification and usage rights apply. Avoid making a business depend on an account it does not control. These are practical questions, not a legal interpretation of a contract; binding rights require agreement and specialist review where appropriate.
Example: a lightweight site versus an operational portal
An infrequently updated services site may have simpler operations than a portal with accounts, data and reports. But if editors publish daily, ease of content management becomes important. Compare scenarios across an ownership period appropriate to the owner, including hosting, support and migration, without assuming a free tier will always remain free or sufficient.
Maintenance is not an unlimited promise
Distinguish fixing a defect in agreed scope from dependency updates, new features or a redesigned journey. Define the support period, scope, reporting route and backup responsibility. Include a restoration test and review cost when usage changes. Clear terms protect expectations more effectively than the phrase “support included” on its own.
EDUCATIONAL EXAMPLE / REVIEWABLE STEPS
Comparison worksheet: ownership cost & handover
An educational worksheet populated from actual proposals using the same period and currency. Estimated cost = setup + months × monthly operation + annual items during the period + maintenance and transition; this example supplies no assumed prices or quotation.
- One-time setup: list discovery, design, content, languages, development, migration, testing and handover, marking every item included or excluded for each proposal.
- Fixed operations: enter monthly and annual hosting and subscription charges, renewal dates and account owners. Do not count annual fees twice inside monthly totals.
- Variable usage: separate messaging, storage, transfer, payment and AI assumptions. Record the billing unit, dated source and low, expected and high usage levels.
- Continuity: define dependency updates, monitoring, backups, restoration, support duration, reporting channel and ownership; distinguish defect resolution from new features.
- Ownership and transition: for code, design, content, domain, accounts and data, record owner, handover timing, export formats, licenses and known exit cost.
- Final comparison: align period, currency and tax inclusion and show unknown items as missing data. Do not treat blanks as zero or cost difference alone as evidence that a proposal is better.
COMPARE YOUR ASSUMPTIONS
A simple ownership cost calculator
Enter costs for two options using the same period and currency. Include maintenance, backups and usage in the appropriate category once, and use a consistent tax basis. No prices are assumed; enter zero when a category has no cost.
Complete the values to compare costs. Calculation stays local; no data is sent.
Compare fit, not popularity.
Setup
Fits: Design, content, development, testing and handover.
Consider: Scope changes or content delays may change cost and timing.
Operations
Fits: Infrastructure, services, usage and accounts.
Consider: Needs measurement, limits and ownership rather than guesses.
Continuity
Fits: Updates, recovery, support and improvement.
Consider: Duration, response and deliverables must be agreed.
This is decision support, not a service offer or a performance guarantee. Your final choice depends on your requirements and the versions selected at implementation.
Official sources for further reading
Cloudflare — Pages platform limitsopens in a new windowWordPress — security and maintenanceopens in a new windowOWASP — ASVSopens in a new windowSources describe technology characteristics. The scenarios and trade-offs are contextual guidance, not benchmark results.