Apollo

@Apollo search for VP of Engineering contacts at Series B SaaS companies in the Bay Area with 50-200 employees

Found 127 contacts matching your criteria. Here's a sample: Sarah Chen (VP Engineering, DataFlow Inc., sarah.chen@dataflow.io), Marcus Williams (VP of Engineering, CloudSync, marcus@cloudsync.com), and 125 others. Results include title, company, email, and LinkedIn profile where available. Note: This search does not enrich contact data — you'll need to run bulk enrichment separately to get phone numbers, employment history, and other detailed fields.

Apollo's people search is capped at 50,000 records per query, so narrow filters yield better results. This example shows a read-only search; the MCP returns contact identifiers but not enriched data. To get full profiles (phone, social links, job history), follow up with the bulk people enrichment tool using the returned contact IDs.

@Apollo add contacts sarah.chen@dataflow.io and marcus@cloudsync.com to our 'Q1 Outreach - Engineering Leaders' sequence

Initiated background job #8472 to add 2 contacts to sequence 'Q1 Outreach - Engineering Leaders'. Job status: processing. Contacts will begin receiving emails once the job completes (typically 1-3 minutes). You can check job status with the job ID if needed. Both contacts must exist in your Apollo account; if either email is new, create the contact first before adding to a sequence.

This action triggers an asynchronous job rather than instant confirmation, so there's a brief delay before contacts enter the sequence. Requires that contacts already exist in your Apollo account and that the sequence ID is valid. Side-effect: contacts will start receiving automated emails per the sequence cadence, so verify the sequence configuration before running this.

@Apollo create a deal for DataFlow Inc. called 'Enterprise Plan Upgrade' at the Proposal stage, owned by me, worth $45k ARR

Created deal 'Enterprise Plan Upgrade' (ID: deal_9x4k2) for account DataFlow Inc. Stage set to 'Proposal', owner assigned to your user ID, amount $45,000 ARR. The deal is now visible in your Apollo pipeline. Note: You must provide valid existing IDs for owner, account, and opportunity stage — if 'Proposal' isn't a stage in your Apollo instance, the create will fail. Check your pipeline configuration first.

Deal creation requires pre-existing valid IDs for owner, account, and stage. Apollo does not auto-create accounts or stages, so ensure DataFlow Inc. exists as an account in your CRM before running this. This example demonstrates Apollo's write capability for pipeline management; pair it with account/contact creation tools if you're building a full lead-to-deal workflow.

When Apollo wins for batch-enrolling prospects into cadences

A 3-person sales team runs weekly prospecting sprints where they identify 50-100 new leads from a target account list and enroll them in a 7-touch email sequence. Apollo's MCP is the right call here because the "Add Contacts to Sequence" tool handles async batch jobs—you can queue enrollments without blocking the workspace. The "Bulk people enrichment" tool (up to 10 profiles at once) fills in missing emails and titles before enrollment. If your team runs sequences with fewer than 20 adds per week, the overhead of API key management probably isn't worth it; just use Apollo's UI. But once you're enrolling 40+ contacts weekly and cross-referencing them with Linear tasks or Slack threads, the MCP pays off by keeping enrollment logic in the same workspace where your team plans the sprint.

Apollo MCP handles multi-org enrichment during deal qualification

A 5-person account exec team qualifies inbound enterprise leads by researching the org structure and decision-makers at each target company. Apollo's "Bulk organization enrichment" tool (10 orgs per call) and "Apollo people search" (filters by title, seniority, department) let you pull firmographic data and build a contact map without leaving Switchy. The "Create Apollo deal" tool writes the qualified opportunity back to Apollo's pipeline so your CRM stays current. This works best when your team qualifies 5-15 new enterprise accounts per month; if you're doing 50+ per month, you'll hit Apollo's 50,000-record search ceiling and need a data warehouse instead. For mid-volume qualification where you're toggling between Apollo, your product docs, and Slack customer threads, the MCP keeps the research loop tight and the deal records accurate.

When Apollo's stage-update tools sync CS workflows to CRM

A 4-person customer success team manages 80 active accounts and moves them through stages like Onboarding, Active, At-Risk, and Renewal. Apollo's "Bulk update account stage" tool lets the team update 10-20 account stages at once after a weekly review meeting where they triage support tickets and usage data. The "Create Apollo contact" tool adds new stakeholders discovered during onboarding calls, linking them to the parent account. This setup works when your CS team reviews accounts in batches and needs Apollo to reflect the current stage for reporting. If your team updates stages one-off throughout the day (not in batch reviews), the MCP adds friction; just use Apollo's UI. But for weekly or bi-weekly stage syncs tied to a Switchy workspace where you're already reviewing Zendesk tickets and product analytics, the MCP keeps your CRM current without context-switching.