BitBootcampBitBootcamp ← all explainers 🔄 Review ⚙ Settings

Drill 63 — The Acquisition

Theme: Vendors & Dependencies · Format: 20-min drill · Difficulty: advanced

The story

Your niche-but-critical document-verification vendor announces it has been acquired — by the main competitor of your biggest client. Within a quarter, product sunset is announced. You pull the contract and find the data-return terms say "commercially reasonable efforts," which turns out to mean a CSV export, eventually, format subject to change. Meanwhile your client is asking pointed questions about where their applicants' documents now physically live.

⏸ Stop here and ask the room: three clocks are running — the sunset, the migration, and the client's trust. Which runs out first?

Run it — facilitator script

Timing: 2 min story · 10 min questions · 3 min reveal · 5 min transfer.

Read the story and pause at the ⏸. Let the room argue about the three clocks for a minute — there's no single right answer, and the argument itself surfaces who's thinking about contracts, who about migrations, and who about the client. Then steer to the questions.

"When did we last assess this vendor's viability and conflicts of interest — or did we only look at procurement time?"

Listen for: an annual vendor review with teeth — ownership, funding runway, acquisition exposure, conflict-of-interest mapped against our clients, not just against us — and at least one example of a review that actually changed something.

Weak signal: due diligence as a one-time procurement gate, years stale. Companies get acquired on their own timeline, not on our review cycle — a point-in-time assessment of a moving counterparty is a photograph of weather.

"What exactly does our contract specify about getting our own data back?"

Listen for: specifics someone can recite — format, timeline, escrow where warranted, deletion attestation. The best answer in the room: someone has actually exercised the export clause and validated what came back.

Weak signal: "there's a data clause, I think" — or "commercially reasonable efforts" read aloud as if it were reassurance. That phrase is a blank cheque drafted by the vendor's counsel, and it was cashed in this story.

"How long would switching actually take — do we know, or do we hope?"

Listen for: a rehearsed exit plan with a measured number — the switch has been walked through end to end, the replacement shortlist exists, the data mapping is documented, and "weeks" comes with evidence attached.

Weak signal: estimates that are hopes with units — "a month or two?" — never tested against anything. The story's real answer was three quarters, discovered only when all three clocks were already running.

Facilitator close: land the reveal's last line — every week of the pain was purchased years earlier, at signing, by a clause nobody read adversarially. The incident started long before the announcement.

The reveal

The migration to a replacement takes three quarters — raced against the sunset clock, with contractual ambiguity about retrieving your own data, while the client relationship absorbs damage the entire time. Every week of that pain was purchased years earlier, at signing, by a clause nobody read adversarially.

Why this happens — the mechanics

Contracts are drafted by the party that plans to outlive them. "Commercially reasonable efforts" is not sloppy language — it's deliberately elastic, costs the vendor nothing to grant at signing, and gives them everything at sunset, when "reasonable" gets defined by whoever has less to lose. Exit clauses share a cruel property with backups: they're only ever tested at the worst possible moment. Nobody reads a data-return clause adversarially while the relationship is healthy, and by the time someone does, the leverage that could have fixed it is years gone.

An acquisition reprices every incentive overnight. The vendor you assessed at procurement — its roadmap, its independence, its interest in keeping you happy — no longer exists; a new owner's strategy now governs your dependency, and you had no vote. Conflict-of-interest is the sharpest version: risk isn't just "will this vendor survive?" but "who might end up owning them, and what would that owner want?" — a question that has to be re-asked annually, mapped against your clients' competitive landscape as well as your own, because your client's trust is exposed to your vendor choices whether or not anyone wrote that down.

And exit cost accumulates silently, which is why "how long to switch?" gets answered with hope. Data gravity, undocumented integration depth, format lock-in — none of it shows up on any dashboard while the vendor is healthy; every quarter of successful operation quietly deepens the hole. Without a rehearsed exit, the migration clock is unmeasured until the moment it's already racing two others — the sunset and the client's patience. Rehearsal doesn't make the switch free; it makes the number known, and a known number is the difference between a plan and a scramble.

Diagrams

Problem — how the failure unfolds:

timeline
    title Three clocks against one migration
    section The announcement
        Quarter 0 : Acquired by client's competitor : Client asks where documents live
    section The squeeze
        Quarter 1 : Product sunset announced : Contract says commercially : reasonable efforts only : Data return is a negotiation
    section The scramble
        Quarters 2-3 : No exit plan on the shelf : Migration from zero begins : Client trust eroding weekly
    section The finish
        Quarter 4 : Migration lands against sunset : Every week bought at signing

Solution — where the guardrails go:

flowchart TD
    V["Annual vendor review:<br/>viability, ownership,<br/>conflict of interest"] -.-> AL["Acquisition risk flagged a<br/>quarter early"]
    AL --> B["Exit plan pulled off the<br/>shelf — rehearsed last<br/>year"]
    A["Acquisition announced"] --> B
    B --> C["Switch executes in weeks,<br/>not quarters"]
    A --> D["Contract clause: data<br/>return with format,<br/>timeline, deletion<br/>attestation"]
    D --> E["Data returned and deletion<br/>attested on schedule"]
    E --> F["Client questions answered<br/>with specifics, trust<br/>intact"]
    C --> F

What good looks like

The lesson

Vendor viability and conflict-of-interest are risk dimensions to review annually, not just at procurement — companies get acquired, and their new owners have their own interests. Contracts need data-return and escrow clauses with specifics: format, timeline, deletion attestation. And for every critical dependency, maintain a rehearsed exit plan — you don't need a second vendor live, you need to know the switch takes weeks, not discover it takes quarters.

Named concepts: vendor viability risk, data-return/escrow clauses, exit rehearsal, concentration risk.

Real-world echoes

Transfer

Which vendor's acquisition would hurt us most? Pull that contract today and read the data-return clause — what does it actually specify, in format-and-timeline terms?

Make it a ticket: extract that data-return clause verbatim into the dependency registry this week; if it lacks format-and-timeline specifics, open the renegotiation item now — and draft the exit-rehearsal plan with a measured switch estimate attached.

Related