Strategy Track · Script · v6 — RECORDED Sep 22
~11 min · Artifact: Credit Ledger (/ledger) · Exercise: /quiz + worksheet · 5 reel cues
v6 (2026-09-22, read-aloud pass 1 — OPEN) — cold-open stories replaced with Sarmad's real ones: story 1 = GTM team burned 120K credits in one accidental run (enrichment on the entire audience, no segment on top); story 2 = company on a 600K package used only 150K (testing + one-off lists; no CRM sync, no data foundation, no inbound/outbound), new button "they paid for an engine and never turned it on." First paragraph reframed: know how Clay charges (data credits + actions) before approving any run; horror stories = credits burned unknowingly, protocols never set. Downstream callbacks synced (recap story references; Q1 rollover-cap callback now points at the 600K company). Standing rule: NO em dashes anywhere in spoken script lines — full sweep done on S2 (commas/periods instead); metadata and production notes exempt.
v5 (2026-09-20) — pre-emptive editorial pass applying every S1 learning BEFORE Sarmad's read-aloud: (1) pricing re-verified against Clay's live pages (clay.com/pricing + university.clay.com docs + FAQ, fetched 2026-09-20) — success-only billing CONFIRMED in Clay's own words ("You'll only be charged Data Credits when Clay successfully returns data. The same is true of Actions"); meter prices updated to Clay's published numbers (data credits from ~5¢; actions under 1¢); CSV-export-is-free claim REMOVED (exports/syncs are Actions under the 2026 model); rollover made precise (actions expire monthly; data credits roll to a 2× cap); top-ups at a 30% premium; NEW guardrails beat (pre-run cost estimate, import confirmation modal, the >5%-of-budget warning); (2) in-script visual scaffolds added per the standing rule (meters diagram, filter-funnel flow, two-lane BYOK split, numbered question lists — all render on the page/teleprompter/cue cards) + Hassan seed ideas per scaffold; (3) recap rebuilt to house style ("Here's a quick recap…" + breakdown in the video's own terms); (4) exercise unscored ("this one's for you"), Skool line removed, Credit Bill Reader tool reserved; (5) FETE/Audiences continuity line ties the meters to S1's two frameworks; providers count aligned to 200+.
v4 (2026-09-19) — v2 voice pass + v3 paid-course opener + flow pass (fragment chains removed). Rewritten against `production/VOICE-PROFILE.md` after Sarmad flagged v1 as robotic.
Track: Strategy (full script, no demo segment — per COURSE-CONTEXT) · Runtime: ~11 min · Artifact: F-02 The Credit Ledger Card (shared with 0.2 by design) · Exercise: two-meter quiz (10 scenarios, self-check 8/10) + decode your own plan into the worksheet — NOT scored, no Skool submission
Sourced from: SARMAD-INTAKE.md — G2, G3, G4, G12 · intake-sources/client-delivery-calls.md §6 (the 10,000-row exchange, anonymized) · brain/02 (stats, pain language) · brain/06 + the Clay Credit Discipline guide (ledger, BYOK) · clay.com/pricing + university.clay.com/docs/actions-data-credits + docs/credit-usage + clay.com FAQ (fetched 2026-09-20 — success-only billing, meter prices, rollover/top-up rules, guardrails) · brain/09 (enemy #2: the Credit Fire) · brain/13 (leader-track template; single big-idea close) · production/VOICE-PROFILE.md.
Differentiation from 0.2: 0.2 = the meters live in the UI (mechanics). S2 = the economics as judgment — read a plan, question a burn, fear the right things. No UI here except one plan-page read. The 95%-one-seat story is reserved for S3 (0.2's draft should move off it at revision — see production notes).
(paid-course opener: orient → stakes → in. No tease grammar.) Okay, this video is about how Clay charges you money. Before you build anything, before you approve anything to run on a set number of rows, you need to know exactly how Clay charges: data credits and actions. And I'll be honest with you, almost every Clay horror story I've seen comes down to credits burned unknowingly, because nobody set the protocols or studied how the billing actually works. So this is where we start.
And I've seen it go wrong in both directions. I've seen a GTM team burn a hundred and twenty thousand credits in one shot. They ran enrichment on their entire audience by accident, no segment on top, and it ate everything they had. And I've seen the opposite. A company sitting on a six hundred thousand credit package that only ever used a hundred and fifty thousand, and that was just testing and a few one-off lists. No CRM connected for ongoing enrichment, no data foundation, no inbound, no outbound. They paid for an engine and never turned it on.
Same root cause both times: nobody could read the bill. So that's what we're fixing right now.
(Master map appears: Strategy Track highlighted.) Quick note on where we are, this is the strategy layer. We're not building any tables today. Today you learn to read the bill.
Okay, so Clay charges you on two meters: data credits and action credits. That's the whole system. (the two gauges animate as spoken)
METER 1 · DATA CREDITS METER 2 · ACTION CREDITS ┌─────────────────────────┐ ┌─────────────────────────┐ │ buying data through Clay │ │ Clay DOING something │ │ email · titles · phone · │ │ enrich · AI call · CRM │ │ tech stack · AI research │ │ sync · export · API call │ │ from ~5¢ each │ │ under 1¢ each │ │ "the grocery bill" │ │ "the delivery fee" │ └─────────────────────────┘ └─────────────────────────┘ FREE: clean & normalize · formulas (sort · score) · dedupe · filter to segments · CRM imports · source from Clay's database · cross-table moves · audience lookups & updates
Meter number one, data credits. You spend these whenever you buy data through Clay. Think of any data gap you're filling: finding someone's email, finding the titles at a company, validating an email, pulling a phone number, looking up a company's tech stack. Running an AI agent that goes out on the internet and brings information back. Even generating content with Clay's AI models. All of that costs data credits. Prices vary by what you're buying, and they start at around five cents each. Think of this one as the grocery bill.
Meter number two, action credits. You spend these whenever Clay does something: runs an enrichment, calls an AI model, syncs a record to your CRM, exports a list out. Even an API call costs you an action. Basically, almost anything Clay performs charges a small action, and these are tiny, under a cent each. Think of that one as the delivery fee.
I said almost anything, because here's the good news. You don't need to worry, a lot of what you do in Clay is actually free, and the whole game is using the free stuff to bring down the number of rows you actually pay to enrich. (the FREE shelf stacks up, line by line) Cleaning your data. Normalizing URLs and company names. Formulas, to clean, to sort, to score your rows. Deduping. Filtering down to the exact segment that matters, so you only enrich those rows. Importing your data from the CRM. Sourcing accounts and contacts straight from Clay's own database. Moving data between tables, looking up your audience, updating it. All of that is free. Logic is free. Moving your own data around is free. Clay can source you a list of companies and people without charging a credit. You pay when you enrich them, or when you export them.
And one more rule, honestly, this is the one that should change how you feel about this whole tool. This is Clay's own billing FAQ, word for word: "You'll only be charged Data Credits when Clay successfully returns data. The same is true of Actions." A provider searches, finds nothing? Costs you nothing.
Now map that onto the two frameworks from the last video. On the FETE flow: Find is mostly free. Enrich spends data credits, plus a small action for the run. Transform with AI spends actions, or data credits, if Clay's models do the thinking. Export spends actions. And all the logic in between stays free.
Let me give you an example of this. A real conversation.
I was advising a founder, she had a list of ten thousand companies, and she wanted to run an AI agent on all of them to qualify them. Read each company, decide if it fits. Reasonable idea, right? So I asked her: okay, what does that cost?
✗ THE EXPENSIVE WAY ✓ THE CHEAP WAY
10,000 rows 10,000 rows
└→ AI agent on ALL of them └→ FREE filter (size · geo)
= 10,000 paid runs └→ 200 rows worth researching
└→ AI agent on 200
If you run the agent across all ten thousand rows, that's ten thousand paid runs, research cost on every single row. But here's the thing, she already knew half those companies were the wrong size and the wrong geography. And knowing that isn't research, right? That's just a filter, and filters are free. So you filter first, that costs you nothing, you get it down to the two hundred companies that actually deserve the research, and you run the agent on just those. Same output, at a fraction of the cost. And she got it in one line. She said: "So if I filter it myself first and give Clay the two hundred names, that's two hundred runs." That is correct. That's the whole game.
Build the free part first, and the paid part last. Every Clay horror story you've heard, and look, the data says teams underestimate their Clay costs by forty to sixty percent, and new users burn like seven hundred to a thousand dollars in their first two weeks, almost all of it is this one mistake, multiplied. Paid columns doing a job the free ones do better.
Second judgment call: whose key pays?
THE DATA LANE THE INTELLIGENCE LANE
emails · phones · firmographics AI research · classify · write
→ buy through Clay's marketplace → bring your own API key
200+ providers, one contract OpenAI / Anthropic bill you at cost
→ costs data credits → Clay charges just the action
So when Clay's marketplace buys you data, emails, phone numbers, company records, you pay data credits. And honestly? Usually a good deal. Clay negotiated rates with two hundred–plus providers so you don't need fifteen contracts. So: buy your data through Clay.
But when the work is intelligence, an AI agent researching, classifying, writing, you can plug in your own API key. Your own OpenAI account, your own Anthropic account, does the thinking. You pay them directly, at cost. And this is Clay's own documentation, not a hack: connecting your API keys eliminates the data credit cost, an action is still consumed. That's it. Bring your own intelligence.
Now, one more thing, and this matters if you're the one signing the check. In March 2026, Clay rebuilt this whole pricing model. They split the meters. They cut marketplace data prices, some by fifty, some by ninety percent. And they started charging an action on every platform call, which used to be free. Older contracts got grandfathered. So if your plan is from before March 2026, don't touch it until you've done the math, right? And if it's not, just know this: the new model rewards exactly one kind of team. The kind that can read this ledger. Which is now you.
Okay, now let's read your actual bill. (one screen capture: a plan & usage page, sandbox account; the only screen in this video)
Your plan is two allowances, so many data credits, so many actions, every month. And there are three questions I ask against this page. Every time.
Question one, what did we buy? That's the plan line. And check the rollover rule while you're there, because the two meters age differently: your actions expire at the end of every month, use them or lose them. Your data credits roll over, but only up to a cap, twice your monthly amount, and then they stop accumulating. Remember that company from the open, sitting on six hundred thousand credits? This is where that money goes to die. The cap hits, and everything above it just stops counting.
Question two, what did we use, and on what? Usage, by table. I'll be honest with you, in one workspace I audited, one single table had burned forty-two percent of everything that company had ever spent. One table. And more than half the tables in there had never used a single credit. The bill was not a mystery. Nobody had looked.
Question three, what happens when we run out? Top-ups, and top-ups come at a thirty percent premium. So if you're buying overage credits every month, that's not a usage problem. That's a planning problem. It means nobody priced the runs before they ran.
And here's something in your favor: the platform itself tries to warn you. Before any run, Clay shows you the estimated cost. If an import is about to trigger paid columns downstream, you get a confirmation screen. And if a single run would eat more than about five percent of your monthly budget, it gets flagged before it fires. Those guardrails are real, but a guardrail only helps if the person clicking through it understands what the warning means. That's the difference between a speed bump and a speed limit.
So here's what you do with all of this. Five questions. They're printed on the back of the ledger card, and they turn any burn, any invoice line, any "hey, should we run this?" into a two-minute conversation. (the list builds on screen, one question at a time)
One: which meter did this touch, data, actions, or neither?
Two: did we pay only for successes? Because if something billed on failure, something's set up wrong.
Three: could a free mechanism have done it? A formula, a filter, a lookup on data we already own?
Four: whose key paid for the intelligence, the marketplace's, or ours?
Five, and this is the one that prevents the disaster instead of explaining it afterwards: what does this cost at the full row count? You ask that one before it runs. Because a reasonable-looking table, multiplied by fifty thousand rows, that's how budgets die.
Ask those five out loud in a meeting and watch what happens. You haven't built a single table yet, and you're already the most dangerous person in the room about this tool.
Here's a quick recap of what we learned in this video.
One: the whole economy runs on one rule. You only pay for results that come back, and logic is free. That's Clay's own billing policy. And once you can read it, both stories from the start of this video disappear. The team that burned everything in one run would have caught it before it ran, and the company sitting on an engine it never used would have known exactly what it was paying for.
Two: there are exactly two meters. Data credits buy information you don't have, that's the grocery bill. Actions pay for Clay doing something, the delivery fee. And the two age differently: actions expire every month, data credits roll over to a cap, the cap that killed those credits in my cold open.
Three: build the free part first, and the paid part last. Filter before you enrich. That one habit is most of the money.
Four: whose key pays, data through the marketplace, intelligence on your own key.
And five: the five questions on the back of the ledger card turn any credit conversation into a two-minute conversation.
And all of this lives on one card, the Credit Ledger. (card on screen) Both meters, everything free, and the five questions on the back. It's under this video. Print it, keep it next to your keyboard, and reading a Clay bill becomes a ten second job.
One thing the card can't do: it can't stop one untrained person from burning an entire balance while everyone else watches. That's not economics, that's governance, and it gets its own video later in this track.
Your exercise is under this video, and it's not scored. Take the two-meter quiz, ten quick scenarios, and answer each one in meters: credits, actions, or free. Then open your own plan and usage page and decode it with the worksheet. Ten minutes, and you can read any Clay bill in the room. You'll also find the credit calculator I built down there, so you never have to guess what a run will cost.
Next up: we step inside the tool. The Clay operating model, how this whole machine is actually put together.