[ Back to work ]

A new website for a Lower Mainland roofing company, designed to turn visitors into quote requests.

Role
UX/UI design
Copywriting
Build in Figma Sites
Team
Solo
Partner as client liaison
Timeline
~2 weeks of design and build
Tools
Figma
Figma Sites
Status
Client project, launched July 2026
[ View live site ]

In short

Problem
A roofer with 30+ years of credentials had a dated site that showed almost none of them.
What I did
Designed, wrote and built a four-page site in Figma Sites, solo, in about two weeks.
Result
Live since July 2026, the layout approved as first designed. The client was very happy with the finished site, and with how clearly the project was communicated from start to finish.

Client
General Roofing, a Lower Mainland roofer with 30+ years of experience.
Goal
More quote requests from a site as established as the company. The client asked for credibility first, ahead of visual flair.
Constraint
One revision round each for design and development, with the layout locked once the build began.

Homepage — desktop

The old General Roofing homepage: a roof photo, a headline and a floating estimate form
The new homepage: aerial video, headline, trust badges and a four-field quote form
Drag to compare. Before, the credentials sat below the fold; after, proof sits directly under the headline.

[ 1 ]One action, on every screen

Client ask

“Better messaging to drive quote requests”

Why

The goal was more quote requests, so everything leads to one action: a quote button in the header of every page, and the form itself in the hero. On phones it becomes a single button, so the headline still fits the first screen.

Trade-off

Less room for imagery above the fold; the aerial video runs behind the headline instead.

Homepage, first screen — desktop
The homepage's first screen: the navigation with a Request a FREE Quote button, the headline, trust badges and a four-field quote form

What to notice

[ 2 ]Proof before promises

Client ask

“A more professional, high-trust look; feature the GAF certification and Home Depot endorsement”

Why

Trust decides who gets the call, so the proof sits directly under the headline, ahead of any services copy.

Homepage hero — desktop
Headline with Home Depot, GAF Certified and 5.0 Google rating badges beneath it

What to notice

[ 3 ]Lower the anxiety of a big purchase

Client ask

“An “Our Process” section”

Why

A new roof is expensive and disruptive, so a five-step process answers “what happens next?” before anyone has to ask, and financing is framed as monthly payments.

Trade-off

A longer homepage, so each step is kept to one sentence.

Homepage process — desktop
Five-step process: consultation, roof and attic inspection, detailed plan, installation, final walkthrough

What to notice

  1. Pencil sketch of the homepage's first screen on desktop and phone, with notes: aerial video behind the headline, proof under the headline, the quote form in the hero, and one button on phones

    [ 1 ] Sketches

    Page structure and hierarchy on paper.

  2. Greyscale wireframes of the homepage on desktop and phone: navigation, hero with trust badges, the four-field quote form, and the single quote button on phones

    [ 2 ] Wireframes

    Homepage and service layouts, low fidelity.

  3. High-fidelity homepage designs on desktop and phone: aerial hero, headline, trust badges and quote form

    [ 3 ] High fidelity

    The design system and every page, approved as first designed.

  4. The built homepage on a laptop and a phone

    [ 4 ] Build

    Built and published in Figma Sites, responsive to phones.

Collect content before design

What happenedBoth revision rounds went to copy and photos the client supplied mid-project.

Next timeI'd gather the client's photos, facts and credentials before high fidelity, so revisions refine the design instead of catching up on content.

Hear the client first-hand

What happenedFeedback reached me through my partner, and detail was lost on the way.

Next timeI'd join the kickoff call to hear priorities in the client's own words and ask follow-up questions on the spot.

Check the tool before scoping

What happenedThe brief's interactive map of completed projects became a Google Maps embed.

Next timeI'd confirm what the build tool supports before features go into the proposal.

The services page on desktop: tabs and the layered roofing system explainer
The about page on desktop
The contact page on desktop
The services page on a phone
The homepage hero on a phone, with the quote form as a single button
The five-step process on a phone

Interested in creating a digital experience?

[ Let’s talk ]