CASE STUDIES

Four renewals. Four different ways they bite.

Anonymised, but not invented: these are the situations we ran by hand for clients across twenty years in the SA channel, told the way the platform now handles them. The numbers are each situation's own arithmetic.

A Johannesburg manufacturing company

The renewal that nearly bought 42 licences for nobody

A 240-seat Microsoft agreement, an annual commit, and a business that had quietly shrunk: a plant consolidation and a project wind-down had taken 42 people out over eighteen months. Nobody had profiled seats against the agreement, because the renewal date lived in one manager's calendar and the change window, the deadline that actually matters, lived nowhere at all.

The five-month notification forced the question early. A seat audit took two afternoons, the reduction was lodged three weeks before the change window closed, and the agreement renewed at 198 seats instead of 240.

At R5 200 per seat per year, that is R218 400 that would have been paid, for a full year, for nobody. The work involved was trivial. The only hard part was ever being asked in time.

R218 400

a year, not spent on empty seats

What did the work

First notification five months out
Reminders timed to the change window, not the renewal date
A named owner who can't quietly go on leave

A national retailer, head office in Cape Town

Thirty firewalls, eight renewal dates, one decision

Branches were opened, hardware was bought when each site needed it, and the security estate grew the way estates actually grow: thirty firewalls spread across eight renewal cohorts, each with its own quote cycle, its own PO, its own chance to slip. Renewal admin ran most of the year, and the unit pricing showed exactly how little leverage eight small deals carry.

The estate was given a master renewal date. At each device's anniversary, the renewal notification carried one extra instruction: co-term this line to the master. Within a cycle, the estate had converged.

One renewal event a year. One consolidated quote at thirty-device volume instead of eight fragments. One notice window to defend rather than eight to remember. The pricing improved the way volume pricing does, and the risk of a quiet gap in cover on any single device fell away with the calendar clutter.

8 → 1

renewal events a year on the firewall estate

What did the work

Master renewal date on every obligation
Category windows: the security estate as one working view
Quote, PO and invoice filed against each line by design

A Durban logistics group

The exchange rate their suppliers hoped nobody would check

Most of the group's software and hardware was priced in dollars and paid in rand, across fourteen suppliers and four divisions. Every quote arrived with an exchange rate already baked in, and with no spot rate on the buyer's side of the table, every rate was accepted as given.

Revaluing the forward book daily at spot changed the conversation. On the day a quote landed, the true rand cost of the line sat next to the supplier's number, and the difference had nowhere to hide. Quotes were challenged line by line; the padding averaged near four percent, roughly the margin a supplier holds to protect themselves through a slow PO cycle, and keeps whenever the rand moves their way.

Budget season changed shape too. The live year snapshotted into a budget window at a prescribed rate, divisional allocations fell out of the quantities, and the annual three-week spreadsheet rebuild became an afternoon with an export at the end of it.

≈4%

average buffer found in dollar-priced quotes

What did the work

Daily spot revaluation on every dollar-priced line
Quote-versus-spot comparison the day the quote lands
Budget window with per-division allocation built in

A Gauteng financial-services firm

The audit that was answered from the record, not from memory

The obligations that scare a financial-services business are rarely the big ones. They are the recurring, evidential ones: the ISO surveillance audit, the insurer's annual questionnaire, the failover tests everyone assumes happen. Here they lived with one operations manager, and when that manager resigned mid-year, the calendar left with them.

Every recurring obligation had already been captured with an owner and an escalation contact, so the handover was the platform's problem, not the business's. Stalled items escalated within their windows; nothing waited for someone to remember what the previous person used to do.

When the surveillance audit came, the evidence was already filed where the work happened: failover tests with dates, results and the ISP thread attached, backup restore tests with sign-offs, policy reviews with recorded decisions. The auditor's continuity questions were answered from the record in an afternoon. The insurer's questionnaire, largely from the same screens. What the firm actually bought was the quiet confidence that none of this depends on any one person's memory.

audit findings on continuity evidence

What did the work

Owner and escalation contact on every obligation
Failover and restore tests as dated, evidenced obligations
An audit trail of who did what, and when

The fifth case study should be yours.

Book a demo