Discount Analysis
Blended discount by rep, product family and deal size, with the approvals requested, how each was decided and the quotes that expired unanswered.
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
Follow the process from start to finish. Select a step to see who acts and what changes.
The rep builds the quote on the opportunity from the account's price book: lines with quantity, unit price and discount, a header with payment terms, billing frequency, validity date, scope of work and any special terms.
noneThe rep submits. The rules check each line's discount against the rep's authority and the entry's maximum discount, and each unit price against the floor. They check the payment terms and billing frequency against the standard, the special terms field for any content, and the total against the deal size thresholds.
approval flag setEach breach becomes an approval step with a reason and an approver. A discount above the rep's authority goes to the first person up the reporting line whose authority covers it; above the entry's maximum it goes to the deal desk regardless. Deal size goes to the sales manager, and to the manager's manager above the second threshold where one is set. Floor price, non-standard terms, payment terms and billing frequency go to the deal desk. Steps are ordered and the first approver is notified; a quote with no breaches is approved by the system here.
approvers notified in sequenceThe assigned Sales Manager or Deal Desk user reviews the quote, buying committee and price history and records the decision in QuoteApprovals. The final approval marks the quote Approved. Rejection retains the rejected step and returns the quote for revision. A delegate must hold the required authority and pass the same self-approval checks.
approved or returnedA rejection returns it to the rep with the approver's comments (Status: Submitted → Rejected → Draft) and the rejected step stays on the record.
When every step is approved the quote moves (Status: Submitted → Approved → Sent) and the PDF goes to the Recipient.
Approval conditions.
The approved quote is rendered to PDF and sent to the recipient contact; the sent date is stamped and the quote is locked. If it is the primary version, the opportunity's values are updated.
opportunity values updatedAccount Executive or Customer Success Manager records the customer's answer. Accepted requires AcceptedDate and AcceptanceDocument for the current version; Declined records a refusal. An unanswered quote becomes Expired after its validity date. Any new version starts at Draft and requires its own approvals and negotiation review.
accepted version ready for the bookings checkQuoteApprovals, Quotes
My Approvals shows each approver their own waiting steps with the requested date.
Anything written in special terms routes to the deal desk. A term the customer was promised that is not on the quote is a term the company has not agreed to, and the deal desk sees every one that is.
Expiry is automatic and Expiring Quotes shows the rep what is about to lapse, so a stale proposal is not still counted at proposal stage.
| Stage | Records | Effect |
|---|---|---|
| 1 Draft | QuotesQuoteLines | none |
| 2 Submit | QuotesPriceBookEntriesUsersApprovalThresholds | approval flag set |
| 3 Route | QuoteApprovals | approvers notified in sequence |
| 4 Approve | QuoteApprovalsQuotes | approved or returned |
| 5 Send | QuotesOpportunities | opportunity values updated |
| 6 Answer | Quotes | accepted version ready for the bookings check |
Blended discount by rep, product family and deal size, with the approvals requested, how each was decided and the quotes that expired unanswered.
Approval conditions.
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 |
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
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
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.