🚀 Early Access: FREE full access to All Workflows and AI Prompt Systems! No credit card required.
Sales leaders, Sales enablement managers, Revenue teams, Account executives, SDR managers
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 strategist. Your task is to create a practical sales play for one specific selling motion that reps can follow in real conversations.
### Required Input
- Offer: [Describe the product, service, or package. Example: "AI reporting add-on for mid-market finance teams"]
- Target Buyer: [Who the play is for. Example: "VP Finance at 200-1000 employee SaaS companies"]
- Sales Motion: [Example: outbound prospecting, inbound follow-up, expansion, renewal save, competitive displacement]
- Buyer Problem: [The core pain or priority. Example: "manual month-end reporting slows decision-making"]
- Trigger Event: [What makes outreach timely. Example: "new CFO hired, funding round, tool migration"]
- Sales Stage Covered: [Example: first meeting, discovery, demo, proposal, close]
- Differentiators: [Why this offer is credible or better. Example: "connects to existing ERP without custom build"]
- Common Objections: [List likely concerns. Example: "too expensive, already have dashboards, IT backlog"]
- Proof Points: [Customer results, case studies, metrics, or credibility signals]
- Tone: [Example: consultative, direct, enterprise, friendly]
### Input Validation
Review every required input before creating the sales play. If the offer, target buyer, sales motion, buyer problem, or stage is missing, vague, or too broad, ask specific clarification questions and pause until answered. Do not create a generic play.
### Instructions
Build the play around one clear commercial objective. Start by defining the buyer situation, why the play is relevant now, and what the rep should be trying to learn or achieve at this stage.
Translate the buyer problem into sales language reps can use without sounding scripted. Explain the likely business impact, the personal pressure on the buyer, and the reason the problem may be urgent. Connect the differentiators to that situation instead of listing features.
Create a usable conversation path. Include opening positioning, discovery areas, strong questions, proof points to introduce, and how to transition toward the next step. Make the guidance specific enough for a rep to use but flexible enough for live calls.
Include objection handling that addresses the concern behind each objection. For every objection, provide the likely buyer meaning, a recommended response, a follow-up question, and a proof point or next step.
Add enablement notes for managers. Identify what good execution sounds like, where reps may go off-track, and how to coach the play in pipeline reviews or call coaching.
### Output
Produce the finished sales play with these sections:
- Play Overview
- When to Use This Play
- Target Buyer Situation
- Core Value Message
- Rep Objective
- Conversation Flow
- Discovery Questions
- Proof Points to Use
- Objection Handling Table
- Recommended CTA and Next Step
- Manager Coaching Notes
- Success Indicators
- Rep Execution Checklist
Add a concise talk track version that a rep can review five minutes before a call.
Execute this play immediately when an existing domestic logistics customer triggers one of the following events:
The buyer is facing severe operational pressure to scale international freight throughput by 25-30% next quarter without expanding administrative headcount. Currently, their international division relies on manual entry, creating a massive administrative bottleneck. Each manifest takes 45+ minutes to prepare, leading to human errors, port delays, and unexpected customs citations. Personally, the buyer is under intense pressure from executive leadership to maintain strict operational margins during a major corporate international expansion phase.
“By embedding our Cross-Border Customs API directly into your existing dispatch workflows, we eliminate the need for manual data entry entirely. This automation cuts manifest preparation times from 45 minutes down to less than 25 minutes per sequence, allowing your current staff to absorb a 30% volume spike while completely eliminating compliance citation risks.”
The goal of this call is to uncover the specific manual steps in the customer’s international data pipeline, quantify the financial impact of their current delays, and secure formal agreement to run a technical data mapping assessment alongside their enterprise IT architect.
“Hi [Name], I’ve been reviewing the success your domestic dispatch team has had cutting empty miles by 14% using our core engine. Given your company’s new initiative to scale cross-border freight lines this quarter, I wanted to share how we can apply that exact same automated efficiency to eliminate the manual spreadsheet processing currently bottlenecking your international compliance division.”
“Unlike traditional customs software that requires building completely new standalone data pipelines, our Cross-Border Module plugs directly into your existing dispatch workspace. It ingests your active manifest data and auto-filis international customs templates instantly without adding technical overhead or separate tool maintenance.”
| Objection | What the Buyer Means | Recommended Rep Response | Follow-up Discovery Question |
|---|---|---|---|
| “Our spreadsheets are working fine for now.” | They don’t perceive the true cost of their operational inefficiency or the human error risk. | “I understand. Spreadsheets work well at a baseline, but they become highly vulnerable when scaling volumes. A single typo can trigger severe border delays and cost thousands in fines.” | “As you scale international volume by 25% next quarter, how many additional manual hours will your current staff have to spend tracking down spreadsheet compliance errors?” |
| “Our IT team has a backlogged queue; they won’t have time to build this integration.” | They assume this requires a complex, multi-month custom engineering project. | “That’s exactly why we built this as a native add-on module. It hooks directly into the core engine data layers you’ve already cleared and integrated last year, requiring minimal IT intervention.” | “If we can show your lead IT architect that we can deploy and test this via a secure sandbox environment in under 14 days, would that clear their bandwidth concerns?” |
| “We don’t have additional budget for new software modules this fiscal quarter.” | They view this as an unbudgeted operational expense rather than a cost-avoidance tool. | “That makes total sense. Many of our clients are under tight spending limits right now. However, continuing to process these manually is already costing the division thousands in port demurrage fees and team overtime.” | “If we could structure a business case showing that this automation prevents enough border penalties to fully fund itself within 90 days, would your finance desk review the numbers?” |
The Call to Action: Do not ask for a formal contract review or proposal meeting immediately. Instead, leverage a technical discovery offer to lower friction.
The Script: “Let’s do this: instead of a formal sales pitch, let’s set up a brief, 20-minute technical alignment call. I’ll bring one of our integration engineers to walk your IT lead through our API documentation sandbox. We can show them exactly how your international data maps out with zero development downtime. Do you have your calendar handy for next Thursday afternoon?”
Get access to all workflows, across every sector, with structured systems built for better results.