One thing we underestimated: How much we need to teach.

We've been sitting with feedback from our first wave of beta users and one theme keeps coming up: What feels intuitive to us isn't intuitive to them.

We're a small team that thinks about data and AI all day. The bulk of our target users don't. They're marketers and GTM folks who want answers, not interfaces. The features that feel obvious from where we sit can feel hidden from where they sit.

The most consistent piece of feedback has actually been kind: "Crunchy is more powerful than it first appears." Which is encouraging, but it's also a problem. If the value isn't visible in the first few minutes, most people won't stick around long enough to find it.

So we're shifting how we think about the product. Less "build features and assume people will find them." More "teach users what's possible at the moment they need it." Empty states with starter prompts. Suggestions for the next question to ask. Walkthroughs for the things people don't know they can do.

The product isn't just what you build. It's what users actually discover.

For anyone else building for non-technical audiences, how have you handled this gap between what's intuitive to you and what's intuitive to your users?