Your work is already the proof. Your website should make it obvious.

A contractor website should identify the work, service area, project fit, process, and person responsible. It should show finished projects in coherent groups, publish specific reviews and credentials, explain what happens before and during a job, and provide an inquiry path that collects location, project type, budget, timeline, and photos. Those elements help a referred homeowner decide whether the contractor is credible and appropriate before making contact.

Cost depends on what is being delivered, not only on the platform. A DIY subscription buys software and leaves strategy, copy, design, image treatment, launch, and upkeep with the owner. A freelancer or studio adds execution, while a custom agency adds broader research and process. Coxswain's published offer is $1,995 for a fixed-scope showpiece homepage. The contractor website cost guide breaks down the other categories and hidden line items.

Squarespace is often the cleaner owner-managed choice when the site is modest and the priority is dependable design with limited upkeep. WordPress is stronger when the business needs a large content system and has someone responsible for updates, security, and plugins. Neither platform fixes weak positioning or project presentation. The right choice follows the operating model, content volume, ownership requirements, and who will maintain the site after launch.

There is no useful universal number. A stronger rule is to show enough images to explain several representative jobs from context to detail. For each selected project, include a wide establishing view, material or craft details, and any view that clarifies scope. Ten disciplined images across three coherent projects can be more persuasive than fifty mixed photos. Remove duplicates, unfinished scenes without explanation, and images that make the work difficult to read on a phone.

Publish pricing when it helps a qualified buyer understand the level of engagement and when the range can be stated honestly. Fixed packages and minimum project sizes are particularly useful. Avoid false precision for work that depends heavily on site conditions, engineering, selections, and scope. In those cases, explain the cost drivers and collect a realistic budget band in the inquiry. The goal is useful self-selection, not a number that creates the wrong promise.

No. Create a service-area page only when the market has genuine demand, relevant proof, and analysis that cannot be copied onto another city page. A clear main market and operating radius are usually better than dozens of near-identical town pages. Separate pages become useful when search evidence, local project material, terminology, and buyer decisions differ enough to justify them. Duplicated locality pages weaken trust and can create doorway-page risk.

Coxswain's fixed-scope homepage is built in a seven-day window once the current site, project photos, launch access, and feedback windows are ready. Larger sites take longer because they require more pages, proof, and review. Speed is realistic only when scope and decision points are fixed. A rushed build without usable photography or access is not a seven-day process; those inputs are prerequisites, not tasks to discover at the end.

The contractor should know who owns the domain, code, content, design files, analytics property, and hosting account before work begins. Coxswain's published offer states that the finished site is yours outright. Third-party software and hosting remain subject to their own terms, but the handover should make access and responsibilities explicit. Avoid arrangements where leaving an agency means losing the domain, the content, or a usable export of the site.