Homes built to be remembered. A website built to hold its own.

A focused builder site usually needs a homepage, project index, individual project pages, services or capabilities, process, about or team, and contact. Add location pages only when there is genuine local analysis and proof. The project pages do most of the commercial work, so they need names, careful location language, scope, image sequence, and a route to inquiry. Page count matters less than whether each page answers a distinct buyer decision.

Premium comes from editing and proportion, not decoration. Use strong project photography at useful sizes, disciplined type, restrained color, specific captions, and enough negative space to let material and architecture read. Avoid stock homes, crowded card grids, generic luxury language, and motion that competes with the work. A premium site also feels operationally sound: fast, clear on mobile, precise about service area, and direct about the next step.

Show budget information when it helps buyers understand fit and when privacy or contractual constraints allow it. A minimum project size, typical range, or scope category can be more useful than publishing exact final costs. Explain what changes the number, such as site conditions, design status, selections, and engineering. If no range can be stated responsibly, collect a budget band in the inquiry and explain why the first conversation needs that context.

Organize by project first, then use filters only if the body of work supports them. Each project should begin with an establishing image and move through exterior, interior, material, and craft details in a deliberate sequence. State whether it was a custom build, renovation, or specialty scope, and use location at the level the client permits. Avoid a single mixed gallery where the buyer cannot tell which images belong together or what the builder delivered.

A one-page site can be enough for a new or tightly focused builder with a small, excellent body of work and one clear service area. It becomes limiting when several project types, locations, teams, or detailed project records need to be understood. Start with the smallest structure that supports the buying decision. Add pages when they earn a distinct role, not because a conventional agency package expects a particular count.

Local search starts with consistent business information, a useful Google Business Profile, relevant project evidence, clear service-area language, crawlable pages, reviews, and local links or mentions. The website should describe real markets and real work without mass-producing town pages. A location page is justified when it contains distinct market insight and evidence. Technical metadata supports that content, but it does not create local authority on its own.

A fixed-scope builder homepage can be completed in seven days when the builder supplies the current site, usable project photography, core services, reviews, access, and feedback on schedule. A large project archive or multi-page search build requires more time. Coxswain treats the seven days as a build window that begins after inputs are ready. That protects quality and makes the promise specific rather than pretending missing photos can be solved on day six.

Coxswain needs the current website, primary services, service area, ten to thirty strong project images, the jobs the builder wants more of, useful reviews, brand files if available, and launch access. For a larger site, project names, scope notes, and client-approved location language are also needed. The first call resolves positioning and gaps. If the photography or proof is too thin, that is identified before the seven-day build window begins.