Resource
Enterprise Clay Deployment Checklist
Thirty controls across six categories — apply before any Clay workflow touches a production CRM.
This is the pre-production gate we apply in engagements. Every unchecked box is a known failure mode from enterprise deployments. Work through it with the owner of each area — workspace admin, data owner, integration owner — before sign-off.
| # | Control | Owner | Evidence of done |
|---|---|---|---|
| W1 | Administrator ownership defined (named primary and backup) | IT / Security | Roster on file |
| W2 | Builder roles defined; build vs production access separated | Workspace admin | Permission audit |
| W3 | User permissions documented and reviewed | Workspace admin | Access matrix |
| W4 | Production / testing strategy established (environments or conventions) | GTM Engineering | Written convention |
| W5 | Naming conventions established for workflows and tables | GTM Engineering | Convention doc |
| D1 | Canonical CRM fields defined (which field is authoritative per attribute) | Data / RevOps | Field map |
| D2 | Source-of-truth rules documented per enriched attribute | Data / RevOps | Precedence doc |
| D3 | Normalization rules defined (formats, casing, country/phone standards) | Data / RevOps | Ruleset |
| D4 | Duplicate handling documented (matching keys, merge policy) | Data / RevOps | Policy |
| D5 | CRM write-back logic documented (which objects, which fields, when) | RevOps | Write spec |
| P1 | Approved data providers documented with purpose per provider | RevOps | Provider register |
| P2 | Waterfall order established (which provider is tried, in what sequence) | GTM Engineering | Waterfall spec |
| P3 | Provider fallback logic established and tested | GTM Engineering | Test results |
| P4 | Credit / cost thresholds established per workflow | RevOps | Budget table |
| P5 | Vendor ownership defined (who manages the relationship, keys, billing) | RevOps | Ownership note |
| F1 | Workflow owner assigned by name | GTM Engineering | Inventory entry |
| F2 | Test dataset established for pre-production validation | GTM Engineering | Dataset |
| F3 | QA process established (sampling, expected-output review) | GTM Engineering | QA checklist |
| F4 | Error-handling behavior defined (retry, alert, degrade) | GTM Engineering | Behavior spec |
| F5 | Rollback procedure documented and rehearsed | GTM Engineering | Runbook |
| I1 | API ownership documented per integration | IT / Security | Register |
| I2 | Credentials securely managed (scoped, stored, rotated) | IT / Security | Key inventory |
| I3 | CRM permissions reviewed for the integration user | IT / Security | Permission set |
| I4 | Webhook behavior documented (payloads, auth, failure handling) | GTM Engineering | Interface doc |
| I5 | Downstream system dependencies mapped | IT / Security | Dependency map |
| G1 | Documentation requirements defined for every production workflow | GTM Engineering | Standard |
| G2 | Change-management process defined (review before production) | GTM Engineering | Process doc |
| G3 | Workflow review process established (cadence, checklist) | GTM Engineering | Calendar + checklist |
| G4 | Monitoring responsibility assigned | Ops | Roster |
| G5 | Incident response defined (who is called, what is the first step) | Ops | Runbook |
Using this checklist
Sign-off means every row has a name against Owner and evidence against Evidence of done. Where a row cannot be closed, that is your remediation list — and exactly what an Enterprise Clay Assessment would prioritize.