Discount governance for a 50-person team: two managers, no deal desk
Almost everything written about discount approvals assumes a deal desk: a small team whose job is to read quotes, a finance partner with time to review them, and a VP who signs the big ones between board meetings. That is a fine description of a 500-person company. It is not what a 50-person company has.
What a 50-person company usually has is a VP of Sales who still carries a number, two front-line managers who close their own deals, and one finance lead who also runs payroll and the month-end close. Every one of them is an approver in theory, and every one of them has a day job that is not approving things. A ladder copied from an enterprise playbook will route quotes to people who are on a customer call, and the deals will wait.
So the design question changes. It is not "how many checks can we add?" It is "what is the smallest ladder that still stops the discounts we'd regret?"
Start from who is actually in the building
Write down, by name, everyone who could say yes to a discount today, and next to each name write how quickly they would realistically see a request. Not how quickly they should: how quickly they would. At this size you will usually end up with three answers: the managers (within a few hours), the person who owns the P&L (within a day), and nobody else.
That list is your ladder. Every rung has to be a role somebody on it holds, and every rung has to be held by at least one person who is reachable in the time a deal can wait.
Two rungs and a ceiling
For most teams this size, the policy that survives a quarter looks like this:
| Discount | Who decides | Why this person |
|---|---|---|
| Up to your self-serve limit | The rep, alone | Most quotes should never route (see below) |
| Above it, up to the second line | Either sales manager | Close to the deal and quick to answer |
| Above that, up to the ceiling | The P&L owner (VP, founder, or finance) | The only person who can trade margin for a logo |
| Above the ceiling | Nobody. The quote is refused | A number you'd turn down even on a deal you badly want |
Two details in that table do most of the work.
"Either sales manager," not "the rep's manager." Route the first rung to the role, not to a named person. With two people holding it, a request waits for whichever is free first, and one manager's holiday stops being the whole team's bottleneck. The most common reason small-team approvals feel slow is not too many rungs. It is one rung held by one person.
The ceiling is a refusal, not a third approver. At this size the P&L owner is usually also the person most eager to close the big logo, so a ceiling they can override will be overridden, and it will happen in the last week of the quarter. Pick the number in a calm month, and make it something the system refuses rather than something a person decides.
Put the self-serve limit where your reps already are
The single most common mistake is setting the first line below the discount your team already gives. Then every quote becomes a request, both managers spend their afternoons clicking approve, and reps start padding the opening number to leave room. We wrote a whole post on where thresholds should sit. The short version is to aim for at least 70% of quotes never routing anywhere. At 50 people that is not a nice-to-have. It is the difference between a policy and a second job for your managers.
The problem small teams hit first: approving your own quote
Enterprise playbooks barely mention this because a deal desk makes it impossible. In a small team it is the default. Your sales managers close deals too, and a manager's own 25% discount lands, by the ladder above, on the manager rung, which means them.
Decide the rule before it comes up: nobody approves a quote they raised. A manager's own discount goes to the other manager, or up a rung. It is a one-line rule, and it is the one that tends to get skipped when the policy lives in a document, because the person it constrains is the person who would have to notice it. If your tooling can't refuse a self-approval, write it into the policy anyway and check for it in the monthly review.
Name the cover before the holiday, not during it
With two managers and one P&L owner, somebody is always away: parental leave, a conference, the first week of August. Decide in advance who covers each rung while its holder is out, and have the request go straight to that person. The alternative, forwarding requests by hand as they pile up, is how a three-hour approval turns into a four-day one in exactly the week a competitor is also quoting.
What to leave out, for now
Triggers are powerful: route any deal over a size, any multi-year term, any non-standard payment terms. At 50 people, add at most one, and only when you can name a deal it would have caught last quarter. Each trigger is another way for a quote to land on a busy person, and the margin floor already catches most of what a size trigger would, because a deep discount on a thin line shows up there first.
Per-product ladders, regional bands and a separate finance review of every quote belong to a later stage of the company. When you need them, you'll know, because a specific deal will have got past you.
Two numbers to watch in the first month
- Self-serve share: the percentage of quotes that never routed. Below 70% means the first line is too tight.
- Median time to approve, per rung: if the manager rung is slow, check whether both managers actually hold the role before you touch the thresholds.
If both look healthy after a month, leave the policy alone for a quarter. The worst thing you can do to a small team's ladder is tune it every week, so that nobody remembers the current numbers.
Where Glime fits (and where it doesn't)
Everything above works as a written policy, and you should run it that way for a month before buying anything. That month tells you whether the ladder fits your people.
When you do want it enforced, Glime is built for exactly this ladder. On Starter a single approval step stands between a rep and a discount above the self-serve limit. The two-rung chain, triggers and named cover while an approver is away are Professional. A quote that needs two signatures on Starter is refused rather than quietly approved by the first person. In both, the server refuses a self-approval and refuses a step taken out of order, and every decision lands in the audit trail.