
consent-safe-b2b-outbound-sdr-architect
Builds compliant B2B outbound SDR workflows that identify target accounts, analyze buying signals, draft personalized outreach, handle objections, and prepare qualified meeting handoffs.
- Generate ICP-aligned target account lists with automated scoring.
- Draft personalized, non-spammy cold emails based on real business triggers.
- Classify prospect replies and draft context-specific objection responses.
Secure checkout via Stripe
Included in download
- Generate ICP-aligned target account lists with automated scoring.
- Draft personalized, non-spammy cold emails based on real business triggers.
- file_read, file_write, browser automation included
- Ready for Compatible with ChatGPT Custom GPTs
Sample Output
A real example of what this skill produces.
=== B2B OUTBOUND SDR PLAN === Seller: B2B SaaS company selling customer onboarding software Offer: Software that helps SaaS teams improve customer onboarding, activation, and time-to-value. Target market: Mid-market SaaS companies. Outbound goal: Book qualified discovery calls with customer success, onboarding, and revenue leaders. ICP: Mid-market SaaS companies with 50–500 employees, recurring revenue model, onboarding complexity, customer success team, recent growth signals, and likely pressure to improve activation or retention. Exclusion criteria: Very small startups without a dedicated customer success function, companies with no onboarding motion, companies outside approved geography, opted-out accounts, and accounts without plausible onboarding pain. Primary personas: - VP Customer Success - Head of Onboarding - Chief Customer Officer - RevOps leader Secondary personas: - COO - Founder - Customer Education Lead Buying signals to research: - hiring onboarding or customer success roles - recent funding or growth announcement - new product launch - public focus on retention or expansion - customer education content - onboarding-related job descriptions - recent platform migration Account scoring model: - ICP fit: 30 points - trigger strength: 25 points - persona clarity: 15 points - likely pain urgency: 15 points - proof relevance: 10 points - compliance/data safety: 5 points Personalization strategy: Use one verified company-level signal and connect it to a plausible onboarding challenge. Do not claim certainty. First-touch email: Hi [First Name], I noticed [Company] is expanding its customer success/onboarding motion, especially around [verified signal]. When SaaS teams grow into more complex onboarding, time-to-value often becomes harder to manage consistently across segments. We help onboarding and CS teams standardize key onboarding steps, spot stalled accounts earlier, and improve activation without adding more manual tracking. Worth a short conversation to see if this is relevant for [Company] this quarter? Best, [Sender] Follow-up 1: Hi [First Name], Quick follow-up on my note about onboarding at [Company]. The reason I reached out is that teams expanding CS capacity often start seeing onboarding variation between reps, segments, or product lines. If activation and time-to-value are already handled, no worries. If they are current priorities, I can share a short checklist of where teams usually find friction. Best, [Sender] Follow-up 2: Hi [First Name], One useful pattern we see: onboarding issues usually become visible before churn, but the signals are scattered across tasks, calls, product usage, and CSM notes. If [Company] is working on this, happy to compare notes for 15 minutes. Best, [Sender] Breakup email: Hi [First Name], I will close the loop here. If improving onboarding consistency or activation becomes a priority later, happy to share a few practical ideas. Best, [Sender] Objection handling: - Not now: acknowledge and ask whether later follow-up is appropriate. - Already have a tool: ask what part of onboarding still feels manual or hard to measure. - No budget: offer a practical checklist and close politely. - Send info: send concise relevant summary, not a generic deck. - Opt-out: stop outreach and mark do-not-contact. Compliance and deliverability checklist: - truthful sender identity - relevant business reason - no fake personalization - no scraped restricted data - no sensitive personal data - suppression list checked - opt-out respected - concise message - no misleading subject line - human approval before sending CRM summary fields: - account name - persona - verified signal - ICP score - message angle - last touch - reply classification - objection - next step - owner - do-not-contact status Human approval workflow: Every message must be reviewed before sending. Approval requires verified personalization, accurate offer, compliance-safe wording, no unsupported claims, and suppression-list check.

consent-safe-b2b-outbound-sdr-architect
Builds compliant B2B outbound SDR workflows that identify target accounts, analyze buying signals, draft personalized outreach, handle objections, and prepare qualified meeting handoffs.
Secure checkout via Stripe
Included in download
- Generate ICP-aligned target account lists with automated scoring.
- Draft personalized, non-spammy cold emails based on real business triggers.
- file_read, file_write, browser automation included
- Ready for Compatible with ChatGPT Custom GPTs
- Instant install
Sample Output
A real example of what this skill produces.
=== B2B OUTBOUND SDR PLAN === Seller: B2B SaaS company selling customer onboarding software Offer: Software that helps SaaS teams improve customer onboarding, activation, and time-to-value. Target market: Mid-market SaaS companies. Outbound goal: Book qualified discovery calls with customer success, onboarding, and revenue leaders. ICP: Mid-market SaaS companies with 50–500 employees, recurring revenue model, onboarding complexity, customer success team, recent growth signals, and likely pressure to improve activation or retention. Exclusion criteria: Very small startups without a dedicated customer success function, companies with no onboarding motion, companies outside approved geography, opted-out accounts, and accounts without plausible onboarding pain. Primary personas: - VP Customer Success - Head of Onboarding - Chief Customer Officer - RevOps leader Secondary personas: - COO - Founder - Customer Education Lead Buying signals to research: - hiring onboarding or customer success roles - recent funding or growth announcement - new product launch - public focus on retention or expansion - customer education content - onboarding-related job descriptions - recent platform migration Account scoring model: - ICP fit: 30 points - trigger strength: 25 points - persona clarity: 15 points - likely pain urgency: 15 points - proof relevance: 10 points - compliance/data safety: 5 points Personalization strategy: Use one verified company-level signal and connect it to a plausible onboarding challenge. Do not claim certainty. First-touch email: Hi [First Name], I noticed [Company] is expanding its customer success/onboarding motion, especially around [verified signal]. When SaaS teams grow into more complex onboarding, time-to-value often becomes harder to manage consistently across segments. We help onboarding and CS teams standardize key onboarding steps, spot stalled accounts earlier, and improve activation without adding more manual tracking. Worth a short conversation to see if this is relevant for [Company] this quarter? Best, [Sender] Follow-up 1: Hi [First Name], Quick follow-up on my note about onboarding at [Company]. The reason I reached out is that teams expanding CS capacity often start seeing onboarding variation between reps, segments, or product lines. If activation and time-to-value are already handled, no worries. If they are current priorities, I can share a short checklist of where teams usually find friction. Best, [Sender] Follow-up 2: Hi [First Name], One useful pattern we see: onboarding issues usually become visible before churn, but the signals are scattered across tasks, calls, product usage, and CSM notes. If [Company] is working on this, happy to compare notes for 15 minutes. Best, [Sender] Breakup email: Hi [First Name], I will close the loop here. If improving onboarding consistency or activation becomes a priority later, happy to share a few practical ideas. Best, [Sender] Objection handling: - Not now: acknowledge and ask whether later follow-up is appropriate. - Already have a tool: ask what part of onboarding still feels manual or hard to measure. - No budget: offer a practical checklist and close politely. - Send info: send concise relevant summary, not a generic deck. - Opt-out: stop outreach and mark do-not-contact. Compliance and deliverability checklist: - truthful sender identity - relevant business reason - no fake personalization - no scraped restricted data - no sensitive personal data - suppression list checked - opt-out respected - concise message - no misleading subject line - human approval before sending CRM summary fields: - account name - persona - verified signal - ICP score - message angle - last touch - reply classification - objection - next step - owner - do-not-contact status Human approval workflow: Every message must be reviewed before sending. Approval requires verified personalization, accurate offer, compliance-safe wording, no unsupported claims, and suppression-list check.
About This Skill
Consent-Safe B2B Outbound SDR Architect helps AI agents, B2B SaaS teams, marketing agencies, consultants, founders, professional services firms, and revenue teams create high-quality outbound sales workflows without becoming spammy or unsafe. It defines ideal customer profiles, scores target accounts, identifies public or user-provided buying signals, creates account research briefs, maps buyer personas, drafts personalized cold emails and follow-ups, audits outbound campaigns, classifies prospect replies, handles objections, prepares CRM-ready summaries, and routes qualified prospects toward human-approved meetings. The skill emphasizes lawful data use, truthful personalization, opt-out respect, human approval before sending, and safe escalation for pricing, legal, procurement, security, or contract questions.
Use Cases
- Generate ICP-aligned target account lists with automated scoring.
- Draft personalized, non-spammy cold emails based on real business triggers.
- Classify prospect replies and draft context-specific objection responses.
- Create CRM-ready account briefs that summarize buyer pain points.
- Audit existing sales campaigns for compliance and deliverability risks.
Known Limitations
This skill creates compliant outbound strategy, message drafts, research briefs, objection responses, and meeting-handoff workflows, but it does not guarantee response rates, meetings, revenue, deliverability, legal compliance, or platform approval. Cold outreach laws and rules vary by region, industry, data source, recipient type, and message content. Human review, legal review, suppression-list checks, opt-out handling, deliverability monitoring, and approved source policies may be required before any outreach is sent. The skill should not be used for spam, deception, unauthorized scraping, or fully autonomous mass messaging.
How to Install
mkdir -p ~/.claude/skills && curl -sL https://www.agensi.io/api/install/consent-safe-b2b-outbound-sdr-architect | tar xz -C ~/.claude/skills/Free skills install directly. Paid skills require purchase - use the download button above after buying.
Reviews
No reviews yet - be the first to share your experience.
Only users who have downloaded or purchased this skill can leave a review.
Early access skill
Be the first to review this skill.
Only users who have downloaded or purchased this skill can leave a review.
Security Scanned
Passed automated security review
Permissions
File Scopes
This skill uses file access to read user-provided lead lists, account notes, CRM exports, approved sales materials, offer descriptions, case studies, proof points, outreach drafts, reply examples, objection logs, suppression-list references, and campaign documents. It uses write access to create structured Markdown/text outputs such as ICP definitions, target account briefs, personalized email packs, follow-up sequences, objection playbooks, reply classifications, CRM summaries, campaign audits, human approval queues, SDR operating prompts, and SKILL.md files. Browser access is optional and should only be used for authorized public business research. The default safe setup should not include unrestricted network access, direct email sending, or environment variable access.
Tags
Compatible with ChatGPT Custom GPTs, ChatGPT Agents, Claude-style workflows, Cursor, Claude Code, Codex CLI, OpenCode, Replit, CRM-assisted workflows, and other AI agent systems that support structured Markdown instruction files such as SKILL.md. It can also be used manually in any AI chat by pasting the instructions. For live outreach, connect only to permissioned CRM or email systems and require human approval before sending.