A thoughtful approach to home projects
A good home starts with good hands.
Understand the work, see how a project takes shape and tell us what you have in mind.
Tell us about your project Sample button treatment; no booking or form is connected.01 / Understand the work
A page for each priority service, with what is included and the questions to ask before starting.
02 / See the process
Explain the estimate, scope, scheduling and approval steps before a homeowner submits a request.
03 / Share the right details
Collect service type, area and timing so the team can respond with a useful next step.
The brief: confidence before contact.
A homeowner may arrive with a project in mind and a long list of unanswered questions: does this company do this type of work, does it serve my area, what does the process involve and how will I hear back? This concept organizes the experience around those decisions.
The business is illustrative. The proposed audience is a homeowner considering a planned project, rather than an emergency call. That choice informs the pace of the copy, the information requested and the next step. A real implementation would confirm service scope, scheduling and response capacity first.
The messaging decision
| Starting point to avoid | Proposed direction | Reason |
|---|---|---|
| Broad claims such as “quality service you can trust” | A clear service offer supported by a visible process | A visitor can assess fit before relying on an unsubstantiated promise. |
| One contact button for every situation | A project enquiry with service type, area and timing | The first request contains information the team can use. |
| Decorative trust badges | Rights-cleared work, verified credentials and explained responsibilities | Confidence rests on evidence the business can actually provide. |
A page system built around the job
- Home: state the offer, show the service categories and make the next step clear.
- Service page: explain suitable projects, what is included, likely dependencies and how estimating works.
- Project evidence: use approved photographs and factual context; explain the work without inventing a result.
- Process: describe the enquiry, assessment, written scope, scheduling and handoff.
- Enquire: collect the minimum useful information and explain how a request is handled.
The enquiry journey, end to end
| Moment | Proposed experience | Operational requirement |
|---|---|---|
| Before the form | Explain the types of project and area served; give clear guidance for urgent needs. | The business confirms its actual coverage and urgent-contact policy. |
| At the form | Ask for contact details, service type, area, short project description and timing. | Use accessible labels, helpful errors and an appropriate privacy notice. |
| After submission | Confirm receipt and explain the next step without implying a confirmed appointment. | Only show success after receipt is verified; identify a fallback if delivery fails. |
| Inside the business | Assign an owner, qualify the request and record the next action. | Test routing and agree a response commitment the team can sustain. |
| At review | Compare suitable enquiries with estimates and accepted jobs. | Record qualification and outcomes consistently, with reasons for lost opportunities. |
What makes the visual direction useful
Warm clay, dark ink and generous spacing give the page a grounded, approachable character. The service information remains more prominent than decorative language. Short sections, readable type and a visible next step support a customer comparing options from a phone.
The prototype deliberately uses no invented testimonials, customer logos, certification marks or project photographs. In a real build, the evidence areas would be populated only after sources and permissions were verified.
How we would build and validate it
- Interview the business owner and the person who answers enquiries; confirm service scope and capacity.
- Review real enquiry questions and prepare approved copy for one priority service.
- Design and build the page, enquiry form, receipt and internal handoff.
- Test phone layouts, keyboard use, error states and successful delivery to the assigned owner.
- Observe qualification and booking outcomes over a suitable window; record other changes that may affect the comparison.
The handoff should be usable.
A scoped implementation would include the page content, reusable layout rules, form and routing configuration, an acceptance checklist and operating notes. Training would show the team how to update service details and keep project evidence current. Hosting, specialist production and additional systems would be stated in the scope.
A delivered page and a working enquiry journey establish completion. Whether they improve qualified enquiries or accepted work requires real use and sufficient evidence. This concept does not claim conversion uplift, revenue or a client relationship.
