Website project brief
A one-page brief for a small-business website project. Goals, audiences, must-have features, constraints, success measures. Plain English, no agency jargon.
Read the how-to first →Resources
When I start a new project with a business or an agency, the first thing I usually ask for is a brief. A good brief saves everyone time and money, but it’s often the hardest thing for a client to write from scratch. So here are the templates I’ve built up over the years and now share with anyone who asks. Use them however you like, even if we never end up working together.
A handful of plain-English templates and checklists. They’re free, they’re editable, and you don’t need to give me your email to use any of them. If you fill one in and want a second pair of eyes before you brief a developer, send it over and I’ll have a read.
A one-page brief for a small-business website project. Goals, audiences, must-have features, constraints, success measures. Plain English, no agency jargon.
Read the how-to first →For Laravel, Filament or custom platform projects. User roles, key journeys, integrations, data structures, what already exists, what good looks like.
Read the how-to first →DNS, SSL, analytics, backups, sitemap, robots, redirects, accessibility, performance. The list I run through before sending any site live for a client.
See it in context →A page-by-page sheet for planning the content for a new website. Headings, supporting copy, images needed, calls to action, who’s writing each one and when.
Read the how-to first →A short list of questions to ask a freelance developer before you hire them. The ones that tell you whether they’ll actually be a good fit for your project.
Read the how-to first →A simple worksheet for setting a realistic budget for a website rebuild. Build, hosting, maintenance, content, and the bits that always get forgotten on the first pass.
Read the how-to first →Send me a few details and I’ll come back to you the same day to talk through how I can help.