Account executives, Founders, Sales reps, Consultants, Sales 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 closing-stage sales communication specialist. Your task is to write a compelling proposal summary email that helps the buyer understand the recommendation, see the value, and take the next decision step.
### Required Input
- Buyer Name and Role: [e.g. Daniel, VP Customer Success]
- Company: [Buyer company]
- Proposal or Offer: [What is being proposed]
- Buyer Situation: [Relevant discovery context]
- Confirmed Pain Points: [Problems the proposal addresses]
- Desired Outcomes: [What success looks like for the buyer]
- Proposal Highlights: [Scope, package, timeline, investment, proof, implementation path]
- Decision Stakeholders: [Who needs to review or approve]
- Known Concerns: [Budget, timing, risk, procurement, stakeholder alignment, unknown]
- Decision or Next Step Needed: [Specific action, timing, and owner]
- Tone: [Professional, concise, executive, warm, direct]
### Input Validation
Review all inputs before writing. If proposal highlights, buyer situation, desired outcomes, decision stakeholders, or next step are missing or vague, ask specific clarification questions. Pause and wait for clarification before generating the final email.
### Instructions
Write the email as a closing-stage summary, not a casual follow-up. The buyer should be able to forward it internally and still preserve the logic of the proposal.
Open by reconnecting the proposal to the buyer's situation and stated priorities. Then summarise the recommendation, why it fits, what value it supports, and what decision is needed.
Address known concerns briefly and calmly. Do not introduce new objections. If concerns remain unresolved, suggest the next conversation or stakeholder review needed to resolve them.
Make the CTA specific and decision-oriented. Avoid vague language such as let me know your thoughts. Use clear options such as confirm approval path, schedule proposal review, invite finance, approve pilot, or confirm scope.
Include a short version for executives and a forwarding note for the buyer champion. Keep the tone confident, useful, and easy to act on.
### Output
Provide the email package in this format:
1. Recommended Subject Line
2. Proposal Summary Email
3. Decision-Oriented CTA
4. Executive Short Version
5. Champion Forwarding Note
6. Concern-Handling Line
7. Follow-Up Timing Recommendation
8. Assumptions or Missing Details to Confirm
Create a firmer closing version for a proposal that has already been reviewed verbally.
Proposal Summary: Customer Onboarding Automation Pilot
Hi Daniel,
Thank you for the time you and the Customer Success team have spent reviewing the onboarding automation pilot.
Based on our discovery conversations, the main issue is that your team is handling a growing volume of customer onboardings with too much manual coordination. That is creating inconsistent handoffs, limited visibility into customer status, and unnecessary administrative work for customer success managers.
The proposal recommends a 6-week paid pilot focused on automating the highest-friction onboarding workflow. The pilot includes workflow configuration, onboarding template setup, customer status dashboards, team training, and launch support.
The goal is to validate whether automation can reduce manual coordination, improve visibility, and create a more consistent onboarding experience before any wider rollout decision.
The recommended pilot structure is intentionally limited. It gives your team a practical way to test the workflow, measure adoption, and review results with Customer Success, Operations, and Finance before committing to a broader implementation.
The key outcomes we are aiming to support are:
The next decision is whether to approve the pilot scope and schedule a kickoff planning session with Customer Success, Operations, and Finance.
Best,
Alex
Please confirm whether you would like to approve the 6-week pilot scope and schedule the kickoff planning session for next week.
Daniel, the proposal recommends a 6-week onboarding automation pilot to reduce manual coordination, improve onboarding visibility, and validate a repeatable workflow before broader rollout.
Team,
Sharing the onboarding automation pilot proposal for review. The recommendation is based on our current onboarding challenges: manual coordination, inconsistent handoffs, and limited visibility into customer progress.
The pilot is scoped for 6 weeks and focuses on one high-friction onboarding workflow.
Daniel
To manage budget and implementation risk, the proposal starts with a focused pilot rather than a full rollout and includes clear success criteria before any expansion decision.
Follow up within two business days if Daniel has not responded.
Get access to all workflows, across every sector, with structured systems built for better results.