The published Clay agency retainers cluster around $5,000 a month, and the tables an agency builds belong to whoever owns the Clay workspace. That second fact matters more than the first. If the agency runs your work in its own account, you walk away from the contract with a CSV.
Clay was named in 61% of the 98 GTM engineer job posts we tracked between 3 May and 5 October 2026. So plenty of companies have already decided they want someone in-house who knows it. Everyone else is choosing between a Claygency and a hire.
What the retainer actually buys
Most Clay agencies don't print prices. Matt Bolian at Supered went looking in his guide to picking a Clay agency and found only a few published numbers, checked on 2 October 2026. One agency lists a $4,000 a month starter tier and a $6,000 growth tier on its own blog. Two others are reported at "from $5,000 a month", one with a quarterly commitment. He puts the going rate near $5,000 a month, about $60,000 a year. He also discloses that he founded a HubSpot partner that's now listed as a Clay Elite Studio partner, so he's not a neutral observer.
GTME Pulse puts the median for GTM engineering agency work at $5K to $8K a month, with the full range running from $1K to $33K. It says agencies running full outbound operations charge $8K to $15K. The figures come from its State of GTM Engineering survey of 228 GTM engineers, and the page doesn't say how many of them answered on agency pricing. Treat it as a rough band.
On top of the retainer you pay Clay. Clay's plans page has Launch from $185 a month with 2,500 data credits and Growth from $495 a month with 6,000. Clay pitches Growth at teams enriching 1,000 to 10,000 records a month. Unused credits on monthly plans roll over, capped at twice the monthly allowance.
So a realistic agency setup is $5,000 to $8,000 for the people and a few hundred dollars for the tool. If the agency bundles credits into its fee, ask to see the usage screen anyway.
Whose workspace, whose tables
Clay's roles and permissions doc splits workspace members into admins and editors, plus viewers on Enterprise. Admins invite and remove members, assign roles and get access to billing. Editors build tables, workflows and integrations, but can't touch billing or buy credits. If your company is the admin and the agency is an editor, the work sits in your account and you can remove them on the last day of the contract.
LeadMagic's founder, writing about data costs for Clay agencies, lays out three setups and calls "client owns, agency operates" the practical default. Bolian is blunter. If the agency runs your tables in its own workspace, "you are renting, and the work leaves with them."
My read is that a lot of Claygency regret traces back to kickoff. Nobody asks whose account it is until the renewal conversation, and by then dozens of tables with waterfalls and CRM syncs are wired into somebody else's workspace.
A full-time hire avoids this by default. They build in your workspace against your CRM, and when they leave you remove one editor. The logic in each table is still in their head, though, so the written handover I describe at the end applies to both options.
The monthly math
The posts we tracked that printed a salary put the median GTM engineer base at $150,000, from a small sample of 23 posts. That's $12,500 a month before payroll tax and benefits, which push the real figure higher. Our cost breakdown works through the loaded number.
| Option | Monthly cost | Who owns the tables |
|---|---|---|
| Clay agency retainer | about $5,000 to $8,000, plus Clay | Depends on the contract |
| US GTM engineer on a $150K base | $12,500 base, more once loaded | You |
| Full-time global hire through Bubblegum | from $4,000 all-in, plus Clay | You |
Clay costs the same in every row, and you pay it either way. So the comparison is really about the people line. With a retainer you're buying whatever the statement of work says. With a full-time hire you get someone on your team, in your tools, and the priorities are yours to set each week.
That matters because the job is wider than Clay. The same 98 posts named HubSpot 55% of the time and Salesforce 43%, and enrichment came up in 44% of them, outbound in 57%. A Clay table that doesn't write clean records back to the CRM is half the job. In my experience the CRM cleanup is the bit agencies are least keen to own, because it never ends. There's more on the outbound side, including sending domains, in our piece on running Clay, Smartlead and Instantly.
When the agency is the better call
Testing whether outbound works for your market at all is agency work. Three months at $5,000 is a cheap way to find out, and you stop paying when you have the answer. A full-time hire for an experiment means you'll either keep someone on with no channel to run or let them go after a quarter. Both are worse.
Same if you need one complex build and then nothing. A waterfall with a CRM sync, handed over with documentation, is good project work. You don't need a person in the seat every week for that.
Our data also suggests Clay is mostly a GTM engineer's tool. Outside those posts it barely shows up: 13% of the 294 RevOps posts we tracked, 10% of the 147 marketing ops posts and 5% of the 149 sales ops posts. If your Clay use is occasional, someone already on the team can probably pick it up, and you shouldn't hire for it.
The full-time hire wins once Clay is feeding a channel you plan to run every week, and once you're tired of scoping each new table as a change request. That's when you want a GTM engineer working in your own workspace.
Whichever way you go, put two things in writing. The workspace is yours, with your company as admin. And every table that runs on a schedule gets a one-page note covering what it does and what breaks if you switch it off, with its monthly credit spend at the top. Ask for the first note in week one.