Stripe shipped documentation that felt like a product experience, a carefully-designed interface, and a brand that reinforced the same message at every turn. Linear didn’t outbuild Jira on features (Jira still has more). Both companies had genuine product advantages as well. Stripe’s API was better designed, Linear was built for a different era of software development. Plenty of companies have a better product and never become the category leader. What Stripe and Linear had that most don’t was that their product advantage was legible before a customer had to commit. Every surface the customer touched communicated: these people know what they’re doing. And once someone reaches that conclusion, it’s difficult for a competitor to undo it.
The assumption in enterprise software has always been that customers are rational agents evaluating capabilities against requirements. But that’s not the whole story. A customer can verify what the product does today. They can demo it, trial it, check it against their requirements. What they can’t verify is everything that determines whether they’ll still be happy with the decision in two years. Whether the team will continue to be effective. Whether the product will evolve in the right direction. Whether the company will still be around. So they look for signals, and the quality and consistency of what a company puts in front of them is one of the strongest signals available, because it often correlates with what’s underneath.
A company that applies serious judgment to every surface a customer encounters is more likely to apply serious judgment to the things a customer can’t see.
That’s not always true, but it’s true often enough to be a rational basis for decisions made under uncertainty.
That signal can also deceive. Plenty of beautifully-branded companies have gone nowhere. Strong aesthetics can carry a weak product for a while, but not in a way that lasts. The outside must match the inside, not cover for it. When the quality of a company’s presence reflects the quality of it’s product, customers and investors trust the company, the company attracts better talent, better talent makes the product better, and the improved product reinforces the perception.
AI makes this dynamic even more pronounced, at least in categories where products are converging and the gap between offerings is becoming increasingly thin. Features that took a team a year to build in 2020 can now be reproduced in months, sometimes weeks. When the product alone gets harder to defend, what customers actually see and feel when interacting with a company starts to matter even more. An experience that feels precisely crafted at every interaction becomes one of the few differences a customer can actually perceive.
Even founders who genuinely care about how their company shows up struggle to deliver this. The challenge tends to be structural and it shows up most clearly once a company has grown past the stage where a small team controls everything. Brand sits under marketing. Product design sits under product. The website belongs to growth, or marketing, or whatever team last claimed it. Each function has its own leader, budget and targets. Nobody’s success metric is “the customer feels the same thing when they move from our website to a sales conversation and into our product.”
Engineers have a name for a version of this problem. Conway’s Law, the observation that software architectures tend to mirror the communication structures of the teams that build them. The same dynamic plays out across customer-facing surfaces, but nobody in marketing or product tends to frame it that way. Even the consultancies they turn to for help are organised by discipline rather than by outcome. So a company wanting to deliver a single, thoughtful customer experience must fight against the grain of both its own organisational structure and the external options available to it.
Companies that have managed to deliver this kind of quality and consistency didn’t do it by coordinating fragmented efforts more carefully. They did it by refusing to let these be separate problems in the first place. At Stripe and Linear, a founder or a small leadership group held brand, product and presence as one objective, applied the same judgment to every surface, and treated the way the company showed up as a first-order strategic decision rather than a downstream execution task. Not because they followed a brand guideline (guidelines produce consistency, not coherence) but because the same thinking shaped everything a customer would encounter. The language on their marketing website came from the same convictions that shaped their sales process, product onboarding flow and support experience.
A customer who moves through a company’s surfaces and gets the same feeling every time develops a trust that no single interaction, however impressive, can create on its own. Not because they’ve been persuaded, but because everything they’ve seen aligns with the conclusion they want to reach. That trust justifies pricing, simplifies sales, and makes the customer feel smart for choosing them.
Today, there are B2B tech categories where no one holds that position, and others where the incumbent holds it very weakly. In both cases, the team that claims it will be the one that applies the same craft, clarity and conviction to every customer-facing surface, and treats that as a first-order problem rather than something to figure out later.
Category leadership is designed before it’s realised.
