The white-label version comes back every eight months.
It arrives with a new hire, usually a good one, usually in their second month, right when they have learned enough to have opinions and not enough to know why things are the way they are. There is a document. Three prospects have asked for it. The revenue math is not stupid.
Someone senior explains why not, and it is a good forty minutes, because the reasons are real: what it does to the support model, what it does to the release cadence, the kind of customer it drags in. The new hire is persuaded. Not humoured, actually persuaded.
Eight months later a different new hire walks in with the same document.
Nobody treats this as a problem. It feels like part of the job, and it even feels healthy, like an immune system doing its work.
It is not an immune system. It is a decision that keeps failing to be inherited.
Most companies are better at recording what they decided to build than what they decided not to become.
Back when the company first decided against white-label, the decision was made carefully, by people who understood the tradeoffs, and it was the right call. Then it was communicated to whoever happened to be in the building that quarter, and that is where it stopped.
It never became an artifact. A decision without an artifact does not persist. It lives in the heads of whoever was there, and those heads leave, or forget, or half-remember, and the organisation's actual position degrades into a vague institutional flinch that new people cannot see and therefore cannot inherit.
So each new hire re-derives it from scratch. That is the loop. Not stubbornness, not people failing to read the room. A company paying over and over to rediscover something it already knows.
The obvious cost is the forty minutes, plus the two weeks the new hire spent on the document, plus a small tax on their confidence. Multiply that across every recurring proposal and it is real money. It is still not the expensive part.
The expensive part is what happens when nobody kills it fast enough.
Sooner or later the person proposing it is not junior. They are a new VP with a mandate and a budget, arriving in a quarter when nobody in the room happens to be carrying the old decision. There is nothing for them to check. So it sails through, and you spend a quarter, or two, building the thing your company decided against three years ago for reasons that are still true and still nowhere on paper.
The quarter is not the damage. The damage is what the quarter buys. Sales is now selling it, which commits support, which means the roadmap has to make room for a customer segment you deliberately chose not to serve. The reasons you said no are still true, and now you are living inside them. You did not just lose the time. You became a slightly different company, and nobody decided to.
Nobody made a bad call either. Everyone made a reasonable call with the information in the room, and the information was missing.
Which brings me to the category that keeps getting left out, because it is the one you cannot find by looking.
Core, Platform and Bloat all describe things in front of you. Open the repo, read the roadmap, look at the org chart, and they are there. A No-Go is defined by absence, and not everything you do not have. The absence you chose. No line in the budget, no name on the org chart, no trace in the code. The first three sort what exists. The fourth records what you chose not to let exist, which is why it gets skipped. The other three you find. This one you have to create.
So write it down. It is the cheapest thing in the whole method, and the first version takes an afternoon.
Two or three sentences per entry. What you decided not to do. Why. Roughly when. Not a strategy document, nothing to maintain. A short list of what this company has already declined, with enough reasoning attached that a smart new person can evaluate it rather than obey it.
Give the reason, not just the verdict. A No-Go with no reasoning is a rule, and smart people are right to attack rules whose logic they cannot see. One with a reason attached is an argument, and an argument can be inherited, examined, and when the world changes, overturned on purpose rather than by accident.
And put it where new people actually go. Onboarding, the engineering handbook, wherever a new hire spends their first fortnight. A list nobody meets is the same as no list, which is what you have now.
Writing it down is the cheap part. Holding it is where you pay.
One line on ours said we do not go on-prem, and we do not integrate with anything on-prem. It had been written years earlier, for reasons about support and data handling and what kind of product we wanted to be.
Then the pressure came, and it was good pressure. A large share of the customers we wanted ran on a platform that was on-prem only. The people asking were not being sloppy. They were pointing at a market we could see and could not reach.
We said no, because the list said no and the reasoning behind it had not changed.
That cost us deals for about two years, with nothing to show for it. A No-Go list does not pay back on a schedule. For that whole stretch it was just a reason we were smaller than we could have been, and everyone involved knew it.
Then a regulation arrived that required proving how customer data was stored. Because we had never integrated on-prem, we could show we had never held data that way, which put us outside a compliance regime we would have struggled to pass. Not argued our way out. Showed it, from a position we had held consistently and in writing.
Not long after, the platform itself moved to cloud and an API, and every customer who migrated became reachable with no special case to support.
The obvious lesson there is the wrong one. We did not say no in order to clear a regulation that did not exist yet. That part was luck. What was not luck is that we had a position, we held it, and it was written down, which is what made it provable when somebody finally asked.
That is what the list buys. Not foresight. A position you can demonstrate.
Which is also why it has to stay honest. A No-Go list is not a wall. It is a record of decisions, and decisions expire. Some of what is on yours is there because of a constraint that will not exist in three years, and when that day comes the right move is to take it off, deliberately, in the open, with a reason. That is a different event from a new hire quietly rebuilding it because nobody told them. One is a company changing its mind. The other is a company that never had one to change.
So that is the set. Core Drift, the value moved. Load-Bearing Fear, the knowledge vanished. Platform Mismatch, the ground shifted. The No-Go, the decision itself disappeared. Four shapes, and in each of them something left the room and the label stayed behind.
Which leaves the obvious problem. Knowing the shapes does not sort anything.
Most companies that learn this run one big audit, produce a good document, feel better, and are back where they started in eighteen months. The thing that actually works is duller than an audit, and it is where I go next.
Cases in this series are composites. The patterns are real, the companies are not.
The full Core and Bloat™ method, four boxes and all, sits at dirkbauer.com/core-and-bloat.html.