7 Hidden Signals Your SaaS Vendor is Dying

1Job Postings Vanish Overnight

If a SaaS company is hiring normally, they're investing in growth. If hiring suddenly stops or reverses—you'll see job postings deleted from their careers page and LinkedIn.

Why it matters: Job posts don't get removed by accident. A team freezing headcount is preparing for cuts. Worse, if they had open roles and quietly delete them, it signals layoffs are coming. When hiring freezes, everything else freezes with it.

What to do: Check their careers page monthly. Set a Google Alert for their company name + "jobs" or "hiring." If posts vanish or go stale (same roles for 6+ months), it's a yellow flag.

2Changelog Goes Silent for 60+ Days

Active SaaS teams publish updates every 1-4 weeks. A changelog that hasn't updated in 2 months usually means one of three things: the product is in maintenance mode, the team is too small to ship, or they've redirected everyone to a dying product line.

Why it matters: If they stop shipping features, they're not acquiring new customers. If they're not acquiring customers, burn rate becomes the only metric that matters—and they're watching it.

What to do: Visit their changelog or blog monthly. If you see radio silence for 8+ weeks, especially after regular updates, escalate to your account team. Ask directly: "What's your product roadmap for Q2?" If they get vague, it's a signal.

3GitHub Activity Flatlines or Slows Dramatically

If your vendor is open-source or posts code publicly, their GitHub repository tells a story. A drop in commit frequency—from daily to weekly to nothing—signals engineering bandwidth is being cut or redirected.

Even closed-source vendors often have internal GitHub activity that maps to their public API versions. If the API version hasn't changed in 6+ months while you're on an older version, they've stopped developing.

Why it matters: Code doesn't maintain itself. If commits slow to a crawl, security patches stop coming. Bugs don't get fixed. Technical debt grows until the system becomes unmaintainable.

What to do: Check their GitHub (if public) monthly. Use GitHub's insights tab to see commit frequency over 3-6 months. If you're their customer, ask about their API version release schedule. Radio silence is bad.

4SSL Certificate Approaching Expiry (or Already Expired)

SSL certificates need renewal every 1-2 years. A vendor that lets their certificate expire—even once—has a serious ops problem. It means nobody's watching the infrastructure. No monitoring alerts, no automation, no process.

Why it matters: An expired cert is fixable in 10 minutes. If it happened, they weren't paying attention. If it was down for more than an hour, their ops team either doesn't exist or isn't responsive. Neither is good.

What to do: Use online SSL checkers monthly (ssllabs.com, sslmate.com). Note the expiry date. If you see it renewed close to the deadline or—worse—it expired and got re-issued after downtime, document it. One incident might be bad luck; a pattern is bad ops.

5Status Page Becomes Unreliable or Goes Dark

A status page that stops updating—or updates hours after an outage—signals that either nobody's monitoring their infrastructure or communication is deprioritized. Both are red flags.

Worse: status pages that show unrealistic uptimes while users report constant issues. If the page says 99.9% uptime but your team experienced 3 hours downtime last week, they're either not monitoring or not being honest.

Why it matters: A company that stops monitoring their infrastructure or stops being transparent about it isn't in control of their service anymore. This is the moment before things get really bad.

What to do: Subscribe to their status page. When you experience issues, check if they've been reported. If you're always finding outages before they do, their monitoring is broken. Escalate to your account team.

6Pricing Changes Without Value Add

A price increase that comes with new features? Normal. A price increase that comes with nothing—or worse, feature cuts—is a desperate move.

Red flags: 20-50% price hikes with no feature additions, tier consolidation (fewer plans), or "features moving to Enterprise." These are moves a dying company makes when they need cash *now*, not next quarter.

Why it matters: Healthy companies invest in their product before raising prices. Dying companies raise prices to slow burn rate. If you get a price hike with no value, they're buying time, not building.

What to do: Track price changes. Compare what you're paying vs. what you're getting. If it's gone up 30% with fewer features, start seriously evaluating alternatives. This is often a 6-12 month warning before shutdown.

7Key Team Members Start Leaving (CTO, Co-Founder, Engineering Lead)

People know something before the market does. If the CTO leaves, if a co-founder exits "for personal reasons," if your account manager gets ghosted—that's signal. LinkedIn profile updates and Glassdoor reviews often reveal departures before official announcements.

Worst-case signal: a sudden wave of departures without explanation, or departing employees giving vague reasons ("pursuing new opportunities") while the company says "reorganizing to focus on core products."

Why it matters: Founding team members don't leave healthy companies. Technical leaders don't jump ship unless they see the iceberg. When multiple people leave the same ship in a short span, it's not coincidence.

What to do: Follow key executives on LinkedIn. Set Google Alerts for them. Check Glassdoor reviews monthly. If you see a cluster of departures, reach out to other customers. You probably aren't the only one concerned.