[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M6EE6MB1AMQTK5EYRS97GEWG":3,"skill-same:01M6EE6MB1AMQTK5EYRS97GEWG":52},{"skillNo":4,"name":5,"nameZh":6,"description":6,"descriptionZh":6,"repositoryFullName":7,"ownerLogin":8,"ownerAvatarUrl":9,"ownerAccountNo":10,"ownerDisplayName":11,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":15,"categories":16,"keywords":17,"publishedAt":19,"linkOnly":20,"markdownContent":21,"markdownBody":21,"frontMatter":22,"refName":23,"commitSha":24,"skillDirectory":25,"forksCount":26,"repositoryHtmlUrl":27,"repositoryHomepageUrl":28,"ownerHtmlUrl":29,"ownerBlogUrl":6,"ownerDescription":30,"updatedAt":31,"install":32,"resources":45},"01M6EE6MB1AMQTK5EYRS97GEWG","bdr-enablement-generator",null,"ComeOnOliver\u002Fskillshub","ComeOnOliver","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F43215937?v=4","01M6E5JNFECJAAVFE0W7SMWWD2","Haoran Shu","01M6E5JNNDQS7AJZDYFQ8TPZCK",67,"MIT","https:\u002F\u002Fgithub.com\u002FComeOnOliver\u002Fskillshub\u002Fblob\u002Fmain\u002Fskills\u002FStallin-Sanamandra\u002Fb2b-saas-marketing-skills\u002Fbdr-enablement-generator\u002FSKILL.md",[],[18],"bdr enablement generator","2026-11-10 10:12:30",false,"# BDR Enablement Generator\n\n> A sequential system for producing everything a BDR needs to work an account:\n> research, outreach sequences, talk tracks, and objection handling. Each phase\n> builds on the previous one. Phase 7 feeds learnings back into Phase 1.\n\n## Why This Skill Exists\n\nBDR enablement at most B2B SaaS companies is one of two things:\n\n1. **A CRM record and a \"go get 'em.\"** The BDR gets an account name, maybe a\n   company size and industry, and is expected to figure out the rest. Research\n   quality depends entirely on the individual BDR's skill and how much time\n   they have before their next dial.\n\n2. **A generic sequence template.** Marketing writes a 5-email sequence with\n   placeholder fields. Every account gets the same structure, same value props,\n   same call to action. Personalization means swapping in {company_name} and\n   {first_name}.\n\nBoth approaches fail for the same reason: the outreach doesn't reflect what the\nbuyer actually cares about. A CISO evaluating compliance automation has different\nconcerns than a CTO evaluating the same product. A company that just raised Series\nB has different urgency than one preparing for an enterprise customer's vendor\nsecurity review.\n\nThis skill encodes the research-to-outreach pipeline so that every account gets\noutreach grounded in actual context, and every persona gets messaging matched to\ntheir priorities.\n\n## When to Use This Skill\n\n- Researching a target account before BDR outreach\n- Building a personalized outreach sequence for a specific account or account tier\n- Creating persona-specific talk tracks (CISO vs. CTO vs. Compliance Manager)\n- Developing objection handling responses for common buyer pushback\n- Onboarding new BDRs who need to ramp on your product and buyer landscape\n- Reviewing BDR outreach performance and iterating on messaging\n- Generating account briefs for ABM Tier 1 and Tier 2 accounts\n- Preparing BDRs for discovery calls with specific accounts\n\n## When NOT to Use This Skill\n\n- Broad demand gen campaign copywriting (this is 1:1 and 1:few, not 1:many)\n- Marketing email nurture sequences (different motion, different cadence)\n- Sales negotiation or closing strategies (this is top-of-funnel, not bottom)\n- Customer success outreach (different relationship, different goals)\n- Cold outreach to accounts with no ICP fit (fix targeting first, then enable)\n\n---\n\n## The BDR Enablement Pipeline: 7 Sequential Phases\n\n```\nPHASE 1              PHASE 2              PHASE 3              PHASE 4\nAccount Research →   Account Brief    →   Sequence Design  →   Message\n                                                               Generation\n\n     ↓                                                              ↓\n\nPHASE 7              PHASE 6              PHASE 5\nPerformance      ←   Objection        ←   Talk Track\nReview & Loop        Handling              Development\n\n     ↓\n     └──→ PHASE 1 (next account batch)\n```\n\n**The closed loop:** Phase 7 captures what worked, what didn't, and what buyers\nactually said. Those learnings refine account research criteria, sequence design,\nand objection responses for the next batch.\n\n---\n\n## Phase 1: Account Research\n\n**Input:** Account name, ABM tier (if applicable), ICP criteria\n**Output:** Structured account research document\n\n### Research Framework\n\nDon't give BDRs a blank page. Give them a structured research template that takes\n30 minutes to complete per Tier 1 account and 10 minutes per Tier 2.\n\n#### Account Research Template\n\n```\nACCOUNT: [Company Name]\nTIER: [1 \u002F 2 \u002F 3]\nRESEARCHED BY: [BDR Name]\nDATE: [Date]\n\nCOMPANY OVERVIEW\n- Industry: [Primary vertical]\n- Employee count: [Range]\n- Revenue estimate: [Range or funding stage]\n- HQ location: [City, Country]\n- Key product\u002Fservice: [One sentence]\n\nCOMPLIANCE & SECURITY POSTURE\n- Known frameworks: [SOC 2, ISO 27001, HIPAA, GDPR, PCI DSS, etc.]\n- Compliance maturity signal: [Early\u002Fbuilding, Established, Advanced]\n  Evidence: [Job postings, case studies, public disclosures, trust page]\n- Current tools (if known): [Competitor platforms, manual processes]\n  Source: [G2 review, job posting, LinkedIn, public case study]\n\nBUYING TRIGGERS\n- [ ] Recent funding round (amount, date, source)\n- [ ] New security\u002Fcompliance hire (name, title, start date)\n- [ ] Enterprise customer acquisition (triggers vendor security reviews)\n- [ ] Compliance deadline approaching (audit date, framework)\n- [ ] Competitor contract renewal (estimated timing)\n- [ ] Regulatory change affecting their industry\n- [ ] Public security incident or data breach\n- [ ] IPO preparation (SOC 2 often required)\n\nBUYING COMMITTEE (KNOWN CONTACTS)\n| Name | Title | LinkedIn | Relevance | Notes |\n|------|-------|----------|-----------|-------|\n| | | | Economic Buyer \u002F Tech Eval \u002F Champion \u002F User \u002F Blocker | |\n\nRECENT ACTIVITY\n- Company news: [Relevant press, blog posts, product launches]\n- LinkedIn activity: [Key contacts' recent posts or engagement]\n- Website changes: [New trust page, compliance mentions, job postings]\n- Review activity: [G2, TrustRadius reviews written or platform evaluated]\n\nOUTREACH ANGLE\nPrimary hook: [The specific reason this account should care right now]\nSupporting evidence: [What makes the hook credible, not generic]\nPersona priority: [Which buying committee member to approach first and why]\n```\n\n### Research Source Priority\n\nNot all sources are equal. Prioritize by signal quality.\n\n| Source | Signal Strength | What to Look For |\n|--------|----------------|------------------|\n| **Job postings** | High | Compliance\u002Fsecurity roles being hired = building the function. Specific tool mentions = current stack. |\n| **Company trust\u002Fsecurity page** | High | Frameworks listed, SOC 2 report availability, security questionnaire process. |\n| **G2\u002FTrustRadius reviews** | High | Reviews they've written (shows what they evaluate) and reviews of competitors. |\n| **LinkedIn (key contacts)** | Medium-High | Recent posts about compliance challenges, conference attendance, tool evaluations. |\n| **Funding announcements** | Medium | Series B+ often triggers compliance investment. Enterprise customer wins require vendor security. |\n| **Company blog\u002Fnews** | Medium | Compliance-related announcements, partnership with audit firms, customer case studies mentioning security. |\n| **Generic company info** (Crunchbase, website) | Low | Good for firmographics. Low value for outreach personalization. |\n\n### Research Depth by Tier\n\n| Tier | Time per Account | Research Depth |\n|------|-----------------|----------------|\n| **Tier 1** | 30-45 minutes | Full template. Every section completed. Named contacts with LinkedIn profiles. Specific outreach angle. |\n| **Tier 2** | 10-15 minutes | Company overview, compliance posture, top 1-2 buying triggers, primary persona identified. |\n| **Tier 3** | 0 minutes (programmatic) | ICP data from enrichment tools only. No manual research. Outreach is template-based. |\n\n---\n\n## Phase 2: Account Brief\n\n**Input:** Completed account research (Phase 1)\n**Output:** One-page account brief that a BDR can reference during outreach\n\nThe account brief distills research into an actionable document. A BDR should be\nable to read it in 2 minutes and know exactly why they're reaching out, who they're\nreaching out to, and what angle to lead with.\n\n### Account Brief Template\n\n```\nACCOUNT BRIEF: [Company Name]\nPrepared: [Date] | Tier: [1\u002F2\u002F3] | Priority: [High\u002FMedium\u002FLow]\n\nWHY THIS ACCOUNT, WHY NOW\n[2-3 sentences. The specific trigger or combination of signals that make this\naccount worth pursuing right now. Not \"they fit our ICP.\" What changed or what's\nhappening that creates urgency.]\n\nPRIMARY CONTACT\nName: [Full name]\nTitle: [Title]\nPersona type: [CISO \u002F CTO \u002F Compliance Manager \u002F VP Engineering]\nLinkedIn: [URL]\nKey insight: [Something specific from their LinkedIn activity, posts, or\nbackground that informs the outreach angle]\n\nSECONDARY CONTACTS\n[Name, Title, Persona type for 1-2 additional committee members]\n\nTHEIR LIKELY PAIN\nBased on [evidence source], this account is probably dealing with:\n1. [Specific pain point tied to their situation, not generic]\n2. [Second pain point if supported by evidence]\n\nWHAT THEY'RE LIKELY USING TODAY\n[Current solution: competitor platform, manual spreadsheets, audit firm handling\nit, or nothing. Source of this info.]\n\nMESSAGING ANGLE\nLead with: [The specific insight or trigger to reference in first touch]\nAvoid: [Any topics or claims that would backfire with this specific account]\nProof point: [The case study, metric, or example most relevant to their situation]\n\nCOMPETITIVE NOTES\n[If they're using a competitor: what that competitor is weak at that matters\nto this account. If greenfield: what the cost of their current manual process is.]\n```\n\n### Brief Quality Check\n\nBefore a BDR uses the brief, it should pass these tests:\n\n- [ ] \"Why now\" section references something that happened in the last 90 days\n- [ ] Primary contact has a specific insight, not just a title\n- [ ] Pain points are inferred from evidence, not assumed from ICP\n- [ ] Messaging angle is specific enough that it wouldn't work for a different account\n- [ ] Competitive notes reflect what the account cares about, not your feature list\n\n---\n\n## Phase 3: Sequence Design\n\n**Input:** Account brief (Phase 2), tier assignment\n**Output:** Outreach sequence structure with channel mix and timing\n\n### Sequence Architecture by Tier\n\n**Tier 1: Fully personalized (14 touches, 28 days)**\n\n| Touch | Day | Channel | Purpose |\n|-------|-----|---------|---------|\n| 1 | 1 | LinkedIn | Connection request with trigger-based note |\n| 2 | 2 | Email | Insight-led opening (not product pitch) |\n| 3 | 4 | LinkedIn | Engage with their content or share relevant research |\n| 4 | 7 | Email | Industry-specific proof point (case study, metric) |\n| 5 | 9 | Phone | Reference email engagement if opens\u002Fclicks detected |\n| 6 | 11 | LinkedIn | Direct message with custom content piece |\n| 7 | 14 | Email | Ask for conversation with specific value prop |\n| 8 | 16 | Phone | Voicemail referencing email + LinkedIn touches |\n| 9 | 18 | LinkedIn | Voice note (pattern interrupt) |\n| 10 | 21 | Email | New angle based on different pain point or persona |\n| 11 | 23 | Direct mail | Physical piece for non-responsive high-value accounts |\n| 12 | 25 | Email | Reference direct mail, tie to specific deadline or event |\n| 13 | 27 | Phone | Final attempt, reference full engagement history |\n| 14 | 28 | Internal | Score engagement, decide: continue, pause, escalate, or multi-thread |\n\n**Tier 2: Persona-templated (10 touches, 21 days)**\n\nSame structure as Tier 1 but personalization is at the persona level (all CISOs\nget CISO-specific messaging), not the individual level. Removes touches 9, 11,\nand collapses direct mail. Phone touches are optional based on BDR capacity.\n\n**Tier 3: Programmatic (5 touches, 14 days)**\n\nAutomated email sequence triggered by intent signals or engagement thresholds.\nNo phone, no LinkedIn, no manual personalization. BDR only engages if the account\nresponds or hits an engagement threshold.\n\n### Sequence Design Rules\n\n1. **Never lead with product.** Touch 1 and 2 are about the buyer's world, not\n   yours. Product enters at touch 4 earliest, and only through a proof point.\n\n2. **Multi-channel is non-negotiable for Tier 1-2.** Email-only sequences for\n   named accounts are not BDR outreach. They're automated nurture pretending\n   to be personal.\n\n3. **Space touches by signal, not just by calendar.** If the prospect opens\n   email 2 three times, pull touch 5 (phone) forward. If there's zero\n   engagement through touch 6, don't keep the same cadence. Adjust.\n\n4. **Each touch must add new value.** If touch 4 says the same thing as touch 2\n   with different words, it's not a sequence. It's repetition.\n\n5. **End with a door open, not a guilt trip.** Touch 13-14 should leave the\n   relationship intact for future outreach. \"Not the right time\" is a valid\n   outcome. \"I've reached out 14 times and you haven't responded\" is not.\n\n---\n\n## Phase 4: Message Generation\n\n**Input:** Sequence structure (Phase 3) + account brief (Phase 2)\n**Output:** Ready-to-send messages for each touch in the sequence\n\n### Email Templates by Persona\n\nEach template follows the same structure. The content changes based on persona.\n\n**Structure:**\n```\nSubject line: [Specific to their situation. No \"Quick question\" or \"Checking in.\"]\n\n[Opening: 1-2 sentences referencing their specific trigger or situation.\nNot \"I noticed your company...\" generic opener.]\n\n[Insight: 2-3 sentences sharing a perspective on their problem that they\nhaven't considered. Not your product pitch. Something they'd find useful\neven if they never buy from you.]\n\n[Bridge: 1 sentence connecting the insight to how you've seen it solved.\nThis is where your product enters, indirectly.]\n\n[Ask: 1 sentence. Specific, low-friction. Not \"Would love to set up a call.\"\nInstead: \"Worth a 15-minute conversation to see if [specific outcome] applies\nto your situation?\"]\n```\n\n#### CISO \u002F Head of Security\n\n**Primary concerns:** Risk reduction, audit readiness, board reporting, team bandwidth\n**Language to use:** Risk posture, evidence collection, audit cycles, control mapping\n**Language to avoid:** \"Easy,\" \"simple,\" \"automate everything\" (CISOs are skeptical\nof silver bullets)\n\n```\nCISO EMAIL TEMPLATE (Touch 2)\n\nSubject: [Framework] evidence collection before [their audit timeline\u002Ftrigger]\n\n[Name],\n\n[Reference trigger: \"Saw that [company] just brought on [enterprise customer] -\ncongrats. In our experience, that usually triggers a SOC 2 evidence request\nwithin the first 90 days of the vendor review process.\"]\n\n[Insight: \"The teams that handle this smoothly aren't the ones with the most\ncompliance staff. They're the ones who mapped their controls to evidence\nsources before the auditor asked. The scramble happens when evidence collection\nis manual and scattered across 4-5 tools.\"]\n\n[Bridge: \"We've helped [similar company in their vertical] cut their audit prep\nfrom 12 weeks to 3 by automating evidence collection against [relevant framework].\"]\n\n[Ask: \"If [company] is heading into a SOC 2 cycle, worth a 15-minute look at\nhow [similar company] handled it?\"]\n\n[Name]\n```\n\n#### CTO \u002F VP Engineering\n\n**Primary concerns:** Engineering time spent on compliance, integration burden,\ndeveloper experience, build-vs-buy\n**Language to use:** Engineering hours, API-first, CI\u002FCD integration, automated\ncontrols, developer workflow\n**Language to avoid:** \"Compliance made easy\" (CTOs don't buy \"easy,\" they buy\n\"doesn't waste my engineers' time\")\n\n```\nCTO EMAIL TEMPLATE (Touch 2)\n\nSubject: engineering hours on [framework] at [company]\n\n[Name],\n\n[Reference trigger: \"Noticed [company] is hiring a compliance engineer.\nIn most teams we talk to, that role ends up spending 60% of their time\non evidence collection and 40% on actual compliance architecture.\"]\n\n[Insight: \"The ratio flips when evidence collection pulls directly from\nyour existing stack. If your controls are already in AWS\u002FGCP and your\nCI\u002FCD pipeline, the data exists. The work is mapping it to framework\nrequirements, not generating it from scratch.\"]\n\n[Bridge: \"At [similar company], their compliance engineer spends about\n5 hours per week on evidence, down from 20+, because the collection\nruns against their existing infrastructure.\"]\n\n[Ask: \"Would it be useful to see how that mapping works against your\nstack? Happy to walk through it in 15 minutes.\"]\n\n[Name]\n```\n\n#### Compliance Manager \u002F GRC Manager\n\n**Primary concerns:** Day-to-day compliance operations, audit management,\ncross-framework efficiency, evidence gaps, reporting to leadership\n**Language to use:** Control libraries, evidence repositories, continuous\nmonitoring, framework overlap, audit trail\n**Language to avoid:** Technical jargon beyond their role (API endpoints,\ninfrastructure-level language)\n\n```\nCOMPLIANCE MANAGER EMAIL TEMPLATE (Touch 2)\n\nSubject: [framework] evidence gaps before Q[X] audit\n\n[Name],\n\n[Reference trigger: \"Saw that [company] added ISO 27001 to your trust page\nalongside SOC 2. Managing overlapping frameworks is where most compliance\nteams hit a wall, not because the work is hard but because the same evidence\ngets collected twice in two different formats.\"]\n\n[Insight: \"Teams running 2+ frameworks find that 40-60% of controls overlap.\nThe ones who map that overlap once and automate evidence collection against\nshared controls cut their workload nearly in half. The ones who treat each\nframework as a separate project double their work every time they add a new\nstandard.\"]\n\n[Bridge: \"[Similar company] went from SOC 2 only to SOC 2 + ISO 27001 +\nHIPAA in 6 months without adding headcount. The shared control mapping\ndid most of the heavy lifting.\"]\n\n[Ask: \"If you're managing the overlap manually right now, worth 15 minutes\nto see how [similar company] structured it?\"]\n\n[Name]\n```\n\n### Subject Line Rules\n\n| Do | Don't |\n|----|-------|\n| Reference their specific situation | \"Quick question\" \u002F \"Checking in\" \u002F \"Following up\" |\n| Use lowercase (feels like a real email) | Title Case Every Word |\n| Keep it under 8 words | Write a sentence as a subject line |\n| Include their framework or trigger | Use your product name in the subject |\n| Make it scannable in a mobile notification | Add brackets like [IMPORTANT] or [ACTION NEEDED] |\n\n### LinkedIn Message Rules\n\nLinkedIn messages have a 300-character limit for connection requests and work\ndifferently than email. Adjust accordingly.\n\n| Rule | Rationale |\n|------|-----------|\n| Connection request note: 1-2 sentences max | Anything longer gets truncated or ignored |\n| Reference something specific (post they wrote, mutual connection, company news) | Generic \"I'd love to connect\" has \u003C5% accept rate |\n| No pitch in the connection request | You haven't earned the right to pitch yet. Connect first, add value, then message. |\n| First DM after connection: share something useful, don't ask for anything | A relevant article, a congratulations on a specific win, or a question about their recent post |\n| Pitch (if at all) comes in DM #2 or later | And it should feel like a natural extension of the conversation, not a script |\n\n---\n\n## Phase 5: Talk Track Development\n\n**Input:** Persona templates (Phase 4) + account brief (Phase 2)\n**Output:** Discovery call frameworks and persona-specific talk tracks\n\n### Discovery Call Structure\n\nThis is not a script. It's a structure. BDRs who read from scripts sound like\nBDRs reading from scripts. The structure ensures key ground is covered while\nallowing natural conversation.\n\n```\nDISCOVERY CALL FRAMEWORK (15-20 minutes)\n\nOPENING (2 minutes)\n- Thank them for the time\n- Confirm the agenda: \"I'd like to understand [specific aspect of their\n  situation] and share how [similar companies] have handled it. If it makes\n  sense, we can talk about next steps. If not, no pressure.\"\n- Key: set the expectation that \"no\" is an acceptable outcome. This reduces\n  defensiveness.\n\nSITUATION (5 minutes)\n- \"Walk me through how your team handles [relevant process] today.\"\n- \"How many people are involved in [audit prep \u002F evidence collection \u002F\n  compliance management]?\"\n- \"What tools are you using for this currently?\"\n- LISTEN. Do not pitch during this section. The goal is to understand their\n  current state, not to react to every pain point with a feature.\n\nPAIN (5 minutes)\n- \"What's the most time-consuming part of that process?\"\n- \"When's your next [audit \u002F compliance deadline]?\"\n- \"What happens if [evidence gap \u002F audit finding \u002F compliance miss] occurs?\"\n- \"How does your leadership team view compliance investment right now?\"\n- Note: pain questions should be informed by the account brief. If you\n  already know their trigger, ask about it specifically rather than fishing\n  generically.\n\nIMPACT (3 minutes)\n- \"If you could reclaim the hours your team spends on [manual process],\n  where would that time go?\"\n- \"What would it mean for your team if [audit prep \u002F evidence collection]\n  took 3 weeks instead of 12?\"\n- \"Is [compliance expansion \u002F new framework] something leadership is\n  asking about?\"\n- Goal: get them to articulate the value of solving this problem in their\n  own words. Their words become your closing argument later.\n\nNEXT STEP (2 minutes)\n- If qualified: \"Based on what you've shared, I think it's worth showing\n  you how [specific outcome] works in practice. Can I set up a 30-minute\n  demo with [name], who works with teams like yours?\"\n- If not qualified: \"Sounds like the timing isn't right for [reason]. Mind\n  if I check back in [specific timeframe] when [trigger] might be closer?\"\n- If unclear: \"Would it help to see a quick [framework coverage matrix \u002F\n  time-savings calculator \u002F case study] before deciding if a deeper\n  conversation makes sense?\"\n```\n\n### Persona-Specific Talk Tracks\n\n#### Talking to CISOs\n\n| They Say | You Do |\n|----------|--------|\n| \"We handle compliance internally.\" | Don't challenge. Ask: \"How much of your team's time goes to evidence collection vs. actual security architecture?\" The goal is to surface the hidden cost, not argue. |\n| \"We already have a tool for this.\" | Ask which one. Then ask: \"What's the one thing you wish it did better?\" Competitors have known gaps. Know them before the call. |\n| \"I report to the board on this.\" | This is your opening. Ask: \"What does your board reporting process look like today? How much prep time goes into each report?\" Board reporting pain is a strong buying trigger. |\n| \"Security is our top priority.\" | Don't agree generically. Ask: \"Where does compliance sit relative to security in terms of team bandwidth?\" This separates the statement from reality. |\n\n#### Talking to CTOs\n\n| They Say | You Do |\n|----------|--------|\n| \"My engineers shouldn't be doing compliance work.\" | Agree. Then ask: \"How many engineering hours per month go to compliance-related tasks right now?\" Quantifying the problem makes it real. |\n| \"We'll build this ourselves.\" | Don't argue. Ask: \"What's your estimated build time and ongoing maintenance cost?\" Then share what similar companies found when they ran the same analysis. Most underestimate maintenance by 3-5x. |\n| \"We need something that integrates with our stack.\" | This is buying intent. Ask about their specific stack. Map it to your integration list. If there's a gap, be honest about it. |\n| \"Compliance isn't my problem.\" | Ask: \"Who owns it today?\" If the answer is \"nobody\" or \"shared,\" that's a pain signal. If it's a named person, ask to be introduced. |\n\n#### Talking to Compliance Managers\n\n| They Say | You Do |\n|----------|--------|\n| \"We're managing fine with spreadsheets.\" | Don't judge. Ask: \"How long does evidence collection take before each audit cycle?\" The answer is usually measured in weeks, which makes the case for you. |\n| \"We're adding a new framework next quarter.\" | This is your trigger. Ask: \"Have you mapped the control overlap between [current] and [new framework] yet?\" If no, that's the value you bring. If yes, ask how they're handling evidence for shared controls. |\n| \"My auditor handles most of it.\" | Ask: \"What does that cost per audit cycle?\" External auditor dependence is expensive and opaque. Quantify it. |\n| \"I'm the only compliance person.\" | This is a strong signal. A solo compliance person managing multiple frameworks is overwhelmed. Ask about their biggest time sink. The answer becomes your pitch. |\n\n---\n\n## Phase 6: Objection Handling\n\n**Input:** Common buyer pushback patterns + talk track outcomes (Phase 5)\n**Output:** Objection response framework\n\n### Objection Handling Principles\n\n1. **Never argue.** Agree with the concern, then reframe it. \"You're right that\n   [concern]. What we've found is [reframe].\"\n\n2. **Use customer evidence, not product claims.** \"We can do X\" is marketing.\n   \"[Similar company] achieved X\" is proof.\n\n3. **Quantify the status quo.** Most objections defend the current state. Make the\n   cost of the current state concrete. \"How many hours per audit cycle?\" is more\n   persuasive than \"our tool saves time.\"\n\n4. **Know when to walk away.** Not every objection is a buying signal. Some are\n   genuine disqualifiers. Recognize them early and exit gracefully.\n\n### Objection Response Matrix\n\n| Objection | Category | Response Framework |\n|-----------|----------|-------------------|\n| **\"We're not looking at this right now.\"** | Timing | \"Understood. When is your next [audit cycle \u002F compliance deadline]? Most teams start evaluating 3-4 months before. Mind if I reach out then with a prep checklist?\" (Set a specific callback date. Don't accept \"sometime next year.\") |\n| **\"We already use [Competitor].\"** | Competitive | \"Good to know. How's it working for [specific use case you know the competitor is weak on]?\" (Don't trash the competitor. Find the gap through questions. Every platform has gaps.) |\n| **\"It's too expensive.\"** | Price | \"What are you comparing it to?\" (Often they're comparing to their current cost of zero, ignoring the hidden cost of manual work. Quantify: \"[Similar company] was spending $X in labor hours before switching.\") |\n| **\"We can build this in-house.\"** | Build vs. buy | \"Totally fair. What's your estimated build timeline and ongoing maintenance commitment?\" (Share data: \"Teams we talk to estimate 3 months to build, but maintenance usually runs 2-3x the initial build cost annually.\") |\n| **\"I need to talk to my team \u002F boss.\"** | Authority | \"Of course. Would it help if I put together a one-page summary you could share? What questions do you think they'll have?\" (Enable the internal champion. Don't just wait for them to sell it themselves.) |\n| **\"We're too small for this.\"** | Fit | \"What frameworks do your customers require from you?\" (If the answer is SOC 2, ISO 27001, or similar, they're not too small. They're at the stage where compliance is becoming a revenue blocker.) |\n| **\"We just went through our audit.\"** | Timing | \"How did it go? What was the most painful part?\" (Post-audit is actually a great time. The pain is fresh. Position continuous monitoring as a way to avoid repeating the worst parts.) |\n| **\"Send me some information.\"** | Brush-off | \"Happy to. What specific question would the information need to answer for you?\" (If they can't name a specific question, it's a brush-off. If they can, you now know their real concern.) |\n| **\"We're focused on security, not compliance.\"** | Misframe | \"Makes sense. How do you handle the evidence and reporting side when auditors or customers ask for proof of your security controls?\" (Security and compliance are different. But the evidence burden is the bridge.) |\n\n### Disqualification Signals\n\nNot every objection is worth overcoming. Recognize when an account doesn't fit.\n\n| Signal | Interpretation | Action |\n|--------|---------------|--------|\n| No compliance requirement from customers or regulators | No buying trigger exists | Remove from active outreach. Add to long-term nurture. |\n| \u003C50 employees with no enterprise customer base | CAC won't justify the deal size | Disqualify unless they're pre-IPO or have explicit compliance deadlines. |\n| Recently signed a 2-3 year contract with a competitor | No switching opportunity for 18+ months | Note contract end date. Set a reminder for 6 months before renewal. |\n| \"We had a bad experience with [your product] before\" | Trust deficit | Escalate to a senior team member. Don't try to overcome this at BDR level. |\n| No one in the organization owns compliance | No internal champion possible | Disqualify unless a recent hire or job posting suggests this is changing. |\n\n---\n\n## Phase 7: Performance Review & Feedback Loop\n\n**Input:** Outreach activity data + BDR qualitative feedback\n**Output:** Performance review document that updates Phases 1-6 for the next batch\n\n### BDR Performance Metrics\n\nTrack these at the individual BDR, sequence, and persona level.\n\n**Activity metrics (leading indicators):**\n\n| Metric | Definition | Benchmark |\n|--------|-----------|-----------|\n| Emails sent per day | Total outreach emails (not automated nurture) | 40-60 for Tier 2-3, 15-25 for Tier 1 |\n| LinkedIn touches per day | Connection requests + messages + engagement | 15-25 |\n| Calls per day | Dials, not just connections | 30-50 |\n| Research briefs completed per week | Tier 1 account briefs fully prepared | 5-10 |\n\n**Effectiveness metrics (lagging indicators):**\n\n| Metric | Definition | Benchmark |\n|--------|-----------|-----------|\n| Email reply rate | Replies \u002F emails sent (exclude bounces) | 5-15% for cold, 15-30% for ABM |\n| Positive reply rate | Interested replies \u002F total replies | 30-50% of replies |\n| LinkedIn acceptance rate | Connections accepted \u002F requests sent | 20-40% |\n| Meeting booked rate | Meetings \u002F total accounts worked | 5-10% for cold, 10-20% for ABM |\n| SQO conversion rate | SQOs \u002F meetings booked | 30-50% |\n| Sequence completion rate | Accounts that received all touches \u002F accounts started | 70%+ (low means BDRs are giving up early) |\n\n**Quality metrics (reported to marketing):**\n\n| Metric | Definition | Why Marketing Cares |\n|--------|-----------|---------------------|\n| Top-performing subject lines | Open rates by subject line across the team | Informs ad copy and campaign email headers |\n| Objection frequency | Which objections come up most often, by persona | Signals messaging gaps. If \"too expensive\" is #1, pricing page or ROI content needs work. |\n| Competitor mentions | Which competitors are in deals, by segment | Informs competitive positioning and battlecard updates |\n| Pain points confirmed | Which pains from the brief actually resonated | Validates or invalidates ICP assumptions |\n| Channel preference by persona | Which channel generated the most replies per persona | Informs channel allocation for ABM orchestration |\n\n### Monthly Performance Review Template\n\n```\nBDR ENABLEMENT REVIEW: [Month] [Year]\n\nVOLUME\n- Accounts worked: [X] (T1: [X], T2: [X], T3: [X])\n- Total touches: [X] (email: [X], phone: [X], LinkedIn: [X], other: [X])\n- Meetings booked: [X]\n- SQOs created: [X]\n\nEFFECTIVENESS\n- Email reply rate: [X]% (vs. [X]% prior month)\n- Meeting booked rate: [X]% (vs. [X]% prior month)\n- SQO conversion: [X]% (vs. [X]% prior month)\n\nTOP PERFORMING\n- Best sequence: [Which tier\u002Fpersona sequence had highest meeting rate]\n- Best channel: [Which channel drove most meetings this month]\n- Best subject line: [Highest open rate subject line]\n- Best outreach angle: [Which trigger\u002Fhook resonated most]\n\nWHAT BUYERS SAID (verbatim quotes from replies and calls)\n- \"[Direct quote about their pain]\" - [Persona type, company size]\n- \"[Direct quote about competitor]\" - [Persona type, company size]\n- \"[Direct quote about objection]\" - [Persona type, company size]\n\nUPDATES FOR NEXT MONTH\n\nResearch updates:\n- [Add\u002Fremove research criteria based on what actually mattered in outreach]\n\nSequence updates:\n- [Adjust timing, channel mix, or number of touches based on data]\n\nMessage updates:\n- [Specific subject lines, opening lines, or proof points to rotate in\u002Fout]\n\nTalk track updates:\n- [New objection responses or discovery questions based on call feedback]\n\nICP feedback to marketing:\n- [Signals that the ICP needs refining: certain verticals converting better,\n  certain company sizes not responding, certain triggers not real]\n```\n\n### The Feedback Loop in Practice\n\n| What BDR Reports | Where It Goes | What Changes |\n|-----------------|---------------|--------------|\n| \"CISOs respond better to risk language than ROI language\" | Phase 4 (message templates) | CISO emails rewritten with risk-first framing |\n| \"Compliance managers don't know what SKILL.md means\" | Phase 4 (messaging) | Remove technical jargon from compliance manager sequences |\n| \"[Competitor] contract renewals are happening in Q3\" | Phase 1 (research) | Add competitor renewal timing to research template |\n| \"Nobody responds after touch 8\" | Phase 3 (sequence design) | Shorten Tier 2 sequence or change channels for touches 9+ |\n| \"IPO prep is a stronger trigger than funding round\" | Phase 1 (research), Phase 2 (brief) | Reprioritize buying triggers in research template |\n| \"We keep losing to [competitor] on [feature]\" | Marketing (competitive intel) | Update battlecards, create content addressing the gap |\n\n---\n\n## Integration Notes\n\n### With Other Skills in This Repo\n\n- **ABM Program Orchestrator:** Phase 6 of the ABM skill (BDR Coordination)\n  provides the strategic framework. This skill produces the actual content: briefs,\n  sequences, messages, talk tracks. Use ABM Orchestrator to design the program,\n  then BDR Enablement Generator to arm the team.\n\n- **GRC Messaging Guardrails:** Every message generated by this skill that references\n  compliance frameworks must pass through GRC Messaging Guardrails. SOC 2 is an\n  attestation, not a certification. HIPAA has no certification. ISO 27001 is\n  certified by an accredited body. Getting this wrong in BDR outreach to a CISO\n  is the exact credibility kill that motivated the guardrails skill.\n\n- **Pipeline Attribution Narrator:** BDR-sourced pipeline attribution should be\n  tracked using the narrator's framework. Specifically: if a BDR books a meeting\n  with an ABM account that marketing warmed with ads, attribution should credit\n  both (ABM-sourced, BDR-converted). The narrator's \"sourced vs. influenced\"\n  distinction applies here.\n\n- **Product Context Template:** Upload your approved messaging, case studies, and\n  competitive positioning alongside this skill. The message generation phase will\n  pull proof points and customer evidence from your context file.\n\n### With Your Tech Stack\n\n- **HubSpot:** Use Sequences for Tier 2-3 outreach automation. Tier 1 should be\n  manual sends tracked in the CRM, not automated sequences, to ensure\n  personalization quality. Use Contact properties for persona type and ABM tier.\n  Log call notes in the Activity timeline for handoff context.\n\n- **LinkedIn Sales Navigator:** Primary research tool for Phase 1. Use Saved\n  Searches for Tier 2-3 prospecting. Use Account alerts for Tier 1 trigger\n  monitoring.\n\n- **Outreach\u002FSalesloft:** If using a sales engagement platform, map the sequence\n  structures from Phase 3 directly into the platform. Use A\u002FB testing on subject\n  lines and opening lines to generate data for Phase 7 review.\n\n---\n\n## Common BDR Enablement Mistakes\n\n| Mistake | What Happens | How to Avoid |\n|---------|-------------|--------------|\n| **Generic sequences for all accounts** | Reply rates drop to 2-3%. BDRs burn through the account list. | Tier the list. Personalize Tier 1. Template by persona for Tier 2. Automate Tier 3 only. |\n| **Leading with product features** | Buyers tune out because they don't see their problem reflected. | First 2 touches are about their world, not yours. Product enters at touch 4 through proof points. |\n| **No research before outreach** | BDR calls a company that uses a competitor and doesn't know. Or pitches HIPAA to a company with no healthcare customers. | Phase 1 research is not optional for Tier 1-2. 15-30 minutes of research saves hours of wasted outreach. |\n| **Same message to CISO and Compliance Manager** | Both are in compliance, but they care about different things. CISOs think in risk. Compliance managers think in process. | Separate persona templates with different language, pain points, and proof points. |\n| **BDR feedback stays in Slack, never reaches marketing** | Messaging gaps persist. The same objections come up every month. Marketing creates content that doesn't match buyer reality. | Monthly review template (Phase 7) is mandatory. BDR qualitative feedback is one of marketing's most valuable inputs. |\n| **Measuring activity instead of effectiveness** | BDRs optimize for emails sent, not meetings booked. Volume goes up, quality goes down. | Track reply rates and meeting rates alongside activity. A BDR sending 100 generic emails is less effective than one sending 30 personalized ones. |\n| **No disqualification criteria** | BDRs spend weeks on accounts that were never going to buy. | Define disqualification signals (Phase 6). Make it safe and expected for BDRs to disqualify accounts. |\n\n---\n\n## Validation Checklist\n\nRun this before deploying new outreach sequences or enabling a new BDR.\n\n### Content Quality\n- [ ] All compliance terminology validated against GRC Messaging Guardrails\n- [ ] Email templates reviewed for persona-appropriate language\n- [ ] No product jargon in first two touches of any sequence\n- [ ] Subject lines are under 8 words and reference the buyer's situation\n- [ ] Case studies and proof points are from the buyer's vertical or company size\n- [ ] All claims are accurate and sourced (no invented metrics)\n\n### Sequence Structure\n- [ ] Each tier has a defined sequence with channel mix and timing\n- [ ] No two consecutive touches use the same channel\n- [ ] Each touch adds new value (not a rephrased version of the previous touch)\n- [ ] Sequence includes clear exit criteria and next-step actions\n- [ ] Tier 1 sequences include non-digital touches (phone, direct mail)\n\n### BDR Readiness\n- [ ] BDR has completed account briefs for all Tier 1 accounts\n- [ ] BDR can articulate the difference between each persona's priorities\n- [ ] BDR knows the top 3 competitor weaknesses relevant to their accounts\n- [ ] BDR has practiced the discovery call structure (not memorized a script)\n- [ ] BDR knows disqualification criteria and when to exit\n\n### Measurement\n- [ ] Tracking configured for reply rates, meeting rates, and SQO conversion\n- [ ] A\u002FB testing enabled for subject lines (minimum)\n- [ ] Monthly review cadence set with marketing\n- [ ] Feedback loop template shared with BDR team\n\n---\n\n## Changelog\n\n- **v1.0** (March 2026): Initial release. 7-phase sequential pipeline, account research framework, brief template, sequence architecture by tier, persona-specific message templates and talk tracks, objection handling matrix, performance review template, closed-loop feedback system.\n",{},"main","def8531e65114c0fca8fb8551c1871ee0eed705c","skills\u002FStallin-Sanamandra\u002Fb2b-saas-marketing-skills\u002Fbdr-enablement-generator",24,"https:\u002F\u002Fgithub.com\u002FComeOnOliver\u002Fskillshub","https:\u002F\u002Fskillshub.wtf","https:\u002F\u002Fgithub.com\u002FComeOnOliver","AI & Blockchain Engineer\r\n","2026-06-24 22:07:19",{"source":7,"skillName":5,"commands":33,"prompt":43,"zipAvailable":44},[34,37,40],{"tool":35,"command":36},"npx","npx skills add ComeOnOliver\u002Fskillshub --skill bdr-enablement-generator",{"tool":38,"command":39},"bunx","bunx skills add ComeOnOliver\u002Fskillshub --skill bdr-enablement-generator",{"tool":41,"command":42},"pnpm","pnpm dlx skills add ComeOnOliver\u002Fskillshub --skill bdr-enablement-generator","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002FComeOnOliver\u002Fskillshub\u002Fblob\u002Fmain\u002Fskills\u002FStallin-Sanamandra\u002Fb2b-saas-marketing-skills\u002Fbdr-enablement-generator\u002FSKILL.md",true,[46],{"path":47,"resourceType":48,"resourceTypeDesc":49,"sizeBytes":50,"sourceHtmlUrl":51},"customize.toml","OTHER","其他",3294,"https:\u002F\u002Fgithub.com\u002Fjsacko\u002FOpenDFIR\u002Fblob\u002Fmain\u002F.claude\u002Fskills\u002Fbmad-agent-pm\u002Fcustomize.toml",[53,67,77,86,92,99],{"skillNo":54,"name":55,"nameZh":6,"description":6,"descriptionZh":6,"repositoryFullName":7,"ownerLogin":8,"ownerAvatarUrl":9,"ownerAccountNo":10,"ownerDisplayName":11,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":56,"categories":57,"keywords":63,"publishedAt":19},"01M6FKJN13GMG4KY57J3QD8GY5","model-hierarchy-skill","https:\u002F\u002Fgithub.com\u002FComeOnOliver\u002Fskillshub\u002Fblob\u002Fmain\u002Fskills\u002Fzscole\u002Fmodel-hierarchy-skill\u002Fmodel-hierarchy-skill\u002FSKILL.md",[58],{"categoryNo":59,"categoryName":60,"taxonomyType":61,"taxonomyTypeDesc":62},"01JBSEEDCAT000000000000023","Skill与智能体开发","SCENARIO","使用场景",[64,65,66],"model","model hierarchy","model hierarchy skill",{"skillNo":68,"name":69,"nameZh":6,"description":6,"descriptionZh":6,"repositoryFullName":7,"ownerLogin":8,"ownerAvatarUrl":9,"ownerAccountNo":10,"ownerDisplayName":11,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":70,"categories":71,"keywords":73,"publishedAt":19},"01M6FKJJJ6GCAMR4PPPRD12M5X","zoom-mcp","https:\u002F\u002Fgithub.com\u002FComeOnOliver\u002Fskillshub\u002Fblob\u002Fmain\u002Fskills\u002Fzoom\u002Fskills\u002Fzoom-mcp\u002FSKILL.md",[72],{"categoryNo":59,"categoryName":60,"taxonomyType":61,"taxonomyTypeDesc":62},[74,75,76],"MCP","zoom","zoom mcp",{"skillNo":78,"name":79,"nameZh":6,"description":6,"descriptionZh":6,"repositoryFullName":7,"ownerLogin":8,"ownerAvatarUrl":9,"ownerAccountNo":10,"ownerDisplayName":11,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":80,"categories":81,"keywords":82,"publishedAt":19},"01M6FKJE3KYT3KPEZMEEHYKA6K","zoom-apps-sdk","https:\u002F\u002Fgithub.com\u002FComeOnOliver\u002Fskillshub\u002Fblob\u002Fmain\u002Fskills\u002Fzoom\u002Fskills\u002Fzoom-apps-sdk\u002FSKILL.md",[],[83,84,85,75],"sdk","zoom apps sdk","apps",{"skillNo":87,"name":88,"nameZh":6,"description":6,"descriptionZh":6,"repositoryFullName":7,"ownerLogin":8,"ownerAvatarUrl":9,"ownerAccountNo":10,"ownerDisplayName":11,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":89,"categories":90,"keywords":91,"publishedAt":19},"01M6FKJ9EDH9Q5VWDF8HAJRSP0","windows","https:\u002F\u002Fgithub.com\u002FComeOnOliver\u002Fskillshub\u002Fblob\u002Fmain\u002Fskills\u002Fzoom\u002Fskills\u002Fwindows\u002FSKILL.md",[],[88],{"skillNo":93,"name":94,"nameZh":6,"description":6,"descriptionZh":6,"repositoryFullName":7,"ownerLogin":8,"ownerAvatarUrl":9,"ownerAccountNo":10,"ownerDisplayName":11,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":95,"categories":96,"keywords":98,"publishedAt":19},"01M6FKJ666BEEFC3AE9GJ72Q93","whiteboard","https:\u002F\u002Fgithub.com\u002FComeOnOliver\u002Fskillshub\u002Fblob\u002Fmain\u002Fskills\u002Fzoom\u002Fskills\u002Fwhiteboard\u002FSKILL.md",[97],{"categoryNo":59,"categoryName":60,"taxonomyType":61,"taxonomyTypeDesc":62},[94],{"skillNo":100,"name":101,"nameZh":6,"description":6,"descriptionZh":6,"repositoryFullName":7,"ownerLogin":8,"ownerAvatarUrl":9,"ownerAccountNo":10,"ownerDisplayName":11,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":102,"categories":103,"keywords":104,"publishedAt":19},"01M6FKJ21WFCDGTJQ2Q91T9DVW","websockets","https:\u002F\u002Fgithub.com\u002FComeOnOliver\u002Fskillshub\u002Fblob\u002Fmain\u002Fskills\u002Fzoom\u002Fskills\u002Fwebsockets\u002FSKILL.md",[],[101]]