UserLens
Which features actually earn their place, decided with evidence.
UserLens connects your product analytics (PostHog, Google Analytics 4, Plausible or Microsoft Clarity) and shows how each product area is really used. Usage becomes explicit keep/investigate/deprecate decisions, and an AI action plan grounded in the evidence.
Connecting a provider
Connect your analytics provider under Integrations. UserLens reads event data (it never writes to your analytics), and each provider has a short setup hint for the credentials it needs.
UserLens projects
Create a UserLens project and map which events or tags belong to which feature. This mapping is what turns raw event streams into a per-feature view.
Usage and trends
Each feature shows its usage with a four-week trend and sparkline, no dashboard building required. Rising, flat and dying features become obvious at a glance.
Decisions
Mark each feature keep, investigate or deprecate. The point is to make the roadmap reflect reality: an explicit deprecate decision beats a feature that quietly rots while everyone assumes someone is watching it.
AI action plan
Generate an action plan grounded in the usage evidence (what to keep investing in, what to investigate, what to wind down), aligned with what is already on your backlog. Generation counts toward your monthly AI actions.
Version planning
Use the version-planning view to group decisions into a release: what ships, what gets flagged for investigation, what is scheduled for deprecation.
Removal candidates and backlog alignment
UserLens flags removal candidates (features in the bottom band of usage that almost no one touches) so a deprecate decision has evidence behind it. Backlog alignment matches the project's open tickets, from every connected tracker, against low-usage and deprecated features, so you stop building on top of things users have already left behind.
From decision to release
The version-planning view groups your keep, investigate and deprecate decisions into a release plan, and selected actions from the AI plan can be pushed straight to your tracker's backlog, turning 'we should look at this' into a ticket someone owns.
Adding to your backlog, anywhere
Add to backlog creates the item in Jira, GitHub, GitLab, Bitbucket, Linear, Azure DevOps or Notion, wherever your team keeps its backlog. For Bitbucket, only repositories with the issue tracker switched on are offered.