Every answer knows who gave it
Responses arrive already joined to the respondent’s attributes - plan, tenure, city, any event or profile property - so you can slice free from paid instead of reading an undifferentiated list.
In-app user research
Talk to your users,
continuously.
userpulse reads the events you already have and asks the question inside your app the moment someone drops off - while they still remember what they were doing.
Early access - we’re onboarding teams one at a time, so sign-up is by invitation. Not invited yet? Sign up anyway and we’ll add you to the list.
Fired 2s after milestone_marked
Answer tagged premium · 34 days
Live without an app release
Founders can’t get feedback good enough to decide what to build. Interviews mean cold-contacting strangers, so they get postponed. Generic surveys return one-liners that never say what the person was trying to do. And the real blocker is earlier: deciding what to ask, who to ask, and when is itself the work that never happens.
How it works
Three steps, and no app release.
From a sentence to a live study running against your existing analytics events.
- Why are users churning?
Start with a question
Say what you want to learn. Claude reads your events, properties and cohorts through userpulse and drafts the study - or you build it yourself.
- WhoPremium · 30d+Whenmilestone_markedWhat2 questions
Review before it ships
Nothing reaches a user until you publish it. The audience, the trigger and every question stay editable here, with a live preview of the sheet your users will actually see.
What were you trying to do?
Track a habitSomething elseApprove, and it’s live
The survey appears in-app at the moment you chose, as a short bottom sheet that never blocks what the user was doing.
Why it works
Why the answers are worth reading.
Response rate and depth are design problems, not persuasion problems.
Asked in context, answered in a tap
The question arrives seconds after the behaviour it’s about, while the person still remembers what they were trying to do. Tap-first by design, because every extra keystroke costs response rate.
Interviews that book themselves
Invite a respondent to a call right after they answer. Instead of cold outreach, people self-select in - and every interview arrives warm, with their answer already attached.
Install
One line, around the client you already have.
userpulse wraps your existing analytics client - Mixpanel or PostHog - so every event your app already sends becomes something a study can trigger on. No call sites change and nothing is re-instrumented.
It fails open, which is the part worth checking: if userpulse throws or is unreachable, your original track() or capture()still runs and its return value still comes back. The worst outage here is that a survey doesn’t appear.
Mobile apps, starting with React NativeMixpanel and PostHog