Pipeline by Stage
Open amount and deal count at each stage, weighted and unweighted, by owner and territory in the reporting currency, with the movement since last week and the deals whose close date slipped between the two weekly snapshots.
The weekly rhythm: reps categorise every open deal and submit, managers review and adjust on the record, and the period locks so the forecast can be checked against what closed.
6 stages · 2 approvals
Follow the process from start to finish. Select a step to see who acts and what changes.
Before the submission day, each rep works through their open deals in the period, sets the close date, and sets the forecast category on each: commit, best case, pipeline or omitted. Stage suggests the category; the rep's judgement sets it, and a category that differs from the stage default is visible as such.
noneBooking waits for the deal desk.
The rep submits the weekly forecast in the quota currency, each deal converted at the period rate and measured on the quota's basis. Closed is calculated from validated wins in the period; commit is the sum of deals in commit; best case is commit plus the deals in best case; pipeline is best case plus everything else open. The rep may adjust commit down with a comment. The submission stores the four numbers and a line per open deal as they stood that week.
weekly snapshot stores each deal and its applied conversion rateReview waits for the sales manager.
The manager opens each submitted forecast and sees the deals behind the numbers with stage, category, next step, last activity and quote status. The manager challenges what does not hold up, and the rep updates the deal, which updates the next submission.
deals updated by the repThe manager applies an adjustment to commit, signed either way, with a comment, and marks the forecast reviewed. The rep's number and the manager's adjustment are kept side by side. The manager's own submission upward is built from the reviewed team forecasts.
manager number recordedReview waits for the sales manager.
Sales Manager locks the team's submissions at period end. Locked forecasts cannot be changed and are what the attainment report and the executive read.
period closed for editsThe Sales Manager reviews it deal by deal, applies a ManagerAdjustment with a comment, and marks it reviewed (Status: Submitted → Reviewed).
Review waits for the sales manager.
After the period closes, the forecast as it stood at each week is compared with what closed, by rep and by manager, deal by deal from the weekly lines. The comparison feeds quota setting and the conversation about what commit means on this team.
attainment and accuracy reportedBooking waits for the deal desk.
ForecastSubmissions, Opportunities, Activities
ForecastSubmissions
Users
Quotas
ForecastSubmissionLines
The weekly forecast lines show close-date slips between submissions. Pipeline by Stage compares those snapshots; Team Pipeline supplies the current deal list for the review.
The weekly snapshots show whether a rep's commit is consistently below or above what they close, and by how much. The manager's adjustments show whether the manager corrects for it.
The review happens on the submission, with the deals one click away, and the locked submission is what the executive reads, so a spreadsheet copy carries nothing the record does not.
| Stage | Records | Effect |
|---|---|---|
| 1 Categorise | Opportunities | none |
| 2 Submit | ForecastSubmissionsForecastSubmissionLinesQuotasExchangeRates | weekly snapshot stores each deal and its applied conversion rate |
| 3 Review | ForecastSubmissionsOpportunitiesActivities | deals updated by the rep |
| 4 Adjust | ForecastSubmissions | manager number recorded |
| 5 Lock | ForecastSubmissions | period closed for edits |
| 6 Compare | ForecastSubmissionsForecastSubmissionLinesQuotasOpportunities | attainment and accuracy reported |
Open amount and deal count at each stage, weighted and unweighted, by owner and territory in the reporting currency, with the movement since last week and the deals whose close date slipped between the two weekly snapshots.
| Owner | Opportunity Name | Account | Stage | Amount |
|---|---|---|---|---|
| LV | Opportunity 715 | ACC-66564 | PS-5338 | 340 |
| KY | Opportunity 462 | ACC-18461 | PS-2598 | 460 |
| BN | Opportunity 584 | ACC-49712 | PS-6274 | 690 |
| FP | Opportunity 114 | ACC-46364 | PS-1897 | 910 |
| WX | Opportunity 613 | ACC-35644 | PS-6289 | 300 |
| UZ | Opportunity 380 | ACC-74461 | PS-9757 | 680 |
Closed, commit and best case against quota per rep, with open pipeline as coverage of the quota remaining, rolled up through manager to region at the period rate, with the manager adjustment shown separately.
| Forecast Number | Period | Week Ending | Closed | Commit |
|---|---|---|---|---|
| FS-15160 | Q1 | 22 Sep | 60 | 230 |
| FS-69293 | Q2 | 18 Sep | 290 | 350 |
| FS-99658 | Q3 | 12 Sep | 610 | 430 |
| FS-21134 | Q4 | 29 Sep | 320 | 900 |
| FS-53762 | Q1 | 11 Sep | 430 | 660 |
| FS-96206 | Q2 | 22 Sep | 510 | 640 |
New opportunities and amount added per week by owner, source, campaign, partner and type.
| Owner | Opportunity Name | Account | Stage | Amount |
|---|---|---|---|---|
| LV | Opportunity 715 | ACC-66564 | PS-5338 | 340 |
| KY | Opportunity 462 | ACC-18461 | PS-2598 | 460 |
| BN | Opportunity 584 | ACC-49712 | PS-6274 | 690 |
| FP | Opportunity 114 | ACC-46364 | PS-1897 | 910 |
| WX | Opportunity 613 | ACC-35644 | PS-6289 | 300 |
| UZ | Opportunity 380 | ACC-74461 | PS-9757 | 680 |
The configured workflows must keep lead acceptance with Account Executive, negotiation approval with Sales Manager and bookings validation with Deal Desk. An agent can prepare evidence and drafts for those decisions. Forecast review, quote approval and realignment approval also remain human actions. Rehearsal must verify refusal of unauthorised actions and attribution of every permitted write before the agent is enabled.
From a lead arriving to a signed contract handed to customer success: routing, qualification, acceptance, proposal, negotiation, the bookings check and the handover, with the gates where a person decides.
6 stages · 3 approvals
How a priced proposal gets from a rep's draft to the customer's inbox: the rules that decide who must approve, the steps in sequence, and what happens on rejection, revision and expiry.
6 stages · 1 approval
From a contract's notice deadline to the next contract signed: the opportunity the system opens, the risk call, the renewal quote and approval, and what happens when the customer says no.
6 stages · 2 approvals
Changing who owns which accounts without losing deals in flight: modelling the new rules, approving the moves, applying them in bulk, handing over open deals, and checking nothing was orphaned.
6 stages · 2 approvals
Create your ERP.AI account and get started with Proto.
We use essential cookies to run the site and optional cookies for features, analytics, and relevant content. See Cookie policy
We use cookies to enhance your experience, analyze site traffic, and serve relevant content. By clicking "Accept All," you agree to our use of cookies. You can customize your preferences at any time.
Learn more about how we use cookiesThese cookies are required for the website to function properly. They ensure security, enable basic features like page navigation, and store user session data. You cannot disable these cookies.
These cookies enable additional features that enhance your experience, such as live chat, video playback, personalized content recommendations, and remembering user preferences.
These cookies help us understand how visitors interact with our site by collecting anonymous usage data. This allows us to measure performance, detect issues, and continuously improve the user experience.
These cookies allow us and advertising partners, including X, to deliver ads tailored to your interests. They track browsing habits across sites to provide relevant advertising and measure ad effectiveness.