Resource
Resources
Things to use rather than read: what to ask for at handover, how to write a brief that gets you a real quote, what we check before a launch. Several are the public version of documents we issue to clients. Take them to whoever you hire, including if that is not us.
- Resource · 6 min · updated 25 August 2026What you get at handoverAt the end of a website project you should hold the domain, the hosting project, the repository with its full history, an export of your content, and notes complete enough for a new developer to deploy it. If any of that sits in your agency's account instead, you are renting the site you paid to own.
- Resource · 5 min · updated 25 August 2026How to write a website briefA website brief answers nine things: the business, the audience, the problem, what success looks like, what is in scope, what is explicitly out of it, the constraints, who decides, and what the supplier needs from you. The last four are the ones usually missing, and they are why quotes vary.
- Resource · 5 min · updated 25 August 2026The launch checklist we useMost launch checklists list things nobody forgets. The useful ones cover the failures that survive review: a page that returns 200 with nothing on it, a hostname nobody tested, a redirect that loses the path. This is the list we run, with the thresholds we actually assert.
- Resource · 6 min · updated 25 August 2026The tools we actually useA short list of what this site is actually built with, verifiable against the package manifest in the same repository, and the documentation we open most often. It is deliberately small, because a list of everything popular tells you nothing about what anyone uses.