Camilla S Andersen

I used to keep a detailed public roadmap with target launch dates to build trust with early users.

But as soon as dev work ran behind the constant check-ins from subscribers made me feel accountable to a schedule I couldn't control.

Removing hard dates stopped the unnecessary anxiety but I still want to keep the community looped in on upcoming stuff.

If you keep an open roadmap, what limits or guidelines do you put on it so delayed features don't feel like broken promises?

In our Product Hunt launch last month, we got a great question from the community: What do the insight types mean?

The Occasio Insights Management Protocol is designed to give your micro-data the context it needs to become scalable, reliable intelligence for both you and your machine.

Building used to be the bottleneck. Now I can get a working app faster than I can write a good landing page copy for it. So the "idea guy with no code skills" excuse is basically gone.

But almost none of my vibe-coded weekend projects have real users, and I don't think that's a coding problem anymore.

For those of you actually getting traction - what's eating your time now that building isn't the bottleneck?