Every RFP scoring sheet I've seen weights features about ten times heavier than vendor survival. The archive says that's backwards. Features converge within a category in a couple of release cycles; survival doesn't. And February — contract and RFP season, when half the logistics teams in North Texas are scoring vendor responses between winter dock drills — is exactly the month to study the platforms that aren't around to respond anymore.
So let's do a Then & Now. Two stories, one lesson.
Then: Temando. Temando was an Australian shipping-software company — a genuine contender in its market, well funded, well covered, the kind of name that showed up on shortlists with a strong demo and a confident roadmap. It later sold a majority stake to a large global mailing-technology group, and after a stretch under that ownership, it was shut down. SmartCompany covered the shutdown among the era's notable Australian startup closures. The roadmap slides didn't survive; the article did.
Here's what matters for your scoring sheet: the shippers running on Temando didn't do anything wrong by the feature columns. The product worked. The references checked out. What they bought, without a column for it, was a dependency on someone else's corporate strategy — and when the strategy changed, every one of those shippers inherited an unplanned migration on a deadline they didn't set. A forced migration is the most expensive project in shipping software, partly because it's the only one where the timeline belongs entirely to somebody else.
Now: the consolidation version of the same story. Shutdown is the dramatic ending; absorption is the common one. Walk the Wayback Machine over to Logistyx's homepage as it stood in 2020 — an independent company, growth language everywhere, a platform with a future tense. Then read E2open's announcement acquiring Logistyx for $185 million (S4). Then read the document that tells you how the story runs from there: E2open's legacy SLA page for Logistyx, which describes maintenance-grade support (S11). Homepage, press release, maintenance page. Three documents, one product lifecycle, all public. The archive remembers what the vendor's redesign forgot.
Neither story makes the acquirers villains. Consolidation is what mature software markets do, and E2open did nothing exotic — it bought platforms and rationalized them, which is the job. The lesson isn't "avoid vendors who might get bought." Almost any vendor might get bought, including the one writing this blog's paychecks. The lesson is that ownership trajectory is a scoreable risk, and your RFP probably scores it nowhere.
So add the column. Five questions for every vendor on this season's shortlist, weighted like you mean it:
One: who owns you, and what happened to the last three products your owner acquired? Not the diplomatic version — the specific version. Names of products, dates, and where their customers are now.
Two: what is the contractual escape? Source-code escrow, data-export guarantees in usable formats, rate-table and rules-engine portability. The day you need these provisions is the worst possible day to discover their absence.
Three: if your roadmap stopped tomorrow, what still works in five years? Carrier compliance is the honest stress test. Rate tables, label formats, and service maps change constantly; a platform in maintenance mode falls behind compliance within a couple of cycles, and then it isn't "stable software" — it's a slowly failing certification.
Four: show me the legacy tier. Most consolidated vendors maintain one, even when the website doesn't advertise it. Ask to see the SLA language for their oldest acquired product line. That document is the truthful preview of how they retire platforms — far more truthful than any roadmap deck.
Five: what's the migration path off, priced today? A vendor confident in their continuity will answer calmly. A vendor offended by the question has answered it anyway.
The tradeoff, named honestly: weighting survival means sometimes scoring an exciting, well-built challenger below a duller incumbent, and your engineers may grumble. Sometimes the challenger is still the right call — price, fit, or capability can justify the risk. The discipline isn't avoiding the risk; it's pricing it. Take the risk on purpose, with an exit provision in the contract, instead of discovering it in a press release three years in.
Around the Alliance corridor this is anything but theoretical. The new buildings going up here will outlast several generations of the software inside them — a DC shell is a forty-year asset wrapped around five-year systems decisions. The companies signing leases this quarter are also signing software contracts this quarter, and only one of those documents tends to get a survivability review.
Concrete next step: we keep a one-page vendor-viability checklist — the five questions above, plus the contract provisions worth demanding and the public-record checks worth an hour of an analyst's time (ownership history, legacy SLA pages, and yes, the Wayback Machine). Request it before you score this season's RFP responses. It adds one column to your sheet. Temando's customers would have traded a lot of feature columns for that one.