Skip to content
◇ Case study · Investor-relations fintech · North America
Fintech & PaymentsFintechNorth America

ShareChest.rebuilt as infrastructure, not a campaign.

ShareChest is an investor-relations fintech heading into a category-defining raise. Their buyers sit in capital markets, where a vendor's process gets audited as closely as its results.

We rebuilt outbound as infrastructure: one account list, a signal layer that scored it daily, and email, LinkedIn and calling sequenced against the same view — handed over with the dashboard the board would read.

◇ Snapshot
The brief
Replace three vendors and a burning domain with one outbound system a Series B board could audit.
Who they needed to reach
Capital-markets and investor-relations leaders.
Market
Canada and the United States.
Channels
Cold email, LinkedIn, and calling against one shared account list.
Timeline
Nine days to the first SQL; a six-month run.
47
Meetings / month
11.4%
Reply rate
9 days
Time to first SQL
Before
  • Outbound duct-taped across three vendors with no shared data model
  • The primary domain burning under its own sending posture
  • Forty-seven days from kickoff to a first sales-qualified lead
  • A 1.8% reply rate and six meetings a month
After
  • First SQL in nine days, down from forty-seven
  • Reply rate at 11.4%, up from 1.8%
  • Forty-seven meetings a month, up from six
  • Primary domain quarantined and delivering at 99%

Engagement timeline

How the build landed

Delivered
  1. 01Day 0–3

    Quarantine

    Primary domain pulled out of outbound; sending infra spun up.

  2. 02Day 4–9

    First live sequence

    Email + LinkedIn live against the first 400 accounts.

  3. 03Week 2–4

    Signal layer online

    Clay graph scoring accounts daily; sequences re-segmented.

  4. 04Week 5–8

    Calling layer + reply ops

    Operator-led queue; demo handoff inside 4 hours.

  5. 05Month 3+

    Board-grade reporting

    Auditable dashboard handed to CRO for board review.

◇ Challenge

An outbound stack that wouldn't survive a board review.

ShareChest was approaching a category-defining raise. Their existing outbound was duct-taped together across three vendors, no shared data model, and a sending posture that was actively burning the primary domain.

The CRO needed a system the board could audit — not a slide that promised meetings. Every artifact had to be inspectable: domains, sequences, scoring, routing, the lot.

◇ Approach

Triage first, then architecture.

  1. 01

    Quarantine the burning domain

    Move all outbound off the primary, stand up a dedicated sending infrastructure, and stop the bleed in week one.

    • 6 sending domains
    • Warmup orchestration
    • Deliverability monitor
  2. 02

    One account list, one signal layer

    Replace three vendor lists with a single Clay-orchestrated source of truth, signal-scored against actual buying intent.

    • Clay enrichment graph
    • Signal scoring
    • ICP definition
  3. 03

    Sequence email, LinkedIn, and calling against the same list

    Three channels, one account view, one reply queue. SDR replaced with operator-led handling; demo handoff inside 4 hours.

    • Multi-channel sequences
    • Reply ops queue
    • Demo handoff SLA

Shipped

What the client owns

Handed off
  • Sequence
    Multi-channel outbound system

    Email + LinkedIn + calling sequenced against the same account list with shared reply ops.

  • Workflow
    Clay → HubSpot enrichment graph

    Signal-driven enrichment scoring accounts on intent, fit, and timing — refreshed daily.

  • Dashboard
    Board-grade outbound dashboard

    Reply rate, meeting rate, SQL conversion, and pipeline sourced — auditable to the message level.

  • Playbook
    Series B outbound playbook

    Documented system the in-house team owns end-to-end, with calibration cadence.

Results

Movement, line by line

Client-supplied
MetricBeforeAfter
Time to first SQL47 days9 days
Reply rate1.8%11.4%
Meetings / month647
Primary domain healthBurningQuarantined · 99% delivery
◇ Results

Nine days to the first SQL.

Quarantining the primary domain in week one made everything after it possible: deliverability recovered to 99% and the first sales-qualified lead landed on day nine, against a forty-seven-day baseline.

The steady-state numbers held. Reply rate moved from 1.8% to 11.4% and monthly meetings from six to forty-seven, on one account list the in-house team now runs itself.

Would your outbound survive a board review?

Book a 30-minute audit →
◇ In their words
“They rebuilt our outbound stack like infrastructure. Nine days from kickoff to our first SQL, and it hasn't stopped compounding.”
Chief Revenue Officer · CROShareChest
◇ Related engagements
◇ Let's talk

Want a stack your board can audit?

We build outbound as inspectable infrastructure — domains, sequences, scoring and routing, documented and handed over. Thirty minutes tells you whether yours is close.

Book a call →See all case studies