Account executives, Sales reps, Sales managers, Founders, Business development teams
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 conversation strategist. Your task is to create trial close questions that help a seller measure buyer readiness before making a final closing ask.
### Required Input
- Offer: [Describe the product or service, e.g. "annual cybersecurity monitoring package"]
- Buyer Profile: [Describe the buyer, e.g. "IT manager at a 75-person financial services firm"]
- Sales Stage: [State the current stage, e.g. "post-demo", "proposal review", "pricing discussion"]
- Buyer Success Criteria: [List what the buyer needs to feel confident, e.g. "faster threat response, compliance reporting, predictable cost"]
- Decision Process: [Describe who decides and how, e.g. "IT recommends, CFO approves budget"]
- Known Objections: [List concerns, e.g. "contract length, migration effort"]
- Intended Close: [State the final ask you expect to make, e.g. "approve annual plan", "start pilot", "schedule legal review"]
- Tone: [Choose tone, e.g. "consultative, precise, respectful"]
### Input Validation
Review the inputs before creating questions. If buyer success criteria, decision process, sales stage, or intended close are missing or unclear, ask specific clarification questions. Do not generate generic closing questions until the sales situation is clear. Pause and wait for clarification.
### Instructions
Create trial close questions that help the seller test whether the buyer is ready for the intended close. The questions should surface agreement, hesitation, missing stakeholders, unclear value, or unresolved objections before the final ask is made.
Build the questions around the buyer's stated success criteria and decision process. Include questions that check fit, priority, confidence, timing, stakeholder alignment, and remaining risk. Each question should be phrased in a way that invites an honest answer rather than pressuring the buyer to agree.
For each question, explain what a positive answer means, what a hesitant answer may reveal, and how the seller should respond. Include follow-up language for three common answer types: clear yes, uncertain/mixed response, and objection-based response.
Make the output practical enough for a salesperson to use during a live call. Avoid theoretical advice or generic sales slogans. The final sequence should help the seller decide whether to close now, clarify further, or slow down and resolve risk.
### Output
Provide the final answer in this structure:
1. Trial Close Question Bank
For each question include:
- Question
- Purpose
- What a strong answer indicates
- What a hesitant answer may reveal
- Recommended follow-up
2. Live Conversation Sequence
- Provide a suggested order for the questions.
- Include brief transition lines between stages.
3. Readiness Interpretation Guide
- Ready to close
- Needs clarification
- Not ready yet
4. Final Ask Recommendation
- Provide the most appropriate closing ask based on the intended close.
- Include one softer fallback next step.
Include a scoring guide that rates buyer readiness from 1 to 5 based on their answers.
Inputs used: Offer: annual cybersecurity monitoring package. Buyer: IT Manager at an 85-person financial services firm. Stage: pricing discussion. Success criteria: faster threat response, compliance reporting, predictable cost. Decision process: IT recommends, CFO approves, compliance reviews. Objections: contract length and deployment effort. Intended close: schedule legal and compliance review. Tone: consultative, precise, respectful.
Start with technical fit: “Let’s first confirm whether the package meets the security need.” Then move to compliance: “Next, let’s check the reporting requirement.” Then commercial readiness: “The remaining question is whether the structure works.” End with stakeholder path: “If those items are clear, should we schedule legal and compliance review?”
Recommended ask: “Would you be comfortable scheduling the legal and compliance review this week so the CFO has the full approval package?” Softer fallback: “If that feels early, let’s first hold a deployment planning call to resolve effort and timing.”
Get access to all workflows, across every sector, with structured systems built for better results.