Back to prompts
Sales11.10.2026
Write a Q4 Sales Pipeline Close Plan for the Last Weeks of the Year
#q4#sales pipeline#forecast#year end#deal review#viral
You are a practical sales manager. There are only a few working weeks left in the year once holidays are counted. Turn my open pipeline into an honest close plan for Q4. Use only the deals and numbers I give you. Do not invent deal sizes, close dates, or buyer names. If a detail is missing, mark it [NEEDS INPUT]. My Q4 target and what is already closed: [TARGET AND CLOSED] Open deals with stage, value, expected close date, and next step: [PIPELINE] Known buyer holiday closures or budget freeze dates: [BUYER DEADLINES] My own time off and team holidays: [TIME OFF] Sales cycle length for a typical deal: [CYCLE] Requirements: 1. Calculate the gap between target and closed. Show the math. 2. Sort [PIPELINE] into commit, likely, and stretch using only the stage and next step I gave. Flag any deal whose expected close date falls after [BUYER DEADLINES] or inside [TIME OFF]. 3. Flag deals that have no next step or a next step older than two weeks as at risk. 4. For each commit and likely deal, write one concrete next action with a date before the holidays. 5. Suggest which stretch deals to move to next year now so the forecast stays honest. 6. Never suggest fake urgency, invented discounts, or pressure tactics. 7. End with a weekly 15 minute pipeline review agenda through the end of December. Deliverables: 1. Target gap summary 2. Commit, likely, and stretch table 3. At risk deal list with next actions 4. Weekly review agenda
How to use this prompt
- 1Copy the prompt using the button above.
- 2Open your AI tool (ChatGPT, Claude, Midjourney, etc.)
- 3Paste and customize any variables in the prompt.
- 4Generate your result.
Tip
Fill every placeholder before you run the prompt. Keep one clear goal per run, then refine with a follow-up if needed.
When to use this prompt
- •Good for first drafts in Sales
- •Keep variables filled so the model has enough context
- •Review AI output before sending or publishing