Most Growth Frameworks Tell You What to Build. BELT Tells You What Will Last.
Every SaaS founder has a list of features to build, channels to try, and experiments to run. The problem isn't a lack of ideas. The problem is that 80% of those ideas won't matter in 12 months.
You ship a feature. Usage spikes for two weeks. Then it flatlines. You launch on a new channel. First month looks great. Then it dries up. You solve a customer problem. They churn anyway because the problem only happened once.
BELT is a framework we developed at Growth Pigeon to test whether a product decision will compound or evaporate. We use it in every clarity map teardown we publish. It's four questions that separate durable growth from temporary spikes.
What BELT Stands For
Behavior. Enduring problem. Lock-ins. Transient distractions.
Each letter tests a different dimension of product durability. A product that scores well on all four is built to compound. A product that fails on even one is leaking growth somewhere, even if the metrics look fine today.
B: Behavior
The question: Does your product attach to an existing behavior, or does it require users to create a new one?
Products that build on existing behaviors grow faster and retain better than products that ask users to change. This isn't a theory. It's observable in every product category.
Instagram built on the behavior of taking photos with your phone. People were already doing it. Instagram just gave them a place to share. Slack built on the behavior of messaging coworkers. People were already doing it in email and chat. Slack just made it better.
Contrast that with products that require new behaviors. "Check your dashboard every morning." "Write a weekly retrospective." "Tag your tasks with energy levels." These features might be valuable, but they require the user to remember to do something they weren't doing before. Most won't.
When we analyzed Publy.me in a clarity map, we found their strongest card was behavior attachment. The product hooks into git push, something developers do multiple times a day. No new behavior required. No dashboard to check. No content to write. You push code and marketing happens. That's why the behavior score was so high.
Contrast that with a tool that asks developers to "write a build-in-public update after each commit." Same outcome, completely different behavior requirement. One compounds. The other gets abandoned in a week.
How to Score Your Product on Behavior
- Strong: Product activates during something the user already does daily (messaging, browsing, committing code, checking email)
- Medium: Product requires a small new behavior but attaches to an existing trigger (e.g., "after your standup, check this board")
- Weak: Product requires the user to remember to open it, check it, or do something they weren't doing before
If you're weak on behavior, you have two options: redesign the product to attach to an existing behavior, or invest heavily in notification-based re-engagement (which is a band-aid, not a fix).
E: Enduring Problem
The question: Will this problem still exist after you solve it once?
Some problems are enduring. They come back. Repeatedly. Your inbox fills up every day. Your team needs to coordinate every week. Your customers need support every month. Products that solve enduring problems have natural retention because the problem regenerates the need.
Some problems are one-time. You need to build a website. You need to migrate a database. You need to design a logo. Products that solve one-time problems have a structural retention challenge. Once the job is done, the user has no reason to come back.
This doesn't mean one-time problem products can't succeed. But they need a different business model (higher price, marketplace dynamics, or adjacent recurring problems).
When we analyzed own.page, we found the enduring problem was identity fragmentation. Every new social platform, career change, or side project creates more scattered profiles that need consolidating. The problem literally gets worse over time. That's a strong enduring problem score.
If own.page had positioned as "build your personal website" instead, the enduring score would be weak. You build it once. You're done. But "keep your online identity consolidated as your life changes" is a problem that regenerates quarterly.
How to Score Your Product on Enduring Problem
- Strong: The problem regenerates naturally (daily, weekly, or with each new project/quarter/hire)
- Medium: The problem recurs but infrequently (annually, or triggered by specific events)
- Weak: The problem is solved once and doesn't come back
If your problem isn't enduring, find the adjacent enduring problem. "Build a website" isn't enduring, but "keep your website updated as your business evolves" is. Same product, reframed as an ongoing relationship instead of a one-time transaction.
L: Lock-ins
The question: What makes switching away from your product emotionally or practically costly?
Lock-ins aren't about making it hard to leave. They're about making it natural to stay. The best lock-ins are ones the user creates themselves, often without realizing it.
There are several types:
- Data lock-in: Your history, preferences, and content live in the product (Notion, Evernote, any CRM)
- Identity lock-in: The product becomes part of how you see yourself or present yourself (your own.page URL in your bio, your Linear workspace)
- Workflow lock-in: The product is embedded in how you work, and removing it means changing your process (Slack, GitHub, Figma)
- Social lock-in: Other people expect you to be on this product (WhatsApp, Slack channels, shared Notion spaces)
- Learning lock-in: You've invested time learning this tool, and switching means learning a new one (Vim, Excel, Photoshop)
The strongest lock-in is usually identity. When someone puts your product URL in their Twitter bio, they're not just using your tool. They're telling the world "this is part of who I am." That's incredibly hard to switch away from.
How to Score Your Product on Lock-ins
- Strong: Multiple lock-in types active. Switching would require changing identity, migrating data, AND updating workflows
- Medium: One strong lock-in type. Users would lose something meaningful by switching, but could do it in a weekend
- Weak: No meaningful switching cost. User could replace you with a competitor (or a spreadsheet) tomorrow
If your lock-in score is weak, design for it intentionally. Add features that accumulate user-created value over time. Make the product more useful the longer someone uses it. Create reasons for users to share their product presence publicly.
T: Transient Distractions
The question: What should your product deliberately NOT do?
This is the most counterintuitive part of BELT. Most frameworks help you decide what to build. This one helps you decide what to ignore.
Transient distractions are features, markets, or trends that look appealing right now but would dilute your core value if you chased them. They're the "while we're at it" features. The "our competitor just launched this" reactions. The "a big customer asked for this" one-offs.
Every feature you add makes your product slightly harder to understand, slightly harder to onboard, and slightly less focused. The cost of each individual feature is small. The cumulative cost is death by a thousand cuts.
In our Publy.me clarity map, we identified several transient distractions: adding a content editing dashboard, building analytics for post performance, supporting manual post creation. Each of these sounds reasonable. Each would break the core promise of "you never have to think about marketing." The moment you add a dashboard, the user has to check the dashboard. The zero-effort promise evaporates.
How to Score Your Product on Transient Distractions
- Strong: Clear "what we don't do" list. Team can articulate why specific features were rejected. Product has stayed focused for 6+ months
- Medium: Some feature creep happening but core is still clear. Team debates new features but usually defaults to focus
- Weak: Product roadmap is driven by competitor moves and customer requests. Core value proposition is getting buried under features
If you're weak here, do a feature audit. List every feature in your product. For each one, ask: "Does this reinforce the core promise or dilute it?" Be honest. Cut or hide anything that dilutes.
Using BELT: A Practical Example
Let's say you're building a habit tracker app. Here's how you'd score it:
Behavior: Medium. Users need to create a new behavior (logging habits daily). But you can attach it to an existing trigger (morning alarm, coffee routine). Design the product to activate at an existing trigger point.
Enduring Problem: Strong. The desire to build better habits is enduring. It regenerates with every New Year, every life change, every moment of self-reflection. People don't solve this once and move on.
Lock-ins: Medium to Strong. Streak data is a powerful lock-in. Nobody wants to lose a 90-day streak. Historical data creates a personal record they can't take elsewhere. But if you don't design for streaks and history, lock-in is weak.
Transient Distractions: High risk. Social features, gamification, AI coaching, integration with fitness trackers, mood tracking, journaling. All of these sound great. Most would dilute the core experience. A habit tracker that tries to be a life management platform loses to the one that just makes logging habits dead simple.
BELT verdict: Strong potential, but only if you resist the temptation to expand scope. The winning move is to be the simplest, most reliable habit tracker. Not the most feature-rich one.
BELT in Your Clarity Map
Every Growth Pigeon clarity map includes a full BELT analysis specific to that product. We don't just score each dimension. We identify the specific behaviors to attach to, the specific enduring problems to center on, the specific lock-ins to build, and the specific distractions to avoid.
If you want a BELT analysis for your product, request a clarity map. We'll tear apart your positioning, apply BELT, and give you a clear strategic recommendation.
The Bottom Line
Growth hacking is about finding the next spike. BELT is about finding the next compounding loop. Spikes fade. Loops compound.
Before you build the next feature, launch the next campaign, or chase the next channel, run it through BELT:
- Does it attach to an existing behavior?
- Does it solve an enduring problem?
- Does it create meaningful lock-ins?
- Is it a real priority, or a transient distraction?
If it doesn't pass all four, it might still be worth doing. But it won't compound. And in SaaS, the things that compound are the only things that matter.
Further Reading
- 10 SaaS Positioning Mistakes That Silently Kill Your Growth - The most common positioning errors we see in teardowns
- own.page Clarity Map - BELT applied to a personal page builder
- Publy.me Clarity Map - BELT applied to an automated developer marketing tool
- All Clarity Maps - Every positioning teardown with full BELT analysis