Forecast versus quota
Shows period closed-won revenue alongside pipeline coverage.
Authored by Sid Chaudhary
Founder & CEO at Intempt
Agentic workflow
Coming soon1 step Blu runs end to end. It drafts a plan and nothing runs until you approve it.
- 1
Compare closed, forecast and quota
Coming soonBlu builds a step
About this recipe
When to use it
Finding out you missed quota on the last day of the quarter is too late to do anything about it. This tracks forecast vs. actual vs. target continuously, with pipeline coverage ratio and a projected close, so the miss is visible weeks out.
What it delivers
Compares period-level revenue forecast, actual closed-won, and quota target side by side, with pipeline coverage ratio and a projected close date calculated from current trajectory.
How you prompt this
Describe the outcome in your own words and Blu Agent maps it to this recipe, or run it by name. It drafts a plan first and nothing runs until you approve it.
Tell Blu Agent what you want
“Shows period closed-won revenue alongside pipeline coverage.”
recipe.md preview
Built from the published catalog. Blu Agent's full step prompts load in your workspace when you run it.
Inputs & outputs
What the recipe needs before it runs, and what it leaves in your workspace.
Inputs
- Nothing declared beyond an Intempt workspace. Blu asks for anything else it needs as it goes.
Outputs
How the recipe runs
Blu follows the steps in order and shows you each one before anything goes live.
- 01Compare closed, forecast and quotaCreate an Insights report called "Forecast vs Actual vs Quota". Series A: Sum of Deal won.amount per period (closed-won revenue), unit: $, label: "Actual Closed-Won" Series B: Sum of (open-deal amount × historical close-rate of current stage) for deals with close_date in the period: the weighted forecast, unit: $, label: "Weighted Forecast" Series C: Workspace-configured quota target for the period, unit: $, label: "Quota Target" - Default: pulled from a workspace-level quota attribute (per-period dollar target). If unconfigured, recipe degrades gracefully and surfaces just A and B. Series D: Computed: Series A / Series C × 100, unit: %, label: "Quota Attainment" Series E: Computed: (Sum of all open-deal amounts) / Series C, label: "Pipeline Coverage Ratio" - The canonical 3:1 ratio benchmark: pipeline-to-quota of 3x is the industry minimum for reliable close. Series F: Computed: Sum of deal amount where close_date IS within next 30 days AND stage is in late-stage (negotiation/proposal/contract), unit: $, label: "Projected Close (Next 30d)" Time granularity: Monthly (or per quota period: quarterly for most B2B teams) Time range: Trailing 4 quota periods + current + next period (forward-looking forecast) Breakdown: By owner_id (per-rep): pushed down so each rep's forecast/actual/quota is visible Compare: Previous period AND year-over-year same-period Chart type: Combo chart: Series A (actual) and B (forecast) as bars, Series C (quota) as a horizontal target line, Series D (attainment %) on a secondary axis as a callout, Series E (coverage ratio) as a separate KPI tile Annotations: - Add the canonical pipeline coverage benchmark: 3:1 minimum, 4-5:1 healthy, <2:1 indicates pipeline shortfall. - Flag any period where forecast (Series B) significantly exceeded actual (Series A): forecast-accuracy issue, investigate which deals slipped. - Flag any rep whose pipeline coverage ratio fell below 2:1 (acute risk for next period). - Highlight the period attainment trend: 4+ consecutive periods below 100% attainment indicates either quota is set too aggressively or systematic execution issues. - Surface forecast accuracy as an explicit metric: |Actual − Forecast| / Actual × 100 over trailing 4 periods. Top-quartile sales orgs forecast within ±10%; below ±20% accuracy indicates the forecasting process needs refinement. Use case: the canonical sales VP / CRO weekly report. Pipeline coverage ratio (Series E) is the most-cited B2B sales KPI; forecast accuracy is the leading indicator of sales-process maturity. Taxonomy notes: - Deal won.amount and Deal won.close_date are canonical properties. - Deal stage changed has new_stage and amount per state change; "current open-deal amount" comes from the most-recent Deal stage changed.amount per deal_id. - owner_id is a canonical property on Deal created and Deal stage changed; also on Users object. - IMPORTANT: quota target dependency: this recipe assumes the workspace has quota targets configured per period per rep, OR a workspace-level aggregate quota. If neither is configured, Series C and Series D return null and the report renders Series A, B, E, F only. Sales teams typically inject quota targets via HubSpot/Salesforce sync or as a manual workspace-level attribute. - "Late-stage" classification for Series F (Projected Close) follows the project's deal-stage configuration; standard convention is the final 2-3 stages before Deal won/Deal lost.
Install Intempt and run it
- 1
Sign up
Create a free Intempt workspace.
- 2
Connect your data
Add the sources this recipe reads from.
- 3
Ask Blu
Type /forecast-vs-actual-quota in Blu once this recipe is live there.
- 4
Review and approve
Blu builds each step and waits for your OK before anything goes live.
Related recipes
Sid ChaudharyDiscovery call qualification fieldsGenerates an AI summary for Discovery calls from meeting data using the qualification framework in the summary recipe.View recipe Sid ChaudharyPost demo nurtureKeeps a demo warm for 90 days with a playbook, a case study, an ROI calculator and a customer story, and pulls the AE in early if they bite.View recipe Sid ChaudharyReturn rate by categoryShows which product categories get returned most, and which ones have got worse since last quarter.View recipe 