When to rebrand, and when you just need a better product

"Our brand feels dated" and "our product isn't converting" get reported to us as the same problem more often than you'd expect. They're rarely the same problem, and treating one as the other wastes a rebrand's worth of budget solving nothing.

A rebrand is the right call when the company itself has changed and the brand hasn't caught up — you raised a round that repositions you against a different set of competitors, you pivoted who you actually sell to, you outgrew the tone you launched with three years and one very different roadmap ago. In every one of those cases, the mismatch is between what the company is and what the brand says it is. That's a Foundation problem: strategy, positioning, identity.

A rebrand is the wrong call when the actual complaint is that people land on the site and don't do the thing you want them to do. That's not a perception problem, it's an experience problem — the interface doesn't make the value clear, the flow has friction, the product doesn't demonstrate itself fast enough. A new logo does nothing for a checkout flow that loses people at step three. That's an Interface or Build problem, and dressing it up in new colors is an expensive way to not fix it.

The diagnostic we actually use, before we let anyone commit budget to either: ask whether the complaint is about how the company is perceived, or about what happens once someone is already trying to use the thing. The first is brand. The second is product. Most "rebrands" that fail to move any real number were the second problem wearing the first problem's clothes.