Skip down to the research record

Hold deals at $10,000 or more: 8 steps to set the rule

Quota Forecast Editorial Team · Published · 13 min read

A deal value threshold sends any deal at or above a set dollar amount to a manager for sign-off before a proposal goes out. A rep builds a quote, sends it to the buyer, and only later does the manager see that the price is too low, the terms are unusual, or the discount is bigger than anyone intended. By then the buyer has the number, and fixing it is awkward for everyone.

Key takeaways

  • Decide which deal value counts, such as first-year value, total contract value, or monthly recurring value, and write it down.
  • Pick one dollar amount and hold deals at or above it for manager sign-off before any proposal goes out.
  • Name a primary approver and a backup, with a response window the whole team knows.
  • Give the approver a short checklist to work through for every held deal.
  • Review the threshold after each review cycle, and record every change with its reason.

Why a dollar threshold works

A deal value threshold solves this with one clear rule. You pick a dollar amount. Deals below it move on the rep's own authority. The rule is easy to explain, easy to check, and easy to automate.

This post uses $10,000 as the example because the title does. It is not a recommendation for your team. A business selling small monthly subscriptions and one selling large multi-year contracts should choose very different numbers. The right figure is the point where a mistake starts to cost real money, real margin, or real risk.

Nutshell's guide to sales automation includes a scene that will be familiar to many sales leaders: "Picture a sales manager with a 12-person team with one request for her CRM." The same guide describes the rule this post covers: "Deals over $10,000 take one path, everything else takes another, and nothing goes out until she signs off." (Nutshell, "Sales automation without an admin")

Decide what the threshold measures

Before you write the rule, settle what "deal value" means. Teams often argue about this later, after a large deal slips through or a small one gets held up for no good reason. Decide these points in advance:

  • Which number counts. Choose one: first-year value, total contract value, or monthly recurring value. Write down which one you use.
  • Before or after discount. Decide whether the threshold is checked against list price or the price the rep proposes.
  • Multi-year and add-on terms. Decide whether a multi-year contract is measured by its full length, and whether add-ons quoted in the same proposal count toward the same deal.
  • Split deals. Decide that related quotes for one buyer are added together, so a large purchase cannot be broken into smaller quotes to avoid review.

If your CRM stores weighted amounts, read the weighted deal amount rules before you choose the number.

Illustrative example: one buyer, two quotes

This example is illustrative and uses made-up figures. The $10,000 quote meets the threshold on its own. The $8,980 quote falls below it, but the split-deal rule counts related quotes to one buyer together, so it goes to review as well. Neither proposal leaves your team until the manager signs off.

Write the rule in plain words

A rule people can recite is a rule people follow. Write it as one sentence and put it where reps will see it every day:

> Any deal with a total contract value of $10,000 or more needs manager approval before a proposal is sent to the buyer. Deals below that amount may be sent by the rep once the standard checks are complete.

Then add three more sentences that answer the questions reps will ask: what counts as approval, who gives it, and what happens when the approver says no. Keep the answers short. Long policy documents get skipped.

Set up the two paths

Once the rule is written, build two paths. The first is the standard path for smaller deals. The rep follows the normal steps, checks the proposal against a short list, and sends it. The second is the review path for large deals. The deal goes into a queue for the manager, and the proposal stays in draft until the manager signs off.

The important detail is the word "until." Nothing about a review-path deal should leave your team before approval. That includes the first draft, a "quick look" price sheet, and an emailed PDF to a buyer who asked for numbers. If reps find a way around the queue, the threshold becomes a suggestion.

Name an approver and a backup

A rule that depends on one person fails the first time that person is on vacation, in meetings, or sick. Name a primary approver and a backup for every review queue. Make sure the backup can see the same deal records and has the same authority.

Agree on a response window too. Pick a length of time your team can keep, write it down, and track whether it is met. The exact window matters less than the fact that reps know how long to expect. If the window keeps slipping, that tells you the threshold is set too low for the number of approvers you have, or that the approver needs more support.

Explain the reason, not just the rule

Reps push back on a rule they don't understand, and they usually understand it faster when they know what it protects. Explain the threshold in terms of outcomes the team cares about: avoiding quotes with the wrong price, keeping discounts consistent, and making sure delivery commitments can be met. Show two or three real examples from your own history, with the names removed, where a review caught a problem. A rule backed by a story sticks better than one backed by a memo.

Also tell reps what the rule does not do. It does not mean their judgment is in doubt on small deals, and it does not give the manager a veto over every decision. It sets one checkpoint for one kind of deal. Written this way, the rule is easier to defend in a team meeting and easier to follow on a busy Friday.

Give the approver a checklist

Approval without criteria is a rubber stamp, and a rubber stamp is worse than no review, because it creates a false sense of safety. Give the approver a short checklist to work through for every deal. Useful items include:

  • Price and discount fall inside the policy for this product and customer type.
  • Scope matches what the buyer asked for and what the team can deliver.
  • Payment and renewal terms are the standard ones, or the exception is named and justified.
  • Contract terms come from the approved standard contract, and any changes are flagged for legal review.
  • The buyer is qualified: the right decision maker is involved and the need is documented.
  • Commitments outside the standard offer, such as custom delivery dates, are confirmed with the people who must deliver them.

The checklist should fit on one screen. If it takes longer than a few minutes for each deal, the approver will start skipping items. For a related list of checks on quoted amounts, see Quote approval checklist: 4 checks on quoted amounts.

Make the review a conversation

The review path works best when the approver asks questions instead of just reading the proposal. Start with the rep's reason for the deal: why this buyer, why this scope, and why this price. Then check the proposal against the checklist and talk through anything that falls outside it. A good review ends with one of three outcomes: approved as written, approved with named changes, or sent back with the reason recorded.

Keep the conversation short and specific. Ask about the buyer's timeline, the decision process, and any promises made in early calls. If a rep has to explain a number twice, the proposal probably needs work before it goes out. Reviews are also a good time for coaching, because the same questions come up across many deals and the answers help the whole team.

Make the rule part of the CRM

Manual review works for a handful of deals a month. Once volume grows, the rule should live in your CRM so the system routes deals and records decisions. The question is how much technical help you need to set that up.

Nutshell's guide compares several tools. Nutshell, Pipedrive, and Monday all let a manager build automations, and Nutshell includes sales automation from its Pro plan at $42 per month for each user, with free onboarding. HubSpot's full workflow builder requires its Professional plan at $90 per seat per month, plus a mandatory $1,500 onboarding fee. Salesforce typically requires a trained admin to build and maintain automation beyond basic defaults. (Nutshell, "Sales automation without an admin")

Two details matter here. The guide's prices are per month for each user or seat, billed annually, taken from each vendor's pricing page as of October 2026. Flow Builder has been Salesforce's only no-code automation tool since Salesforce retired Workflow Rules and Process Builder on December 31, 2025. (Nutshell, "Sales automation without an admin")

If a manager should be able to change the rule without filing a ticket, favor a tool where managers can build automations over one that needs a trained admin for every change. Check current prices and plan details on the vendor's pricing page before you buy, because they change.

Keep one source of truth

Xactly's guide to sales productivity says to operationalize go-to-market plans with a single source of truth for managing territories, people, opportunities, credits, and quotas. (Xactly, "What is Sales Productivity?") Apply the same idea to your approval rule. Store the threshold, the approver list, and the decision log in one place that the whole team uses, and make sure the CRM, the proposal tool, and any spreadsheet agree with it.

Set an owner for the number

Someone has to own the threshold, and the owner should not be whoever complains loudest. Often that is the sales leader, working with finance on margin and with legal on contract terms. Write down who owns the number, who can propose a change, and how changes are approved. A threshold that nobody owns drifts. Over time, reps learn that the number is out of date and start ignoring it.

Revisit the number when something material changes: a new pricing model, a new product line, a shift in typical deal size, or a change in how the company recognizes revenue. Each change is a reason to check the threshold, not automatically a reason to move it. Record each decision and the reason for it, so the next person can see why the number is where it is.

Handle renewals and deals in progress

Renewals raise a question the threshold must answer. A renewal can cross the number even when the original deal did not, or it can stay under the number while the customer adds seats. Decide in advance whether renewals are reviewed on their own value, on the value of the expiring contract, or only when the terms change. Write the answer into the rule so reps do not have to guess at renewal time.

Deals already in progress need a clear cutoff too. Choose a date on which the rule starts to apply, and state whether deals with a proposal already sent are grandfathered. A deal that was in draft on the day the rule started is usually simplest to route through review. Tell reps the cutoff in writing, and answer questions about specific deals quickly so the new rule does not stall the pipeline.

Avoid the common failures

  • Threshold too low. If many routine deals wait, reps will slow down, route around the rule, or stop bringing you the middle-sized deals that need help most. Raise the number or add a faster lane.
  • Threshold too high. If large deals slip through unreviewed, the number sits above the point where mistakes start to cost you. Look back at recent deals where margin was lost or terms caused trouble, and check where those deals sat against the number.
  • Split deals. Reps may divide one purchase into several quotes. Count related quotes together, as described above.
  • Edits after approval. A change to price, scope, or terms after sign-off sends the deal back for review. An approved proposal is approved as written, not as a starting point.
  • Silent exceptions. A rep who wants an exception asks in the same queue, and the answer is recorded in the deal record. Exceptions you cannot see cannot be managed.
  • Approval with no record. Log who approved, when, and what they checked. The record helps with coaching and with any later dispute about terms. For a similar record of field changes, see Close date change log: why the date moved.

Answer the objections reps will raise

Expect a few objections in the first month, and prepare short answers. The answer is that the review is for the deals where a mistake is most expensive, and a clean deal should pass in a short conversation. "The manager is slow" is a fair complaint if the response window is not kept, so track it and fix the cause, whether that is capacity or the window itself.

"Why can't I send a draft to the buyer for a quick look?" is another common question. Explain that a draft sent to a buyer is a proposal in the buyer's eyes, and that the rule exists so that the first number the buyer sees has been checked. "The threshold is arbitrary" is sometimes true of any single number. Answer it by pointing to the reason for the number and by offering to review it at the next scheduled check.

Measure whether the rule works

Track a small set of numbers over a full review cycle: how many deals were held for review, how long they waited, how often the approver changed the price or terms, how many exceptions were requested and granted, and how often a held deal was later lost for reasons tied to the wait. Reviewing these numbers each cycle tells you whether to move the threshold up, down, or leave it alone. Avoid changing the number too often, because reps need time to learn the rule.

Launch checklist

  1. Define deal value and write down which number counts.
  2. Choose the threshold and write the rule in one sentence.
  3. Build the review path so nothing goes out before sign-off.
  4. Name a primary approver and a backup, and agree on a response window.
  5. Give the approver a short checklist.
  6. Set up the rule in your CRM, and check current pricing for that tool.
  7. Tell the team when the rule starts, and what happens to deals already in progress.
  8. Review the numbers after one review cycle.

Start small and adjust

A threshold is not a sign that you distrust your reps. It is a way to put your attention where a mistake would cost the most, and to let everything else move without waiting. Start with a number you can defend, write the rule in plain words, and adjust it with data.

Your next step today

Write down which deal value your team will measure, and draft the threshold rule in one sentence. Send both to your sales manager for a decision this week.

Frequently asked questions

Does a deal exactly at the threshold go to review?

Yes. The rule covers deals at or above the amount, so a deal equal to the threshold needs approval before a proposal goes out.

Who should approve held deals?

A named primary approver, often the sales leader, with a backup who can see the same deal records and has the same authority.

How should renewals be handled?

Decide it in advance and write it into the rule: renewals can be reviewed on their own value, on the value of the expiring contract, or only when the terms change.

Do I need a CRM to run this rule?

No. Manual review works for a handful of deals a month, and a CRM becomes worth setting up as volume grows.

Sources