Look — the most honest document a software vendor will ever show you isn't the RFP response. It's their homepage from twenty years ago, preserved in the Internet Archive, making promises you can now grade. RFP season is open, the decks are flying, and every founder or investor evaluating a shipping-tech bet should spend an hour in the Wayback Machine before spending a dollar anywhere else. The archive remembers what the vendor's redesign forgot.
This one's for the founder and the people writing them checks, because vendor mortality is a line item nobody puts in the model.
Exhibit one: iShip, 2003
Pull up iShip's homepage as it stood in February 2003. Read the pitch: compare carriers, ship, and track from a web browser. Multi-carrier shipping, delivered over the internet, no software install. That's a quarter century ago, and it is — nearly word for word — the pitch you'll hear in 2027 from a dozen vendors with better fonts. The pitch was right then and it's right now. iShip the independent brand, meanwhile, is a memory. First lesson of the archive: in this category, being correct about the future is not a survival strategy. The promise outlives most of the companies that make it.
Exhibit two: ConnectShip, 2018 — and the portal that never died
Now look at ConnectShip's site in August 2018 — enterprise multi-carrier shipping, the toolkit behind plenty of big operations. Today ConnectShip lives on quietly as part of the UPS corporate family, which matters to a buyer for an obvious reason: when one carrier owns your multi-carrier engine, ask the rate-shopping question with a straight face and watch the answer.
Then look at the stranger artifact: a Progistics shipping portal still answering on the public internet at a Pitney Bowes address. That's production-era shipping infrastructure from a previous architectural epoch, still live, still serving pages. Second lesson: shipping systems don't die. They stop being anyone's roadmap, and then they run for another fifteen years with nobody home. If your operation is on one of those, you don't have a vendor. You have an unattended machine.
Exhibit three: Temando, the cautionary consolidation tale
For the founders specifically: read the Temando story. Australian shipping-tech startup, real funding, real customers, acquired into a bigger logistics-software ambition — then shut down. Third lesson: the acquisition is not the happy ending. For customers, it's a coin flip between "new investment" and "maintenance mode while the acquirer rationalizes the portfolio." The archive is full of homepages that announced an acquisition as great news for customers. Follow the snapshots two years forward and see how the news aged.
The archive audit, as method
When the RFP shortlist is set, run each finalist through five checks. Takes an hour per vendor:
- Promise drift. Compare the homepage at five-year intervals. Stable claims that compound are good. Pitches that pivot wholesale every cycle tell you the strategy is the marketing.
- Roadmap graveyard. Products announced loudly, then absent from later snapshots. Every vendor has one or two. A pattern of them is a forecast for whatever they're promising you.
- Logo churn. Customer logos appearing and vanishing between snapshots. Logos that quietly disappear mid-cycle had a reason to.
- Ownership trail. Names, acquisitions, rebrandings across the snapshots. Each handoff is a place where your contract, your SLA, and your roadmap leverage got renegotiated without you in the room.
- The pricing page test. Public pricing that existed and later vanished usually marks the move upmarket — and the moment implementations stopped being eight weeks (the cloud mid-market benchmark sits at 8–12 weeks, while legacy replacements run 12–18 months, S26) and started being statements of work.
And once the archive has made you appropriately paranoid, write the paranoia into the contract. The protections that matter when a vendor gets consolidated are the unglamorous ones: assignment clauses that require your consent or trigger exit rights on change of control, SLA terms that survive acquisition rather than reset to the acquirer's standard, data-export rights in a documented format on demand, and source-code escrow with release conditions you'd actually be able to invoke. None of that costs much to ask for in RFP season, when you're the prize. All of it is unobtainable three years later, when you're the maintenance revenue.
Why a guy from the ramps cares
Because in this region, February doesn't negotiate. When the lake-effect bands set up and the gateway slows, the question isn't whether your vendor's deck was pretty in RFP season — it's whether someone competent answers the support line at 2 a.m. during the fifth winter of your contract. Twenty years around the Joliet ramps taught me to evaluate everything — chassis, carriers, software, people — on one axis: does it still work in February, five Februaries from now? The Wayback Machine is the only due-diligence tool that answers that question with evidence instead of assurances, because it shows you what the vendor's last five Februaries actually looked like.
Concrete ask: we keep an archive-audit checklist — the five checks above, plus the snapshot URLs worth pulling for the major shipping-software vendors. Ask and it's yours before your next shortlist meeting. One hour per vendor. The redesign forgot. The archive didn't.