Disciplines / Launch & evolution
Launch Is just The start.
Deploy / Document / Monitor / Evolve
A site keeps changing after it goes live.
01 / The long viewLong-term ownership
Beyond the go-live
Great work continues
after launch.
Launch day should be boring. Domain, content, testing and documentation are sorted out before it, and the site keeps getting fixed and improved after it.
02 / Before we go liveThe checklist
What gets checked before launch.
Content & metadata
Every page proofread, in every language, with titles and descriptions for search.
Forms & communication
Each form sent for real, and the e-mails checked to arrive where they should.
Infrastructure & DNS
Domain records, hosting, certificates, and redirects from the old addresses.
Performance & accessibility
The main paths through the site tested again, so nothing got slower or broke.
Handover & ownership
Short CMS instructions, accounts with the right access, and who looks after what.
03 / Documented handoverYour team runs it
Built for whoever updates it on Monday.
A custom CMS has to make sense to the person who edits the pages, not only to me. If they need to call me to change a price, I’ve done it wrong.
Engineering & CMS service
04 / Continuous improvementAfter launch
Fewer changes, better ones.
Observe
Find out where visitors and editors actually get stuck.
Maintain
Security updates and dependencies kept current.
Improve
Fix first what bothers the most people.
Grow
New sections, languages or features when there’s a reason for them.
05 / Launch weekFour phases
How a launch goes.
01
Prepare
A launch plan, and a list of what has to work before we switch.
02
Verify
Forms, content, accounts and servers checked against that list.
03
Launch
The switch, with someone watching it happen.
04
Evolve
Support afterwards, and changes in order of importance.
Start something worthwhile / 2026
What Comes After Launch?
A launch is one day. The site has to work for years after it.
Start a project