Crestward Roofing

Crestward Roofing doesn’t exist — its roof problems faithfully reproduce ones that do. This study follows one job from the moment an ad answers them to the moment a structured enquiry lands in a CRM queue.

An intent worth keeping

Paid home-services ads meet people mid-problem: a stain spreading across a ceiling, tiles in the gutter after the second storm of the season. Clicking the ad is already a small act of intent.

Most websites then spend that intent. The visitor lands on a generic homepage, re-reads what the company does, hunts for a phone number, and meets a contact form that asks everything except what is wrong with the roof.

This concept explores the opposite posture for a Melbourne roofing business: every campaign resolves into an experience that continues the promise the ad made, in the vocabulary of the problem that prompted it.

From click to qualified enquiry

The intended journey is deliberately short, and every step earns the next one:

1. Ad — promises one specific answer to one specific problem, not “quality roofing services”.
2. Landing experience — continues that answer: what causes this issue, what it usually means, photographed and named in the homeowner’s words.
3. Understanding options — repair, restoration and replacement framed as genuinely different paths, with honest signals about when each applies.
4. Roof qualification — a few deliberate questions that map symptoms to likely scopes.
5. Inspection request — a short flow asking only what an inspector needs, plus optional photo context.
6. Structured lead — a summary a CRM can route without human decoding, ready for follow-up.

Qualification works in both directions. The homeowner learns what shapes their outcome; the roofer receives enquiries worth driving across town for.

Certainty before commitment

Roofing customers carry four quiet uncertainties, and each one costs enquiries when left unanswered:

• What is actually wrong? Problem-led content names causes in plain language before any service is mentioned.
• Repair, restoration or replacement? Fear of an upsell is real. The decision guide presents all three paths and the conditions that favour each — including “not us today”.
• What happens after I submit? Silence reads as risk. The flow states exactly who makes contact, how, and when.
• Am I committing to anything? An inspection request is not a contract, and the interface says so beside every submit action.

None of this requires invention. It requires answering, in order, the questions a worried person actually holds.

What the experience does

• Problem-led landing pages, one per intent family, continuing the ad instead of restarting the pitch.
• A roof decision guide that turns symptoms into a probable scope, with uncertainty acknowledged rather than hidden.
• Multi-step qualification that asks in the homeowner’s order — roof first, identity last.
• Optional photo context via the device camera, compressed locally before upload.
• A single, unambiguous inspection CTA repeated wherever readiness occurs, never competing with three other offers.

The whole flow is drawn mobile-first, because roof trouble is discovered on a phone — often while standing in the room it is dripping into.

How it would be built

Stated as engineering intent, consistent with how this site itself is made:

• Static-first, on Astro. Content and landing surfaces pre-render to HTML through the same collection pipeline that serves this case study.
• Minimal client JavaScript. The site’s interactive baseline is about a kilobyte; any scripting budget belongs to the qualification flow, not the brochure.
• Progressive enhancement where it counts. Flows degrade to ordinary multi-step form posts; enhancement replaces reloads, never gates destinations.
• Accessible interaction as a floor. Visible focus, keyboard operability, reduced-motion respect and AA contrast targets come from the design system, not per-project heroics.
• Local-only demo submissions. In the concept build, submitting sends nothing anywhere: the structured summary is rendered on screen and held only in your browser’s local storage, erased the moment the demo submission completes.
• A lazy Live Project Player. The build below loads through Stack Quarters’ existing player facade — a poster until you ask, then an isolated sandboxed frame you can eject or reload.

Why this concept exists

This concept demonstrates how a high-ticket local-service campaign can carry its message from the ad click through to a structured enquiry without forcing the homeowner through a generic corporate website.

It also documents the standard we hold ourselves to: reasoning written out, decisions given names, outcomes described as intentions rather than invented scoreboard numbers. When we take on a real engagement, this is the shape its case study will inherit — minus the fiction label, plus whatever figures our client is happy to publish.

If your funnel currently spends the intent your ads have already paid for, this page is the shortest possible introduction to how we would fix it.