From spreadsheet to governed pricing: a 30-day rollout
Most quote-to-cash rollouts are sequenced backwards. They start with the catalog — the part that is measurable, tedious and safe — and reach the approval policy in week five, by which time the team has learned that the new tool is a data-entry chore. The policy is the part that changes how the company sells. It should go first.
What follows is the order we suggest, and the two numbers worth watching once it is running. None of it is Glime-specific until the last section.
Week one, day by day
Day 1 — write down the policy you already run
Including the parts nobody has written down. Not the policy in the handbook: the one that actually happens when a rep needs 22% at quarter end. Who says yes, how fast, and where the decision is recorded.
If this exercise ends with nobody able to say what today's limit is — that is the most common answer, and it is the finding. You do not have a discount policy that needs a tool; you have an undocumented practice that needs a decision first.
The policy builder drafts the wording and estimates how many of your quotes each threshold would route. It is free and it does not ask for an account.
Day 2 — import accounts, contacts, and your top twenty products
Not the whole catalog. Twenty products is enough to quote the deals you will close this month, and the long tail can arrive in month two without blocking anything. A catalog import is a week of work that nobody can feel; a working ladder is a day of work that changes what happens on the next deal.
Day 3 — turn on two rungs
A self-serve band, one manager band, and a ceiling. Add a director rung when you have a director who would genuinely decide differently from the manager. Each extra rung adds latency to exactly the deals already under time pressure, so start shallow — you can always deepen it in month two, and deepening a ladder is much easier than explaining why a rung was removed.
A note on the ceiling, because it is the rung people get wrong: a threshold routes a quote to a person, a ceiling is the discount past which no quote may be finalized by anyone. A ceiling with an override is just another threshold. Its entire value is that quarter-end pressure cannot move it.
Day 4 — put one real quote through it
A live deal, not a test record. Discount it past the self-serve limit, send it for approval, and have somebody else decide it. Either answer counts: the first refusal is usually the moment the team understands what changed.
This is the day the rollout either happens or quietly does not. A team that reaches day 4 and routes a real quote almost always keeps going; one that reaches day 4 still importing products usually does not.
Day 5 — tell the team, in one paragraph
What is self-serve, who approves what, and that denials come back with a reason. Governance nobody was told about reads as a system outage — the rep hits a wall they were not warned about, on a deal, in front of a customer. One paragraph in the channel they already read is enough.
Week 2 — watch two numbers
Self-serve share. The proportion of quotes that never needed an approver. If it is under about 70%, the first threshold is too tight: the deal desk becomes a queue and reps learn to route around the policy rather than through it. Raise the entry threshold — that is a fix, not a retreat.
Median approval latency, per rung. If one rung is slow, add a second person who holds that role. Do not lower the threshold: that trades a queueing problem you can fix for a governance gap you cannot see.
The first 30 days
Four moments worth putting in a calendar. The questions are more useful than the meetings.
| When | What happens | The question that matters |
|---|---|---|
| Day 1 | Setup | Who decides a discount today, and where does the decision get recorded? What is the first approval you would want to have happened here rather than in chat? |
| Day 7 | Ten-minute check | What would be different here if you had a full audit trail and an enforced margin floor by the end of the month? If the honest answer is "not much", the discounting problem is smaller than the one you are actually trying to solve — better to know now. |
| Day 14 | Working session | Has any quote been reviewed and approved yet? If not, ship one together, on the call. Do not leave it as homework — it is the step that never gets done alone. |
| Day 30 | Review | The four below. |
The day-30 review
- How many quotes were reviewed? More than five in a month means it is in the workflow. Fewer than three means it is not — and that is a question about how the team quotes, not a configuration to tweak.
- Did the ladder actually stop something? A quote that was caught, forwarded and decided is the moment the policy becomes load-bearing rather than decorative.
- What is the self-serve share? Under 70% means the first threshold is too tight. Fix the policy before the team concludes the tool is friction.
- What would make this obviously worth keeping next month? Ask it exactly like that, and write the answer down word for word.
What Glime does with this
The sequence above is tool-agnostic, but it is also the thing Glime is built around, so here is the specific version.
- Day 1 lives in the Quote Builder's approval policy. Bands, the ceiling, and the triggers that add a step for something a percentage cannot see — a margin floor, a long payment term, a deal size. The server refuses a policy no business could sell against: bands that do not climb, or a step held by a role that cannot approve.
- Day 4 is measured, not assumed. The workspace home shows a four-step ladder — limit set, approver invited, quote routed, decision recorded — read back off your own workspace rather than off a checklist somebody clicked. It also prints the three numbers from week two, so the day-30 review does not need a report to be built first.
- Approvals are decided by the server. Role-gated, in order, and a rep cannot approve their own quote. A hidden button is a courtesy; the control is the API refusing.
- The audit trail and the export are not gated by plan. Putting a security control or a customer's own data behind a paywall is a different decision from selling a feature, and we did not make it.
One honest caveat while you plan: approval notifications are in-app and by webhook. If your team lives in email for this, say so before you start — see the deal desk page, which says the same thing.
Run day 4 right now — open the sandbox
Keep reading
- The policy builder — draft day 1's wording and see the routing load each threshold would carry.
- Discount approvals — what the ladder does once it is on.
- The CPQ buyer's guide — if you are still choosing a tool rather than rolling one out.
- The ROI calculator — the benefit side, with its assumptions printed.