Most SaaS products live in the forgettable zone and do not know it
Reforge's Casey Winters teaches a framework called the Frequency Spectrum. It splits products into two zones based on the natural frequency of the problem they solve. The habit zone is daily to monthly. The forgettable zone is anything less than monthly. Slack, Instagram, Zoom: habit zone. Airbnb, TurboTax, Carvana: forgettable zone.
The framework matters because retention strategy is completely different in each zone. Habit zone products win by becoming part of the user's routine. Forgettable zone products win by layering on a higher-frequency hook that keeps them top of mind between the rare moments the core problem fires. Founders who do not know which zone they are in usually try habit-zone tactics on forgettable-zone products. It fails predictably.
This article explains how to diagnose your zone, what each zone requires, and the specific playbook for moving a forgettable product closer to habit. For the broader retention strategy this fits into, read the BELT framework pillar.
What the frequency spectrum actually measures
The frequency spectrum is not about how often users open your product. It is about how often the underlying problem the user is trying to solve fires for them. The distinction matters because the problem frequency caps the realistic ceiling on usage frequency.
Slack solves "I need to communicate with my team." That problem fires multiple times a day for most knowledge workers. Slack therefore lives in the daily end of the habit zone. Usage caps at multiple-times-a-day because that is when the problem cap is.
Airbnb solves "I need a place to stay while traveling." That problem fires once or twice a year for most consumers. Airbnb lives in the forgettable zone. No amount of push notifications will turn Airbnb into a daily app for the average user, because the underlying need does not exist that often.
The four bands of frequency
Reforge teaches four practical bands.
Daily: Slack, Gmail, Instagram, banking apps, music streaming. The problem fires almost every day. Retention curves stabilize fast (4-8 weeks) and stay high.
Weekly: Pinterest, Zoom (for most users), Spotify (for casual users), expense management, social scheduling tools. Problem fires a few times a week. Retention curves take 8-12 weeks to flatten.
Monthly: Personal finance tools, payroll, subscription boxes, project review tools. Problem fires every few weeks. Retention curves take 16-24 weeks to flatten and tend to sit lower.
Less than monthly: Tax software, travel booking, real estate, car buying, life insurance, wedding planning. Problem fires once a quarter or once a year. Retention curves are bumpy and often look like they have failed when they have not.
How to figure out your zone in 30 minutes
You do not need a research team. You need three data points.
Step 1: Ask 10 paying customers
Reach out to 10 customers who have been around at least three months. Ask them one question: "How often do you actually have the problem this product solves?" Not "how often do you use the product." That is the wrong question because it conflates the underlying problem with your specific solution.
Aggregate the answers. If 8 of 10 say "every day or two," you are in the habit zone. If 8 of 10 say "every few weeks" or "a few times a year," you are in the forgettable zone. The split is usually obvious. Founders who get a mixed result are usually serving multiple use cases at different frequencies, which is its own problem.
Step 2: Pull a histogram of last-28-day usage
For your 1,000 most recent active users, count how many days out of the last 28 each one used the product. Plot the distribution. If most users cluster at 20-28 days, you have a daily product. 8-15 days: weekly. 1-3 days: monthly or less. The shape is more revealing than the average.
A common mistake: looking at the average and seeing 4 days, then concluding "weekly product." That hides the fact that you might have two populations: 80% who used it once and bounced, and 20% who use it daily. The histogram shows the bimodal distribution. The average hides it.
Step 3: Check the retention curve shape
A flat retention curve after the initial drop means the product matches a real problem at the right frequency. A retention curve that decays continuously to zero means the problem frequency is lower than your nurture cadence. Users are getting prompted to use the product more often than they actually need to, so they tune out and churn.
A retention curve that is high but trends down slowly often indicates a forgettable-zone product where users come back when the problem fires but eventually move to a competitor. That is the hardest pattern to fix because it is not obvious from cohort numbers alone.
The habit zone playbook (daily to weekly)
If you are in the habit zone, the job is to become routine. Specific tactics:
Match nurture to nature
Casey Winters' phrase. Notifications, emails, and prompts should match how often the user naturally has the problem, not more. If users have the problem twice a week, sending daily emails is spam. They tune out, you lose the channel, and the actual nudge that matters gets ignored.
Test by sending different cohorts different nurture cadences and measuring 4-week retention. Most habit-zone products are sending nurture too often. The fix is sending less, not adding more channels.
Find the trigger
Habit-zone products are defined by a clear trigger. Slack's trigger: a colleague sends a message. Instagram's trigger: feed update or a friend posts. The trigger is what makes the user open the app without thinking. If your product does not have an obvious trigger, you do not have a habit. You have an intention.
For most SaaS products the trigger is a workflow event (new deal, new ticket, new lead) or a recurring schedule (Monday morning planning, Friday review). Build the trigger into the product so it fires reliably. Email digests, in-app notifications, and integrations are the three main delivery mechanisms.
Track an XaY habit metric
"X uses in Y days" is the canonical habit metric. Pinterest tracks Weekly Active Repinners (W-A-R). Slack tracks Daily Active Users with at least 2,000 messages exchanged within a workspace. The frequency in the metric must match the natural frequency of the problem.
Setting the frequency higher than natural is the most common mistake. "We want users to open the app daily" when the problem only fires weekly leads to spam-heavy nurture, low NPS, and high churn. Set the frequency to match nature, not to match what you wish were true.
The forgettable zone playbook (monthly or less)
If you are in the forgettable zone, the job is layering. The core problem is rare. You need a secondary use case at higher frequency to stay top of mind.
Layer on a higher-frequency hook
Reforge's go-to example: Zillow. Buying a house is a once-every-7-years event. Yearly retention on a home-buying app would be impossible. So Zillow layered on the Zestimate. Checking the value of your own home (or your neighbor's) is a weekly habit. The Zestimate gets users into the app every week. When the rare buying problem fires, Zillow is the default destination.
Pattern: the higher-frequency hook should be related to the core problem but not require the core problem to fire. Often it is a tracking, monitoring, or status-checking behavior on something the user owns or cares about.
Practical examples of layered hooks
TurboTax could layer on a weekly "tax savings tracker" that estimates current-year liability based on recent transactions. Carvana could layer on a monthly "your car's resale value" update. SaaS examples: an annual contract renewal tool could layer on a quarterly contract risk dashboard. A wedding planning tool could layer on a weekly vendor inspiration feed.
The hook needs to be useful on its own, not just a manufactured reason to log in. Users see through manufactured loyalty mechanics within a week. Real utility holds.
Accept the longer retention curve shape
Forgettable-zone retention curves naturally flatten lower and take longer to stabilize. A SaaS founder benchmarking forgettable-zone retention against habit-zone retention is comparing apples to oranges. 30% one-year retention on a yearly-problem product can be excellent. 30% on a daily-problem product is a disaster.
The right benchmark is similar products in the same frequency band. Travel booking apps have similar retention curves to each other. Compare within your band.
What this means if you are still pre-product-market-fit
The frequency of your problem partly determines how big your business can get and how hard retention will be. If you are choosing between two ideas and one is in the habit zone while the other is in the forgettable zone, the habit-zone idea is almost always easier to grow.
That does not mean forgettable-zone businesses are bad. Airbnb, TurboTax, and Carvana are all huge businesses. But they each layered on higher-frequency mechanics over years of work. As a solo founder building from scratch, picking a habit-zone problem to start lowers the difficulty by a meaningful amount.
If you are not sure which zone your idea lives in, run the 10-customer ask before building too much. Five-minute interviews now save 18-month detours later.
FAQ
What is the difference between the habit zone and the forgettable zone?
The habit zone covers products where the underlying problem fires daily, weekly, or monthly. Users naturally come back. The forgettable zone covers products where the problem fires less than monthly. Users do not naturally come back. Retention strategy is different in each zone. Habit zone products win by becoming routine. Forgettable zone products win by layering on a higher-frequency hook.
Can a forgettable zone product move to the habit zone?
Not the core problem itself. The underlying need is what it is. But you can add a secondary use case at higher frequency that keeps users engaged. Zillow added the Zestimate. The home-buying problem stays yearly but the Zestimate check is weekly. That moves the overall product engagement into the habit zone even though the core transaction is still rare.
How do I know if I am in the habit zone?
Three signals. First, when you ask 10 customers how often they actually have the problem, the answer is daily, weekly, or monthly. Second, your last-28-day usage histogram shows clustering at 8 or more days. Third, your retention curve flattens within 12 weeks rather than continuing to decay. Two of three usually means habit zone.
What is an XaY habit metric?
The format "X uses in Y days," where X and Y are calibrated to your product's natural frequency. Pinterest tracks Weekly Active Repinners. Slack tracks Daily Active Users with message exchange. The frequency must match the actual problem frequency, not what you wish it were. Setting X or Y too high creates pressure to spam users and leads to churn.
How long should my retention curve take to flatten?
Daily products: 4-8 weeks. Weekly products: 8-12 weeks. Monthly products: 16-24 weeks. Less-than-monthly products: 6-12 months or longer. If your curve has not flattened within these windows, you may be in a different zone than you think, or your nurture is not matching your nature.
What is the most common mistake habit-zone founders make?
Over-sending nurture. Push notifications and emails get fired at a higher frequency than the actual problem. Users tune out. The nurture channel dies. The fix is sending less, not adding more channels. Match nurture to nature.
What is the most common mistake forgettable-zone founders make?
Building habit-zone tactics into a forgettable-zone product. Manufactured daily emails, streak mechanics, gamified check-ins. Users see through it because the core problem does not justify daily engagement. The right move is to find a real higher-frequency use case the user values, not to fake one.
What to do this week
If you do not know which zone you are in, find out. Specific actions:
- Email 10 customers. Ask how often the underlying problem fires for them. Not "how often do you use us." The problem itself.
- Pull a last-28-day usage histogram. Look at the shape, not the average.
- If you are in the habit zone, audit your nurture cadence. Is it matched to nature, or are you sending more than the problem justifies?
- If you are in the forgettable zone, identify one higher-frequency hook you could layer on. What does the user already care about between the rare moments the core problem fires?
For the deeper retention frameworks this connects to (BELT, retention metrics, growth loops), read the BELT framework pillar. To see whether your homepage actually communicates the problem your product solves (which is upstream of retention), run it through the positioning grader.