The mirror of the site you built me.
This is the mirror image of the site you built me. Yours said "here's the role and where you come in." This one says "here's the engine I've prepared, and how it delivers the quarter."
Built before day one, and built to co-shape. The durable value is the engine itself, and it holds up against whatever targets we land on together.
Every figure on this page is labeled one of three ways. This is the integrity contract, so no number is left to guess at.
You said pipeline is a system output. I built the system.
We already agree on the worldview: reps should be selling, not researching, and pipeline should come out of a system instead of manual grind. So I will not re-argue it. The part a strategy page cannot show is the running machine underneath it, and the rails that prove it works. That is what the rest of this page is.
Your page made the case for the engine. This one is the engine: built, gated, and measured, so the thesis runs every week instead of living on a slide.
Your Golden List, with the build pack that stands it up.
The Golden List is your foundation, and you have already defined what it does. What did not exist yet is the click-by-click build that turns the concept into a live Clay base on Day 1. I wrote it.
A click-by-click Clay Build Pack. Tables, columns, enrichment waterfalls, fit and grade formulas, signal columns, source-tag writes, and webhooks, all in build order. It stands the Golden List up as a live Clay base in about two hours on Day 1, instead of being designed from scratch while the quarter is already running.
It also feeds the current Star Ratings enrichment from 40+ sources, with the fit and grade formulas that decide which accounts a rep works first. Verified
That is the difference between a concept on a page and a base a rep can pull from in week one.
One weekly motion. Seven stages. Gated where it matters.
A single conductor runs the week from end to end, and stops dead at the gates. The gates are not optional steps; they are the point.
The draft engine
Refreshes, re-scores, scans signals, and drafts outreach for every record. Fast and tireless, but it never gets the last word.
An objective critic
An independent reviewer that holds bad drafts on deliverability, ICP/persona, in-scope motion, verified-claims, and length. It can't be sweet-talked by the maker.
Dallas / the rep approves
Nothing leaves the building without a person. The judgment stays human, and the gate is where it lives.
The single front door: one screen with headline numbers, the seven-step diagram, and a tile per window. The numbers shown are seeded until Salesforce and Clay connect on go-live.
A single state file every dashboard reads and the conductor writes. It kills dashboard drift, so there is exactly one version of what is true at any moment.
The guardrails are the product.
This is what separates engineered from sprayed. The governing principle, in order:
WIP-of-one
Only one motion scales at a time, which prevents sprawl. Star Ratings is the one; everything else waits in backlog until it earns the slot.
Throughput-by-operator
Alarms if my share of weekly releases exceeds a 20% ceiling. "Done" means the team runs it unaided, not "works when Dallas runs it."
Operator-test
A motion only flips to "operable" after two consecutive batches released by a non-Dallas operator. The system has to survive me.
The bar you set, and how I am built to hit it.
How I hit it: Clay sources and enriches, the records write into the CRM already source-tagged, and the weekly run scales from a test slice to full volume. That is the path to new pipeline inside a month.
How I hit it: signal-triggered sequences, a team-wide experiment loop, and a deliverability check that holds quality as volume climbs. The 2x came with no engineering team.
Four targets, and how the engine delivers each.
Per your welcome note, these are a rough sketch we'll shape together. Every target below is provisional. Open any card for how the engine delivers it, the pre-mortem risk, and the leading indicator I own.
Sourced via the Star Ratings motion (MA payers at the bonus cliff) plus the back-office motion via Clay. Enriched, scored, and contextual.
Meetings live in reps' reply-handling, and those are people I don't manage. Conversion isn't fully mine to control.
Qualified replies sourced and source-tagged. The part of the funnel the engine owns end to end.
One push becomes a motion that runs every week. Gated by a deliverability floor so a multiple means real replies, not volume.
Vanity volume burns domains. A "10×" measured in sends would poison the sourced contacts we depend on.
Qualified replies per week, behind a deliverability gate. The honest definition of throughput.
Sourced via Clay inside the install base and sold into existing customers. This number is mine regardless of product timing.
Sourcing against a non-existent ICP. Fixed by defining the ICP with Scott Kemme in Week 1.
Enriched, source-tagged contacts added to the install-base white-space view.
A living system that stays current: lists, signals, measurement, cadence, agents, calculators, control plane. All maintained, not shipped once.
A system that works Day 1 and rots by Day 90. The throughput + operator tripwires exist to prevent exactly this.
The engine stays green: preflight passes, guardrails report no integrity errors, the team runs it unaided.
Where I come in: I own the GTM engineering behind all three numbers. The Clay build, the enrichment and signal library, the list expansion, and the measurement that turns a number into a motion that repeats.
One motion scales at a time. On purpose.
The team has Star Ratings live and working. My job is to make it produce more, and to scale exactly one motion at a time. Back Office is staged behind that line on purpose.
Star Ratings
The team's live play at the CMS 4208 cliff. Director-plus contacts in Finance, Stars, and Medicare across non-customer plans under 4.0, enriched and drafted on Clay. I won't restate it. I'll show how I make it produce more.
The 2028 call-center measures are the cleanest, most finite attribution window. That is exactly why measuring credit and scaling safely matter now. Here is where the engine comes in.
Back Office
The manual back-office white space inside existing customers. Held behind two things, deliberately:
ICP definition with Scott Kemme.
Back Office Optimizer GA, targeted around September (Chris Busbee's product).
Correctly not scaling yet. One motion at a time. It earns the slot when Star Ratings has handed off.
Today it is a one-time CMS pull. I wire the signal library into the weekly run, so a fresh trigger re-fires that account with an updated angle on its own. A Tier 1 CMS release, or Stars language in a filing. A Tier 2 plan slipping under 4.0, or a new quality leader. The 157 becomes a queue that re-prioritizes itself, not a static blast.
Grade the 38 plans by how far each sits from 4.0, weighted by how much the call-center measures can actually move it. Reps work the most winnable contracts first instead of the whole list at once.
The 2028 window is finite. Source-tagged credit at the qualified-reply line, plus a live two-motion funnel, shows what this motion sourced while it still counts. Not in a write-up months later.
An independent reviewer and a deliverability check sit in front of every send. We can push real volume without burning the 157 high-value Stars contacts. Volume that stays clean.
The tools are already live. Here they are.
Your page made the case for tools instead of decks and calculators instead of spreadsheets. I will not restate it. These are the actual tools, open and clickable today.
Command Center
The single live front door. Gates, approvals, deliverability, variant winners, and attribution credit in one screen.
Golden List board
Accounts scored and graded. The foundation layer, made visible and sortable.
Control Plane
The install-base white-space view. The 200 back-office target, mapped per account.
ROI Calculator
A live economic-impact tool. The CFO business case, built from inputs instead of a static PDF.
Mission Control
The daily personal tracker. What to work, in what order, today.
this page is the engine
I'm showing you.
Nothing left to build. Here's the proof.
All of this was built pre-access. It runs dry-run today and goes live Jul 6 by wiring the marked hooks, with no structural change.
--preflight. Fail-closed.engine_state.json. Every dashboard reads it, the conductor writes it.Nothing here needs to be built. It needs to be wired to real data on Day 1. The pre-access work is design, spec, and content. The go-live work is four checklist items.