Script Room

SCRIPT 00 · THE INTRO — teleprompter cut (v5)

[FACE — direct to camera. Chapter card: "Start Here"]

Let me guess what's happening with Clay at your company right now.

Somebody's burning credits testing things. The vendor who built your tables is gone — or on their way out. And the last time your team needed a simple list enriched... it took four days and three Slack threads.

I've audited a workspace where four hundred thousand credits expired. Unused. While the company paid an agency every single month.

That's not laziness. Nobody ever trained the team. That's the whole problem. And that's what this course ends.

[beat]

So — who am I, and why should you listen to me?

I've been building in Clay every working day for over two years. And I didn't come to it as a content guy — I came to it as an operator. I ran my own agency before this. I owned sales and marketing end to end. I learned revenue by carrying the number.

[VISUAL: Bootprint website feature → Student Spotlight → Nathan podcast clip. Lower-third: "300+ applications · 2 scholarships"]

When I decided to go all-in on Clay, I applied to the Clay Bootcamp — it's called Bootprint now, Nathan Lippi's program. Three hundred–plus people applied. Two got full scholarships.

I was one of the two.

The week I graduated, I had multiple offers waiting — agencies, companies, one enterprise. I joined a Clay agency, helped scale it past fifty thousand dollars a month selling Clay as a service... and after seven months, I exited.

[beat]

[VISUALS: community events montage — rooms, whiteboards, crowds. Lower-third: "500+ GTM engineers · 3 clubs"]

Here's the part I'm most proud of, though.

In May 2025, I brought Clay Clubs to Pakistan. Today I run one of the biggest GTM engineering communities in the country — five hundred–plus engineers, three clubs, built entirely on people teaching each other. I've personally trained over three hundred people, one-on-one. Clay itself has given us shout-outs more times than I can count.

You're watching some of those events right now.

[VISUALS: Clay Cup — San Francisco venue, the stream, Javeria, THE TROPHY PHOTO]

And then Clay announced its first world championship. The Clay Cup.

I coached our contestant — Javeria Shah. The semifinals and the finals were in San Francisco. And here's the strange part: I got the visa. She didn't. So I was there, on the ground, representing us — while she competed remotely, from Karachi.

Four countries in the semifinal. We advanced. We won the final.

First Clay Cup world champions. That trophy photo you're seeing? That's real.

[VISUALS: Sculpt 2025 photos — with Jordan Crawford, Eric Nowoslawski, The Kiln founders; Clay office; speaking shots. Names on lower-thirds — VERIFY SPELLINGS AT EDIT.]

I was at Sculpt — Clay's conference — that same year. The people in these photos run the biggest Clay agencies in the world. This is the arena I live in. Not adjacent to it. In it.

[beat — settle in. FACE, closer.]

Now, after the championship, I started a company delivering Clay as a service to mid-market SaaS. And within a couple of months, I noticed something that honestly bothered me.

Everyone was buying Clay as an outbound tool. A silo. Bolted onto the side of the business. Nobody — nobody — was looking at the go-to-market system underneath it. The CRM. The routing. The lifecycle. The data model.

So I made a deliberate call. I joined LeanScale — a consulting firm for revenue operations and GTM operations, working with tech companies from Series A to Series D, ten to a hundred million in ARR. I'm still there today, building GTM engines for enterprises and unicorn-stage companies — and deploying Clay the way it's actually meant to work: as a layer inside the stack. Not a toy next to it.

And in every single engagement, I kept meeting the same person.

A sharp, experienced revenue leader — someone who's run go-to-market for a decade — completely dependent on vendors for something their own team should own. Not because they're not smart. Because GTM got rebuilt in the last three years — AI, agents, systems — and nobody built a structured path for the leaders living through that shift.

So I built it.

[DIAGRAM: course map — 8 milestones, two tracks]

Here's how it works. This is not a video library — Clay University is free, it's good, go there for feature tours.

This is a training system. Eight milestones. Every video ends with a build your team does in your own workspace. You submit the work. It gets scored. You don't move on until you pass — and if you blow the credit budget, you fail the exercise. Because that's exactly how it works in production.

Leaders — you get your own track. Four hours. No table-building. Governance, credit economics, how to audit any vendor's table in fifteen minutes, and how to make sure automation never poisons your CRM.

[FACE — final]

Walk in as a team that has Clay. Walk out as the team that runs it — with scored work to prove it.

One honest filter: if you're here to start a freelance agency, this isn't for you. And if your team won't submit work or can't take scored feedback — it won't work. That's the deal.

Everyone else: Milestone Zero starts now. First lesson — the three things everyone gets wrong about Clay before they've spent a single dollar.

[END CARD: "0.1 — The Clay Operating Model" · mastery meter at 0%]

Editor notes: visuals carry the proof; his voice stays candid and even. Names on Sculpt lower-thirds must be verified before render (Jordan Crawford · Eric Nowoslawski, Growth Engine X · Patrick Spychalski + Enzo, The Kiln — dictated spellings were unreliable). Written Bootprint citations verbatim per brain/12. Javeria's permission for name/footage. Final-opponent name (Norway per Sarmad) — confirm against the finale recording before adding to narration.

SCRIPT 0.1 · The Clay Operating Model

A company I worked with bought Clay, cancelled their outreach tool the same week — and discovered a month later that Clay had never sent a single email. Because Clay doesn't send email.

They're not stupid. They're the norm. Most teams buy Clay for what they think it is, and quit it for what it actually is. This video fixes that in nine minutes — because every dollar you spend after this depends on getting the mental model right.

Here's the picture that should be in your head. (Elements appear as narrated.)

On the left: your data sources — your CRM, your product, spreadsheets, the open web, and a marketplace of over a hundred data providers.

On the right: the places work happens — your CRM, your email sequencer, your ad platforms, Slack.

And in the middle: Clay. A programmable data layer. It pulls from everything on the left, applies logic — enrichment, AI research, scoring, formatting — and pushes clean, decided, ready-to-act data to everything on the right.

It's a factory between your data and your go-to-market. Not a database you browse. Not a sending tool. A factory.

Let me show you what that means in a real workspace — and bust the three myths while we're in here.

(Step 1 of 3 — a real table, wide view)

Myth one: "Clay sends my outbound." Look at this table — four hundred companies, enriched, scored, personalized. And this last column? It pushes to a sequencer. Clay loads the gun; something else pulls the trigger. Cancel your sending tool and you've cancelled your arms, not your ammunition.

(Step 2 of 3 — the enrichment panel)

Myth two: "Clay is like ZoomInfo — my reps will look people up in it." Watch what happens when I open this enrichment panel — waterfalls, run conditions, provider settings. This is an operator's cockpit, not a rep's search bar. ZoomInfo has two halves: the bulk-data half, which Clay replaces and beats — and the rep-self-serve half, which it doesn't. Your reps will get Clay's power a different way, and I'll show you that in Milestone Six.

And here's the myth that costs real money. Myth three: "It's plug-and-play." This is a real column a team built before training — an AI model researching something a two-cent lookup already knew. It ran on every row, all weekend. (zoom on the run history) There's no sandbox here by default, no draft mode, no undo. One misconfigured column, multiplied by fifty thousand rows. That's not a Clay problem. That's a training problem — the exact one we're solving.

Back to the map. (Pyramid builds.) Everything you can do in Clay stacks in a pyramid: at the base, your data foundation — the market map, clean records. Then outbound on top of it. Then inbound — speed-to-lead. And at the tip, the custom plays everyone wants to start with. Most teams jump straight to the tip. We build from the base — data quality first, broken processes second, new plays last. That order is the whole course.

Three decisions from today. One: Clay is the factory between your data and your GTM — plan around what it feeds, not what it replaces. Two: operators build in it, reps consume from it — staff accordingly. Three: build up the pyramid, never down.

Leaders — this is Artifact F-01, the Use Case Pyramid, one page. Print it. When anyone proposes a Clay project, ask them to point at the layer it lives on. If they point at the tip and your base is empty, you already know the answer.

Your exercise: six real scenarios. Place each one on the pyramid — or outside Clay entirely. Five out of six passes. Submit in the community; you can resubmit.

Next up: the two-meter pricing model — what's actually free in Clay, what isn't, and why knowing the difference is most of credit discipline.

SCRIPT 0.2 · The Two-Meter Pricing Model

One person. Five hundred thousand credits in the account. He burned a hundred and fifty thousand of them — testing. Random enrichments, no plan. Ninety-five percent of the whole company's spend, one seat. The rest? Three hundred and fifty thousand credits expired. Unused. Paid for.

Nobody taught him the meter. Ten minutes from now, nobody on your team will have that excuse.

Since March 2026, Clay charges you on two meters. (Two gauges appear.)

Meter one: Data Credits. You pay these when you buy information — an email lookup, company firmographics, an AI agent researching the web. Price varies by provider. Think of it as the grocery bill.

Meter two: Actions. You pay these when Clay does something — runs an enrichment step, calls an API, syncs a record to your CRM. Every operation, one Action, and an Action costs roughly a tenth of a credit. The delivery fee.

And here's the sentence that should be tattooed somewhere: (third element appears, highlighted) most of what people fear is expensive is actually free. Formulas. Filters. Imports. Looking up data you already own. Manual edits. CSV exports. Free, free, free, free, free, free.

One more rule that changes everything: you only pay for successful results. A provider that finds nothing charges nothing.

Let's read a real table through the two meters.

(Step 1 of 4 — import) I'm importing two thousand companies from a CSV. Watch the meters. (zoom: zero) Nothing. Imports are free.

(Step 2 of 4 — formula) Now a formula column — classifying these companies by domain ending. Two thousand rows classified. (zoom) Still nothing. Logic is free. This is why we build the free parts first, always.

(Step 3 of 4 — enrichment) Now I enrich fifty of them with a provider. (zoom on the cost preview) THERE'S the grocery bill — data credits per successful match, plus one action each. And notice: the twelve rows where the provider found nothing? Zero charge.

(Step 4 of 4 — CRM sync) And syncing the results to HubSpot — no data was bought, so: actions only. Pennies.

Now the failure that produces horror stories. This column here uses an AI agent with web research to find something that... (zoom) ...this free lookup column already had. Same answer. One costs three credits a row; one costs nothing. Run that mistake across a fifty-thousand-row table and you've spent thousands of dollars re-buying your own data. The most expensive column in most workspaces is doing a job a free column does better. Remember that sentence — it comes back in Milestone Two.

The full ledger, one screen. (table builds line by line) Marketplace enrichment: credits plus an action. Your own API key doing AI research: NO data credits — just an action. Signals: credits plus an action. Syncs, sends, pushes: an action. Formulas, filters, imports, lookups, manual work, exports: free.

That top-right cell — bring your own key, pay no data credits — is a strategy, not a footnote. Milestone Two is built on it.

Three decisions. One: know which meter every column touches before it runs — the ledger card makes that a ten-second check. Two: build free-first — logic and lookups before any paid step, every time. Three: failures are free, so a well-ordered waterfall is cheap to attempt — order is everything, and that's the next milestone.

Leaders: Artifact F-02 is the Credit Ledger Card. It also shows how to read your plan — how many credits and actions you're actually buying a month, and what happened in March 2026 when Clay split the meters. If your contract predates that, you're grandfathered, and the card tells you what to check before you ever switch.

Your exercise: ten scenarios — "your SDR imports 5,000 rows and runs two formulas: what does it cost?" Answer all ten in meters: credits, actions, or nothing. Eight right passes.

Next: workspace hygiene — the fifteen-minute setup that stops someone re-running the wrong table at three in the morning.

SCRIPT 0.3 · Workspace Setup & Hygiene

I audited a workspace with a hundred and fifty-two tables. Ninety of them — fifty-nine percent — had never used a single credit. Dead tables. Duplicate names. "Test," "Test 2," "Test final," "FINAL final."

Here's why that's not just messy: somebody on that team once re-ran the wrong table — because two tables had almost the same name — and re-bought data they already owned. Hygiene isn't cosmetic. Hygiene is money.

Four rules. That's the whole system. (Four tiles appear.) Nest — every table lives in a folder, nothing at root. Number — workbooks get numbers, their tables inherit them: workbook 1, tables 1.1, 1.2, 1.3. Describe — names say what a thing does, and the description field gets filled. Separate — your team's builds live in a team folder, apart from anything a vendor or another department builds.

Why numbering matters more than it looks: when you send data between tables, Clay shows you a picker. With numbers, the right table is obvious. Without them, you're guessing — with your budget.

Let's build it, from an empty workspace.

(Step 1 of 4) Folders first: one per motion — Inbound, Outbound, Data Foundation — plus the team folder, and one named Archive. That Archive folder is where dead tables go instead of haunting your pickers.

(Step 2 of 4) First workbook, numbered: "1 — Inbound Enrichment." Its tables: "1.1 — Intake," "1.2 — Company Resolution." Watch the picker now (zoom) — see how 1.1 and 1.2 sort together and read like a sentence?

(Step 3 of 4) Descriptions. Two sentences: what it does, what feeds it. Sixty seconds now; hours saved for the next person — who is usually you, in four months, having forgotten everything.

(Step 4 of 4) Column hygiene inside a table: inputs on the left, logic in the middle, paid enrichments after, exports last. And name columns for what they hold — "Verified Work Email," not "email 3."

The failure to burn into memory: two near-identical tables. (shows "Enrichment Q3" and "Enrichment Q3 v2") One is live and feeds the CRM. One is an abandoned copy. New teammate runs the wrong one — real story — and enriched two thousand rows that were already enriched, at full price. The fix costs nothing: the dead one goes to Archive, the live one gets a number. That's it. That's the whole discipline.

Three decisions. Nest and number everything — the picker is where hygiene pays. Archive ruthlessly — a dead table in the root is a loaded trap. And separate your team's work from everyone else's — because when a vendor offboards, you need to know in one glance what's yours, what's theirs, and what's feeding your CRM. That last one becomes a whole leader lesson later.

Leaders: F-03 includes the four rules as a one-page team policy. Adopting it costs one meeting. Not adopting it costs an audit — I've run those audits; take the meeting.

Your exercise: set up your workspace to the four rules — folders, one numbered workbook, descriptions, an Archive — and submit the screenshot. The rubric checks all four.

Next: the Quick-Wins Bank — fifteen things you could build this week, and how to pick your first three.

SCRIPT 0.4 · The Quick-Wins Bank — what to build THIS week

The most dangerous week in your Clay journey is week one. Not because you'll break something — because you'll wander. You'll enrich a random list, poke at an AI column, burn a few hundred credits on nothing in particular, and conclude Clay is "interesting." Interesting doesn't survive a budget review.

So before we go deep, I'm handing you fifty things worth building — and a way to pick your first three by Friday.

Every idea in the bank is tagged three ways. (Tags appear.) Function — is this a sales win, a marketing win, or a RevOps win? Effort — under an hour, under a day, or a real project? Cost — free, pocket change, or budget-worthy?

Your first three builds should all come from the same corner: (quadrant highlights) your OWN function, under an hour, pocket change or less. Wins first, ambition later. The pyramid from lesson one applies even here — you'll notice none of the fifty live at the tip.

Let me walk the shelf — five of my favorites, live in the workspace, so you can feel the size of them.

(Step 1 of 5 — sales) The event-list rescue. Marketing hands you a conference spreadsheet: half names, no companies, titles typed by hand. Import, normalize, domain-match, enrich emails through a waterfall. Thirty minutes. This exact pipeline once replaced a vendor a client was paying monthly — for lists like this one. (shows finished state)

(Step 2 of 5 — RevOps) The CRM gap-fill. Filter your CRM for prospect accounts with a blank industry field. Enrich ONLY those rows — gap-fill, never re-buy. Watch the run condition: "only run if empty." That single setting is the difference between a smart fill and a full re-purchase.

(Step 3 of 5 — sales) Champion job-change alerts. Your closed-won contacts from the last three years — are they still where you left them? A job-change check on your champions list is the highest-converting signal in B2B, and your first taste of Milestone Five.

(Step 4 of 5 — marketing) The competitor-customer scrape. Their case-study page is a target list they published for you. An AI column extracts company names from the page; a lookup turns names into domains. Twenty minutes, and weirdly satisfying.

(Step 5 of 5 — anyone) The meeting-brief generator. Tomorrow's demo call: one row, one enrichment pass, one AI summary column — a one-page account brief. Reps love this one, and it's how leaders usually first see Clay working.

The week-one failure: doing all five of these... on ten thousand rows each. Every quick win here is a small-batch build — fifty rows, a hundred. The win is proving the mechanism, not boiling your TAM. Volume comes after Milestone One teaches you what volume costs. Scope small, win fast, show someone.

Three decisions. Pick from your own function — a win you can't use isn't a win. Stay under an hour — momentum beats mastery in week one. And show the result to one other person — a quick win that nobody sees changes nothing politically, and politics is half of adoption.

Leaders: the bank doubles as your roadmap menu. In your track's final lesson you'll pick pilot projects from these same fifty — tagged by cost, so you can pre-approve budgets in one sitting.

Your exercise: open Artifact F-04, pick the three wins for YOUR org, and scope one of them with the Pre-Flight Calculator — rows, columns, estimated credits and actions, on one page. That scoping one-pager is your submission. It passes when the math is real.

That's Milestone Zero. Next milestone: the Data Engine — where you build your first production-grade table, and where the budget cap starts being enforced.