We’re the team behind Prism AI, and we’re excited to share what we’ve been building.
At Rajit’s previous company, they built a new onboarding flow, set up a dashboard to analyze it, and realized that it was broken. The problem was that this realization came four months later.
This is the core insight that led us to start Prism.
Existing product analytics solutions are inflexible. They require comprehensive instrumentation and break every time an engineer adds a new flow or modifies an existing one.
With Prism, developers get insight into what's broken on day one. No event-tracking necessary.
Instead of trying to reverse-engineer user behavior from charts, you can ask:
“What’s breaking onboarding?”
“What are the main pain points users are experiencing?”
“Which sessions have repeated confusion?”
🧠 Behind the scenes:
We record DOM changes + user interactions
Replay sessions in headless Chrome
Use VLMs to flag friction
Cluster similar sessions to reveal patterns across flows
💡 Prism is for PMs, devs, and product engineers who want to fix friction fast without being buried in noise.
🎁 For the PH community: We’re offering 500 free sessions to any pre–Series A team until June 15 with the code PH500.
We’d love your feedback — especially on how you spot friction today and what would make that process faster or clearer.
