Mecka case study · Wellspring

Context · the client

One operating system for the automotive aftermarket

Mecka Inc. is a Canadian SaaS company. Its platform runs ACES/PIES catalog management, B2B portals, eCommerce storefronts, real-time inventory feeds and direct eBay Motors integration in one system.

Partner status

One of three

eBay Motors VIP partners worldwide, and the only one based in Canada.

Coverage

One platform

Manufacturers, wholesalers and retailers run on the same system, with data flowing between them in real time.

Market position

Category of one

One system in place of five. There is no direct equivalent in the market.

Diagnosis · a growth engine that had capped

An exceptional product with only one way to find buyers

Every new customer came through a warm intro, a partner handoff or word of mouth. That worked until the network slowed, and then the pipeline slowed with it.

Referral dependency

When the network slowed, pipeline slowed. There was no second engine.

Generic outbound failed

Spray-and-pray copy, bought lists and sending from the main domain. Deliverability collapsed and replies never came.

Small digital footprint

Little content, little inbound traffic, and nothing to amplify or retarget against.

Two broken layers, rebuilt from zero

Lists were broad and unsegmented, so a 3-person retailer got the same email as a 500-person wholesaler. And the sending setup put most of those emails in spam. The result was high volume, no traction and real brand damage. Flip the switch to see each layer before and after.

Outbound setup

TargetingBroad auto parts lists, no segmentationSignal-qualified accounts in three ICP segmentsBroken Rebuilt

PrioritizationEvery contact treated the sameScored on fit and signal, effort set by tierBroken Rebuilt

MessageOne email written for everyoneTwo angles, routed by signal, no calendar linkBroken Rebuilt

Sending domainThe main mecka.com domain3 secondary domains, 9 inboxesBroken Rebuilt

WarmupNone21 days before the first sendBroken Rebuilt

AuthenticationSPF, DKIM and DMARC partly configuredFull SPF, DKIM and DMARC alignmentBroken Rebuilt

TrackingOpen tracking onOpen and link tracking offBroken Rebuilt

Bounce rateAbove 8%Under 2% at send timeBroken Rebuilt

The sending layer, as built

Drawing · sending infrastructureWarmed

Domain 01 · secondary

Inbox 01

Inbox 02

Inbox 03

Domain 02 · secondary

Inbox 04

Inbox 05

Inbox 06

Domain 03 · secondary

Inbox 07

Inbox 08

Inbox 09

Warmup before first sendDay 21 of 21

Day 0Day 7Day 14Day 21

Send pace25emails per inbox per day

Daily ceiling2259 inboxes × 25 sends

Authentication

SPF DKIM DMARC

Tracking pixels

Opens off Links off

MethodHow the engine thinks

Four principles, one rule: every email needs a reason to exist

This is not cold email. Cold email starts from a list; signal-based outreach starts from a reason. The method is the part that transfers. Volume came last. First we decided who deserved an email, scored how much effort each account had earned, then chose what they would get from it and which version of the story fit them.

DetectA signal firesHiring, tech, visits, news

ScoreFit plus signal strengthThe tier sets the effort

RouteSignal picks the angleProof or comparison

OfferValue before a meetingAn asset, never a calendar link

P-01

Signal-based targeting

Only contact accounts showing observable evidence of a problem Mecka solves. Every prospect had a documented signal and a score.

See the signal map

P-02

Score before you send

Every account was scored on ICP fit and signal strength. The tier decided the effort: a hand-finished email, a sequence, or a wait for a stronger signal.

Try the scorer

P-03

Value-first messaging

No calendar link in the first email. Each angle offered something to opt into without booking a call: a case study or a comparison chart.

See the email anatomy

P-04

Two parallel angles

Different buyers respond to different framing. Signals sent skeptics to proof and evaluators to a comparison.

Try the router

P-01Signal map · three ICP segments

Every prospect showed up on the radar for a reason

Each observable sign of a Mecka-fit account was documented and built into a Clay table, one per segment. Lists were rebuilt every week from fresh signal data, never left static. Pick a segment, then select any signal on the radar.

Lists rebuilt weekly

Segment trigger · inner ringShared signal · outer ring

The pain we listened for

Segment triggers

Shared by all three segments

P-02Scoring · who gets what

The score decided how much effort each account earned

A signal says an account might be ready. A score says how ready, and how much effort it deserves. Every account was scored on two axes, fit with Mecka's ICP and the strength of its signals, and the resulting tier set the treatment. Toggle the example account and watch it move.

Account 01 · example

Fit2/2

Shared signals1/5

Segment triggerOff

FitHigh

Signal strengthWeak

TierTier 3

Weak signalsStrong signalsTrigger fired High fit Low fit

Example account with simplified rules. Real scores weighed every signal in the segment's Clay table.

P-03 · P-04Routing · two campaigns

The signal chose the story

A prospect never got a generic pitch. Once an account was scored and tiered, the signal behind it decided which angle they received: proof for senior buyers who needed reassurance, or a comparison for teams already living with a legacy tool. Pick a signal to watch it route.

Detected signal

RouterWhich angle?Waiting for a signal

Angle 1820 reached

Case study

Opens with: A similar company's outcome with Mecka
Offers: The case study one-pager, nothing more
Calendar: No meeting ask in the first email
Result: 57 replies · 34 opportunities · $216K

Angle 2450 reached

Comparison chart

Opens with: The legacy tool we detected in their stack
Offers: A one-page, feature-by-feature comparison
Calendar: No meeting ask in the first email
Result: 43 replies · 16 opportunities · $102K

Cycling through signals until you pick one

P-03 · Value first

Why the first email never asked for a meeting

A meeting request asks a stranger for their time before they have any reason to give it. Mecka's first email asked for something that cost nothing to accept, and let the meeting come later.

The usual cold email

Touch 1Asks for 30 minutes on a calendar linkCommitment: high

Most likely resultIgnored. There is no reason yet to say yes.

What Mecka sent

Touch 1Would you like the one-pager?Commitment: none

Touch 2Sends the asset. A real conversation opens.Commitment: low

ThenThe meeting ask, once it has been earned 50 opportunities

Workflow · the daily pipeline

Signal to send, every weekday. The handoffs are the workflow.

Every morning the pipeline runs in the same order: detect every signal, enrich and score, send, route replies. Apart from hand-finishing Tier 1 emails, the only manual step was a review before new sequences launched in the first week. Scroll through it.

Step 1 · Detect every signal Signal feeds

Listen to the whole market, every morning

Website visits were one input among many. Each morning the engine pulled fresh signals from every source on the signal map, for all three segments at once: who visited mecka.com, who runs a legacy system, who is hiring, who raised money or changed leaders, who is exhibiting at SEMA or AAPEX, who engaged with a competitor, who made the trade press.

Morning signal feed · exampleLive

Website visits · RB2BTech stack · legacy ERP and PIMHiring · job feedsFunding and leaders · CrunchbaseTrade shows · SEMA, AAPEXAssociations · directoriesLinkedIn · competitor engagementPress · trade publicationsMarketplace · eBay store level

InNine signal families, refreshed dailyOutNew and changed signals, matched to accounts in Clay

Step 2 · Enrich and score Clay

Stack every signal on one account

One Clay table per ICP segment took the morning's signals and stacked them on the right account, so a company that was hiring, running a legacy ERP and visiting the site showed up as one strong account, not three loose events. Contacts were found and enriched across the sources below, then every account was scored on fit and signal strength. Nothing was sent until its tier was set.

Sales NavigatorApolloRB2BTrade show listsAssociation directoriesJob feedsPublication scrapers

ScoreFit + signal strength, then tierCatch rateAbove 80% of contacts foundBounceUnder 2% at send time

Step 3 · Push to sequences Instantly

Send on infrastructure built to land

Tier 1 accounts got a hand-finished first email; Tier 2 accounts flowed into the matching angle's sequence. Everything went out across three secondary domains and nine warmed inboxes, at a pace that protects inbox placement.

Pace25 emails per inbox per dayTrackingOpens and links off, by design

Step 4 · Route replies Inbox

Turn replies into opportunities

Replies were routed for follow-up, where a yes to the asset became the opening for a real conversation. Half of all replies became a sales opportunity.

Replies100 across both anglesOpps50 sales opportunities

Results · the 90-day build

$318K in pipeline from 1,270 prospects

Everything here happened inside the 90-day build. Each dot below is one real prospect. Switch angles to see where replies and opportunities came from, and select a number to light up just those dots.

Prospects reached1,270Across both angles

Pipeline value$318KSignal-based outreach only

Every email was triggered by a signal. No ads, no calls, no referrals.

The funnel, step by step

Reached1,270prospects7.87%

Replied100replies50%

Qualified50opportunities$6.4K

Pipeline$318Kaverage $6.4K per opportunity

Sharper signal, higher reply rate

The comparison angle replied more often because every prospect was already running a tool Mecka replaces. It converted fewer replies into opportunities because a fulfillment step comes before a prospect qualifies. The case study angle earned more pipeline per prospect.

Case study angleComparison chart angle

No open tracking, by designOpen tracking was off, so there is no open rate to report. Tracking pixels signal automation to inbox providers and hurt deliverability. We traded the metric for inbox placement.

Takeaways

What carried the result

Scoring decides the effort
Not every signal earns the same email. Triggered, high-fit accounts got a hand-finished note within a day; warm accounts got a signal-led sequence; fit-only accounts waited for a stronger signal; low-fit accounts were never contacted. That is how a small sending footprint produced $318K of pipeline in 90 days.
Fit × signal → tier → treatment
Signal beats volume
A 450-prospect list with the right signal beat an 820-prospect list on reply rate. Smaller, sharper lists earn more replies for every email sent.
9.56% vs 6.95% reply rate
Value first beats the meeting ask
No first email carried a calendar link. Less friction lifted replies and made the second touch feel earned.
0 calendar links in first emails
Infrastructure is the floor
Three secondary domains, nine warmed inboxes, full SPF/DKIM/DMARC and no tracking pixels. This is the minimum, not the ceiling.
Bounce rate from above 8% to under 2%
Visitor data turns intent into reach
Visitors who never raised a hand still showed intent. Identifying them consistently produced the highest-converting replies.
Daily feed into Clay

Closing note

Signal-based outreach didn't replace referrals. It built a second engine beside them.

Engine 1 · ReferralsUnchanged. Scales with network depth.

Engine 2 · Signal-based outreachFires every weekday. Scales with infrastructure.

Mecka already had what most companies lack: a real product, a real differentiator and customers who prove the model. What it lacked was a repeatable way to reach new buyers. The new engine produces pipeline the business can plan around. The product is unchanged. What changed is who knows about it.

EpilogueAfter the build · months 4 to 9

The engine kept running: +$476K in the six months that followed

The 90-day build ended with the engine handed over and live. As part of our ongoing work with Mecka, the same system kept firing every weekday and added another $476K in pipeline over the next six months.

Time

90-day buildMonths 1 to 3OngoingMonths 4 to 9

Pipeline

$318KBuilt+$476KAdded

Pipeline to date$794KNine months, one engine, signal-based outreach only

Same daily signal feed

Every weekday morning, fresh signals from all nine families kept flowing into Clay.

Lists rebuilt weekly

Each week's lists came from fresh signal data, so the engine never ran on a stale list.

Same scoring and routing

Tiers kept setting the effort and signals kept choosing the angle, with no change to the method.

Mecka built a $318K pipeline in 90 days with signal-based outreach