Can you migrate us from Outreach to Salesloft (or vice versa)?

Yes. Cadence migration is part of our onboarding when you switch sequencers.

Integration · Outreach & sequencing

Salesloft: Enterprise sequencer with strong dialer, cadence design, and conversation intelligence.

Salesloft is the alternative to Outreach for enterprise sequencing, with a stronger native dialer and the Drift acquisition tying conversations across channels. We operate it identically to Outreach.

Short answer

How should Salesloft be configured for outbound?

Salesloft is the execution layer: cadences, dialer, and rep workflow. The configuration that decides results is upstream and downstream, not inside the cadence editor. Send from dedicated, warmed domains, load only scored contacts, keep each cadence tied to one trigger, and write dispositions and meeting sources back to the CRM so reporting reflects the motion.

One cadence per trigger. Generic cadences produce generic results.
Cap sends per mailbox per day regardless of what the platform allows.
Rep tasks should be steps in the cadence, not a separate to-do list.
Meeting source must write back to the CRM or attribution breaks.

What we operate

How our pod runs Salesloft.

Build cadences by persona, segment, and trigger
Operate the dialer for personas where phone outperforms email
Wire activity to CRM timelines and reporting
Run inbound triage and SLA enforcement

Use cases

Where Salesloft earns its place in the stack.

Dialer-heavy outbound

For personas (VPs of IT, security, finance) where phone outperforms email, we cadence calls inside Salesloft and track connect-to-meeting rates per SDR.

Example workflows

Real Salesloft plays we ship.

Phone-first cadence

01Day 1: cold email + LinkedIn connection
02Day 2-4: 3 call attempts via Salesloft dialer with voicemail drop
03Day 5: follow-up email referencing call attempt
04Day 8: LinkedIn voice note

Best fit

B2B SaaS with phone-receptive personas and an existing SDR motion that needs a strong dialer.

Pairs well with

Salesforce HubSpot Clay ZoomInfo Gong

Setup

How we configure Salesloft in week 1.

The Foundation build installs Salesloft in your own account in this order. Each step is documented in the operating playbook we hand over.

01
Connect sending infrastructure
Attach dedicated sending domains with warmed mailboxes and correct SPF, DKIM, and DMARC, separate from the domain your customers already trust.
02
Structure cadences by trigger
Build one cadence per signal, such as new hire in role, funding, or technology change, each with copy that only makes sense for that trigger.
03
Blend the channels
Interleave email, call, and LinkedIn steps within the same cadence day so the account experiences one motion rather than three.
04
Set person and volume limits
Cap daily sends per mailbox, exclude open opportunities and customers, and enforce a single active cadence per contact.
05
Wire reporting
Push cadence, step, disposition, and meeting source into the CRM, then report meetings and pipeline by trigger rather than by rep activity.

Benchmarks

What good looks like with Salesloft.

Metric	Benchmark	Context
Reply rate	4-9%	On signal-triggered cadences with verified contacts.
Positive reply share	20-30%	Of total replies, on a tightly defined ICP.
Touches per contact	12-18	Across email, call, and LinkedIn over 3 to 4 weeks.

Ranges reflect what we observe running B2B SaaS mid-market motions. Treat them as starting targets, not guarantees.

Failure modes

How Salesloft builds go wrong.

Sending from the primary corporate domain and damaging billing and support deliverability.
Running a single mega-cadence across every persona and trigger.
Measuring emails sent and calls logged instead of meetings and pipeline by trigger.
Letting a contact sit in three cadences at once because exclusions were never configured.

FAQ