The executive summary.
The entire public AnchorWorks site and the full lead-funnel chain were re-voiced from an "agency" positioning to the Revenue Engine category — one consistent vocabulary, credibility-safe, and structurally complete from first click to booked call.
One canonical language now runs sitewide — Revenue Engine (the machine), the Local Authority System™ (the method), the Authority Score™ (the diagnostic), and the four Engines (Traffic · Conversion · Sales · Nurture). Every unsupported claim was stripped from the funnel, two supporting deliverables shipped alongside — an operator team section and a ~90% image-weight performance pass — and an internal QA link hub plus a production launch-readiness checklist were produced.
The site no longer reads like a generic agency. It presents one coherent, ownable category — and the money path, from opt-in to booked strategy session, is fully built and consistent.
Current stage: Foundation → Launch. Site content is essentially done on a preview branch; production (www, a separate Webflow site) is untouched and not yet cut over — a deliberate NO-GO until launch operations clear.
What was decided.
Reframed the whole site around Revenue Engine as the category; retired "agency," "Anchor Revenue System™," "Authority Machine™," and the old "Leads · Sales · Scale" model.
lockedLocked the canonical naming hierarchy: Revenue Engine (machine) · Local Authority System™ (method) · Authority Score™ (diagnostic) · four Engines (Traffic / Conversion / Sales / Nurture).
lockedMade the funnel credibility-safe — removed unsupported stats, the "4.9 from 200+" rating, "top 10%" framing, and hard revenue claims from every funnel page.
lockedStandardized the primary funnel CTA to "Book My Strategy Session" → /strategy-session/book/; retired "Map My HVAC Growth Plan" and "HVAC Growth Strategy Session."
lockedReplaced homepage fabricated testimonials with Use Cases, unverified stat counters with Structure-Proof counters, and reworked the guarantee to "We don't win until your Revenue Engine does."
lockedRewrote the About page around the founder asset-test story — "A business is not an asset if you can't leave it."
lockedAdded an operator team section (8 people) to About, built entirely from the existing design system.
lockedConverted the 8 team portraits to WebP and removed the unused source copies.
lockedKept every page's design, layout, CSS, structure, routing, and SEO mechanics unchanged — words and assets only.
lockedBuilt an internal, noindex QA link hub at /_qa/links/, not linked from the site.
locked
What was done.
02The complete funnel chain, aligned & credibility-safe
03The operator team, on About
04Performance & launch discipline
05Why this increases enterprise value.
By the numbers.
Where we are.
Foundation → Launch
Decisions still required.
- Homepage topbar proof & scarcity. Home still shows "4.9 from 200+ HVAC owners" and "Only 3 Q3 install slots left" (removed from every funnel page). Prove it or remove it — recommend remove unless documented.
“Strip every unsupported proof, manufactured-scarcity, and income claim from the webinar funnel and the homepage topbar — no ratings, "trusted by," "limited spots," or "$100K/month."”
Resolved by Brief 015 · The Webinar Funnel Gets Real - Launch scope for Webinar + Careers. Finish both, or exclude them (noindex + out of sitemap) and ship later.
- Production cutover timing. When to repoint www from Webflow to the Cloudflare Worker — irreversible, and needs the owner's explicit go.
What comes next.
- 01Launch hygiene sweepConfirm or remove the homepage topbar rating + scarcity; remove /_qa/links/; fix-or-hide Careers.
- 02Finish or exclude the Webinar funnelThe biggest unfinished funnel — complete the placeholders or cleanly exclude it (noindex + out of sitemap).
- 03Install analytics + pixelsGA4 + Meta Pixel via GTM, with Lead / CompleteRegistration / Schedule events. No paid traffic until live.
- 04Production config + cutover mechanics404.html, _headers / CSP, pin html_handling, add the production route; merge → main.
- 05Cut over wwwRepoint DNS to the Worker (explicit go), then a post-cutover smoke test and analytics confirmation.
