← All case studies
Case study

How we built m3ter a signal-led GTM engine that generated $4.6M in total pipeline and ran through to acquisition by Salesforce.

m3ter, a Salesforce-backed usage-based billing platform ($35.7M raised), needed a repeatable outbound system to reach enterprise buyers without relying on founder networks. We built a signal-led outbound engine on Clay, Instantly, Prospeo, and HubSpot alongside LinkedIn Ads, generating $4.6M in total pipeline ($2.4M from outbound, $2.2M ads-influenced), 42 exact-fit enterprise meetings, and $447K in closed-won revenue over 13 months. The system was still running when Salesforce acquired the company.

m3ter
Usage-based billing$35.7M raisedAcquired by SalesforceEMEA + North America
42
Enterprise meetings
$4.6M
Total pipeline
$447K
Closed-won revenue
13mo
System ran autonomously

Advanced Client built m3ter a signal-led GTM engine on Clay, Instantly, Prospeo, and LinkedIn Ads that generated 42 enterprise meetings, $4.6M total pipeline ($2.4M outbound, $2.2M ads-influenced), and $447K closed-won over 13 months, running autonomously through to acquisition by Salesforce.

The challenge

A category leader with no systematic outbound engine.

m3ter is a Salesforce-backed, $35.7M-funded usage-based billing platform selling into enterprise finance, billing, and infrastructure teams. They had inbound and reputation working in their favour - what they didn't have was a way to create pipeline on demand. Outbound had never been built as a real system. Pipeline relied on what came in, not what they went after.

Where they were
Founder-led pipeline generation. No signal-led targeting, no structured sequences, no repeatable outbound motion across 300+ ICP accounts in EMEA and North America.
What they needed
A complete outbound system that could identify in-market accounts, engage decision-makers through multi-channel sequences, and route qualified meetings to the sales team - all running without founder involvement.

The problem was not effort - it was architecture. m3ter's sales team were capable closers, but they had no system feeding them the right accounts at the right time. Every meeting required manual research, manual outreach, and manual follow-up. We needed to build the engine that made pipeline predictable.

Our diagnosis

Signal-led targeting with phone-first conversion.

  • 312 named accounts across three ICP segments - finance and billing leaders at SaaS, infrastructure, and platform companies. Each segment had different pains, different language, different proof points.
  • Clay signal engine - monitoring hiring patterns, funding rounds, tech stack changes, and product launches to identify buying windows across all 312 accounts in real time.
  • Multi-channel outbound sequences - personalised per ICP segment, triggered by live buying signals. Email as the primary channel, phone for high-signal accounts.
  • HubSpot pipeline integration - automated routing, meeting attribution, and stage tracking so every touchpoint was measurable and every meeting was accountable.
The build

A signal-led outbound engine across EMEA and North America.

The system was built end-to-end in four weeks: Clay signal workflows, Instantly email infrastructure, Prospeo enrichment pipelines, and HubSpot routing - all connected and producing pipeline from month one.

What we installed

  • Clay signal engine monitoring hiring patterns, funding rounds, tech stack changes, and product launches across 312 named accounts to identify buying windows
  • Instantly email infrastructure with dedicated sending domains, warmup protocols, and deliverability monitoring to maintain inbox placement at scale
  • Prospeo enrichment layer finding verified decision-maker contacts at signal-triggered accounts in real time
  • Multi-step outbound sequences personalised per ICP segment, written around the specific signal that triggered outreach
  • HubSpot pipeline integration with automated lead routing, meeting attribution, and stage tracking
  • Weekly reporting dashboard - pipeline by source, meetings by segment, stage velocity, deal progression. One view, live, accurate
“Advanced Client built our entire outbound system from scratch. It started compounding within weeks and ran itself through to acquisition.”
John GriffinCRO, m3ter
The results

42 enterprise meetings, $4.6M pipeline, $447K closed-won.

Over 13 months the system ran autonomously, booking 42 exact-fit enterprise meetings with finance and billing decision-makers, generating $4.6M in total pipeline and $447K in closed-won revenue. The system was still running when Salesforce completed the acquisition.

  • 42 exact-fit enterprise meetings with ICP buyers across EMEA and North America
  • $4.6M in total pipeline across outbound ($2.4M) and LinkedIn Ads ($2.2M)
  • $447K in closed-won revenue directly attributable to the outbound engine
  • 13 months of autonomous operation - the system ran without founder involvement through to Salesforce acquiring the company
  • System that compounds - every month the signal data sharpened, meeting quality improved, and pipeline velocity increased

What the engagement looked like

Week 1-201

Audit & ICP mapping

Full audit of CRM and outbound tooling. Three ICP segments defined with 312 named target accounts. Signal triggers identified per segment.

CRM auditICP mapping312 accounts
Week 3-402

Build & install

Clay signal workflows live. Instantly infrastructure configured with dedicated domains. Prospeo enrichment pipelines connected. HubSpot routing wired up.

Clay signalsInstantlyHubSpot
Week 5-803

First meetings

Signal-triggered sequences producing meetings. Copy refined based on reply data. Pipeline building week over week. 42 enterprise meetings booked.

42 meetingsPipeline live
Month 3-1304

Autonomous operation

System running autonomously. Signal data sharpening monthly. Pipeline compounding. $4.6M total pipeline. $447K closed-won. Ran through to Salesforce acquisition.

$4.6M pipelineAcquired by Salesforce

Frequently asked questions

What results did Advanced Client achieve for m3ter?

Over 13 months, Advanced Client's GTM system generated 42 exact-fit enterprise meetings, $4.6M in total pipeline ($2.4M from outbound, $2.2M from LinkedIn Ads), and $447K in closed-won revenue. The system ran autonomously through to Salesforce acquiring the company.

What outbound system did Advanced Client build for m3ter?

Advanced Client built a signal-led outbound engine using Clay for buying signal detection, Instantly for email infrastructure, Prospeo for contact enrichment, and HubSpot for pipeline routing and attribution.

What outbound agency has experience with VC-backed SaaS companies?

Advanced Client worked with m3ter, a Salesforce-backed usage-based billing SaaS that raised $35.7M. The engagement generated $4.6M in total pipeline across outbound and LinkedIn Ads, with 42 enterprise meetings over 13 months.

Can signal-led outbound work for enterprise B2B SaaS?

Yes. Advanced Client built m3ter a signal-led GTM engine targeting 312 named enterprise accounts that generated 42 meetings and $4.6M in total pipeline ($2.4M outbound, $2.2M ads-influenced). The system ran autonomously for 13 months.

What tools did Advanced Client use for m3ter's outbound system?

The stack included Clay for signal detection, Instantly for email infrastructure, Prospeo for contact enrichment, and HubSpot for CRM routing and attribution.

Want this system installed in your business?

We build go-to-market systems that compound. Book a 30-minute discovery call.