Buy a website or choose an ongoing managed service?

The labels “buying” and “managed service” reveal little about the actual scope on their own. A one-off project may include a thorough handover or only the finished website. A monthly model may be little more than rental, or it may combine creation, operation and ongoing work. Compare the responsibilities and deliverables, not just the labels.

The real difference: what happens after launch?

A purchase model usually centres on a defined project: plan, create, approve and hand over. You then organise operation and future development yourself or commission them separately.

In a managed monthly model, launch is not the finish line. Hosting, technical maintenance, troubleshooting and agreed updates form part of the ongoing relationship. In return, you commit to a provider for an agreed period and should understand the exit route before you sign.

A purchase model can fit when you can secure ongoing operation

A defined project handover makes sense when someone can reliably handle hosting, updates, backups, technical errors and content. That may be a person inside the business or an existing technical partner.

Work does not disappear after a purchased website goes live. Domains renew, systems change, content ages and forms still need to work. Plan for the next few years, not only for the build.

• You want a clearly defined handover at the end of a project.
• You have technical ownership and time for regular maintenance.
• You can make later updates yourself or commission them individually.
• You know which accounts, licences and files are required for operation.

A managed model can fit when you want one point of contact

For many self-employed professionals, creating a website is not the main problem. Maintaining responsibility over time is. A managed model can bring this together: one point of contact for design, content, hosting, technical maintenance and an agreed update allowance.

This is particularly useful when your offer is focused, you expect regular small changes and you do not want to coordinate several suppliers. It is less suitable if you need complete internal control from day one or expect frequent major feature changes.

• You do not want to organise hosting and technical maintenance yourself.
• Small content changes occur, but an internal web team would be disproportionate.
• You want a reachable person after launch, rather than a one-off handover.
• Planned ongoing work matters more to you than an isolated project completion.

Compare the complete scope of responsibility

Compare not only the entry price, but also the ongoing costs and services. Ask the same questions of both models and record what is included, optional or explicitly excluded.

1. Creation: Which pages, copy, images, forms and revision rounds are included?
2. Operation: Who is responsible for hosting, domain, SSL, backups and recovery?
3. Maintenance: Which technical and content updates are included?
4. Response: Is there a response time, and what does it explicitly not guarantee?
5. Handover: Which files, accounts and usage rights do you receive, and when?
6. Exit: What term, notice period and technical transition apply?

Ask these questions before you decide

• Is the website individually designed or based on an unchanged template?
• Who registers and controls the domain and other customer accounts?
• What counts as a small update, and what is quoted separately?
• Who fixes implementation errors, and do they use up an update allowance?
• Which content and technical components are handed over when the agreement ends?
• Which third-party costs may arise in addition?