RAIN Group knew which buying signals mattered. They had no way to detect them.

Being good at inbound has a hidden cost.

RAIN Group has spent two decades building one of the strongest content and SEO engines in sales training. It works. Hundreds of qualified enquiries arrive every year without anyone lifting a phone.

The problem is what inbound selects for. Enquiries cluster in the mid-market. The enterprise organisations RAIN Group wanted, the ones running sales teams of 500 or more, arrive occasionally and unpredictably. A handful of large opportunities a year, none of them chosen, none of them repeatable. Jason Murray, RAIN Group's Chief Sales Officer, wanted a mechanism he controlled.

The time of need is elusive. Jason had already named the problem.

Enterprise sales training is not a utility. Nobody has to buy it. A company with 2,000 sellers can decide to improve sales performance a dozen other ways, and most of the time it is not thinking about capability at all. That creates a specific targeting problem, and Jason had a name for it: the time of need is elusive. RAIN Group wins a strong share of the conversations it gets with organisations that are actively looking. Finding out who is looking, this month, out of an enterprise universe of thousands, was the part nobody had solved.

He also knew exactly what the answer looked like. Three conditions, ideally all three, at minimum two:

• Executive mandate. Someone senior has decided the company needs to change how it sells in order to hit its objectives.
• Preference to partner. The organisation, or the person running enablement, buys expertise externally rather than building courses in-house.
• No incumbent lock. No entrenched training provider already embedded in the account.

Size the market before building anything.

The first decision was to refuse to guess. There is no point hiring SDRs, buying tooling or designing cadences before you know how many companies actually meet the criteria. If the answer is 200 accounts, that is a named-account motion with a handful of sellers. If the answer is far larger, it is a different build entirely.

So the engagement opened by defining and counting the market: organisations above the seller-headcount threshold, in in-scope industries, North America as first priority, with clear exclusions for segments RAIN Group does not sell into. That scope was agreed and signed off in writing before any data work started. Everything after that was built on a number, not an assumption.

Three phases, built inside RAIN Group's own tools.

Phase 1: A verified target market inside their CRM

The account universe was built in Clay against the agreed criteria, then filtered on estimated direct B2B seller headcount, so the list was sized by sales team rather than by revenue or employee count. Two client approval gates ran before any enrichment spend: an account review, so RAIN Group could confirm the accounts were genuinely in scope, and a contact-title review, so they could sign off on persona coverage first. Enrichment then ran as a waterfall through Prospeo, with BounceBan and ClearOutPhone verifying deliverability and validating numbers. The dataset was mapped to RAIN Group's Salesforce fields, pushed as a test batch, checked by their Salesforce expert, and only then loaded in full.

Phase 2: Three conditions, turned into a scoring model

Two of the three conditions are observable from public information. Executive mandate shows up in leadership changes, restructuring, and the language a company uses about how it wants to sell. Incumbent lock is visible in partnership and vendor signals. The third, preference to partner, is a mindset rather than an event, so it gets read at the individual level and confirmed in conversation rather than by the machine. In total, around fifteen live signals were built to detect these conditions across the market. BirdDog was configured to monitor the loaded target market, with the scoring model weighting the three primary conditions above surface-level activity and separating hot, warm and monitoring tiers. The feed is scoped to the loaded accounts only, so it never surfaces noise, and a refreshed score writes onto every Salesforce account record daily. A sample of flagged accounts went back to RAIN Group to mark false positives, and thresholds were retuned against that feedback before any rep saw the system.

Phase 3: A motion five enterprise sellers would actually run

RAIN Group's sellers are experienced enterprise closers. They will work an opportunity. They will not sit and cold prospect, and asking them to would have killed the whole system. So the motion was designed to hand them a reason, not a list. A Trellus parallel dialer was connected to Salesforce with call activity logging back to the record. A multi-touch cadence across phone, rep inbox and LinkedIn was sequenced around the signal rather than a fixed calendar. Each morning, prioritised accounts surface in Salesforce with the signal, the reason to call, and the queue already loaded. The reps got onboarding covering signal reading, the dialer, cadence execution and the daily workflow.

RAIN Group owns the whole system.

At handover, RAIN Group took full ownership of the system, with admin access to every tool in the stack. Everything was integrated into their own Salesforce and existing systems, so their team could take it straight over. Nothing in the build is proprietary to Advanced Client. The system runs without us. Their team owns it, changes it, and extends it. If they hire an SDR, that person walks into a working motion instead of a blank Salesforce instance and a hiring manager's hope.