AnchorWorks ← The Briefing Room On the record
AnchorWorks
Executive Brief 012 · July 3, 2026

The First Live Reading

report
Prepared by Ethan Tryhubczak AnchorWorks
The Briefing Room · 2026
  • Read-only, isolated, honest§ Executive Decisions · Decision Log

    Real data lands in a staging table so the approved demo stays pristine; nothing is ever written back to GoHighLevel; the strip shows only what is truly live and labels the rest sample.

See every standing order in the SOP Library →
01 · Executive Summary

The executive summary.

Brief 011 left two decisions open: where the cockpit would live, and which live source to turn on first. Today both were answered and shipped. The Command Center was deployed to a permanent URL on cloud infrastructure, and its first real reading came in — live acquisition data flowing from GoHighLevel onto the Sales board.

Until today the instrument ran on modeled sample figures. Now it reads reality. The first slice is deliberately small — a read-only snapshot of live opportunities into an isolated table, surfaced as a labelled "Live from GHL" strip — but even four opportunities is a categorical change: the pipe from the live system of record to the boardroom screen is proven end to end, and the seeded demo board it sits beside was never touched.

Prove the pipe on the smallest honest slice — read-only, isolated, idempotent — then widen it once the journey is mapped.

Current stage: Foundation nearly complete — deployed, connected, first live thread pulled. Live capture is now beginning.

02 · Executive Decisions · Decision Log

What was decided.

  • First live source is GoHighLevel — the acquisition system of record — chosen over Stripe for the first slice.

    locked

  • Deploy target locked. The cockpit lives on Cloudflare Pages against cloud Supabase, on a permanent URL — localhost retired.

    locked

  • Blueprint before code. B.L.A.S.T. — a design doc and task plan were written and approved before a line of ingestion was built.

    locked

  • Read-only, isolated, honest. Real data lands in a staging table so the approved demo stays pristine; nothing is ever written back to GoHighLevel; the strip shows only what is truly live and labels the rest sample.

    locked

  • Defer the deep model. Dimensions (team / offer / source) and the delivery track wait on the customer-journey mapping still owed with Chris.

    locked
03 · Major Accomplishments

What was done.

01Chose the first live source — GoHighLevel

The problemBrief 011 left it open: Stripe (cash) or GoHighLevel (leads) first? And what the GoHighLevel account actually represents was unconfirmed.
What was doneDecision: Turn on GoHighLevel first — the acquisition system of record — and confirm the model directly against the live account. Implementation: Read the live structure: five pipelines, all AnchorWorks selling its own services to HVAC companies (acquisition) — not a lead-selling account. A second delivery track will be tracked once clients onboard. Dependencies: Customer-journey mapping with Chris to define the acquisition → delivery handoff.
The impactThe map is now the territory. We know exactly which data feeds Sales today and where Client Success delivery data will come from next.

02Deployed the cockpit to a permanent URL

The problemThe Command Center was canonical on main but still lived on localhost — no one but the builder could see it.
What was doneDecision: Deploy to a permanent, shareable URL on cloud infrastructure — closing Brief 011's open deploy decision. Implementation: Cloudflare Pages against cloud Supabase, seeded demo data, at kpi-command-center.pages.dev. A stable production alias so the link never breaks on redeploy. Dependencies: None. Live behind the stable alias today.
The impactThe whole team — and Chris — now read the same board from anywhere. The instrument left localhost for good.

03Blueprinted, then shipped, the first ingestion slice

The problemThe board ran on modeled figures. It needed real data — but the customer journey is still being shaped, so a full pipeline would be guessing.
What was doneDecision: B.L.A.S.T. — blueprint first, then ship the smallest honest slice: read-only, isolated, idempotent. Prove the pipe without locking any open decision. Implementation: A read-only GoHighLevel snapshot → isolated staging table → clean live view → a "Live from GHL · Acquisition" strip on the Sales tab. Four real opportunities in, idempotent re-runs, the seeded demo untouched. PR opened for Chris. Dependencies: Chris + ChatGPT final messaging — this brief's narrative is a structural draft.
The impactFirst real numbers on the board — and the first pull already exposed true data quality (thin, unvalued, unassigned), which sharpens the journey work rather than hiding it.

04Why the first reading matters.

What was doneA model of the business is a story. A connected instrument is evidence. Today the Command Center crossed that line — even on four opportunities — on a foundation that is safe by construction. Reality · Reads, doesn't model: The board now reflects the live system of record, not tuned assumptions — credibility with a founder and a buyer alike. Reliability · Safe by construction: Read-only, idempotent, isolated. A re-run never duplicates; the demo never corrupts; GoHighLevel is never written to. De-risked · Truth over polish: The first pull exposed real data quality — thin, unvalued, unassigned — informing the journey work instead of hiding it. One board · A permanent URL: The team and Chris read the same live screen from anywhere. Localhost is retired for good.
04 · Metrics

By the numbers.

1
Live source chosen (GoHighLevel)
4
Real opportunities ingested
1
Permanent URL live
0
Writes to GoHighLevel (read-only)
2
Blueprint docs before code
1
Pull request opened (#4)
100%
Deployed to a permanent URL
100%
First live source connected
15% · next
Full acquisition pipeline (appts, dimensions)
0% · queued
Delivery track (Client Success)
05 · Current Company Stage

Where we are.

01
Foundation
02
Launch
03
Scale
04
Expansion
05
Acquisition

Foundation — the first live thread pulled.

06 · Open Decisions

Decisions still required.

  • Customer journey mapping (with Chris). The acquisition → delivery handoff, and which delivery stages to track. The one decision that unblocks everything downstream.
  • Dimensions. How team / offer / source get filled — derived in code from mappings, or read from GoHighLevel custom fields.
  • Cadence. When to move from a manual snapshot to scheduled or real-time ingestion (pg_cron or webhooks).

    “Rebuild the pull as a scheduled service on the locked database stack, so it runs on its own every half hour.”

    Resolved by Brief 017 · The Pipeline, By Stage
  • Narrative sign-off. Chris + ChatGPT's final copy to lift this brief from DRAFT to canonical.
07 · Next Priorities

What comes next.

  1. 01
    Map the customer journey with Chris
    Acquisition and delivery — the mapping that unblocks the full pipeline.
  2. 02
    Wire appointments (show / no-show)
    So real close rates light up on the Sales board.
  3. 03
    Fill the dimensions
    Team / offer / source, so by-team and by-offer breakdowns come alive.
  4. 04
    Stand up the delivery track
    Client Success — stage velocity and stall alerts for onboarded clients.
  5. 05
    Manual snapshot → automated
    Scheduled or real-time ingestion once the journey is locked.
Executive Brief · Nº 012 · July 3, 2026 · Canonical