One team I know added an AI assistant because every competitor had one six months later, almost nobody used it. The bigger problem wasn’t adoption though; it was that customers started expecting everything to be AI-powered, and support got messier because the AI occasionally gave wrong answers. They ended up spending more time managing expectations than building.<div>
</div><div>Another founder I talked to had the opposite experience. AI became their best retention feature, but only because it solved a real, specific pain point not because it was AI.</div><div>
</div><div>The pattern I keep noticing: adding AI isn’t the regret. Adding AI without a clear job for it is. If you can’t name the exact workflow it improves, the engineering time is probably better spent elsewhere first.</div>