Neotic
Context aware product experiences, without the code.
Every time you want to:
announce a new feature
show onboarding to a specific user
notify Pro users about something
trigger an experience after an event
show something only on a specific page
…it often ends up becoming another frontend task.
Add some logic.
Add a component.
Deploy.
Repeat.
Neotic is my attempt to separate product experiences from frontend releases.
You connect Neotic once, define the context and conditions, and control what experience appears inside your product.
For example:
Show the new dashboard announcement only to Pro users who visit
/dashboardafter they’ve used the old dashboard.
The interesting part is that Neotic is being built developer-first.
I’m also working on an MCP integration so AI coding agents can work directly with a Neotic workspace.
The workflow I’m aiming for is:
Code → AI agent → Neotic → Product experience
Still early, and I’m actively figuring out the right positioning, pricing, and feature set.
If you build SaaS products:
Would you actually use something like this, or would you just keep hard-coding these experiences?
I’d genuinely like to hear how you handle this today.
1 Comment
The positioning question here feels more consequential than the feature set. You’re defining a new layer between product code and the user experience, which makes the category itself important.