Your vendor SLAs are buried in 18 months of email. That's where the leakage is.

Pull up the contract with your most important hosting provider. Find the service level commitments. Now find the last six months of incidents where they failed to meet those commitments. The first part takes a minute. The second part is, for almost every SME, effectively impossible, because the evidence of those incidents is scattered across two hundred email threads, three Slack channels, and the memories of two people on your team.

If you cannot easily compare what was promised against what was delivered, you cannot enforce SLAs. And if you cannot enforce SLAs, the suppliers know it, and your contracts effectively don't exist. The thing on paper is a fiction. The real relationship is whatever the supplier feels like delivering.

This is not a rare situation. It is the default for SMEs. And it is one of the most direct cost leaks in the entire procurement function.

The asymmetry that costs you

Your suppliers track their SLAs. They have systems for it. They know exactly how many minutes of downtime they had this quarter, exactly what their support response time has been, exactly how many tickets breached the agreed threshold.

You don't track any of this. Your evidence of SLA performance is in your inbox — the emails where someone reported the outage, the support thread where the response was slow, the message where the quality issue was acknowledged. None of it is consolidated, none of it is timestamped against the SLA thresholds, none of it is queryable.

The result is that when an SLA conversation comes up, your supplier knows the numbers and you don't. The negotiating position is wildly asymmetric. Your only option is to take their word for it, or to spend a week reconstructing the evidence manually — which, for most SMEs, is not worth it for any individual incident.

So the SLAs go unenforced. The penalty clauses are never triggered. The credits you were entitled to are never claimed. And over a year, you are quietly paying for service quality you contractually should not have had to.

Where the SLA evidence actually lives

If you reconstructed the last twelve months of any major supplier relationship, the evidence of SLA performance is distributed across roughly four surfaces.

The contract itself sets the thresholds. Response time within X hours. Uptime above Y percent. Quality criteria Z. This is the easy part to find, though it is often in a PDF buried in a Drive folder.

The incidents themselves are in your team's communications. Email threads reporting issues. Slack messages from frustrated team members. Tickets opened with the supplier. Internal discussions about how to handle a breach.

The supplier's responses are in their email replies, their ticket updates, their post-incident communications. The pattern of how quickly they responded, how completely they addressed the issue, how often they escalated.

The downstream effects are in your team's reaction — the work that had to be redone, the client-facing apologies that had to be sent, the time lost to working around the supplier failure.

None of these four are individually hidden. They are all there, in your systems. What is missing is the layer that pulls them together into "supplier X's actual SLA performance over the last quarter, compared to the contract".

"But we'd have to do this manually for every supplier"

Yes, and that is exactly why it doesn't get done. The manual cost per supplier is high enough that no individual SME does it for any but the largest contracts, and even then, only when there is already a fight underway.

The economics flip when the consolidation is automatic. If your communications are continuously structured by counterparty — every email, ticket, and chat thread relating to supplier X consolidated into one queryable view — then "show me SLA performance for supplier X over the past quarter" becomes a single query, not a week of work.

This is the practical case for treating supplier communications as a structured operational record, not as transactional clutter. You are not changing what you record. You are changing what you can read.

The conversation with the supplier changes

The moment you can show a supplier "here are the eleven incidents from the last six months, here are the response times for each, here is the contractual threshold, here is the gap" — the relationship reshapes.

In some cases, the supplier already knew and was hoping you wouldn't. In some cases, they didn't know and are genuinely surprised, and you have just earned a meaningful improvement in service without having to switch providers. In some cases, the contract triggers credits or penalties that you can now actually claim.

In all cases, you are no longer the side without evidence. The asymmetry that was costing you closes. The supplier knows you are watching. Compliance with the SLA rises sharply, not because you have switched providers, but because the cost of non-compliance has stopped being zero.

The procurement function rewires

A second-order effect is that procurement at your company stops being a one-shot event (negotiate the contract, sign it, forget it) and becomes a continuous function. The contract is alive. Its terms are being checked against actual performance, week by week. When renewal time comes, you have data, not impressions, on which to base your decision.

This is what large enterprises do with dedicated procurement teams. Most SMEs cannot afford a dedicated procurement function and consequently operate in the "negotiate-and-forget" mode. The point of consolidating supplier communications is that you can have the procurement function's outputs without the procurement function's headcount.

The leakage estimate

For a typical SME of twenty to fifty people, with somewhere between fifteen and forty active supplier relationships, the leakage from unenforced SLAs typically runs to several percent of total supplier spend. Not because suppliers are deliberately gouging you. Because, in the absence of enforcement, service quality drifts down to whatever the supplier finds convenient, and you absorb the gap.

Several percent of supplier spend is, at most SMEs, a five-to-six-figure annual loss. It is one of the most under-visible cost categories in the business. And it is one of the few that can be substantially closed without changing any supplier, any contract, or any process — only by changing what you can read.

The contract is only as real as your ability to enforce it

Every SLA conversation eventually reduces to this. The supplier knows whether you can enforce. Their behavior adjusts accordingly. The contract on paper is a starting position. The contract in practice is determined by the asymmetry of evidence.

Closing that asymmetry is not a procurement project. It is an information project. The data is already in your inbox. The only question is whether you can read it. When you can, the contracts you already signed start delivering the value they were supposed to. The leakage closes. The negotiating position changes. The supplier behaves.

Eighteen months of email is a lot of evidence. It is yours. Use it.