A prospect doesn't experience your org chart. They experience whoever answers the phone that week, whether that's the same person as last time or a total stranger who needs the whole story repeated from scratch. Enterprise deals get lost in that gap more often than they get lost on price.
The tell-tale sign of a silo problem
If a customer has to reintroduce themselves, their setup, their history, every time they talk to someone new, that's not a training issue. That's a structure issue, and no amount of individual effort fixes it, because the individuals aren't actually the problem.
Two shapes worth considering
Some companies do better with one dedicated person owning an account start to finish. It's a great fit early on, and for your highest-touch accounts where the relationship really is the product. It gets expensive and hard to scale past a certain point, and it puts a lot of institutional knowledge in one person's head.
Other companies do better with a small team sharing an account, split by function, but genuinely accountable to each other, not just to their own manager. This scales further, but only if the incentives actually line up. If one function gets rewarded for closing fast and another gets rewarded for retention six months later, they'll quietly work against each other no matter how many shared Slack channels you create.
Neither shape is automatically right. The wrong one for your stage is whichever one your incentive structure can't actually support yet.
The handoff test
Next time an account moves between teams, sales to onboarding, onboarding to support, whoever, watch what actually gets passed along. If it's just an account number and a login, that's the leak. If it includes the customer's actual goals, their concerns, and what's already been promised, that's a handoff that respects the relationship instead of resetting it.
Feedback that goes nowhere is worse than no feedback
If your team logs customer feedback and nothing visibly happens with it, they'll eventually stop logging it, and customers will eventually stop offering it. Close that loop publicly, even briefly: here's what we heard, here's what we did about it, here's why on the ones we didn't act on. That visibility matters more than whatever system you use to track it.
A great product with a fragmented team behind it loses to a decent product with a team that feels like one team. That's not a controversial claim. It's just one most org charts aren't built to honor.
Common questions
Why do enterprise deals get lost to silos?
Customers don't experience your org chart. They experience whoever answers the phone that week. Deals are lost in the gaps between teams more often than they're lost on price.
What is the telltale sign of a silo problem?
A customer having to reintroduce themselves, their setup, and their history every time they talk to someone new. That's a structure issue, not a training issue.
Should one person own an account, or a team?
One dedicated owner works well early on and for your highest-touch accounts, but gets expensive to scale. A small shared team scales further, but only if incentives actually line up. The right shape is the one your incentive structure can support.
What should a good account handoff include?
More than an account number and a login. A good handoff passes along the customer's goals, their concerns, and what's already been promised, so the relationship continues instead of resetting.