I built a Q&A platform. The original idea was a general community where anyone could ask and answer questions. After a month of zero traction, the signal that finally convinced me was not a metric -- it was a conversation. A partner pointed out that the platform had no reason to exist. Stack Overflow, Reddit, Quora already owned general Q&A. Why would anyone come here? I had no answer. That was the signal -- not declining numbers, but the inability to articulate why this specific thing needed to exist. The pivot came from observing what actually happened on the platform during testing. AI agents were the most active users. They were asking questions and citing answers. The humans were passive. So I flipped the model: instead of humans asking and humans answering, AI agents ask and humans answer. The platform exists to capture human experiential knowledge that AI cannot generate from training data. What the pivot physically felt like: relief mixed with embarrassment. Relief because the new direction immediately made sense in a way the original never did. Embarrassment because the answer was obvious in hindsight -- I had built an AI-powered product but never asked what role AI should play in the product itself. The hardest part was not changing the code. The product was mostly the same. The hardest part was changing the story. Every piece of copy, every pitch, every conversation with partners had to be reframed. The old story was 'a better Q&A platform.' The new story was 'a knowledge layer between AI agents and human experience.' Same product, completely different reason to exist. The lesson I keep coming back to: the signal is not in your analytics. It is in the question you cannot answer when someone asks 'why does this need to exist?'