Start with a website review
Use it when the site already exists and you need to understand what is weak: speed, SEO, mobile UX, trust, messaging, and the lead path.
Next step
Website review vs brief checklist
This page helps decide whether the next useful step is to inspect the live site or to collect the brief details that will guide the build. Both are useful, but they solve different problems.
Choose the next stepStart with the brief checklist
Use it when the next build still needs direction: business goals, services, languages, proof, pages, and launch limits.
What the pair solves
The review shows what should change. The brief shows what the new structure should include before design begins.
What to send
Send the live site, the goal, the audience, the current proof assets, and any limits on what can be shown publicly.
What not to invent
Do not invent proof, goals, or launch readiness. The point is to clarify the real next step, not to guess.
FAQ
Questions worth answering before the build.
Which should come first?
If there is already a live site, start with a review. If the current problem is unclear scope or missing input, start with the brief.
Can this be used before launch?
Yes. The brief path is especially useful when the build still needs structure, proof, and content decisions.
Does the review replace the brief?
No. The review diagnoses the current site. The brief defines what the next build should contain.
What happens after this page?
The next step is usually the proof checklist, launch checklist, 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.