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.
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
Follow the process from start to finish. Select a step to see who acts and what changes.
Sales operations creates a realignment with an effective date and drafts the new territory rules under it: new territories, changed rules over countries, states, postcodes, industries, employee-count bands and named-account lists, changed owners. The draft rules start on the effective date, so they sit beside the live rules without touching assignment.
noneApproval waits for the sales manager.
The draft rules are run over the live accounts and leads without changing anything. The output is a move per account: its current territory and owner, its proposed territory and owner, and the open pipeline and contract value that would move with it. Territory Coverage shows the totals per territory before and after, beside each rep's quota.
move list producedApproval conditions.
Sales managers review the moves for their teams and mark the exceptions they want: an account that should stay with its rep because a deal is closing, or a named account that should move now. When every affected manager has approved their team's moves, the realignment is approved as a whole, with the exceptions listed on it.
approvals and exceptions recordedwhen every affected manager has decided, the realignment is approved (Status: Modelled → Approved).
Approval waits for the sales manager.
On the effective date the new rules take effect and approved account moves apply. Each account retains its previous territory, previous owner and realignment reference. Leads in the affected territories are re-routed. Open opportunities retain their current owner until a separate handover is confirmed; an account move does not authorise that change.
previous owner kept on each accountApproval conditions.
For each open opportunity that changes owner, the outgoing and incoming reps hold a handover. It is logged as an activity on the deal with the state of the buying committee and the next step. The manager confirms the handover before the deal's owner changes. Contracts follow the account; renewal deals move with the contract owner as the manager decides.
confirmed handover logged before deal or contract ownership changesTerritory Coverage is run against the new structure: accounts with no owner, territories with no rep, leads that matched no rule. Each is fixed or explicitly parked. Quotas are republished where the book changed.
coverage checked and quota changes reviewedApproval conditions.
RealignmentMoves, Realignments
Opportunities, Contracts, Activities, AccountTeamMembers
Territory Coverage lists accounts with no owner and leads that matched no rule the morning after the change.
It cannot, without a handover the manager confirmed.
The model shows pipeline and contract value per territory before and after, beside the quota, before anyone approves.
| Stage | Records | Effect |
|---|---|---|
| 1 Propose | RealignmentsTerritoryRulesTerritories | none |
| 2 Model | RealignmentMovesAccountsLeads | move list produced |
| 3 Approve | RealignmentMovesRealignments | approvals and exceptions recorded |
| 4 Apply | AccountsLeadsTerritoryRules | previous owner kept on each account |
| 5 Hand over | OpportunitiesContractsActivitiesAccountTeamMembers | confirmed handover logged before deal or contract ownership changes |
| 6 Verify | AccountsLeadsTerritoriesRealignmentMovesQuotas | coverage checked and quota changes reviewed |
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 |
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 |
Contracts by notice deadline month with owner, annual value, renewal risk and the status of the renewal opportunity, and the value not renewed with its churn reason.
Accounts, contacts, open pipeline and closed revenue by territory and sub-territory, with unowned accounts flagged, and the before and after of a modelled realignment.
| Account Number | Account Name | Industry | Tier | Type |
|---|---|---|---|---|
| ACC-70636 | Account 788 | Software | Strategic | Prospect |
| ACC-33912 | Account 463 | Manufacturing | Key | Customer |
| ACC-64097 | Account 802 | Distribution | Strategic | Partner |
| ACC-27605 | Account 688 | Services | Key | Former |
| ACC-42602 | Account 181 | Healthcare | Strategic | Prospect |
| ACC-38511 | Account 705 | Finance | Key | Customer |
Deals won and lost in a period by loss reason, competitor, source, campaign, deal size band and industry, including lost renewals by churn reason.
Days spent in each stage and total cycle length by deal size band and type, from stage history.
Leads by source, channel and campaign through working, qualified, accepted and converted, with time to first touch and time to convert.
Approval conditions.
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
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
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
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.