The engine, built
before day one.
Ready to run, built to co-shape. A GTM acquisition engine, enriched, scored, measured, and gated, prepared for July 6, so we start from a system instead of a blank page.
This is a contribution to shape with Naveen and the team. The durable value is the engine itself, and it holds up against whatever targets we land on together.
Where I’d point the engine first.
Two things before any of the build below: the sharper target I would aim the live motion at, and how to read every number on this page.
Not all 38 sub-4.0 plans are ours to move. A Star Rating is a composite, and most plans miss the line on measures we do not touch. The winnable set is the plans whose gap sits in the call-center measures Queue Optimizer is built to move, not the clinical or HEDIS ones. So the engine’s first job is not raw volume against 38. It is isolating the subset where our lever changes the rating. That is the first cut I would make, and I would want your read on it.
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.
Every target account scored by fit and intent, so reps work the most winnable first instead of the whole list at once.
Director-plus contacts enriched from 40+ sources, so each record carries the context a message needs to land.
Hiring, tech-stack, news, and contract signals layered on, so outreach fires when the account is most ready.
The list feeds sequences directly through Clay, so a scored account becomes a contextual touch with no manual handoff.
The grade tells a rep which accounts to work today, so attention follows the highest-probability revenue.
Source-tagged from the first touch, so every meeting traces back to the motion that produced it.
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.
Every run starts by re-reading the build spec and re-asserting the single in-scope motion. Drift is logged. The conductor never wanders off-brief.
Pulls the latest account and contact data into the Golden List, so the week runs on current reality, not last week's snapshot.
Re-scores fit and grade across the list, so the most winnable accounts rise to the top before a single message is drafted.
Sweeps the signal library for fresh triggers and routes each to the right owner. A new signal changes the outreach angle.
The maker drafts a contextual message per record at the top of the queue. Fast and tireless, but it never gets the last word.
An independent reviewer holds any draft that fails deliverability, ICP and persona, in-scope motion, verified claims, or length. The maker cannot sweet-talk it.
Dallas or the rep approves, edits, or rejects. Nothing leaves the building without a person. The judgment stays human.
Send is gated on a green deliverability check: warmup, rotation, spam and blacklist monitoring. Scaling cannot turn into spray-and-burn.
Every send is source-tagged and metered into the attribution funnel, so credit is captured while the window still counts.
WIP-of-one, throughput-by-operator, and the operator-test recompute every cycle. The system has to survive me.
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.
Only one motion is allowed to scale at a time. Star Ratings holds the slot; Back Office and every modernize-OKR item sit in backlog. The conductor flags a violation the moment a second motion is marked scaling, so sprawl cannot creep in while my back is turned.
An alarm fires if my share of weekly releases passes a 20% ceiling. The point is that "done" means the team runs the motion unaided, not "it works when Dallas runs it." If I become the bottleneck, the number tells on me before anyone has to.
A motion only flips to "operable" after two consecutive batches are released by a non-Dallas operator. Every release I make resets the streak. The system has to survive me leaving the room, or it is not really done.
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.
Star Ratings is live and scaling. Back Office is staged behind it, on purpose. Pick a motion, then click through why it is a buyer now, how the engine runs it, who it reaches, what fires the outreach, the cadence, and where it stands.
Powers Star Ratings
The contact-center lever, in beta this year. It moves the call-center Star measures, so it is the capability behind the new-logo motion into MA plans at the cliff.
Powers Back Office
GA targeted September. It opens the back-office white space inside our customers, where the back office has not bought yet. That is the 200-contact motion.
The next signal
The supervisor view inside Decision Intelligence, replacing Burnout Indicator. As it lands, it becomes the adoption and expansion signal, and the in-product messaging surface.
Why Medicare Advantage payers are a buyer now
Each MA contract earns a Star Rating. Cross 4.0 and the plan earns the 5% CMS quality bonus on its benchmark. Miss it and the money is gone. Many plans sit just under the line.
Intradiem holds contact-center service level and cuts answer times in real time, with no added headcount. That moves the call-center measures that feed the rating, contract by contract.
Validated against the April 2026 final rule, the call-center measures count through the 2028 Stars, then drop first. The window to sell this clean attribution story is open now and finite.
How the engine runs the motion
From CMS data, Clay finds Director-plus contacts in Finance, Stars, and Medicare across 38 non-customer plans under 4.0, and enriches each record from 40+ sources.
It drafts a contextual message per record. An independent reviewer holds anything off-spec, deliverability is checked, and a person approves before a single send.
The signal library re-fires accounts on fresh triggers, a movability grade ranks the most winnable plans, and source-tagged credit proves what the motion sourced.
Who the motion reaches
VP and Director Finance who own the quality-bonus math and feel the 5% benchmark lift on the contract directly.
Director-plus Stars and Quality leaders who are accountable for the rating itself.
Medicare and contact-center operations leaders who can actually move the call-center measures.
The signal library that fires outreach
CMS releases, Stars language in SEC filings, and earnings-call mentions. The hard, dated events.
A plan slipping under 4.0, a new quality leader, or hiring clusters in quality and Medicare.
Background firmographics, technographic shifts, and secondary intent that raise priority.
One weekly motion, run by the conductor
A 7am weekday signal scan surfaces the day's priority strikes and expansion signals.
Monday 8am: preflight, the conductor run, and a refreshed Command Center. One push becomes a motion that repeats.
Every send clears the reviewer, the human approve gate, and a deliverability check before it leaves.
Where the motion stands today
157 Director-plus contacts across 38 plans under 4.0, built on 5,000 Clay credits.
Security review complete. Clay rolled out to the outreach team after training and build sessions.
These are the team's confirmed current state, not projections.
The white space inside our own customers
Manual back-office work inside existing customers that has not bought anything yet. We replace spreadsheets, not an incumbent.
Front-office relationships have not handed over back-office leads, so we source them ourselves through Clay.
Back Office Optimizer GA, targeted around September (Chris Busbee's product), turns the white space into a real motion.
The same engine, re-pointed
Clay sources contacts inside the install base and maps the back-office white space per account.
The same enrich, draft, review, approve, and deliverability-gated send engine, aimed at a new segment.
Source-tagged, so the 200-contact target is measured the same way as Star Ratings.
Who we reach, once the ICP is set
Back-office and operations leaders inside existing customers.
The exact ICP is defined with Scott Kemme in week one, before any sourcing.
Sourcing against an undefined ICP is the fastest way to waste the install base. ICP before sourcing.
Expansion signals inside the base
Install-base growth, new back-office hiring, and process-change signals.
Service or backlog signals that open a back-office conversation.
The trigger set is finalized after the ICP work, so it fires on the right moments.
It joins the weekly run when it earns the slot
Staged in backlog today. Only one motion scales at a time.
It earns the slot when Star Ratings has handed off and Back Office Optimizer is GA.
It folds into the same Monday conductor run, with no new machinery.
Staged, by design
ICP definition with Scott Kemme, and Back Office Optimizer GA around September.
200-plus back-office contacts inside existing customers, sourced through Clay.
Correctly not scaling. It is real, and it is held on purpose.
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.
The canonical front door. One screen with the gate states, the approval queue, deliverability, the winning variants, and attribution credit. The numbers are seeded until Salesforce and Clay connect on Day 1, and the chips say so.
The foundation layer made visible: every account scored and graded, sortable by fit, intent, and signal. Live today; it reads the real Clay base the moment it is wired.
The install-base white-space view. The 200 back-office target mapped per account, so the staged motion is ready to point the day the ICP lands with Scott Kemme.
The CFO business case as a live tool. Inputs in, economic impact out, instead of a static PDF. The lever behind both the Star Ratings and Back Office economics.
My daily personal tracker: what to work, in what order, today, so the weekly motion keeps its rhythm. Seeded until go-live.
A running head start, not a finished system.
I built the foundation before day one so we do not start from a blank page. It runs dry-run today. Day 1 wires it to live data, and the build keeps going from there, tuned to what each quarter needs.
--preflight. Fail-closed.engine_state.json. Every dashboard reads it, the conductor writes it.This is a foundation, not a finished system. Day 1 wires it to live data. From there the real work runs: tuning it, expanding it, and building what each quarter needs. The head start just means we are not designing from a blank page while the clock is running.