Cursor · Anysphere
Review app usage each week and pick which users to follow up with
A solo founder selling report software to home inspectors uses the Cursor agent with a Firebase connection to analyse user activity every week and decide who should get a follow-up email.
What they did
Each week the agent reads user activity through the Firebase MCP and reports which users to prioritise, where they seem to get stuck and how seriously they are engaging. The same founder has the agent turn each release's code changes into a changelog and keep usage docs up to date on the Webflow site, and used it to build search tools for finding inspector contact details.
How it went
The poster says this lets him, working about one day a week, ship a release every week and still keep follow-ups and docs current. He gives no figures on how many followed-up users stayed.
Worth knowing
One founder's forum post, and he is a senior developer, so the setup may be harder for non-technical people. The follow-up analysis is described in a single sentence with no example output, and collecting contact details for outreach must respect privacy and anti-spam rules.
Try it with Cursor
Using read-only access to <your app database or analytics tool>, look at user activity from the last 7 days. List the <number> users most worth a follow-up, say where each one seems stuck and how engaged they are, and draft a short personal follow-up email for each. Do not send any email; save the drafts in <folder or tool> for me to review.
Swap the parts in angle brackets for your own details. This prompt is adapted from the case, not copied from the original.
What this label means: User story
Someone using it at work posted about it. Any numbers are theirs, so we write "the poster says".
Summarised from the original source; the link has the full story. The people and companies here are not Wize customers.