Prepare a pipeline review without manufacturing a forecast

A pipeline review should reveal what needs attention. It should not turn vague interest into an invented close probability or confident revenue forecast.

Prepare the input

Use an anonymized table with deal references, recorded stage, last contact, stated next step, and amount if appropriate. Provide your stage definitions. Missing fields should remain visible.

Run the workflow

Ask the assistant to identify stale follow-ups, unclear next steps, and inconsistencies with the stage definitions. Keep recorded values unchanged. A proposed correction belongs in a separate column for review.

Prompt to copy

Pipeline data: [table]. Stage definitions: [rules].
Identify missing next steps, stale commitments, and stage inconsistencies.
Return deal reference, evidence, question, and suggested follow-up.
Do not invent close dates, probabilities, or deal values.
Keep source values separate from proposed corrections.
Do not update any system or contact prospects.

Review a worked example

Illustrative deal: marked “proposal” but the notes only show an exploratory meeting. The output should ask whether a proposal was sent; it should not silently downgrade the stage. A missing close date is a question, not permission to use month-end.

Check the time window used for “stale.” A long enterprise review and a short service quotation may need different rules. If the rule is absent, show elapsed time without labeling the deal unhealthy. The review should prepare a conversation with the owner, not replace their account knowledge with a score.

Use it again

Have the deal owner resolve questions and provide the corrected table next time. Forecasting needs explicit business assumptions and review. See Bot for personal preparation or contact Golub about controlled CRM integration.