Glime for the deal desk
You are the human the policy runs through. Glime turns that from an inbox you triage into a queue that arrives with the numbers already attached.
What breaks today
Requests arrive in four places
Email, chat, a tagged comment, and someone stopping by. There is no single queue, so "what is waiting on me" is a question you answer by searching rather than by looking.
You approve a number that has already moved
The quote you reviewed on Tuesday is not the quote that went out on Wednesday. Without version pinning, your approval silently transfers to a deal you never saw.
Context has to be assembled every time
The discount is in the request, the margin is in a spreadsheet, the history is in the CRM, and the reason is in somebody's head. Every decision starts with ten minutes of gathering.
What Glime does about it
- One inbox — the quotes waiting on your decision, scoped to your role, with the discount, blended margin, and stated reason on the same screen.
- Approval pinned to a version — editing a quote that is pending resets its chain, so you never carry a decision forward onto numbers you did not review.
- Ordered steps — you cannot be skipped by someone routing straight to Finance, and you cannot accidentally decide a step whose predecessor is still open.
- Denials that teach — a rejection carries a reason back onto the record, so the resubmission is a different quote rather than the same one an hour later.
- Every decision recorded for you — you do not keep the log; the audit trail does, with your name and the timestamp on it.
How the approval ladder works → · Draft your own policy →
At a 50–200 person company the deal desk is one person
Usually the sales ops manager doing it between forecast reviews, occasionally the CFO on Tuesdays. Everything above still applies, with one change of emphasis: with a single approver per rung, queue depth is not a volume problem, it is an availability problem — and the in-app-only notification limit below is felt harder in this seat than anywhere else in the product.
Take a 120-person SaaS company: fourteen reps, about 60 quotes a month, two thirds of them carrying some discount, and a median discount of 8% on the ones that do. Put those numbers through the model the policy builder prints on its own page and the default 10/20/35/50 ladder routes roughly 10 quotes a month to a Sales Manager, 5 to a Director, and 1 to Finance, refusing less than one at the ceiling — which leaves about 44 that never touch an approver at all. Modelled, not measured: put your own quote volume and median discount into the builder and the estimate changes with them.
- The workload is about four decisions a week — at the volumes modelled above, roughly 16 quotes a month route to somebody. One person absorbs that easily. What hurts is the two days a quote waits while that person is at a conference.
- The fix for a backed-up rung is a second person with the role, not a higher threshold — approval authority follows the role, so adding an approver takes a settings change and costs nothing in policy.
- Until approval notifications ship, put the inbox in a routine — first thing and after lunch is what pilot teams do. It is a workaround and we would rather name it than let a rep discover it.
What you can measure in the first month
| Metric | Why it is the one to watch |
|---|---|
| Median time-to-decision | Yours specifically. It is the number that decides whether reps route around you. |
| Queue depth by rung | Where quotes actually pile up — usually one rung, and usually because it has one approver. |
| Resubmission rate | How often a denied quote comes back. High means the reasons are not landing. |
| Requests below the first threshold | Quotes routed to you that policy says never needed to be. Pure recoverable time. |
What Glime will not do for you
Notifications are in-app today. There is no email or Slack delivery of an approval request yet, so a rung with a single, busy approver still depends on that person opening the app — a real limitation at the moment, and the one we would fix first. The Slack and Teams pages describe the intended shape.
Questions deal desk and sales ops managers ask
Can we have more than one approver at a rung?
Yes — approval authority follows the role, so anyone holding that role in the workspace can decide the step. That is the fix for the queue-depth problem: a rung that backs up usually needs a second person with the role, not a lower threshold.
What happens to a quote we deny?
It returns to the rep as a draft with the denial reason attached, and the whole exchange stays on the record. If they reprice and resubmit, the chain starts again from the rung the new discount requires — which may be a lower one, if they came down.
Where to go next
- Discount approval workflows — the ladder, the refusals, and the audit trail in detail.
- Discount policy builder — set your thresholds and take the written policy away with you.
- ROI calculator — what the current process costs, in a number you can forward.
- Glime vs the alternatives — scored on the same eight dimensions, including where they win.
See it in the sandbox
The product is the demo. Open a live, read-only workspace — no signup — or start a free 14-day trial.