RevOps: running the signal

Read this first

Your job is four things: get the leads where reps already work, route them by account ownership, hold the 48-hour SLA, and keep your CRM clean enough to prove attribution.

Nothing here asks your reps to log into a new tool. If they have to, the pilot fails.

Where the leads go

The right answer is wherever your reps already get leads. Don’t build a new place for them to look. We drop into the existing funnel and add context and priority to it.

We write to:

DestinationWhat it’s good for
HubSpot / SalesforceThe default. Contacts and accounts land in your CRM with our fields populated, so you can build lists and reports off them.
SlackImmediate notifications. Best for account owners who need to know today.
Google SheetAuto-updated in real time. Good for a pilot, or for teams without a clean CRM path yet.
ClayClone our template and it handles updates for every contact we’ve written. Map fields from there.
ClaudePull the leads directly if your team works in Claude.

All updates happen in real time, whichever destination you pick.

Fields we create

We create these at the contact and account level in HubSpot or Salesforce. All plain text, so you can build HubSpot lists and Salesforce reports off them without any extra work.

FieldWhat’s in it
PriorityHigh, medium, or low. This is what your SLA keys off.
Guessed StageHow far along the evaluation looks.
CompetitorsWhich competitors we’re seeing on the account.
ReasoningWhy we flagged it, in plain language, so a rep doesn’t have to ask.

We also write individual activity as Tasks / Activity records, so the history sits on the record rather than in a separate report.

If you connect your CRM, we create these custom fields automatically. It’s a one-click integration.

Emails and phone numbers

When we write to your CRM we enrich with contact info as best we can. Full enrich succeeds around 70% of the time on average.

Decide this before you start

If your process hard-requires an email address, you will lose leads. Not every LinkedIn profile can be enriched with one.

That's a real trade-off, not a bug to fix later. A flagged account with no email is still workable by phone and LinkedIn, and your reps are on LinkedIn anyway. Dropping those records because a field is blank throws away good accounts.

Account ownership and routing

We can look up account ownership from your CRM. Tell us which fields to read and we’ll follow whatever ownership patterns you already have. Accounts with no owner, or that don’t match anything, can be round-robined.

Our strong recommendation:

See the routing table for who works what by account type. Flagged current customers go to CS, not sales.

Expect accounts outside your ICP

Your competitors sell to companies you don’t target. Those accounts will show up, and that’s information, not noise.

Customers use this two ways:

What the reps actually see

Don’t make BDRs think. A rep needs two things: a contact, and the SLA they’re working it within. That’s it.

Attribution

Attribution is built in, as long as your CRM has all outreach activity in it. Meetings booked and opportunities created need to be logged cleanly. If they aren’t, no attribution model will save you.

We report meetings and opportunities created:

If you want booked meetings to go up, the team has to act within 48 hours of a signal. Without that, holding the pilot to a booked-meetings number isn’t a fair test of the data.

What has to be true for this to work

Be honest about these before the pilot starts, because each one invalidates the measurement.

Interception timing

Most flagged accounts are ones your competitors are prospecting. A fraction are live opportunities: about 1 in 4 of the high-priority ones, and 1 in 7 across the whole list.

Accounts merely being prospected aren’t time sensitive. Active opportunities are. By the time a signal is detected, delivered, worked, and a meeting lands, two weeks may have passed since that account started talking to a competitor. You need enough cycle left to compete:

Under 45 days, interception isn’t viable. The defense play on existing customers still is.

Tiers and the 48-hour SLA

How the pilot gets verified

What customers measure to decide whether this is worth a long-term investment.

The volume ladder

Before the gates, know what the numbers actually look like, because the gate and the expectation are not the same number.

StageWhat to expect
Raw feed30+ accounts a day
Marked high priority~10% of the feed, so roughly 40 to 200 a month
Live competitive opportunities1 in 4 of the high-priority ones, and 1 in 7 across the whole list, so roughly 20 a month
The gates are floors, not forecasts

The gates below are deliberately set well under what the ladder implies. They are the minimum bar for saying this works, not the number to plan against.

If you only just clear them, the pilot is technically passing and something else is worth debugging.

The gates

GateCriterionVerified by
Defend5 existing customers with competitor activity identifiedCRM cross-reference
Win net-new5 newly created opportunities flagged by the signal, created within 30 days of or after the first signalYour CRM, using the attribution window
Convert1 meeting bookedYour CRM
The meeting gate only counts if three things are true

A booked meeting is a test of your outbound motion as much as the data, so it is only a fair gate when:

  • You have a working outbound motion, and aren't testing new messaging in parallel.
  • The 48-hour SLA was actually followed on the accounts you're counting.
  • The numbers in the ROI calculator check out against your real ACV, booking rate and win rate.

If any of those is false, judge the pilot on the first two gates and fix the third condition before you judge it on meetings.

The leader-facing version of these same gates is on the leader page.

Ramp

Month one is structurally the weakest. Your team is learning the motion, and detection strengthens over the pilot as coverage and the feedback loop build. Weight the back half accordingly. Longer sales cycles extend the conversion window, not the detection gates.

We’ll do the setup with you

You don’t have to work this out alone, and most teams shouldn’t.

Ask and we’ll do the RevOps setup with you.

Related: Who works what · How reps work a signal