Systems we have shipped.

The design, the system, the stack. Selected builds across service trades — shown the honest way.

A client is named only when written approval is on file. Everything else is anonymized: trade, region, what was installed.
No metrics. We do not publish rankings, lead counts, or revenue — ours or a client's.
Spec builds are labeled as spec. They show the system and the craft, not a client result.

CASE STUDIES

Baseline, installed, watched.

Every case study follows the same three steps: what we measured first, what was built, and what we track. Metrics are named, not quoted — results stay private until a client approves them in writing.

CASE STUDY / 01 · Flux-owned demo property · illustrative, not a client result

Flux Contractor Demo

HVACTreasure Coast, FLBaseline since 2026-08

Websites AI call handling

01 · BASELINE

What we measured first

Every inbound path inventoried before launch: main line, form, demo text-back, and the tel: links in the nav, sticky bar, and footer.
Missed-call behavior recorded for a two-week window — which hours went to voicemail, and how long a caller waited for any reply.
Inquiry sources tagged from day one so nothing arrives as “direct / unknown”: GA4 cta_click, call_click, and form events plus UTM capture on every form.
First-viewport audit on a phone: is the number tappable, is the estimate path visible, does the page hold up on a 9pm no-cool call.

02 · INSTALLED

What was built

Dispatch-first homepage with click-to-call and a three-field estimate path in the first mobile viewport.
Missed-call text-back on the demo line — the same message a real shop's callers receive, running on Flux's own number.
Sticky call / text / book bar, service pages by problem type, and CRM wiring that stamps each inquiry with its source.
Tried against written scenes: after-hours call, form at midnight, no-show, review request.

03 · WATCHED

What we track Tracking in progress

Missed calls that received a text back: CRM conversation log, matched against the carrier call record.
Time from missed call to first reply: Timestamp delta in the CRM; target is seconds, reported as a distribution, not an average.
Inquiry source per lead: GA4 events (cta_click, call_click, audit_form_submit) joined with UTM fields on the form payload.
Form-to-booked-estimate rate: CRM pipeline stages, counted per month once volume is meaningful.

CASE STUDY / 02 · Client case study · details publish with written approval

Treasure Coast roofing company

RoofingTreasure Coast, FL

Websites AI call handling AI search (AEO)Google listing

Baseline, install, and watched metrics for this engagement publish here when written approval is on file. Until then: trade, region, and scope only.

CLIENT BUILDS

Installed for operators.

Client build · anonymizedRoofingTreasure Coast, FL

Treasure Coast roofing company

The whole path: an inspection-first site, storm-week missed-call text-back, a cleaned-up Google listing, and a tracked set of ChatGPT-style questions measured against national directories.

WebsitesAI call handlingAI search (AEO)Google listing

Client build · anonymizedPaintingFlorida

Florida painting contractor

A website built to get the phone to ring: call button and a three-field estimate form on the first phone screen, job pages by surface type, every lead tagged with its source.

Websites