Most website projects fail in the brief, not in the build. By the time a designer presents the first mockup, the decisions that will determine whether the site actually works have already been made — or left unmade, which is worse.
Here is what to lock down before you bring in any outside help.
Define the one job the site must do
A website can inform, convert, qualify, support, or build trust. It cannot do all five equally well. Pick the primary job. Everything else is secondary. If the site’s job is to generate qualified inquiries, every page should be evaluated against that goal. If it is to support existing customers, the navigation and content hierarchy should reflect that.
Inventory what you actually have
Before you can plan what to build, you need to know what exists. Audit your current content: what is accurate, what is outdated, what is missing. Audit your brand assets: do you have a logo in the right formats, a defined color palette, approved photography? Gaps in this inventory become delays in the project.
Write the sitemap yourself
You do not need a designer to produce a sitemap. A simple list of pages, organized by hierarchy, is enough. This exercise forces you to make decisions about what content the site actually needs versus what you think you might want someday. It also gives any vendor you hire a concrete starting point instead of a blank canvas.
Decide who owns what
Website projects stall when it is unclear who can approve copy, who can approve design, and who can approve launch. Name those people before the project starts. Define how decisions get made when there is disagreement. This is not bureaucracy — it is the difference between a six-week project and a six-month one.
Set a realistic timeline
A well-scoped website for a professional services firm takes eight to twelve weeks from brief to launch. If you need it faster, something has to give — scope, quality, or both. Be honest about the constraint before you commit to a deadline.