Step 1
You file the brief
The five things we would ask in a first conversation: the problem, what done looks like, the data you can share, a deadline, a budget if there is one.
Clay Certifications for companies
Hand a real GTM problem to an operator who is being graded on solving it.
Every Clay certification ends with a project. Yours can be one of them: an operator builds your outbound, inbound, or paid ads system in Clay, Clay reviews the work, and you say whether it landed. Filing costs nothing.
Step 2
A certifying operator builds it
Clay scopes the brief into an assessment, matches an operator on the right track, and they build in Clay against your data with test runs, never live sends.
Step 3
You confirm, Clay certifies
The operator hands the work over. One click from you confirms delivery. Clay's reviewers grade the build and the interview; the operator's credential carries your project.
File a company brief
Three minutes. Steven reads each one and replies from his own inbox with a scoped project or a straight no.
What companies ask
- Do we pay the operator?
- Only if you choose to. The certification is the operator's reason to do the work well; a budget makes the project more attractive and is paid to the operator directly, never through Clay.
- Will anything be sent to our prospects?
- No. Certification builds push to test campaigns and test CRMs. Live sends and real CRM writes are yours to switch on after handover.
- What happens to our data?
- The operator sees what you give them, in your workspace or a sandbox you control. Reviewers read the build, not your raw customer rows. The public work sample, if you allow one, shows the system and the results you agree to name, nothing else.
- How long does it take?
- Certification projects run on a two week clock from the day the operator starts. Tell us your deadline and we match to it.