5 Things You Should Never Say to a Founder Post-Acquisition

A founder's engagement after the deal closes is not a soft metric. It is the difference between an integration that goes smoothly and one that quietly works against you — and it is shaped less by strategy decks than by a handful of specific things said in the wrong way, at the wrong moment.

Most founders go into this process genuinely onboarded. They want to see what they built succeed. Some hope to stay long term, fully invested in the next chapter. This isn't a piece about bad-faith operators — it's about how good intentions, said the wrong way, can quietly undo that goodwill anyway.

Here are five common turndowns to avoid — and what to say instead.

1. "Nothing is going to change."

This is almost always said to be reassuring. It almost never survives contact with reality — and when it doesn't, it costs more than the change itself ever would.

You didn't buy this company for its processes. You bought it for its people, its product, its culture — the things that actually drove the result you paid a multiple for. If you aren't prepared to stand behind "nothing will change" completely, the moment you make your first change, you've broken trust with everyone you said it to. Not bent it. Broken it.

The better version of this conversation isn't a promise. It's a plan, said honestly from day one: here is the change process we're looking to implement, here are our actual goals, here is how this will be built and discussed with the people who run this business day to day.

And one more thing, worth saying directly: key employees and founders are not stupid. The absence of an MBA or a shiny title does not mean they don't understand what's happening. These are people who made real money and navigated genuinely difficult market conditions — not despite a lack of sophistication, but because they stayed relentlessly focused on what actually mattered. If your real goal is to change or align something, you have a choice: fight them on it, or bring them into it. Telling them nothing will change, when you already know it will, is about as costly a lie as you can tell.

2. "We just need this to look more professional."

Professionalism is subjective, and it was never the founder's goal in the first place. He built this business to make money, in a good atmosphere, working toward something he cared about. Nobody asked him for a business education, and nobody asked you to give him one.

Here's what actually happens when this phrase gets said: the founder goes quiet. He follows your professional process, because pushing back feels like a losing argument about a thing — what counts as "professional" — that was never the point to begin with. In the good scenario, you end up paying real money to make something look more polished than it needs to be. In the bad scenario, you break something that was working, for a fraction of what it now costs you to fix.

What works instead: ask why it works before deciding it needs to look different. "Walk me through why you do it this way" gets you the context. "Make it more professional" gets you a founder who stops explaining — and a process that costs more than the one it replaced.

3. "The team will adjust."

Before saying this, understand who your team actually is. How critical each person is. How much capacity they already have — or don't.

A lean, highly profitable business doesn't happen by accident. If a company runs at 55% EBITDA margins with 35% growth, the founder has already made sure the key people are working at near full capacity. That's not a coincidence — it's a precondition. If your instinct is that the team has slack to absorb more, that's not an observation about the team. It's a sign you don't yet understand the level of complexity they're managing.

This is what makes "the team will adjust" so dangerous when it's attached to formalizing a process — and even more dangerous when it touches contracts. You are not simply standardizing vacation days when you do this to a product manager who has been building the product for fifteen years. You are touching the terms under which your most critical person agreed to keep showing up. Done carelessly, this can quietly kill both the product roadmap and the willingness of your best people to keep collaborating with you at all.

What works instead: before formalizing anything, map who is actually carrying the business and what a contract or policy change touches for them personally. Some formalization is genuinely needed. It has to be sized to people already operating at capacity — not assumed onto room that doesn't exist.

4. "Let's keep this simple."

This tends to appear in the same conversation as #3 — usually in response to someone explaining why something isn't as straightforward as it looks. To a person with years of hands-on experience, the nuance they're describing isn't complexity for its own sake. It's the obvious stuff. Explaining it can feel like stating the obvious to someone who keeps insisting it isn't.

"Keep it simple" sounds efficient. What it actually communicates is: I don't want to hear the reason this isn't simple. When the thing genuinely isn't simple — a customer exception, an unusual term, a workaround for a real constraint — simplifying it doesn't make the complexity disappear. It just moves the cost somewhere less visible, usually onto the person who understood it in the first place.

What works instead: assume the complexity is there for a reason until proven otherwise. "What happens if we simplify this?" is a far better question than a directive to simplify it.

5. "I know how this works in other places" / "We've done this many times before."

These two get said in the same breath, and they share the same flaw: confidence borrowed from elsewhere, applied to a business that earned its results doing things differently. There may genuinely be a more standard way to do it — the founder can Google that just as easily as you can. What he has, that research doesn't give you, is the specific reason this business does it differently, often figured out the hard way.

Sometimes that reason is a bad one — an outdated habit nobody questioned. But sometimes it's the entire reason the business works. "We've done this many times before" doesn't answer which one it is. It just tells the founder his specific business is being treated as a category instead of a particular set of decisions made by people who got somewhere real.

What works instead: pair experience with curiosity. "We've seen patterns like this before, but walk me through what you were solving for when you built it this way" gets you both the pattern-matching and the context.

The Closing Thought

None of these phrases are malicious. They are the natural language of people trying to reassure, motivate, or move quickly. But a founder who has spent years building something hears each one as evidence — sometimes the first evidence — of how this relationship is actually going to work.

The fix isn't complicated, and it isn't expensive. It's saying less and asking more, in the first few conversations that matter most.