S7 · The 90-Day Adoption Roadmap

(paid-course opener: orient → stakes → in) Okay, this is the last video of the course, and it's the one that decides whether everything before it actually matters. Because here's the number that should be on the wall of every company that buys this tool: a Clay instance without a named owner becomes shelfware within about six months. Not because the tool failed. Because nobody's name was on it.

You've spent this whole course building judgment. This video turns it into a plan: ninety days, in the right order, with owners, metrics, and a review that actually happens. And if you're a team of one, this still works. You're the owner and the sponsor both, the roadmap doesn't change, your review meeting is just shorter.

The sequence is the pyramid from the very first video, turned into a calendar. Bottom first, always.

  DAYS 1–30 · FIX THE DATA        one pilot: enrichment + hygiene on the
                                   records you already own
  DAYS 31–60 · FIX WHAT'S BROKEN   a process that's already failing:
                                   speed-to-lead, routing, dead form fills
  DAYS 61–90 · BUILD NET-NEW       the signal play you actually bought
                                   Clay for

Days one to thirty, fix the data. One pilot, nothing more. Enrichment and hygiene on the records you already own. This is unglamorous and it is non-negotiable, because everything you build later stands on it. And it produces the thing you need most in month one: something visible. A CRM that's suddenly complete is a result the whole company can see.

Days thirty-one to sixty, fix something that's already broken. Not a new idea, a current failure. Leads sitting for two days before anyone routes them. Form fills nobody enriched. A handoff that drops. Fixing a known-broken process is the easiest ROI conversation you will ever have, because the pain already has a number attached and somebody is already angry about it.

Days sixty-one to ninety, build net-new. Now, and only now, the signal play you actually bought Clay for. And notice what it's standing on: clean data, a process that works, and a team that has watched you ship twice. That's why it survives.

Almost every failed rollout I've seen inverted this. They started at day sixty-one on day one, built the clever play first, ran it on junk data, and quietly stopped.

Now the part that decides the whole thing: names on the roadmap. Not teams. Names.

  EVERY ROADMAP NEEDS THREE NAMES
  THE OWNER      builds and maintains it (your GTM engineer)
  THE SPONSOR    holds the budget and unblocks it (you, usually)
  THE CONSUMER   the person whose work gets better, by name

The owner builds and maintains. The sponsor holds the budget and clears roadblocks. And the consumer is the one whose job gets better, named specifically, because "sales will love this" is how projects die. "Marcus will use this every morning" is how they live.

Solo? You're owner and sponsor, and you should still name your consumer, even if it's you in a different hat. The reason is simple: the consumer is who you ask "is this actually better," and that question needs a real person to answer it.

And one governance line carries over from earlier in this track: every live table gets a named owner, and when someone leaves, their rows get reassigned the same week.

Three metrics. Not a dashboard, three numbers, baselined before you start, because a number without a baseline proves nothing.

  THE THREE ROI METRICS
  1 · DATA QUALITY   % of records complete on the fields that matter
  2 · SPEED          time from trigger to action (lead in → rep contact)
  3 · OUTPUT         pipeline or meetings from Clay-sourced work

Data quality, the percentage of records complete on the fields that actually matter. Speed, the time from trigger to action, a lead arriving to a rep touching it. And output, pipeline or meetings from Clay-sourced work. Those three, measured on day zero, day thirty, day sixty, day ninety.

Then the review, and this is where roadmaps die quietly. Thirty minutes, monthly, in the calendar, with the sponsor in the room. Four questions: what shipped, what did the three numbers do, what did we spend against budget, and what's next month's one thing. That's it. Solo, it's fifteen minutes with your own notes, and you still write the answers down, because future you is a different person and deserves a record.

Thirty minutes a month is the entire difference between a tool that compounds and a tool that quietly becomes a line item.

So let's go back to where we started. In the very first video I told you Clay is not a tool you buy, it's a capability you build. At the time, that was an idea. Now look at what you're actually holding.

You can read any Clay bill in ten seconds. You can govern spend without a single per-user cap, because you have protocols instead. You can open anyone's table and know in fifteen minutes whether it's good work. You can take over a workspace somebody abandoned and keep it alive. You know which mechanism answers which question at the lowest cost. You've built with every feature in the tool. And now you have ninety days, in the right order, with names and numbers on it.

That's the capability. Nobody can rent it to you, and nobody can take it out of your company, because it isn't in the tool. It's in you.

Here's a quick recap of what we learned in this video.

One: without a named owner, Clay becomes shelfware in about six months. The roadmap exists to put names on it.

Two: ninety days in the only order that works. Fix the data, fix what's broken, then build net-new. Almost every failed rollout inverts that.

Three: three names on every roadmap. Owner, sponsor, consumer, and the consumer is a person, not a department.

Four: three metrics, baselined. Data quality, speed, output. And a thirty-minute monthly review that actually happens.

The Adoption Roadmap template is under this video, with the role-to-module sheet, and the solo variant filled in as an example.

Your final exercise is under this video. Draft your own ninety-day roadmap. One pilot for the first thirty days, the three names, your three metrics with today's baseline, and the date of your first review. One page. Do it before you close this tab, because the roadmap you write today is the one that happens.

And then there's one more thing, and it's the last thing I'll ask you to do. When you've shipped your first pilot, book your call with me. Thirty minutes, every member who finishes this course. Show me what you built, tell me what you're building next, and we'll work out how I can best support your growth with Clay. The link is under this video.

You didn't just buy the tool. You built the capability. Now go put it to work. I'll see you on the call.