Process
Can I update the website myself afterwards?
That depends on what was built and it should be agreed before, not discovered after. A CMS build gives you an editor for content changes; a static build usually means asking the developer. Neither is wrong — but being surprised by which one you bought is.
What each approach gives you
- CMS
- Edit content yourself, add pages, upload images. More maintenance, more attack surface.
- Static with a CMS layer
- Same editing experience, static output. More setup, best of both for many sites.
- Static, edited in code
- Fastest and cheapest to run. Content changes go through a developer.
The question to ask before signing
"Which specific things will I be able to change myself, and which will need you?" A clear answer — text and images yes, layout and new page types no — is normal. A vague one usually means the answer is less than you expect.
What to negotiate either way
A written handover: how to log in, how to publish, how to roll back, and where everything lives. That document is worth more than the training session, because you will need it in six months rather than in week one.
The longer version
This answer is deliberately short. If you want the full treatment, Who actually owns your website — a checklist you can verify today covers it in about 3 minutes — free, ungated, written from client work.
Who answered this
Anas Bin Masud builds e-commerce sites and does technical SEO for businesses in the UK, Canada and Pakistan — fifteen live client sites, six of them stores taking real payments. These answers come from those projects rather than from a content brief. More about how I work, or ask me something directly.