BraindBrainD← Back to home

The Unprinted Bottles

Last updated: September 2026

account_treeProcess map Screen print → fill → stock
groupsHandover Knowledge changes hands
crisis_alertMissed signal A dependency goes unowned

Field note / Integration failure

A documented process, handed over for weeks, ignored. Then the stockouts.

From an interview with the former COO of a consumer-products ecommerce company, August 2026. Published with her permission, anonymised at her request. She is not a BrainD customer and BrainD had no involvement in any of this. The account is hers.

Six people ran a multi-million dollar consumer dental products business. A strategic buyer in the same space acquired it. The reaction to the headcount was: no way six people can run a business. Most of the team was written off in the planning.

What the seller had already paid

Before the deal that closed there were others that did not. One collapsed late in the process. Another moved fast and was not the right partner. The third closed, and she stayed on through the transition. The seller paid for all of them, in preparation time.

The assumption

They felt they had a strong team and did not need knowledge transfer.

The acquirer's position, going in

The team she dealt with was disconnected and showed no interest in how her processes worked. They said they would figure it out on the go, it would take some time, and then they would move on.

Then there was the screen printer. Blank components had to go there to have the bottles printed before they went to the co-manufacturer for filling. The sequence had a lead time. Forecasting and purchase orders had to account for it. It was documented. She walked the acquiring team through it for weeks. The person responsible for learning it made clear he was not especially interested in how things had been done, because he had his own way.

The chain

  1. inventory_2
    01

    Blank, unprinted bottles are sent directly to the co-manufacturer for filling.

  2. pause_circle
    02

    Production stalls. The sequence cannot be run backwards.

  3. remove_shopping_cart
    03

    Out-of-stock conditions across multiple SKUs.

  4. reviews
    04

    Customers cannot get product. Reviews reflect the frustration of people who only know the thing they wanted is unavailable.

  5. person_remove
    05

    The Director of Wholesale leaves.

  6. trending_down
    06

    The acquiring company runs out of product, and valuation is lost quickly.

Her summary: it was a painful lesson for them.

The data loss

The company had no technical team, just an IT person who could set up computers and had never worked in Google's environment. The acquirer was on Microsoft. An outside firm was brought in and made its own assumptions about how the transfer would run, without consulting the person who knew what was being moved.

Years of work was lost in the transfer.

Not misfiled. Destroyed, by people who did not know what they were moving, because nobody asked the person who did.

Where the knowledge actually was

Not in process documentation. In vendor relationships. She ran inventory and ordering, worked with the contract manufacturers, and had built an efficient way of getting products made over several years. The person she handed over to showed up on calls with no interest in learning any of it.

This is the version of institutional knowledge loss that rarely gets talked about. It is not always about people leaving. Sometimes it is about people arriving who do not believe the existing process has anything to teach them.

The most expensive assumption in any integration is that your way is better before you understand what you are replacing.

What it cost

  • report_problemStockouts across multiple SKUs, with the revenue and the reviews that follow.
  • personThe departure of the Director of Wholesale, on top of the team already written off.
  • deleteYears of data destroyed in a migration nobody checked.
  • warning_amberValuation lost quickly, on an asset the buyer had just paid for.
  • historyMultiple failed diligence processes before the one that closed, all paid for by the seller.

What would have caught it

None of this was hidden. The process was documented and the person who knew it was still in the building, trying to hand it over. It was offered and declined, and nobody noticed it had been declined until the bottles arrived blank.

Software would not have fixed the incuriosity. It might have caught the contradiction, a documented sequence on one side and a purchase order skipping a step on the other, in front of someone senior enough to see both. Acting on it is a separate problem, and that is the one this deal failed.

BrainD field notes / September 2026 / used with permission, anonymised at the source's request. One of 34 recorded conversations with operators, integration leads and acquirers.
© 2026 BrainD
PrivacyTermsTrust Center