Rep Said Commit. Manager Said Maybe. Vesso Logged Both.
Vesso's sales forecasting separates what reps believe will close from what managers will defend. Three-tier deal categorization, manager overrides with reasons, pacing status, and point-in-time snapshots track how the forecast number changed across a quarter.

Most forecast conversations start with a number and end with a disagreement. The rep says commit. The manager adjusts it. The CRO wants to know what changed from last week. By the end-of-quarter review, nobody remembers what the forecast said in week two.
Vesso's forecasting view is designed around this problem. Each rep submits three numbers per period, managers can apply an override with a reason attached, and point-in-time snapshots capture where the forecast stood at any moment so you can compare week-two expectations against week-twelve actuals.
Three tiers, not one guess
When a rep submits a forecast, they fill in three fields:
- Commit: what the rep is willing to defend if the quarter ends tomorrow
- Best Case: what closes if everything breaks right
- Pipeline: the full active book, including long shots
Each deal in the pipeline also carries a category tag (Commit, Best Case, Pipeline, or Omitted) that ties individual opportunities to the rep's overall number. The forecast view rolls these up to show totals across all three tiers alongside the period quota and the current gap to close.
The Weighted Pipeline card runs a separate calculation. It applies per-stage probability weights to the full deal book and returns three scenario outputs: Conservative, Expected, and Upside. That number is a check against rep sentiment. Stage-weighted math doesn't hope, it multiplies.
Manager override, with a reason on record
Managers can adjust any rep's forecast from the By Rep tab. The override modal shows the rep's self-submitted Commit and Best Case alongside the system-tracked Closed amount, then prompts for an override amount and a reason field.
The reason isn't optional decoration. It shows up next to the override amount in the forecast table, so when the QBR question is "why did we adjust this number down in week eight?" the answer is in the record. The Adjustments tab logs every override chronologically across the team, with the override type tagged on each row.
Pacing keeps context visible
Each rep row carries a pacing badge: Ahead, On Track, Behind, or At Risk. The badge reflects the rep's closed-to-quota ratio at the current point in the period. Combined with the commit number, it tells you whether a rep who is "behind" has real pipeline coverage or is running on optimism.
Snapshots and forecast drift
The Snapshots tab records point-in-time captures of the full team forecast. You can create a manual snapshot at any moment. Each snapshot stores the total Commit, Best Case, Pipeline, and Quota values at that date.
The comparison view lets you place two snapshots side by side. Pick one on the left, one on the right, and see the delta. That diff answers the most common end-of-quarter audit question: when did the number change, and by how much? The Accuracy tab extends this by comparing historical forecasts against what actually closed.
Views by rep, team, and territory
The same period data surfaces in three rollup views. By Rep shows individual quota attainment bars and the full three-tier breakdown per person. By Team aggregates those numbers up the management chain. By Territory is available when forecasts are structured around territory-based aggregation.
All views support monthly, quarterly, and annual period types. Switching periods recalculates the rollup from the underlying forecast submissions.
The number that matters
A forecast is only as useful as the trail behind it. When a rep's commit drops between week four and week ten, the question is not just "what is the number now" but "who saw what, when, and what changed their view." Vesso stores enough state to answer that question from within the product, without digging through Slack threads or email chains.

Vee is a contributor to the Vesso blog.