🚀 Early Access: FREE full access to All Workflows and AI Prompt Systems! No credit card required.
Sales enablement managers, Product marketers, Sales managers, RevOps teams, New sales hires
Prepare the Required Inputs listed in the Workflow Prompt. Use as much detail as necessary.
1. Copy the Workflow Prompt.
2. Paste it into your AI tool.
3. Replace the "Required Inputs"
4. Run the prompt.
Get access to this workflow and 1000+ others designed to save hours and get better results with AI.
You are a sales enablement trainer. Your task is to create a product training framework that helps sales teams understand the offer well enough to sell it clearly.
### Required Input
- Product or Offer: [Describe what needs to be taught. Example: "new compliance reporting module"]
- Sales Audience: [Who needs training. Example: "new AEs, SDRs, account managers, partner sellers"]
- Target Buyer: [Who the product is sold to. Example: "Heads of Compliance in financial services"]
- Buyer Problems: [Problems the product addresses]
- Key Capabilities: [Important features or service components]
- Differentiators: [What makes it meaningfully different]
- Sales Use Cases: [Example: discovery, demo, renewal, expansion, competitive deal]
- Common Misunderstandings: [What reps often get wrong]
- Proof Points: [Customer examples, metrics, product facts, screenshots, demo moments]
- Training Format: [Example: one-hour workshop, self-paced module, team enablement session]
### Input Validation
Review the input before building the framework. If the product, buyer problems, sales audience, or use cases are unclear, ask focused questions and pause. Do not create feature-only training.
### Instructions
Design the training for sales execution, not product memorisation. Begin by translating the product into the buyer problem it solves, the business outcome it supports, and the conversations where reps need to use it.
Organise the framework so reps learn in a practical sequence: buyer context first, product relevance second, sales application third. Explain which features matter most to buyers, what each feature proves, and how to discuss it without overwhelming the prospect.
Include training activities that test understanding. Add role-play prompts, discovery practice, demo positioning exercises, and objection drills. Make the framework usable for a live enablement session or as the basis for internal documentation.
Address common misunderstandings directly. Explain what reps should avoid saying, where they may overpromise, and how to escalate technical or product questions. Include manager follow-up actions so training becomes behaviour change, not a one-time session.
### Output
Produce the framework with these sections:
- Training Objective
- Sales Audience and Skill Gaps
- Buyer Problem Overview
- Product Value Explanation
- Key Capabilities and Buyer Relevance
- Differentiator Messaging
- Sales Conversation Use Cases
- Common Misunderstandings
- Practice Activities
- Knowledge Check Questions
- Manager Reinforcement Plan
- Rep Quick Reference Guide
Add a 60-minute training agenda with timing, exercises, and facilitator notes.
The objective of this enablement framework is to equip Account Executives (AEs) and Account Managers (AMs) with the commercial fluency required to position the Cross-Border Customs API Hub. Reps will move away from feature-heavy pitching and learn to lead high-velocity, value-driven conversations focused on operational capacity, bottleneck reduction, and cost-avoidance. By the end of this session, reps will be able to confidently uncover international dispatch friction, navigate IT infrastructure objections, and secure technical sandbox evaluations.
Target Audience: Mid-Market and Enterprise Account Executives (AEs) and Account Managers (AMs).
Our target buyers—Directors of International Operations and VPs of Supply Chain Logistics—are facing an unprecedented operational squeeze. Driven by aggressive corporate expansion or sudden new international freight contracts, they are mandated to scale cross-border shipping throughput by 25% to 30% next quarter. However, corporate finance has locked their headcount budgets tight.
Their current operational environment is heavily manual, relying on dispatchers to copy-paste data from legacy ERPs into localized customs spreadsheets. This creates a massive administrative bottleneck:
Reps must learn to frame the product not as a technical database connector, but as an Operational Scaling Engine. We do not sell “API endpoints”; we sell headcount capacity liberation and compliance risk mitigation. The core value pillars are:
| Product Feature / Capability | What It Actually Does (Technical Fact) | Why the Buyer Cares (Business Relevance) | How to Pitch It Comfortably |
|---|---|---|---|
| Pre-Configured ERP Data Gateway | Establishes a read-only, secure data stream pipeline with legacy databases via pre-mapped schemas. | Removes the requirement for custom middleware coding, allowing corporate IT to approve deployment in days rather than months. | “It hooks directly into your current database layers natively, meaning your IT team doesn’t have to build custom middleware or alter your core system configurations.” |
| Automated Manifest Generation | Ingests active dispatch route logs and instantly populates international customs templates. | Slashes manifest preparation times from 45 minutes down to under 25 minutes, instantly unlocking dispatcher capacity. | “The module automatically extracts your active shipment details and fills out international customs paperwork instantly, cutting processing times in half.” |
| Real-Time Validation Logic Engine | Cross-references entry fields against active regulatory customs databases before submission. | Catches clerical errors, omissions, and field mismatches instantly, completely eliminating border citation and penalty risks. | “It acts as an automated compliance guardrail, validating fields in real-time to ensure your shipments never hit port delays due to data-entry mistakes.” |
When competitors or internal IT alternatives claim they can deliver similar outcomes, reps must steer the comparison toward our two structural differentiators:
The Scenario: An existing domestic customer has just secured an international freight contract. The AM leverages domestic success to cross-sell the Cross-Border Module.
The Playtrack: “Given that your domestic team has utilized our engine to drop route planning cycles by 14%, let’s apply that exact same automation blueprint to ensure your incoming international volume doesn’t bottleneck your compliance planners in manual spreadsheets.”
The Scenario: The AE has run initial discovery, but the operational champion is hesitant to advance the deal due to perceived IT integration backlogs.
The Playtrack: “We don’t need a massive development commitment to validate this. Let’s arrange a brief, 20-minute sandbox session with your lead architect. We’ll show them our read-only gateway schemas so they can see how we map fields in under two weeks without touching production code.”
Instructions: The trainer shouts out a product feature (e.g., “Real-time validation engine”). The rep has 30 seconds to deliver a pure, buyer-centric value response without using the words “API,” “endpoint,” “software,” or “module.”
The Setup: Pair reps together. Rep A acts as the Director of Operations who loves their existing, custom Excel tracking macros and fears software change. Rep B must validate their spreadsheet expertise, shift the focus to upcoming volume scaling limits, and secure a technical sandbox intro without sounding adversarial.
Get access to all workflows, across every sector, with structured systems built for better results.