Most Clay writeups stop at founder-led social or community. The harder part is the handoff. Campaigns ship with account lists, rep training, routing rules, and scheduled call blocks. Growth spends roughly half its time making demand usable by sales, then moves to whichever funnel machine constrains throughput.
THE CLAY SYSTEM
Clay
$1M → $100M ARR in roughly two years
Build the brand first, then turn attention into a measurable enterprise factory.
Clay spent six years finding the product and the seventh building distribution. Its current engine is deliberately split: marketing creates demand and social proof; growth finds the bottleneck between attention and revenue. The result is 60% self-serve, 40% sales-led, with no cold outbound in the motion.
6 plays worth stealing.
Open a play for the mechanism, the exact receipt, the failure mode, and a deployment brief Elena can put into your backlog.
01 Turn executives into vertical media channels
Clay pairs each enterprise persona with the executive who naturally has authority with that buyer. The head of growth speaks to growth leaders; the CRO speaks to revenue leaders. Executives write the posts themselves.
The company gets multiple credible distribution nodes instead of one faceless brand account. Each feed runs a portfolio: roughly 20% promotion, 25–40% personal, 40% thought leadership, and up to 15% pattern-breaking humor.
6M organic impressions in one quarter, no paid amplification. One promotional post from Davide Grieco generated 4,500+ webinar registrations.
Map one operator to one buyer. Give them a repeatable editorial mix and one conversion event per month. Keep authorship with the operator; support can sharpen hooks, not manufacture opinions.
This fails when executives are ghostwritten into the same generic voice. Authority is the channel.
Company-reported. Clay’s growth team published the channel mix, impressions, registrations, and operating model.
Open the exact source ↗Turn this observation into a real experiment.
- Run it when
- Two or more executives already have buyer trust and distinct points of view.
- Owner
- Founder or content lead with each executive
- First sprint
- Assign one buyer to one executive. Publish four native posts and route one to a conversion event.
- Leading signal
- Qualified profile visits, replies from target roles, and event registrations by author.
- Stop rule
- Stop after six weeks if target-role response stays flat or authorship has shifted to ghostwriting.
02 Reverse-engineer content from the use case
The “How Clay Uses Clay” series is built around a painful job, such as inbound lead management, not a feature launch. The first half makes the business case for the buyer; the second gives the screen to an operator who builds it live.
One artifact serves executive education, practitioner enablement, product proof, and sales follow-up. It also expands category perception by showing jobs the market did not know Clay could perform.
About 19,000 registrations at a blended cost below $12 per lead; more than one-third came through social.
Choose one high-value job. Teach why it matters, then perform the work live. Give sales a call block immediately after the event while intent is warm.
A feature tour creates interest without intent. Start from the costly job, not the release notes.
Company-reported. Registration volume, blended CPL, format, and sales handoff come from Clay’s operating memo.
Open the exact source ↗Turn this observation into a real experiment.
- Run it when
- A painful use case converts in sales calls but is poorly understood in the market.
- Owner
- Use-case marketer and practitioner
- First sprint
- Write the business case, build the workflow live, then give sales a same-day follow-up list and talk track.
- Leading signal
- Registration-to-attendance, target-account attendance, and meetings booked within five business days.
- Stop rule
- Stop if attendance is high but qualified follow-up and product activation remain below baseline twice.
03 Make expertise confer status
Clay University, certifications, operator cohorts, local Clay Clubs, and enterprise experiences turn learning the product into a visible professional identity.
Education creates competent users; credentials give those users a reason to publish; publishing recruits the next cohort. The community is both enablement and distribution.
The company attributes much of its self-serve engine to user-generated content and reports enterprise customers publicly sharing what they built after cohorts.
Teach a scarce career skill, certify the outcome, and make the finished work easy to show. The status object is more important than the course library.
Certificates without labor-market value become swag. Tie status to a real capability buyers and employers recognize.
Unfairly synthesis. Programs and customer behavior are reported. The status loop is our interpretation of why they reinforce one another.
Open the exact source ↗Turn this observation into a real experiment.
- Run it when
- Product proficiency has real career or commercial value.
- Owner
- Community lead and subject-matter expert
- First sprint
- Teach one scarce job, require a public capstone, and recognize verified completion in the user’s profile.
- Leading signal
- Capstone completion, public shares, and new users attributable to graduate artifacts.
- Stop rule
- Stop issuing credentials if graduates do not use them publicly or employers and buyers do not recognize the skill.
04 Let partners build businesses on top of you
Clay treats agencies and implementation partners as a growth surface, giving them education, visibility, co-marketing, and client demand rather than a logo page.
Partners monetize the product’s complexity. Their incentive to win clients becomes Clay’s incentive-aligned acquisition and retention loop.
Clay reports partner agencies generating more than $1M a year from Clay work, with client workflows routing recurring usage through the product.
Define the paid service your ecosystem can sell, publish the delivery standard, certify providers, and route qualified demand to the best ones.
A partner program launched before repeatable implementation merely externalizes product confusion.
Company-reported. Clay reports partner economics and describes the enablement and demand-routing system.
Open the exact source ↗Turn this observation into a real experiment.
- Run it when
- Customers repeatedly pay third parties to implement or operate the product.
- Owner
- Partnerships lead and solutions lead
- First sprint
- Define one sellable service, certify five providers, publish the standard, and route ten qualified leads.
- Leading signal
- Partner-sourced activation, implementation time, customer retention, and partner revenue.
- Stop rule
- Pause intake if certified partners miss the delivery standard or create more support load than retained revenue.
05 Run sales-led growth as four machines
Clay models demand generation → capture → conversion → closing as machines in series. The team works on the slowest machine, even when the bottleneck falls outside a conventional growth remit.
Throughput cannot exceed the weakest stage. This stops the company from pouring more traffic into a funnel that cannot educate or process the demand it already has.
Enterprise ARR roughly tripled in nine months; sales-led revenue rose from 20% to 33%, or 40% including sales-assist. More than half of pipeline now traces to marketing.
Put one owner, capacity metric, conversion metric, and queue-time metric on each machine. Fund the constraint, not the loudest team.
Do not copy Clay’s channel mix. Copy its constraint logic; your bottleneck may be product activation or implementation capacity.
Company-reported. The four-machine model and revenue mix are described by Clay’s growth leadership.
Open the exact source ↗Turn this observation into a real experiment.
- Run it when
- Pipeline is growing but revenue throughput is not.
- Owner
- Growth lead with sales and revenue operations
- First sprint
- Map demand, capture, conversion, and close as queues. Add capacity, conversion, and wait time to each.
- Leading signal
- Throughput at the identified constraint and total cycle time from signal to close.
- Stop rule
- Re-diagnose when the constrained stage improves but total throughput does not move within one sales cycle.
06 Market the campaign to your own sales team
Growth spends roughly half its time making campaigns adoptable internally. Reps receive a ready-made account list every Monday, training on the buyer problem, and call blocks immediately after events.
A campaign becomes revenue only when sellers know whom to contact, why now, and what to say. Internal launch design compresses the lag from signal to conversation.
Clay discovered it was disqualifying 85% of demo requests because sellers lacked capacity, then expanded coverage and routed smaller prospects to group demos instead of dead ends.
Ship every campaign with a list, talk track, follow-up window, routing rule, and owner. Track lead handling as part of campaign performance.
More leads can make growth worse when response capacity is the constraint.
Company-reported. Internal campaign adoption, rep capacity, and demo routing are described in Clay’s own postmortem.
Open the exact source ↗Turn this observation into a real experiment.
- Run it when
- Campaign leads age before a rep makes a relevant contact.
- Owner
- Campaign lead and frontline sales manager
- First sprint
- Ship a named account list, buyer brief, talk track, routing rule, and a scheduled call block with the campaign.
- Leading signal
- Time to first touch, account coverage, reply rate, and meeting creation by rep.
- Stop rule
- Do not repeat if more than 20% of qualified signals remain unassigned or untouched after the agreed window.
Do not copy Clay. Adapt the system to your constraint.
Elena learns your product, customer, funnel, and current bets. Then she chooses the relevant pattern, scopes the first sprint, and watches the leading signal.