Industries

A contractor website that helps people scope the conversation

What should a homeowner understand before contacting you?

If search work is part of the scope, our website rule applies. We only do SEO on a site we built.

Before a homeowner sends an inquiry, the website has several questions to answer. Does this company do the kind of work they have in mind? Does the service include design? What can they learn from the project images? What information should they provide when reaching out? Contractor website design becomes more useful when those questions shape the page structure. The objective is a clear introduction to the business’s actual offer and a contact process that fits the conversation the team needs to have.

Ninetyfifth Marketing built a website for Solterra Hardscape, a hardscape design-build business whose documented scope also includes SEO, Meta ads, lead automation, and outdoor-living work. The website build is the evidence for this page. It does not establish a general-contractor or construction portfolio, and it does not substantiate claims about particular features, visual treatments, or measured outcomes. The following sections provide practical criteria for planning and assessing a website engagement without attributing undocumented details to that build.

Turn the service offer into a readable structure

A visitor should not have to infer the service from a collection of attractive images. Start with a plain-language description of what the business offers, then organize supporting information around the decisions a prospective customer needs to make. For a design-build offer, clarify what that term means within the business’s own process. Any description of consultations, planning, installation, or handoff needs owner verification. A familiar industry term is not sufficient evidence that every business delivers the same stages or accepts the same responsibilities.

Separate a service from a project example

A service page explains an offer that is currently available. A project page explains a particular piece of documented work. Those roles overlap, but they should not become interchangeable. A photograph may show an element that the business does not sell as a standalone service, for instance. The surrounding copy should make that distinction clear. During planning, label proposed content by its purpose so the navigation does not accidentally turn every visible project feature into a promise about available services.

Give the visitor enough context to choose

Consider a homeowner arriving with a broad idea for an outdoor space. A useful page could explain what the business needs to assess that idea and which questions belong in an initial conversation. It should avoid presenting an illustrative process as a binding commitment. The owner should approve any statement about site visits, design deliverables, scheduling, or estimates. This level of clarity helps the visitor prepare while giving the business control over the expectations created by its own website.

Treat project photography as information

Images deserve more than a decorative role in the brief. Ask what each selected image helps a prospective customer understand: the overall setting, the relationship between elements, a material detail, or the extent of a particular project. Where the facts are available, concise captions can explain the visible work. Identify concepts and renderings accurately, obtain permission for publication, and avoid exposing unnecessary property details. An image review should cover both what looks appropriate and what the business is entitled to say about it.

A proposed gallery should also have a clear relationship to the rest of the site. Someone viewing a project may need a route to the relevant service explanation or the inquiry form. Someone reading a service page may need an example to understand the offer. Plan those connections deliberately. A large gallery is not automatically a complete explanation, especially when it leaves the visitor guessing about which work the company performed or whether the displayed scope is available for a new project.

Design the inquiry around the first useful conversation

The contact form is an operational decision as well as a design decision. Ask the team which details are necessary to evaluate an initial inquiry and which can wait. A property location and short project description may be useful examples, but the final fields should reflect the actual intake process. Explain required information in ordinary language. Avoid asking for a fully developed project brief from someone who has come to the business precisely because they need help defining the work.

Submission behavior needs equal attention. A proposed website scope should state what the visitor sees after submitting, where the information goes, and who is responsible for reviewing it. If alerts or automation are included, define them separately from personal follow-up. A confirmation should accurately describe what has happened; it should not imply that a project has been accepted or an appointment booked unless that action truly occurred. These details make the contact experience concrete enough to review before launch.

Specify ownership and acceptance before the build

A website proposal should explain what will be delivered and how the business will maintain it. Identify who supplies photographs, verifies copy, approves page structure, and updates information after launch. Ask which content the team is expected to edit and what access or instructions accompany that responsibility. If search work or advertising is also proposed, distinguish those deliverables from the website build. Their presence in the same engagement should not leave either party guessing about what is included.

Review representative pages with real service descriptions and approved images before signing off on the overall design.
Check navigation, readable content, form instructions, and submission behavior on the devices included in the agreed review scope.
Verify every statement about service area, project process, availability, and follow-up with the person responsible for delivering it.
Document content ownership, access arrangements, ongoing responsibilities, and any separately scoped SEO or automation work.

Questions

What documented website work supports this page?

The supporting work is a website build for a hardscape design-build business. The broader documented engagement includes SEO, Meta ads, lead automation, and outdoor-living work. That evidence supports discussing this specific service context, but it does not establish a construction portfolio or a particular website feature list. Any proposed feature should therefore be described and agreed as part of your own scope.

Should we choose the visual design before writing the content?

It helps to establish the service offer, page purposes, and available project material before committing to detailed layouts. Otherwise, a design can reserve space for claims, images, or process descriptions the business cannot supply. Visual direction can develop alongside content planning, but representative pages should use realistic material. That makes it easier to judge whether the design explains the business clearly and accommodates the information visitors need.

What if we have photographs but little written project information?

Begin by recording what can be verified about each selected project and confirming publication permission. Describe only the work and details that are supported. If ownership, scope, or image status is uncertain, resolve that before using the material. A concise, accurate caption is preferable to a detailed invented narrative. The website can still explain current services separately, using owner-approved information rather than extrapolating from photographs.

How much information should an inquiry form request?

Request what the team needs to make the next meaningful decision. Review each field by asking how the answer will be used and whether the customer can reasonably provide it at this stage. Keep later project-development questions for later conversations where appropriate. The form should also explain what submission means and use a confirmation that matches the actual process. A contact request should not silently become an appointment promise.

Does a website build automatically include SEO and lead automation?

Those items should be explicitly scoped. A proposal should identify the website pages and functions, any SEO deliverables, and any inquiry routing or alert behavior. It should also state what the owner supplies and who maintains each part after launch. Although those activities appear together in the documented work supporting this page, their inclusion in one engagement does not define the contents of every future website proposal.