Implementation case study
A roofing website. Connected inquiry paths. Verified delivery.
For a Washington roofing company, we built a full website, five separate offer pages, and the forms, callback scheduling, and tracking behind the inquiry journey.
The project brief
Build the website and the ways customers get in touch.
The assignment covered a complete roofing website and a separate set of pages for specific paid offers. We kept those two surfaces distinct, then connected their inquiry forms, callback scheduling, and source information.
Our work included the page build, embedded contact tools, call-routing configuration, analytics installation, and desktop and mobile checks. The company is anonymous here; the delivery counts and implementation checks come from the project records.
- Industry & market
- Roofing · Washington
- Website structure
- Full website + separate paid-offer pages
- Customer contact options
- Call, inquiry form, or scheduled callback
- Documented work
- Build, integration, and visual checks
What we delivered
A full website and five focused offer pages.
The full site supports browsing the roofing business. The offer pages give paid traffic a destination matched to a specific service or request.
33 routes, one website.
We built and checked the full-site route set, with its own navigation and organic inquiry form. The contact journey also includes a callback calendar.
- Full-site route inventory checked.
- Organic inquiry form embedded and visually reviewed.
- Mobile form and logo presentation corrected during QA.
Five offers, separate destinations.
We created dedicated pages for roof inspection, storm damage, roof replacement, insurance claim help, and roof repair, with a separate paid-traffic inquiry form.
- Offer pages kept separate from the full website.
- Paid inquiry form and callback embeds checked.
- Campaign parameters and click IDs checked through the embed handoff.
The inquiry paths we connected
- 1. Choose a page
Browse the full website or arrive on an offer-specific destination.
- 2. Choose how to connect
Call, complete the relevant inquiry form, or use the callback calendar.
- 3. Carry the source information
Pass URL attribution parameters through to the form and calendar embeds.
Implementation verification
What we checked before calling the website work complete.
The following checks were documented on . Expand each item for the work verified and the kind of record behind it.
Website routes and five offer destinations
The build inventory recorded 33 full-site routes and five separate paid-offer pages. The offer set covered inspection, storm damage, replacement, insurance claim help, and repair.
Record: page inventory and build checks · August 26, 2026Two inquiry forms and a callback calendar
The full website and paid pages used separate inquiry forms. Browser checks covered the embedded forms and callback calendar on desktop and mobile, including their visible layout.
Record: desktop and mobile browser checks · August 26, 2026URL attribution through the embed handoff
We checked propagation of campaign parameters and click IDs from the page URL into the inquiry-form and callback-calendar embeds. This verified the parameter handoff used to carry source context.
Record: URL and embed-parameter checks · August 26, 2026Call-routing settings read back from the platform
The configured call route was checked through an API readback. The route included a Press 1 acceptance step; call recording was disabled.
This verifies the saved routing configuration.
Record: call-routing configuration readback · August 26, 2026GA4 installed on the website
The website implementation included GA4 analytics.
Record: analytics implementation checks · August 26, 2026Fixed mobile form overflow
QA identified a form layout that overflowed on mobile. We corrected the presentation and checked the embedded form on the smaller screen.
Corrected the logo background
We corrected the logo treatment to remove an unwanted white background, then included the updated presentation in the visual review.
The delivered outcome
The website and inquiry system were built and checked.
The completed work brought together the 33-route website, five offer pages, two inquiry forms, callback scheduling, configured call routing, GA4, and URL attribution. The project records also show the mobile-form and logo corrections made during QA.
This case study demonstrates website and inquiry-system delivery. Customer lead, booking, and revenue results were outside these implementation checks.