SocialScalr for B2B SaaS sales teams
B2B SaaS sales teams are the largest single segment of SocialScalr customers. The configuration we recommend changes by role - SDRs run high-volume ICP-wide sequences, AEs run low-volume named-account ABM. Here is the playbook for both, plus the CRM-sync wiring.
The plan
Pro at $49/month per seat for individual SDRs and AEs. Upgrade to Agency at $149/month for 10 seats once you have 5+ people running outbound. Pro unlocks Watchtower (per-account competitive intel) and the AI personaliser; Agency consolidates billing and adds team dashboards.
The SDR motion (volume + ICP-wide)
SDRs are running the top of the funnel. Goal: book first meetings for an AE to take. Daily envelope per SDR account:
- 15-25 connection requests per day across 2-3 ICP-specific campaigns.
- 30-40 follow-up DMs per day to accepted leads in the sequence.
- 5-10 profile views per day as a warm-up touch before invite.
- Workdays only. Saturday/Sunday off (Friday afternoons skip too).
Volume target: ~80 first meetings booked per SDR per quarter. Time spent per SDR in SocialScalr: 60-90 minutes per day.
SDR sequence (4 steps over 14 days)
- Day 0: Connection request with specific, signal-based opener. No CTA. (~270 chars)
- Day 3: First DM. Curious question, soft opt-out. (~75 words)
- Day 9: Second DM. Shorter. Meeting ask: "Worth a 15-min look?" (~35 words)
- Day 14: Third DM. Break-up: "If now isn't the time, no problem - good luck with {their_quarter_priority}."
The AE motion (low-volume named-account ABM)
AEs work the top 30-50 accounts in their territory. Goal: get into multi-threaded conversations with 3-5 stakeholders per target account. Daily envelope per AE:
- 5-10 connection requests per week, all hand-written, targeted at named-account stakeholders.
- 10-15 follow-up DMs per week.
- Direct named-account search in Sales Navigator, not ICP-wide filter.
The AE motion has 2-3x the per-touch conversion of the SDR motion because the targets are warmer (already pipeline accounts) and the messages can reference specific commercial context ("I know your team is evaluating {our_category} - here is something we found that might help your shortlist").
AE-specific tactics
- Watchtower on target accounts. Get notified when target-account contacts publish a post, change roles, or announce a fundraise. Triggers the next touch with a real signal.
- Multi-thread by role. Connect with the economic buyer + the champion + a power user at each target. SocialScalr's Pipeline view shows you the gap by account.
- Engage their content first. Comment on 3 posts before the invite. Acceptance jumps from ~30% to ~55-60% on warmed targets.
CRM integration (Salesforce or HubSpot)
The wiring most B2B SaaS teams want:
- Lead replied → create or update Salesforce Lead, attach a Task with the message text, set Source = "LinkedIn outbound", notify owner.
- Lead connected → upsert HubSpot contact, set lifecycle stage = "SQL", trigger the warm sequence.
- Campaign completed → SDR Slack channel notification with the count of accepted/replied/booked.
- Watchtower alert → if a target-account stakeholder posts or hires, push to the AE owner via Slack DM.
Full recipes with payload shapes and verification at /integrations/.
Quota math (the case for budgeting it)
Typical B2B SaaS unit economics with SocialScalr in the stack:
- 1 SDR at 80 invites/day × 32% accept × 18% reply × 35% meet × 18% close = ~6 meetings/month, ~1 deal/month per SDR.
- At $12K ACV: $12K/month new ARR per SDR.
- SDR loaded cost: ~$8K/month. Tool cost (SocialScalr Pro + Sales Nav): $148/month. ROI: 1.4x on the SDR; the SocialScalr cost is a rounding error.
The real value isn't the per-SDR multiple - it's that LinkedIn-via-SocialScalr is the cheapest channel that produces qualified meetings at scale for B2B SaaS. See the ROI calculator with your own assumptions.
Common mistakes B2B SaaS teams make
- Templating the AE motion. AEs writing ABM messages from a template throw away the entire reason ABM works. Hand-write every named-account touch.
- Skipping Watchtower setup. The Pro plan includes it; teams that don't enable it miss the highest-conversion trigger window (post + 24 hours).
- Treating SDRs and AEs as the same workflow. Different caps, different copy, different sequences.
- Not piping replies to the CRM. Reps tab between SocialScalr inbox and Salesforce; webhooks fix this in 20 minutes.
- Buying Sales Navigator for SDRs but not AEs. AEs need it more - named-account search and InMail credits drive their motion.
Stack we recommend
- SocialScalr Pro or Agency for the LinkedIn motion.
- Sales Navigator (Core or Advanced) - needed for targeting URLs and InMail.
- Apollo or Clay for email enrichment.
- Smartlead or Instantly for the cold-email channel.
- Salesforce or HubSpot as the CRM of record. Webhooks bridge SocialScalr to it.
- Gong or Chorus on the AE side for call review and forecasting.
Total stack cost per rep: $300-600/month, depending on plan tier. ROI dwarfs cost at typical SaaS ACVs.
Frequently asked questions
What SocialScalr plan should a B2B SaaS sales team pick?
Pro at $49/month per seat for individual AEs or SDRs running their own books. Agency at $149/month for 10 seats once you have a sales team. AEs benefit from Watchtower (competitive intel on accounts they're chasing); SDRs need the API for HubSpot/Salesforce sync.
Should AEs or SDRs run LinkedIn outbound in B2B SaaS?
Both, with different volumes. SDRs run higher-volume, ICP-wide LinkedIn sequences (15-25 invites/day per account) to fill the top of the funnel. AEs run lower-volume, named-account ABM mode (5-10 hand-picked invites/week per AE) on the 30-50 top accounts in their territory. The AE motion has 2-3x higher reply and meeting rates because the targets are warmer and the messages more specific.
Can SocialScalr sync with Salesforce or HubSpot?
Yes, via outbound webhooks. Every lead.replied, lead.connected, and campaign.completed event fires a webhook with the full lead payload. Pipe it through Make, Zapier, or directly to a Salesforce Apex REST endpoint. Recipes are documented at https://socialscalr.com/integrations/, with step-by-step setups for the common CRMs.