Priced on leads worked. Logged in your CRM.
You will not rip Salesforce. You will not add a mystery AI that writes to the wrong fields. The team works the list. Activity lands where ops can see it.
What this looks like for revenue operations
Revenue operations will not rip out Salesforce and will not add a mystery AI that writes to the wrong fields. The team works the list and the activity lands where ops can see it: calls, emails, texts, and outcomes recorded against the lead, imported from a CRM export or an inbound webhook and read back over the API and event webhooks. Native two-way sync connectors are not on the public plans today, and the site says so rather than implying it.
The Brain follows the playbook you approved; Earned Autonomy is the exception path, not the default. The price unit is one finance accepts in a sentence: 250 leads worked on Team for $1,999 a month, extra leads at $8. Every send and call is logged with who said what and when, useful the day compliance asks. Clay and Apollo stay where they are as the data layer; this is the team working the rows.
What does RevOps actually have to clean up?
In their words, not ours.
Reps who do not log
Process that exists in a wiki nobody opens
Forecasts built on missing fields
Another tool that creates a second source of truth
Will this break our Salesforce?
The design is to write activity into the CRM you already use, not to become a second CRM. You keep Salesforce or HubSpot.
Logging
Calls, emails, texts, and outcomes land in the CRM you already run.
Process
The Brain follows the playbook you approved. Earned Autonomy is the exception path.
A price unit finance accepts
250 leads worked on Team. Extra lead $8.00. You can explain that in one line.
Audit
Who said what, and when. Useful the day compliance asks.
Keep your data layer
Clay and Apollo stay where they are. We are the team working the rows.
What does the ops week look like?
- Data cleanup-hours fixing what nobody logged
- Pipeline reporting-manual stitching across systems
- Process-nagging people to enter it
- Forecast-padded for known gaps
- Five tools-that do not agree with each other
- Exceptions-not missing notes
- Pipeline-you can open it in the CRM
- Process-the team followed the playbook you approved
- Forecast-still needs judgment, but the activity is present
- One motion-into your system of record
What you actually open in the console
The views RevOps ask for first.
The numbers we can publish
Plan facts and published human benchmarks. Not an outcome rate we cannot back.
Human SDR figures ($11,200-$12,800 a month fully loaded) derive from The Bridge Group 2025 SDR report (on-target earnings), BLS employer-cost release (employer load on payroll), RepVue (SDR compensation), plus a typical tool stack and a manager's share. The cost-per-meeting figure divides that loaded cost by a 10-14.6 meetings-a-month median; it is derived, not a published price. Our own numbers are plan prices and capacity, never outcome promises. Model it on the AI SDR cost calculator.
Related Teams
Put this on your leads.
First 30 days on your own pipeline. No card. Talk to a human if security is the gate.