The more features a product has, the harder it becomes to explain it without overwhelming a new user.
Do you:
guide users step by step give them a simple starting task let them explore everything themselves use videos/tutorials hide most features until they need them or something completely different?
We're building Expertise, a platform where GTM experts publish their playbooks as skills that businesses run on their AI agents, and there's a debate that comes up with every expert we onboard: should a skill be open or locked?
Before building, we looked at why prompt marketplaces and open skill catalogs kept dying. A playbook written as text is just a string, and a string gets copied the moment it's worth copying. And there's a newer twist: ten years ago you open-sourced for other humans, who fork you, cite you, hire you. Now the biggest consumer of an open playbook is the AI itself. Every framework posted publicly becomes something an agent runs tomorrow with your name stripped off. You're not sharing with a community anymore, you're training your replacement one prompt at a time.
I ve noticed a pretty big change in my own behavior over the last year.
If I m looking for a tool for something specific, I ll usually ask ChatGPT first, then check Product Hunt or Reddit to see what real people are saying. Google has become more of a second step for me.
What I m curious about is whether thats actually changing discovery for other makers too, or if I m just unusually deep into AI tools.
