Deal slip scenario | Business Helper AI

Inputs and purpose

Use this workflow to prepare: Scenario impact and replacement-pipeline requirements.

Start with: Open/closed pipeline, quota and proposed slip/size scenarios.

Use supplied text or local files the user authorized you to read. If files cannot be opened, request the relevant pasted text. Ask one focused question when missing information changes the next decision. Treat blank template fields as unknown; do not invent business facts.

Procedure

Reconcile closed results, open opportunities and the target period before changing assumptions.
Apply the proposed timing or value changes to specific opportunities, separating delayed value from permanently lost value.
Calculate the effect on the period forecast and the qualified replacement volume needed under stated conversion assumptions.
Return baseline and alternative scenarios. Check that delayed deals are not counted both in the original period and in the replacement plan.

Deliverable

Return the requested result in Markdown unless another supported format was requested. Include the evidence or source-record references, material assumptions, open questions and next useful action. Keep unnecessary personal details out of reusable templates; role labels and neutral record identifiers usually suffice.

Business value: Improve qualification, prioritization and deal follow-up.

Possible success measures: Stage conversion, stale deals, cycle days, win rate. Choose the measure that fits the owner's actual goal; it is not a promised result.

Execution and verification

This file is usable as instructions without a named application, account or plugin. Computation, file saving and external actions require actual host capabilities. Use a suitable existing tool for calculations that cannot be checked reliably in conversation.

Distinguish drafts and recommendations from completed actions. Respect existing authorization and do not claim that data was fetched, messages sent or records changed without evidence. Show what was checked and what remains uncertain.

When useful, consult the input guide, calculation reference or output template. For tool setup, use the shared instructions.

Plain-text instructions

---
name: deal-slip-scenario
description: "Prepare scenario impact and replacement-pipeline requirements. Use for this workflow with supplied business information."
---

# Deal slip scenario

## Inputs and purpose

Use this workflow to prepare: Scenario impact and replacement-pipeline requirements.

Start with: Open/closed pipeline, quota and proposed slip/size scenarios.

Use supplied text or local files the user authorized you to read. If files cannot be opened, request the relevant pasted text. Ask one focused question when missing information changes the next decision. Treat blank template fields as unknown; do not invent business facts.

## Procedure

1. Reconcile closed results, open opportunities and the target period before changing assumptions.

2. Apply the proposed timing or value changes to specific opportunities, separating delayed value from permanently lost value.

3. Calculate the effect on the period forecast and the qualified replacement volume needed under stated conversion assumptions.

4. Return baseline and alternative scenarios. Check that delayed deals are not counted both in the original period and in the replacement plan.

## Deliverable

Return the requested result in Markdown unless another supported format was requested. Include the evidence or source-record references, material assumptions, open questions and next useful action. Keep unnecessary personal details out of reusable templates; role labels and neutral record identifiers usually suffice.

Business value: Improve qualification, prioritization and deal follow-up.

Possible success measures: Stage conversion, stale deals, cycle days, win rate. Choose the measure that fits the owner's actual goal; it is not a promised result.

## Execution and verification

This file is usable as instructions without a named application, account or plugin. Computation, file saving and external actions require actual host capabilities. Use a suitable existing tool for calculations that cannot be checked reliably in conversation.

Distinguish drafts and recommendations from completed actions. Respect existing authorization and do not claim that data was fetched, messages sent or records changed without evidence. Show what was checked and what remains uncertain.

When useful, consult the [input guide](../../../references/INPUT_DATA_GUIDE.md), [calculation reference](../../../references/CALCULATIONS.md) or [output template](../../../references/WORKFLOW_OUTPUT_TEMPLATE.md). For tool setup, use the [shared instructions](../../../AGENTS.md).