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.

Crunchy surfaces the insights hiding in your data and packages them into dashboards you can actually use. Built for marketing and GTM teams who are tired of waiting on someone else to answer their questions.
After three weeks of posting, commenting, and trying to figure out Product Hunt as a first timer, Crunchy is officially live!

If you've followed along on any of the threads, thank you. If you're just discovering us now, welcome.

We've now had a handful of beta users go from "what is this" to "okay this is actually useful", and the path is more consistent than we expected. So, if you're joining our open beta from Product Hunt, here's what we've learned about how to get there fastest.

1. Don't start with your messiest data

   The instinct is to throw your hardest dataset at it to test if it works. Resist that. Start with something you already understand: a simple sales report, a campaign overview, a CRM export. You want to see Crunchy work first, then test its limits.

2. Ask a question you already know the answer to

   Before you ask Crunchy something hard, ask it something you already know. "Which channel drove the most revenue last quarter?" If the answer matches what you'd expect, you're calibrated. Now you can trust it on harder questions.

3. Then ask the question you've been avoiding

   This is where Crunchy actually earns its keep. Ask the question your team gave up on because it was too painful to set up. What triggers a first purchase? Which campaign actually drove pipeline vs just clicks? What does a high-value customer look like before they convert?

   These are the questions Crunchy was built for. Not faster charts, questions you didn't think you could ask.

4. Edit, don't restart

   If a chart isn't quite right, don't start over. Edit it in its own thread. Tell Crunchy what to change. The whole point is that you stay in the flow instead of starting from scratch every time.

5. Share what you find

   The biggest unlock for our beta users has been realising they can send a Crunchy output straight to a colleague or into a deck. Don't keep it to yourself. The moment you share an insight someone else couldn't get, the value of Crunchy clicks for your whole team.

If you're trying it out, drop your first impressions in the comments. We're listening to everything.

One of our beta users set up Crunchy for her team. Then rolled it out across other markets. Then other teams started asking to use it.

We didn't design for that. It just happened because of how the tool works, one technically capable person sets up the context, builds the template, and the whole team runs it independently from there.

It was about the questions nobody was asking.

Not because the data wasn't there. Because getting to it wasn't worth the setup cost.

We've noticed a pattern in our beta.

First impression: Oh, it makes charts. Nice.

Why is finding people who actually feel the pain so hard?

We're building Crunchy and we have a clear sense of who we're building for: marketers who spend more time wrestling with data than actually using it. But knowing your ICP and finding them are two very different things.

We thought the hardest part would be the product.

It wasn't.

We launched our closed beta for Crunchy last week. The feedback was encouraging. People got it immediately.

The use case was clear. The demo landed well.

Marketing runs on data but somehow crunching it and getting it into something presentable, still eats half your week. We kept running into this ourselves and couldn't find anything that solved it cleanly. So we're building Crunchy.

Drop in your data, get back editable dashboards and insights you can actually share with the people who matter. No SQL, no setup, no cleaning up charts in PPT at midnight.