Ask five people at most SaaS companies "what discount can I give without asking?" and you'll get five answers. That gap is what a deal desk charter closes. It's the single document that says, in plain language, what the rules of engagement are on a negotiated deal — and it's the difference between guardrails everyone can see and guardrails that live in one busy operator's head.
What is a deal desk charter?
A deal desk charter — sometimes called a deal decision charter — is a one-page operating agreement for how your company approves non-standard deals. It answers four questions before any specific deal comes up: what triggers a review, who approves what, how fast each decision happens, and what "good" looks like for pricing and terms.
It is not a policy binder and not a tool. It's the shortest document that lets a rep, a manager, and a CFO reach the same call on the same deal. Run it longer than a page or two and it's too complicated to use under deadline pressure — which is the only time it matters.
Why write a charter down at all?
Every company already has approval rules. The problem is where they live — usually a mix of one leader's memory, a stale Slack thread, and whatever got approved on the last big deal. That works until volume climbs and the person who holds the rules gets busy. Writing the charter down does three things a mental model can't:
- It makes the fast path the governed path. Reps stop guessing and stop pinging Finance for the same answer; the deal that follows the charter moves faster than the one that routes around it.
- It removes the single point of failure. When the rules are on a page, a deal doesn't stall because one person is on a plane.
- It creates something you can improve. You can't refine a rule you never wrote down — a charter is an asset you tighten as your margins and market change.
What goes in a deal desk charter?
A working charter has five parts. Everything else is commentary.
| Section | What it defines | Why it matters |
|---|---|---|
| Trigger rules | What makes a deal "non-standard" and routes it to review | Tells the team what's normal vs. what needs a second set of eyes |
| Approval matrix | Which discount depth and term risk each role can approve | Removes the "who signs off on this?" scramble |
| Review SLA | How fast each tier gets a decision | Keeps governance from becoming a bottleneck |
| Standards | Your real discount ranges, standard terms, and non-negotiables | Defines "good" so approvals aren't reinvented each time |
| Escalation + owner | Who owns the charter and how exceptions get decided | Keeps the document alive and accountable |
What should trigger a deal desk review?
The charter's first job is to draw the line between a standard deal a rep just closes and a non-standard one that needs review. Too low and you review everything; too high and the deals that hurt slip through. A common starting set of triggers for B2B SaaS:
- Discount depth past a set threshold — for many teams, anything beyond 15%.
- Non-standard terms — net-60 or net-90 payment, custom SLAs, auto-renewal or termination changes, non-standard liability language.
- Deal size above the dollar amount where a mistake actually shows up in the numbers.
- Custom structure — multi-year ramps, usage commitments, pilots converting to paid.
Write these as bright lines, not vibes. "Route anything over 15% or with non-standard payment terms" is enforceable. "Route the big or weird ones" is not.
How should the approval matrix be structured?
The approval matrix is the part of the charter people actually use daily. It maps risk — discount depth plus term exposure — to the person who can approve it and the time they have to respond. A typical starting ladder, with the numbers adapted to your own margins:
| Discount / risk level | Approver | Turnaround |
|---|---|---|
| 0–15% | Rep or sales manager | Immediate |
| 16–30% | VP Sales + deal desk lead | Within 8 business hours |
| 30%+ or non-standard terms | CRO + CFO | Within 24 business hours, written rationale required |
Two rules keep a matrix honest: the highest-risk deals get the fewest, most senior approvers (a committee is slower and blurs accountability), and every tier carries an SLA (a ladder with no clock is one reps learn to skip). If you take one table from this post into your own charter, take this one.
How fast should the charter promise a decision?
Speed is what makes a charter get used. A slow review is worse than none — reps route around it and you're back to gut calls with no record. So the SLA belongs in writing next to each tier, and you measure whether you hit it. A rep should never have to choose between closing the deal and doing it right.
What does "good" look like — and who decides?
The last two sections are the ones companies skip and later regret. Standards spell out your discount ranges by segment, your standard payment and renewal terms, and the concessions you will and won't make — turning the charter from a routing map into a judgment guide the rep can read before they ask. Escalation and ownership name one accountable owner (not a committee) and say how genuine exceptions get decided when a deal fits no row. A charter is only as good as the last time someone maintained it.
Deal desk charter vs. discount policy vs. approval workflow
These three get used interchangeably, and they shouldn't be:
- A discount policy is one input to the charter — the specific discount-by-segment ranges that feed the "standards" section.
- An approval workflow is the charter in motion — the actual sequence a live deal follows through the matrix.
- The charter is the document that holds all of it together and makes it legible to the whole team.
The policy is a rule, the workflow is the path, and the charter is the map that ties them into one page. For the broader context, start with the pillar guide on what a deal desk is and treat the charter as its operating document.
A one-page deal desk charter template
Here's the skeleton. Fill each line with your own numbers and you have a v1 charter in an afternoon:
- Scope — one sentence on what this charter governs (non-standard deals).
- Triggers — the bright lines that route a deal to review.
- Approval matrix — the discount/risk → approver → SLA table.
- Standards — discount ranges by segment, standard terms, non-negotiables.
- Exceptions — how a deal that fits no row gets decided, and by whom.
- Owner + review date — who maintains it, and when it's next reviewed.
How do you keep a charter from going stale?
The failure mode of a good charter is age. Norms drift, you move upmarket, the market shifts, and the document quietly stops matching reality — so the team goes back to guessing. Two habits keep it alive: review it quarterly against what actually got approved (are exceptions clustering where the matrix should change?), and ground it in your own deal history rather than generic benchmarks. Your best guide to a defensible discount at a given deal size is the deals you've already signed.
That second habit is the hard one to do by hand — the history is scattered across old contracts, dead CRM fields, and people who've moved on. It's the exact job Precedent is built for: an AI-assisted fractional deal desk that stands up your charter and keeps every approval grounded in your own deal history, delivering a one-page review brief cited to comparable past deals before each deal is signed. It's the deal desk function itself, run for you — not a placeholder until you hire one.