Retention
The Session-Two Problem
Getting a user to try your AI product is a marketing problem. Getting them to come back is a product problem. Most founders only solve the first one. Here's how to solve the second.
There's a number that matters more than your sign-up rate, your traffic, or your Product Hunt ranking.
It's your session-two rate — the percentage of users who come back after their first visit.
For most AI products built by solo founders, this number is somewhere between 8% and 20%. For products with strong retention mechanics, it's above 50%. The gap between those two numbers is not about the quality of the underlying model. It's almost entirely about what happens in the first session and whether the product gives the user a reason — a concrete, specific, self-interested reason — to return.
Here's what creates that reason.
The problem with one-shot AI tools Most AI products are designed around a single transaction: user inputs something, AI outputs something, session ends. That's a useful tool. It is not a sticky product. The user gets what they came for, closes the tab, and has no particular reason to return unless they happen to need the same thing again.
The products with high session-two rates are designed around accumulation. Each session makes the next one more valuable — because the product remembers something, builds something, or improves something based on what came before.
Three mechanics that drive return visits
History that's worth returning to. If users can see a log of their previous outputs and build on them, the product becomes a workspace rather than a vending machine. History is free retention. Most founders don't build it because it feels like a boring feature. It is the most important feature.
Progress that's visible. If your product can show a user that they've done something — generated twenty outputs, saved three hours, completed a workflow — they feel a relationship with it. Progress creates commitment. Commitment creates return visits.
The unfinished thing. The most powerful retention mechanism in any software product is an incomplete task. If a user starts something in session one and doesn't finish it, they will come back. Design your product to have saveable, resumable work states. Give users a reason to leave something open.
The session-two problem is solved before the user closes the tab for the first time. Design for the return from the very first interaction.
