Start with a website brief
Use it when the project still needs direction: business goals, services, pages, languages, proof, and the audience you want to reach.
Next step
Website brief vs launch checklist
This page helps decide whether the next useful step is to gather the brief details or to prepare the launch checks that keep the release clean.
Choose the next stepStart with a launch checklist
Use it when the site structure already exists and the team needs a final QA path for speed, SEO, forms, and launch readiness.
What the pair solves
The brief sets the direction. The launch checklist protects the release and makes sure the live site is ready.
What to send
Send the current site or the project notes, plus any proof assets, launch dates, and limits on what can be shown publicly.
What not to invent
Do not invent launch readiness, SEO status, or final content. The point is to pick the next real step, not to guess.
FAQ
Questions worth answering before the build.
Which comes first?
If the structure is still unclear, start with the brief. If the site is built, start with the launch checklist.
Can this be used before launch?
Yes. The launch checklist is especially useful when the build is close and needs a final quality pass.
Does the brief replace the launch checklist?
No. The brief defines what should be built. The launch checklist defines what must be true before the site goes live.
What happens after this page?
The next step is usually the proof checklist, review page, or the main service page that should carry the decision forward.
Related resources
What comes next
Related pages that turn this into a plan.
Contact
Want to turn this into a site plan?
Send the business type, current site if there is one, and deadline. We will reply with a clear direction.