Cb B2b Sales Enablement Framework Publish

SKILL.md

---
name: International B2B Sales Enablement Framework
description: Build localized B2B sales playbooks, objection-handling scripts, and account-based outreach sequences for any overseas market. Go from "we should sell there" to a complete sales enablement kit with market-specific talk tracks and ROI calculators.
---

# International B2B Sales Enablement Framework

## Overview

A practical framework for building overseas B2B sales narratives, buyer maps, objection handling, collateral, and market-specific sales motions.

This is a pure descriptive OpenClaw skill for overseas expansion planning. It provides frameworks, templates, checklists, decision criteria, and risk reminders. It does **not** execute code, call APIs, access the network, scrape websites, submit forms, make purchases, send messages, or perform any external action.

## When to Use

Use this skill when the user needs structured help with international b2b sales enablement framework in a cross-border or international expansion context.

Typical trigger phrases include:
- international B2B sales
- overseas sales enablement
- foreign enterprise buyer
- global sales deck
- cross-border B2B playbook

## Target Users

B2B founders, sales leaders, export sales teams, and enterprise go-to-market operators.

## Inputs to Collect

Ask for or infer the following context before producing the final framework:

- Target market or list of candidate markets
- Product, service, category, or business model
- Current business stage and domestic traction, if any
- Target customer segment and purchase context
- Expansion goal, timeline, budget range, and constraints
- Existing assets such as brand story, content, team, channels, customer data, or partners
- Known risks, assumptions, compliance concerns, and decision deadlines

If important inputs are missing, state the assumptions clearly and provide a version that can be refined later.

## Workflow

1. Define target account profile, buyer committee, sales cycle, market-entry objective, proof assets, and current objections in the overseas B2B context.
2. Map each buyer role to business pains, success metrics, evaluation criteria, risk concerns, and preferred proof format.
3. Build localized value propositions and talk tracks that connect the product to the buyer's market-specific operating pressure.
4. Prepare enablement assets such as discovery questions, objection responses, case-study requirements, ROI narrative, pilot proposal, and follow-up templates.
5. Design a pilot-to-contract path with qualification gates, mutual action plan, procurement considerations, and handoff to customer success.

## Output Modules

### Target account and buyer committee map
- Purpose: turn the user's market context into a structured planning component.
- Include: assumptions, recommended actions, decision criteria, and questions that require local validation.
- Output style: concise tables, checklists, and bullet-point rationale rather than generic advice.

### Localized value proposition builder
- Purpose: turn the user's market context into a structured planning component.
- Include: assumptions, recommended actions, decision criteria, and questions that require local validation.
- Output style: concise tables, checklists, and bullet-point rationale rather than generic advice.

### Objection and proof-point library
- Purpose: turn the user's market context into a structured planning component.
- Include: assumptions, recommended actions, decision criteria, and questions that require local validation.
- Output style: concise tables, checklists, and bullet-point rationale rather than generic advice.

### Sales collateral checklist
- Purpose: turn the user's market context into a structured planning component.
- Include: assumptions, recommended actions, decision criteria, and questions that require local validation.
- Output style: concise tables, checklists, and bullet-point rationale rather than generic advice.

### Pilot-to-contract pathway
- Purpose: turn the user's market context into a structured planning component.
- Include: assumptions, recommended actions, decision criteria, and questions that require local validation.
- Output style: concise tables, checklists, and bullet-point rationale rather than generic advice.

### Sales manager coaching rubric
- Purpose: turn the user's market context into a structured planning component.
- Include: assumptions, recommended actions, decision criteria, and questions that require local validation.
- Output style: concise tables, checklists, and bullet-point rationale rather than generic advice.

## Example Prompts

Try these real-world scenarios to see what this skill can produce:

**Prompt 1: Sales Playbook for a New Market**
> "We sell enterprise cybersecurity software (SaaS, $50K-$200K ACV) and are entering the Middle East market (UAE + Saudi Arabia). Our US sales playbook doesn't work there — prospects want different proof points and the buying committee includes procurement and IT security jointly. Build a localized sales playbook for this market."
> → Output: UAE/KSA buyer persona profiles (IT Security Director + Procurement VP), value proposition by persona, 5 discovery questions adapted for MENA business culture, objection-handling scripts (budget, competitor, security compliance), proof-point library (GDPR-equivalent PDPL references, regional case study templates), recommended sales sequence (LinkedIn → cold email → WhatsApp → call)

**Prompt 2: Cold Outreach Sequence**
> "I need a 7-touch cold outreach sequence targeting procurement directors at European automotive manufacturers. We sell supply-chain visibility software. Build the sequence with email templates, LinkedIn messages, and call scripts — localized for Germany, France, and Italy."
> → Output: 7-step cadence timeline, 21 templates (7 per step × 3 markets, localized language and cultural hooks), subject lines with A/B variants per market, follow-up rules (timing, channel escalation), ROI calculator link placement, GDPR-compliant opt-out language

**Prompt 3: Buyer Objection Battlecard**
> "Our biggest objection in the US is 'we already have a solution.' But in Southeast Asia, we hear 'we're not ready for this yet' and price sensitivity is much higher. Build battlecards for our sales team covering the top 5 objections in Indonesia, Vietnam, and Thailand."
> → Output: 15 objection-response pairs (5 per market), competitive positioning map for SEA region, pricing objection framework (ROI calculator, tiered packaging suggestion, POC approach), "maturity objection" handling script with local analogies and peer-example references

## Getting Started

👋 **cb-b2b-sales-enablement-framework installed!**

I build complete B2B sales toolkits for any overseas market — playbooks, outreach sequences, battlecards, everything your team needs to close deals abroad.

Quick start:
> "Build a sales outreach sequence for [product] targeting [persona] in [market]. Include email templates and objection handlers."

Paste your sales challenge and I'll give you ready-to-use assets.

## Safety and Limitations

Sales enablement advice must be adapted to local commercial law, procurement rules, and truthful-claims requirements.

Additional limitations:

- No professional legal, tax, financial, medical, employment, investment, or compliance advice.
- No guarantee of market success, conversion improvement, legal compliance, or platform acceptance.
- Verify local laws, platform policies, consumer expectations, and current market facts with qualified professionals and reliable sources.
- Avoid stereotyping cultures or users; treat all cultural observations as hypotheses requiring local validation.

## Acceptance Criteria

- Maps buyer roles and decision criteria
- Creates localized value propositions
- Includes common objections and evidence responses
- Defines required sales collateral
- Provides pilot and follow-up workflow
- Provides structured, market-aware outputs rather than generic overseas expansion advice.
- Includes explicit assumptions, evidence gaps, and validation steps.
- Stays pure descriptive with no code execution, API calls, browsing, network access, or external side effects.