Sales deal approvals: what to automate, what to route, and to whom

Most sales-led companies get approvals wrong on the first attempt.

Sometimes, the process is too thin. A deal moves fast, everyone is pleased, and the problem surfaces weeks later when someone in finance opens the contract and finds payment terms nobody signed off on, a discount that puts the account underwater, or a services commitment the delivery team has no capacity to honor. The customer has already signed, so the concessions are locked in. 

Other times, the process is too heavy. A rep puts together an ordinary deal and then waits, because the workflow demands a sign-off the business didn’t need. The approver is in back-to-back meetings, the request sits for two days, and by the time it clears, the customer who was ready to move on Tuesday has moved on to something else. 

Other times, the process is too thin. A deal moves fast, everyone is pleased, and the problem surfaces weeks later when someone in finance opens the contract and finds payment terms nobody signed off on, a discount that puts the account underwater, or a services commitment the delivery team has no capacity to honor. The customer has already signed, so the concessions are locked in. 

Both failures trace back to the same issue. Nobody defined, ahead of time, which deals need a human to look at them and which ones do not. A proactively defined approval process implemented with the right tools and automation prevents this.

The core principle

Deals defined as standard should move automatically towards signature, no approval required. Anything that deviates from standard should be routed to the person who owns the business risk.

Nearly all of the work in building an approval process is turning those two sentences into specifics. A deal that stays inside your approved products, standard pricing, standard terms, and standard paper does not need anyone’s permission to proceed, and should go out on its own. A deal that breaks from that baseline in a way that creates a meaningful economic, contractual, delivery, or operational risk should go to the function(s) accountable for that specific risk, and to no one else. If there's legitimate disagreement between the seller and the function that owns the risk, it gets escalated to the COO. It should, because the function that owns the risk has an incentive to say no to avoid the risk, and the seller has an incentive to say yes because they want to get the deal done. There's legitimate tension that has to be resolved in exceptional cases. What follows is an elaboration of those ideas: how to define the baseline, how to decide what counts as a meaningful departure, and how to route each departure to the right owner without convening a committee.

What counts as a standard deal?

Defining the standard deal is the most important step. Every approval rule is a comparison against a baseline, so if the baseline is vague, the comparison is vague, and almost every deal starts to look like it might be an exception, requiring an approval. 

Start by documenting the standard deal definition in plain terms. For most sales-led B2B companies it covers a familiar set of things: the products and packaging a rep is cleared to sell, the price or discount range a rep can offer without asking anyone, the contract duration you treat as normal, the payment terms and billing schedule you bill against by default, and the contract template or pre-approved fallback language your legal team has already blessed. It also covers what a standard deal does not contain, which is usually any custom product or roadmap commitment and any unusual implementation requirement.

A deal that fits every part of that description should reach the customer without requiring approval from anyone. The faster ordinary deals pass through untouched, the faster the deal moves because the quote gets to the prospect faster for signature before they go off and evaluate a competitor, and the more of your reviewers’ attention is left for the deals that call for judgment. 

Make the standard something a rep can see

Document the standard deal definition in your quoting tool as well as in your sales enablement materials, and write it precisely enough that a rep can look at their own quote and know, without asking, whether it qualifies. “A small discount” is not precise enough to act on. “Up to ten percent, annual term, invoiced up front, Net 30, our paper” is. When the standard deal is clearly defined, reps will opt to use the fast path with confidence, and the only deals that reach your reviewers are the true exceptions.

What should move on its own, and what should route?

Once a baseline exists, every deviation from it requires a judgement call.  Something about the deal requires a person to weigh a tradeoff and decide whether the company is willing to accept it. A fifteen percent discount, a request for Net 60 in place of Net 30, a custom statement of work with a fixed fee: none of these has an obviously correct answer, and someone has to look at the deal specifics and decide. These belong in an approval queue.

Who owns each risk?

When a deal does need a decision, it should go to the function that will have to live with the consequence. One pitfall is routing by seniority rather than accountability, where anything unusual floats up to whoever is most senior regardless of whether the question is theirs to answer. Another pitfall is the standing committee, where an exception goes to a group and no single person is actually on the hook for the outcome. 

The alternative is to map each kind of risk to the function that owns it. Pricing and discounts sit with Sales. Commercial structure and the interpretation of your own policy sit with Legal. Margin, payment terms, and financial concessions sit with finance. Contract language sits with Legal. Product features and roadmap promises sit with Product or Engineering. Implementation scope and delivery sit with Services. Security commitments and questionnaires sit with Security. Booking completeness and downstream readiness sit with billing. In each case the approver is the person who will answer for the result if the concession goes badly, which is precisely the judgment you want on the decision. If there is a disagreement between two parties, then it should be escalated to a senior leader.

Anyone who only needs to know that a deal happened should be told about it, not handed the power to hold it up. Every additional approver you attach to a deal adds another point where it can stall, and keeping someone informed does not require giving them a veto.

‍

How it comes together on a real deal

Take a standard deal. A rep builds a quote at list price, on standard terms, using standard paper. Because it matches the standard deal in every respect, it goes out with no approval at all. The customer comes back asking for two things: an eighteen percent discount and Net 45 payment terms. First, the Account Executive should try to negotiate for the best terms possible for your business.  Once they have, they should take those terms back to the teams they represent. If we are still looking at a discount and payment terms, those are two separate departures from standard, owned by two different functions, so they route independently and at the same time, the discount to the sales manager and the terms to finance, and both hold the revised quote until they clear. Legal is never involved, because the contract language never changed and there is nothing for legal to weigh in on.

That is how approvals should work. The deal reached exactly two people, each of whom answered one question that was theirs to answer, and every other function was left alone. Apply the same discipline across a full pipeline and the effect compounds. Standard deals move at full speed, exceptions get real high quality scrutiny from the people equipped to give it, and the review load stays concentrated where it belongs instead of being spread thinly across every deal in the funnel.

Frequently asked questions

What is a “standard deal”?

A deal that stays inside your approved products and packaging, your standard pricing or an in-range discount, your standard duration, your standard payment and billing terms, and your standard paper, with no custom product commitments or unusual implementation. A deal that matches all of that should proceed with no approvals required.

Which deals should move forward without any approvals required?

Any deal that fits the “standard deal” definition in full. If nothing about it departs from the baseline, there is no tradeoff for an approver to weigh, so it should reach the customer on its own.

Who should own a deal approval decision?

The single function accountable for the risk the deal creates: sales leadership for discount, finance for payment terms and margin, legal for contract language, product or engineering for roadmap commitments, and so on. Route to a role rather than a named person, and never to a standing committee.

What is the difference between an approval and a validation check?

An approval is a judgment call, where someone weighs a tradeoff such as a deep discount or Net 60. A validation check is a policy check for missing or incorrect information, such as a blank billing contact. The first routes to an owner for a decision; the second simply stops the deal until it is corrected.

Where to go next

Learn what approval rules to create, covered in which deals actually need approval before you send the quote. Then, read how to turn those triggers into rules that hold up without slowing deals down, covered in how to design approval rules that don’t slow deals down. Once the process is live, right-sizing approvals as you grow covers how much of it you actually need at each stage.

Turnstile  is a quote-to-cash system with robust approvals built in. The definition of a standard deal, the routing rules, and the gates all live in the same system that produces the quote, the order form, and the invoice, so an approved deal carries straight through from sign-off to booked without anyone re-entering the terms along the way. Approvals stop being a separate tool you have to wire into everything else and become part of how a deal moves.

‍