Tracking · Forecast / Deal Hygiene Rules

Design a Deal-Push Approval Workflow

Stop reps from silently pushing close dates by requiring manager approval and a written justification for every slip.

foundermanagerAdvancedRecovers 15-25% of slipped forecast
When to use
Use this when close dates are slipping by stealth and the quarterly forecast keeps eroding without anyone noticing. Implement once and your forecast accuracy will jump within one quarter.
The prompt
You are a sales operations leader who has implemented push-approval workflows in HubSpot, Salesforce, and Pipedrive across digital agencies.
Agency: [AGENCY_NAME] — [SERVICES] | CRM: [CRM_TOOL] | Quota: [QUOTA]/quarter | Approval authority: [APPROVER_ROLES] | Current % of deals that slip: [SLIP_RATE].
Design a deal-push approval workflow: define what counts as a "push" requiring approval, the data the rep must submit, who approves it, the SLA, and the [CRM_TOOL] implementation.

- A push = close date moved out by more than [PUSH_THRESHOLD_DAYS] days OR moved past quarter-end.
- Rep must submit: new close date, reason category, new evidence, updated probability.
- Approval SLA must be ≤ 24 hours; auto-escalate if missed.
- Workflow must be enforceable as a required field + automation in [CRM_TOOL] — not a Slack DM.

Workflow doc with: Trigger Definition, Required Submission Fields (list), Approval Path, SLA, [CRM_TOOL] Implementation Steps, and Reporting (how to track approval volume and rejection rate).
Variables
  • [AGENCY_NAME] — Your agency
  • [SERVICES] — Services
  • [CRM_TOOL] — CRM
  • [QUOTA] — Quarterly quota
  • [APPROVER_ROLES] — Who can approve — e.g., Sales Manager, VP Sales
  • [SLIP_RATE] — Current % of deals that slip in a quarter
  • [PUSH_THRESHOLD_DAYS] — Days of slip that trigger approval — usually 7-14
Example input
Agency: Vector & Co — web design + Webflow builds | CRM: HubSpot | Quota: $200K/qtr | Approvers: Sales Manager + Founder | Slip rate: 38% | Threshold: 10 days.
Example output
VECTOR & CO — DEAL-PUSH APPROVAL WORKFLOW

Trigger: Close date moves out by 10+ days OR past current quarter-end.

Required Submission (HubSpot custom "Push Request" form):
- New close date
- Reason (dropdown: client legal delay, scope re-work, champion silent, budget shift, lost to competitor)
- New evidence (text)
- Updated probability

Approval Path: Sales Manager → 24hr SLA → auto-escalate to Founder if no decision.

HubSpot Implementation:
1. Workflow triggers when Close Date is changed by >10 days.
2. Deal locks to read-only, Push Request form sent to rep.
3. Manager gets task with 24hr deadline.
4. On approval: deal unlocks with new date. On rejection: deal stays at old date, mandatory 1:1.

Reporting: Weekly dashboard — # pushes requested, # approved, # rejected, avg slip days, rep leaderboard.
Pro tips
  • Rejection rate of 20-30% is healthy; 0% means it's a rubber stamp.
  • Publish anonymized push reasons monthly to spot systemic issues (scope, legal, etc.).
  • Tie persistent push patterns to commission accelerator eligibility — not just yelling.
Works with
ClaudeChatGPTGemini
Done with prompts? Time to install the system
Book a STAOS call
Related prompts