← work — the registryENG-011sealed — file open
US roofing contractor
growth engineering — ads · lead ops · crm · attribution
A Texas roofing company that needed leads it could trust: a site worth landing on, paid search and local service ads, and a way to know which dollar produced which job.
- sector
- US roofing contractor · Texas
- period
- 2026 — ongoing
- role
- engineer of record — site, relay, reporting, ads plumbing
readouts — measured, sourced
03 on the record · every one names its source
5
pinned delivery sites in the reporting platform
read from — deploy records
2
tag operations that re-fire a stalled speed-to-lead workflow
read from — CRM API, proven on a live contact
0
SPF or DKIM records on the sending domain when replies started bouncing to spam
read from — DNS lookup + message headers
the file — read in order
01
the brief
A new website plus the machinery behind it: every enquiry into the CRM with its source, into the estimating system, into analytics and onto the sales team's phones — and a daily report the whole company can read.
02
the engineering
A lead relay: each form submission upserts the contact, tags the source, opens the opportunity and fires the speed-to-lead workflow; the estimating system gets the job; analytics gets the event.
A reporting platform assembling a daily KPI pack from the ad accounts, the CRM and analytics — five pinned delivery sites, print-identical PDF packs, a dependency-free SVG chart library.
Campaign structure across search, local service ads and social, with a landing page per intent.
03
the hard part
The silent case. A returning contact re-submitting a form matched an existing CRM record, so the workflow that calls the lead back never fired — the tags hadn't changed. Fix: on an existing-contact upsert the relay removes and re-adds the source tag so the trigger re-fires. Proven on a completed contact; the one exception (a contact already inside the workflow cannot re-enter) is the CRM's own rule, written down.
Replies were landing in spam: the company domain had no SPF and no DKIM, and a monitoring-only DMARC. The message headers proved it. A records sheet fixed it.
provenance
- surfaces touched
- website · form → CRM relay · estimating system · ad accounts · reporting platform · DNS
- numbers read from
- CRM API · DNS lookups and message headers · deploy records · ad platforms
- tags
- lead ops · crm integration · reporting · paid media
identity sealed — the sector is on record; the name publishes only with the client's written approval. every readout above was read at source.
the registry
previous file · ENG-013
UK tile retailer
performance rescue — 2.2 s → 47 ms
→
next file · ENG-012
UK locksmith group
brand-site rebuild + technical seo operations
→
the same hands
The person who diagnosed this file is the person who ships the fix. Two plain sentences beat a brief.