Extrovert

@Extrovert check if we already have linkedin.com/in/jane-smith in our prospects, and if not, show me what plan limits we're hitting

I checked your Extrovert workspace and found no existing prospect matching that LinkedIn URL. Your current plan allows 500 prospects total and you're at 487 (97% capacity). You have 2 of 5 Contexts used and 3 of 10 Styles created. Before adding new prospects, consider whether you're close to needing a plan upgrade—adding 13 more profiles will hit your hard cap.

This example pairs two read-only tools (Find Prospect + Get Workspace Plan Features) to prevent quota violations before they happen. Extrovert enforces plan limits server-side, so checking counters first avoids failed writes. The MCP cannot upgrade your plan or purchase add-ons; it only surfaces the numbers.

@Extrovert create a new Context called 'Q1 Enterprise Leads' with the insight that our pricing page was updated last week to highlight annual contracts

I created Context 'Q1 Enterprise Leads' (UUID: ctx_8f3a...) in your workspace. The insight about the pricing page update is now attached and will inform DM personalization when this Context is assigned to a campaign. Remember that your plan caps Contexts at 5 total—you now have 3 active. Deleting a Context later will cascade-delete all its Insights and remove it from any playbook entries.

This write operation demonstrates Extrovert's campaign-personalization model: Contexts store deal-stage or product knowledge that the AI references when drafting LinkedIn messages. The MCP warns about the irreversible cascade on delete because losing a Context mid-campaign breaks playbook logic. Always verify the Context name and insight content before committing.

@Extrovert pull the full config for campaign 'Inbound Demo Requests' and summarize which Style and Contexts it's using, plus how many prospects are enrolled

Campaign 'Inbound Demo Requests' (UUID: cmp_7b2c...) is active and uses Style 'Consultative Opener' with Contexts 'Product Launch 2024' and 'Enterprise Pricing'. It has 34 prospects enrolled, 12 connections accepted, 8 conversations started, and 2 marked as opportunities. The campaign's DM playbook has 4 message steps with 48-hour gaps. This configuration is live—editing the Style or deleting a Context will immediately affect queued messages.

This synthesis example shows how Extrovert campaigns tie together Styles (tone/voice), Contexts (deal intelligence), and prospect lists. The MCP surfaces engagement metrics so you can assess performance before making changes. Be cautious: the response confirms the campaign is active, meaning any Style or Context edits propagate to pending outreach in real time.

When Extrovert beats manual LinkedIn outreach for early sales

A 3-person B2B SaaS startup needs to send 200 personalized LinkedIn connection requests per week without hiring a full-time SDR. Extrovert wins here because the Create Context and Create Style tools let the founder encode their ICP and voice once, then the team reuses those templates across campaigns. The Find Prospect by LinkedIn URL tool prevents duplicate outreach when leads appear in multiple sources. The quota counters matter: check Get Workspace Plan Features before scaling past 50 contexts or you'll hit plan caps mid-campaign. If your founder is already writing every message by hand and closing deals, stay manual until you have 500+ prospects in-pipe. Otherwise, Extrovert turns one good message into a repeatable motion.

Why Extrovert's context isolation matters for multi-client shops

A 6-person growth agency runs LinkedIn outbound for four SaaS clients simultaneously. Extrovert is the right call because each client gets isolated Contexts and Styles—the Get Campaign and Get Prospect tools scope by workspace, so client A's messaging never leaks into client B's playbook. The Delete Context cascade is critical: when a client churns, you can tear down their entire campaign without orphaning data. The API key auth means each account manager can provision access without sharing a master login. The boundary: if a client needs more than 15 custom contexts (rare but possible for enterprise verticals), you'll bump the plan limit and need to pre-check quotas with Get Workspace Plan Features. For agencies running 3+ concurrent client books, Extrovert's workspace model beats shared-spreadsheet chaos.

When to use Extrovert for campaign retrospectives instead of CRM exports

A 12-person sales team wants to understand why Q3 LinkedIn outreach converted at half the Q2 rate. Extrovert's Get Prospect tool surfaces engagement statistics and connection data per profile, and Get Campaign loads the full playbook config that was live during each quarter. This beats exporting CSVs from your CRM because the Context and Style metadata—what messaging actually ran—lives in Extrovert, not Salesforce. The trade-off: if your team already logs every touchpoint in HubSpot and your rev-ops analyst is fluent in SQL, pulling CRM data is faster. Use Extrovert's audit tools when the question is 'did our messaging change' rather than 'did our pipeline change.' For post-mortems on specific campaigns where you need to reconstruct the exact playbook, Extrovert's campaign state beats stitching together Slack screenshots.