Customer story · Outbound & Demand Generation

One outbound engine, several ICP segments, continuously enriched

A services business sold into several genuinely different buyer segments with no RevOps owner and no repeatable outbound motion. LeanScale built a continuous enrichment-to-CRM-to-sequencing engine segmented by ICP, with account tiering and lead-score validation, and prototyped a lower-cost enrichment path.

ProofWhat happened on a real engagement.
Professional ServicesSector
Growth-stageStage
3–6 monthsDuration
2Min read

Anonymized. The company is described by sector and stage only — no customer is named, and quotes are attributed by role.

#The challenge

The business sold into several genuinely different buyer segments, each with its own buying committee and its own message, and had no dedicated revenue-operations owner to build or run outbound against any of them. Prospecting was ad hoc: lists were built by hand when somebody had time, enrichment was inconsistent, and there was no way to tell a good account from a bad one before a rep had already spent a week on it.

#The approach

One engine, segment-specific lanes

Built continuous enrichment with automated CRM imports feeding sequencing campaigns, run separately for each ICP segment — so list logic and messaging stay distinct per segment instead of collapsing into one generic blast.

Tier accounts and validate the score

Added account tiering and lead-score validation so reps work the top of each segment first, and so the score is checked against reality rather than trusted because it exists.

Health checks on the seams between systems

Ran recurring health checks on the pipe between the enrichment tool, the CRM and the sequencer — the failure that starves campaigns silently is a broken import, not a bad email.

Attack the enrichment cost line deliberately

Evaluated enrichment-provider alternatives and prototyped a model-driven scraping waterfall as a lower-cost substitute for part of the paid enrichment spend, delivered as a written migration recommendation rather than a surprise swap mid-campaign.

#Outcomes

A segment engine per ICP

Enrichment, CRM import and sequencing were stood up across every ICP segment rather than as one shared list.

Continuous enrichment rather than manual list builds

Enrichment runs continuously with automated CRM imports, replacing hand-built lists assembled when someone had time.

Tiering and lead-score validation in place

Account tiering and lead-score validation give reps a defensible order to work each segment in.

A documented lower-cost enrichment path

An alternative enrichment approach was prototyped and delivered as a written recommendation, giving the customer a costed option rather than a vendor lock-in.

The method behind it

This ran the Automated Outbound Sequencing playbook

The delivery standard this engagement followed.

Connected

In the knowledge graph

Every entity below has its own page, aggregating what we measured, what we recommend and what guests said.

Related

More on these topics

Proof Outbound & Demand Generation

An automated ABM engine: batch enrollment, generated personalization, and the guardrails that stop a bad send

A late-stage data and market-intelligence platform ran account-based campaigns whose personalization was generated by an internally built research pro…

3 sections · 4 min read
Proof Outbound & Demand Generation

Consolidating two sales-engagement systems into one: 22 cadences rebuilt one-to-one

A long-established enterprise software company ran conflicting activity data across its CRM and its sales-engagement tool, so reps trusted neither. Le…

3 sections · 2 min read
Proof Outbound & Demand Generation

Moving outbound off a native CRM sequencer and wiring a signal-trigger layer into it

A professional-services firm ran outbound inside its CRM's native sequencing tool, with no signal layer and no reliable way to re-engage the people it…

3 sections · 5 min read
Proof Outbound & Demand Generation

Turning public data sources and social monitoring into a scored outbound engine

A software vendor's buying signals were unusually public — public listings, procurement records, social posts — and none of it was reaching the SDR te…

3 sections · 4 min read
Method Revenue Systems

Attribution

Every Attribution project moves through the same four phases. Know what you produce in each — and know that, like CPQ, this is a project you win or lo…

32 sections · 20 min read
Method Automation

Automated Outbound Sequencing

Most playbooks start at Blueprint. This one starts before that — with three things that have to be true before you are willing to run the project at a…

41 sections · 30 min read