Sales Surge
    SALES SURGEAlign•Automate•Accelerate
    OutboundFebruary 202622 min read

    Building a scalable outbound engine: Pipedrive + Instantly + Apollo + Dux-Soup

    A practical guide to setting up a compliant, scalable outbound machine

    Why this guide

    Outbound sales isn't dead, but bad outbound is. Spam no longer works. What does work: a structured system where data enrichment, multi-channel sequencing and CRM integration work seamlessly together. This guide shows how to build it with Pipedrive as hub, Instantly for email sequences, Apollo.io for enrichment and Dux-Soup for LinkedIn assistance.

    Compliance disclaimer: This guide does not promote spam or unethical behavior. All tactics comply with GDPR and respect opt-out requests. Dux-Soup is presented as an 'assisted prospecting' tool within LinkedIn's Fair Use Policy.

    Key Takeaways

    • Outbound only works with clean data, good targeting and respectful cadence
    • Pipedrive is your single source of truth; all tools sync back to CRM
    • Enrich before you mail; incomplete data = low deliverability
    • Multi-channel (email + LinkedIn) significantly increases reply rates
    • Measurement determines success: track reply rate, meeting rate and lead-to-deal time
    • Compliance isn't optional; it's your license to operate

    Outbound architecture: from source to deal

    A scalable outbound engine follows a clear path: Source → Enrich → Sequence → CRM → Handoff. Each component has a specific role.

    1

    1. Source: Where do your leads come from?

    Tools: LinkedIn Sales Navigator, Apollo.io search, website visitors, event attendees

    Output: Raw list with name, company, title

    2

    2. Enrich: Enrich with contact details and context

    Tools: Apollo.io for email/phone, LinkedIn for context

    Output: Complete contact records with verified emails

    3

    3. Sequence: Multi-touch outreach via email and LinkedIn

    Tools: Instantly for email, Dux-Soup for LinkedIn

    Output: Engaged prospects (opens, clicks, replies)

    4

    4. CRM: All interactions sync to Pipedrive

    Tools: Make.com for sync, Pipedrive as hub

    Output: Complete prospect history in one place

    5

    5. Handoff: Warm leads to sales for follow-up

    Tools: Pipedrive automations, Slack notifications

    Output: Qualified meetings in the pipeline

    Core principle: every step must be measurable. If you can't measure how many leads go from source to meeting, you're flying blind.

    Data model in Pipedrive: required fields

    Your CRM is only as good as your data structure. These fields are essential for a working outbound engine:

    Lead Source & Tracking

    FieldTypeValuesWhy
    Lead SourceDropdownApollo, LinkedIn, Inbound, Event, ReferralAttribution for ROI analysis
    Source CampaignTextCampaign ID or nameGranular tracking per campaign
    First Touch DateDateAuto-setMeasure speed-to-lead

    Contact Quality

    FieldTypeValuesWhy
    Email VerifiedDropdownYes/No/UnknownFilter for sequences
    Phone VerifiedDropdownYes/No/UnknownPrioritize for calling
    LinkedIn URLTextProfile URLDux-Soup targeting

    Engagement Tracking

    FieldTypeValuesWhy
    Instantly StatusDropdownNot contacted, In sequence, Replied, BouncedSequence management
    LinkedIn StatusDropdownNot connected, Pending, Connected, MessagedDux-Soup tracking
    Last Outbound TouchDateAuto-updatePrevent over-contact

    Qualification

    FieldTypeValuesWhy
    ICP FitDropdownExcellent/Good/Fair/PoorPrioritize best-fit prospects
    Budget IndicatorDropdownEnterprise/Mid-market/SMBAdapt messaging
    Buying StageDropdownUnaware/Aware/Considering/DecidingPersonalize approach

    Pro tip: Start with fewer fields than you think you need. You can always expand, but empty fields are worse than no fields.

    Enrichment with Apollo.io

    Apollo.io is your data source and enrichment layer. Here's how to use it effectively:

    When to enrich

    • When importing new leads before they go into sequences
    • Periodically (monthly) for existing contacts without email
    • For account research before approaching large prospects

    How to enrich

    1. 1Export leads from Apollo with filters (title, industry, company size)
    2. 2Use 'Enrich' function for existing lists in Apollo
    3. 3Sync to Pipedrive via Make.com or native integration
    4. 4Mark 'Email Verified = Yes' only at Apollo confidence >90%

    Dedupe rules

    • Match on email as primary key
    • Secondary match on LinkedIn URL
    • On conflict: Apollo data wins for contact details, Pipedrive for engagement history
    • Block automatic merge; manual review for important accounts

    Note: Apollo is not a 'scraping tool'. It aggregates publicly available data. Respect GDPR by processing opt-outs and being able to demonstrate legitimate interest.

    Sequencing with Instantly

    Instantly is your email engine for cold outreach. Success depends on deliverability and relevance.

    Deliverability baseline

    • Use dedicated domains (not your main domain)
    • Warm up new domains for at least 2-3 weeks
    • Keep send volume under 50/day per mailbox initially
    • Monitor bounce rate (<2%) and spam reports (<0.1%)
    • Authenticate with SPF, DKIM and DMARC
    • Actively use Instantly's warmup feature

    Sequence best practices

    • 3-5 touches over 2-3 weeks is optimal
    • Vary timing: not every mail at 9:00
    • Personalize at minimum first line and company reference
    • Last mail must be a clear 'break-up'
    • A/B test subject lines with at least 100 sends per variant

    Reply routing

    Reply detection in Instantly
    Webhook to Make.com
    Update Pipedrive: Instantly Status = 'Replied'
    Notification to sales (Slack or email)
    Auto-stop sequence for this contact
    Optional: create Activity in Pipedrive with reply content

    Spam is not just ineffective, it permanently damages your domain reputation. One bad campaign can destroy months of building.

    LinkedIn assisted workflows with Dux-Soup

    Dux-Soup automates LinkedIn actions within safe limits. It's an assistant, not a spam tool.

    Safe operating rules

    Daily limits:Max 50-75 connection requests per day, 50 messages

    LinkedIn's detection thresholds

    Warmup period:Start with 10-15/day, increase gradually over 2 weeks

    Account safety

    Personalization:Always personalized connection request (no generic text)

    Acceptance rate and compliance

    Timing spread:Random delays between actions (30-90 sec)

    Prevent bot detection

    Profile viewing first:View profile 1-2 days before connect request

    Natural behavior

    Sales Navigator targeting:Use filters for relevant prospects

    Quality over quantity

    Typical workflows

    • View profile → Wait 24h → Connect with personalized note → Wait for accept → Send first message
    • Engage with content (like/comment) → Wait 48h → View profile → Connect
    • After email reply → Find on LinkedIn → Connect with reference to email

    CRM sync

    1. 1Dux-Soup exports connected profiles
    2. 2Make.com matches on LinkedIn URL in Pipedrive
    3. 3Update 'LinkedIn Status' field
    4. 4Log Activity for audit trail

    Ethical framework: Dux-Soup is for making actions you would do manually more efficient. If you wouldn't do an action manually, don't automate it either.

    Make.com automation recipes

    Make.com is the glue that connects everything. Here are the essential scenarios in plain English:

    Apollo → Pipedrive sync

    Real-time or daily batch

    Trigger

    New enriched contact in Apollo

    Actions

    Search Pipedrive by email → If not exists: create Person + Organization → If exists: update contact fields → Log Activity 'Enriched via Apollo'

    Instantly reply → Pipedrive + Slack

    Real-time

    Trigger

    Email reply detected in Instantly

    Actions

    Update Person in Pipedrive (Status = Replied) → Stop sequence in Instantly → Send Slack notification to sales → Create Activity with reply snippet

    Dux-Soup connected → Pipedrive

    Daily batch

    Trigger

    New LinkedIn connection (via export)

    Actions

    Match Person by LinkedIn URL → Update LinkedIn Status = Connected → Optionally add to follow-up sequence

    Pipedrive stage change → Instantly pause

    Real-time

    Trigger

    Deal moves to 'Qualified' or later

    Actions

    Find contact in Instantly → Pause all sequences → Update status field in Pipedrive

    Bounce handling

    Real-time

    Trigger

    Email bounce in Instantly

    Actions

    Update Pipedrive: Email Verified = No, Instantly Status = Bounced → Flag for re-enrichment or removal

    Weekly metrics digest

    Weekly

    Trigger

    Every Monday 8:00

    Actions

    Query Instantly for last week stats → Query Pipedrive for new qualified leads → Format summary → Send to Slack/email

    Start with 3-4 essential scenarios. Add complexity when you master the basics. Over-engineering in week 1 leads to unmaintainable chaos.

    Measurement: KPIs that matter

    Not everything you can measure is important. Focus on these metrics:

    Reply Rate

    (Replies / Emails Delivered) × 100

    Benchmark

    10-15% for cold email, 20-30% for warm leads

    Primary indicator for messaging relevance and list quality

    Positive Reply Rate

    (Interested Replies / Total Replies) × 100

    Benchmark

    30-50% of replies should be positive

    Filters noise; measures real interest

    Meeting Rate

    (Meetings Booked / Contacts Sequenced) × 100

    Benchmark

    2-5% for cold outbound

    Ultimate conversion metric for top-of-funnel

    Lead-to-Deal Time

    Average days from first touch to closed won

    Benchmark

    Highly dependent on deal size; track trend, not absolute value

    Measures efficiency of full funnel

    Cost per Meeting

    Total outbound spend / Meetings booked

    Benchmark

    [PLACEHOLDER: varies by industry and ACV]

    ROI metric for budget allocation

    LinkedIn Connection Accept Rate

    (Accepts / Connection Requests) × 100

    Benchmark

    30-50% with good targeting and personalization

    Indicator for targeting quality and message relevance

    Build a Pipedrive dashboard with these metrics. Review weekly. Act on trends, not daily fluctuations.

    Common failure modes + fixes

    Bounces >5%

    Cause: Unverified emails in sequence

    Fix: Enrich and verify before mailing; use Apollo confidence scores

    Reply rate <5%

    Cause: Poor targeting or generic messaging

    Fix: Sharpen ICP; personalize first line; test subject lines

    LinkedIn account restricted

    Cause: Too aggressive automation

    Fix: Reduce daily limits; pause 48-72h; diversify timing

    No replies but opens

    Cause: Messaging sparks interest but no action

    Fix: Strengthen CTA; add social proof; shorten emails

    Spam complaints

    Cause: Irrelevant outreach or no opt-out

    Fix: Always unsubscribe link; better targeting; stop after 3 touches

    Pipedrive full of junk

    Cause: No qualification filter at import

    Fix: ICP scoring at import; auto-archive low scores

    Sales ignores leads

    Cause: Leads don't enter their workflow

    Fix: Real-time Slack alerts; leads directly in Pipedrive pipeline

    Duplicate contacts

    Cause: No dedupe at sync

    Fix: Match on email + LinkedIn URL; merge duplicates weekly

    Sequences don't stop after reply

    Cause: Reply detection not working

    Fix: Test webhook regularly; use Instantly native stop-on-reply

    No ROI insight

    Cause: Attribution not configured

    Fix: Fill Lead Source + Campaign fields consistently

    Domain blacklisted

    Cause: Too fast too many mails from new domain

    Fix: Respect warmup period; dedicated outbound domains

    Team doesn't follow process

    Cause: Too complex or unclear

    Fix: Simplify; document; train; review weekly

    Need help with your outbound engine?

    Sales Surge builds scalable outbound systems that are compliant and effective. Our approach:

    Audit

    We analyze your current outbound setup, data quality and messaging

    Blueprint

    We design your ideal flow: sourcing → enrichment → sequencing → CRM

    Build

    We configure Pipedrive, Instantly, Apollo and Dux-Soup integrations

    Optimize

    We monitor performance and continuously optimize

    Sander VergouwenFounder & CEO

    Developed outbound methodology from 150+ implementations

    Bart-Jan HinCo-Founder

    Leads delivery, client onboarding and training. 20+ years in sales, CRM and RevOps

    As partners of Pipedrive (Platinum), Make.com (Certified), Apollo.io and Dux-Soup (Certified), we have direct access to support and best practices.

    Frequently Asked Questions

    Glossary

    Cold Email
    Unsolicited email to someone without prior relationship, aimed at starting a conversation.
    Deliverability
    The degree to which your emails actually land in the inbox instead of spam.
    Warmup
    Gradually increasing email volume to build domain reputation.
    Sequence
    Series of automated follow-up messages with predetermined timing.
    Bounce Rate
    Percentage of emails not delivered due to invalid addresses.
    ICP
    Ideal Customer Profile. Description of your best customer type.
    Lead Enrichment
    Adding extra data points to a basic record (name, company → email, phone, etc).
    Reply Rate
    Percentage of contacts that respond to your outreach.
    SPF/DKIM/DMARC
    Email authentication protocols proving you are the legitimate sender.
    Connection Request
    LinkedIn request to add someone to your network.
    Break-up Email
    Last email in a sequence explicitly stating you're stopping contact.
    Attribution
    Assigning revenue to specific marketing/sales activities.

    Partners featured in this article

    Click a badge to sign up with our partners:

    Pipedrive Partner Badge
    Pipedrive
    Apollo Partner Badge
    Apollo
    Instantly Partner Badge
    Instantly
    Dux-Soup Partner Badge
    Dux-Soup
    Make Partner Badge
    Make

    Ready to build your outbound engine?

    Request a free outbound audit. We analyze your current setup and provide a concrete blueprint.

    Related reading