Layoffs directly impact the quality of technical support and product development. If you're running their SASE/SD-WAN in production, you should be concerned. Reduced headcount means longer ticket resolution times, less experienced engineers on call, and slower feature/security patches.
From a purely operational risk standpoint:
* **Review your contract SLA terms now.** What are your guaranteed response times? Financial penalties for missing them are negligible compared to business downtime.
* **Escalate renewal discussions.** Lock in longer-term pricing if you must stay, but push for stronger exit clauses.
* **Start a parallel PoC with another vendor.** This is a standard risk mitigation step. Your procurement cycle is now your contingency timeline.
Has anyone with a current support contract seen a measurable degradation in MTTR or ticket escalation quality in the last 60 days? Concrete numbers are more useful than speculation.
cost per transaction is the only metric
This is the right way to think about it. The SLA review is key, but a lot of those contracts have clever loopholes. For example, they might define "response" as an automated ticket acknowledgement, not an engineer actually looking at your case. The financial penalties are almost always capped, too, which makes them toothless for any real outage.
I haven't seen MTTR numbers specifically, but we've had a weird pattern lately where our tickets get bounced between "Support" and "Technical Services" a few more times before landing with someone who can actually help. That's an indirect metric that points to internal strain.
Have you looked at whether your contract guarantees support engineer *tier* levels? That's a specific clause some of our larger deals had, and it might be your only lever.
Spreadsheets > marketing slides.
You're absolutely right about the ticket ping-pong being a canary in the coal mine. We saw that exact pattern with another vendor right before their support cratered. "Support" just became a triage queue that delayed the actual troubleshooting for days.
That mention of guaranteed support tiers is gold. We had to fight for that clause, but it specified that our Severity 1 issues had to be assigned to a Tier 3 or higher engineer within the response time. Without it, "response" meant exactly what you said - an auto-reply from a system, or a Tier 1 person reading from a script. The problem is, if they lay off senior staff, they may breach that clause immediately, and your only recourse is a contractual dispute which takes forever.
Has your legal team ever actually invoked the penalty clause? Ours always called it a "relationship tax" - the credit was so small it was never worth the strain to collect.
buyer beware, but buy smart
Yeah, that "relationship tax" framing is so real. We saw the same thing - a paltry credit that wasn't worth the political capital to chase.
It makes me wonder if the real action, legally, isn't the penalty clause but the *breach of contract* itself. If they can't staff to the guaranteed tier levels, that's a material breach, right? Could that be grounds to exit the contract entirely without penalty, maybe even get some costs back? I've never seen a team push for that, everyone just grits their teeth through the degraded service.
Has anyone successfully used a breach of service level to actually get out of a contract early?