M for Mercury
Book a demo Sign in Get started
Industries

The same engine. A different playbook for every market.

Mercury does not change by industry — the audience, the first line and the definition of a good reply do. Here is how five kinds of team set it up, each with the playbook they actually run.

SaaS & software01 / 05

Reach the buyer who matches your ICP, with a first line that proves you looked.

Search the 450M+ contact database by title, industry, headcount and location, or import the list your RevOps team already built. AI columns read each company and write the reason to reach out; the journey sends it across every sender you have, inside LinkedIn's limits.

  • Find Contacts by title, company size and tech signals, then add a verified work email with Contact Credits for the ones you will also email.
  • AI research columns write a one-line reason per lead — and stay silent rather than invent one when the research runs thin.
  • Two-way CRM sync pushes positives into HubSpot, Salesforce, Attio or Zoho with the activity logged, and follows deletions back.
See plans Book a demo
Playbook · Heads of RevOps, Series A–Cillustrative
AudienceFind Contacts
Title Head of RevOpsHeadcount 51–500Industry SoftwareLocation US · UKAI · Why now?
Journey3 senders
View profile Invite Wait 2 days Message Follow-up

“Saw Northwind just opened a Dublin office — most RevOps teams find their LinkedIn pipeline stalls at exactly that point. Worth a look at how three senders share one inbox?”

Lands in
Unified inboxHubSpot dealExecutive Report
Recruiting & staffing02 / 05

Two audiences, two journeys, one inbox: candidates and the clients who hire them.

A recruiter's LinkedIn account is the business. Mercury runs a candidate journey and a business-development journey on the same senders, paces both inside one daily limit, and stops a thread the instant someone replies — so a consultant never messages a candidate who already answered.

  • Import a Sales Navigator list or a CSV of past applicants; Customer 360 keeps one row per person, matched by profile, however many lists they appear on.
  • Customer 360 tags — meeting, proposal, customer — track a hiring manager from first reply to signed mandate.
  • Working hours per workspace keep every send inside the day you set, and a removed consultant's journeys halt rather than run on.
See plans How safety works
Playbook · Senior engineers, open to workillustrative
AudienceSales Navigator import
Title Staff EngineerSkills Go · KubernetesLocation BerlinAI · Current stack
Journey2 consultants
View profile Invite Wait 3 days Message Stop on reply

“Your Kubernetes migration write-up is exactly the kind of work a client of ours is hiring for in Berlin — remote-first, staff level. Open to a 15-minute call this week?”

Lands in
Unified inboxCustomer 360 · MeetingWeekly report
Consulting & professional services03 / 05

Partner-led outreach that sounds like the partner, without the partner doing it.

The people who win consulting work are the people who cannot spare an hour a day on LinkedIn. Mercury runs from each partner's own account, writes in their voice from the research it did, and lets them review every AI draft before it sends — saved drafts go out word for word.

  • Every partner is a sender with their own daily caps, so a firm of six runs six accounts under one subscription and one inbox.
  • The AI review loop — approve, edit or rewrite each message before the journey reaches it.
  • Executive Report for the Monday partners' meeting: acceptance, replies, positives and meetings, per partner, per campaign.
See plans Book a demo
Playbook · CFOs, mid-market manufacturingillustrative
AudienceFind Contacts
Title CFO · VP FinanceIndustry ManufacturingHeadcount 200–2,000AI · Recent trigger
Journey4 partners · reviewed drafts
Invite Wait 4 days Message Wait 7 days Follow-up

“Your Q2 results mention working-capital pressure from the new plant — that is the exact problem we took off a similar CFO's desk last year. Happy to share what worked, no pitch.”

Lands in
Unified inboxAttioPartners' report
Financial services04 / 05

Outreach a compliance officer can read: every message saved, every send paced, nothing improvised.

Advisers, lenders and B2B fintechs prospect on LinkedIn under rules most tools ignore. Mercury keeps a record of every message sent and received, runs only inside working hours, holds every sender under its own limits, and sends AI drafts only after a person has approved them.

  • Templates, not improvisation — journeys start from a message the team has signed off, with AI research only where you allow it.
  • A full conversation log in the inbox and on the API, reconciled with LinkedIn when a thread is opened.
  • Sender status in three words — Active, Inactive, Restricted — and an amber wait, not a red error, when LinkedIn pushes back.
See plans The safety engine
Playbook · Founders raising a Series Aillustrative
AudienceCSV import · 312 rows
Title Founder · CEOStage SeedLocation Singapore · SydneyAI · Last funding
Journey2 senders · approved template
View profile Invite Wait 2 days Message Stop on reply

“Congratulations on the seed round. We work with founders between seed and A on the credit line that keeps hiring on plan — if a 20-minute call on how that works is useful, I can send times.”

Lands in
Unified inboxSalesforce leadMessage log · API
Events & communities05 / 05

Fill a room, a webinar or a members' list on a deadline, and stop the moment it is full.

Event and community teams run short journeys with a date in them. Mercury spreads the invitations across every host's account, pauses a campaign in one click when the seats are gone, and hands the attendee list to the CRM or to Zapier, Make or n8n for the confirmation email.

  • A campaign per event with its own audience, its own senders and its own numbers on the dashboard.
  • Pause, resume, complete — a paused campaign sends nothing, and a campaign finishes itself when the last person is through.
  • Webhooks and Slack announce each yes as it arrives, so the host sees the room filling.
See plans Integrations
Playbook · Product leaders, London roundtableillustrative
AudienceFind Contacts
Title VP Product · CPOLocation LondonHeadcount 100–1,000AI · Recent post topic
Journey3 hosts · ends 12 Sep
Invite Wait 1 day Message Wait 3 days Last call

“Twelve product leaders, one table, no slides — Thursday 12 Sep in Shoreditch. Your post on discovery interviews is exactly the argument we want in the room. Seat with your name on it?”

Lands in
Unified inboxSlack #roundtableZapier → confirmation

Your market is not on this page?

Book a demo and we will build the playbook with you, on your sender count and your list.

Schedule a demo Browse by department