Being Someone's Default App Cuts Churn Up to 6x. Most SaaS Products Never Try to Earn That Spot.
A 2026 study found default apps retain users up to 6x better than merely satisfied ones. Here's how to engineer default status in B2B SaaS.
Every SaaS retention playbook optimizes for the same two things: usage and satisfaction. Get people to log in more, make them happier when they do, and churn goes down. A 2026 study out of the streaming industry just put a number on a third lever that most teams never touch at all — and it turns out to matter more than either of the other two.
Hub Entertainment Research surveyed 1,600 U.S. TV viewers in August 2026 and asked a question most churn research skips: not "are you satisfied," but "is this service the one you reach for without thinking, and what happens to your loyalty if it is." The answer was a gap too large to be noise. Across every service in the study, being someone's default was worth two to six times as much retained loyalty as simply being used by them.
The gap between "used" and "default" is where retention actually lives
The study's framing matters more than the specific services involved. Respondents were asked which service they'd keep if forced to drop every other one. Among all Netflix subscribers, 28% named it as their one keeper. Among the subset who already called Netflix their default — the service they open first, without a decision — that number jumped to 62%. Disney+ showed the same pattern at a sharper angle: 10% of all subscribers would keep it alone, against 61% of subscribers for whom it's the default.
| Service | Would keep it alone — all subscribers | Would keep it alone — default subscribers | Multiplier |
|---|---|---|---|
| Netflix | 28% | 62% | 2.2x |
| Disney+ | 10% | 61% | 6.1x |
Source: Hub Entertainment Research, "Decoding the Default" (2026), fielded August 2026, census-balanced sample of 1,600 U.S. TV viewers ages 16–74.
Notice what isn't in that table: a satisfaction score. These aren't two different quality tiers of customer. They're the same subscriber pool split by one behavioral fact — whether the choice to use the service is still an active decision or a settled one. Nobody in the "default" column is more satisfied on average than the people in the "all subscribers" column. They're just not re-deciding every month.
Why "default" survives a cancellation urge that satisfaction doesn't
Satisfaction and engagement both get re-evaluated constantly, usually without the customer noticing they're doing it. Every slow page load, every price email, every comparison a colleague mentions in Slack is a tiny re-vote on whether a tool is still worth keeping. A satisfied customer is still, every single day, a customer who could decide otherwise.
A default customer has mostly stopped voting. The decision got made once, early, and then the account accumulated enough personal investment that revisiting it stopped feeling worth the effort. That's the mechanism behind the study's second finding: 68% of respondents said they'd personalized their default service through a profile, watchlist, or saved preferences — 79% among viewers under 35. Personalization isn't a loyalty feature bolted on after the fact. It's the thing that converts a choice into a default in the first place, because every saved setting is a small cost against ever leaving.
Source: Hub Entertainment Research, "Decoding the Default" (2026).
And once the default status sets in, it's durable: 69% of respondents said they'd kept their current default service for more than two years. That's not a number about content catalogs or feature sets. It's a number about how rarely people reopen a decision once they've stopped actively making it.
The B2B version: the tool that's open before you decide to open it
None of your customers are picking between Netflix and Disney+, but every one of them is running the same decision loop between your product and whatever else sits in their stack. For a project management tool, the default competitor isn't necessarily another project management tool — it's Slack threads, a shared spreadsheet, or email. For a CRM, it's the rep's own memory and a notes app. Losing default status in B2B SaaS rarely looks like a dramatic switch to a competitor; it looks like a slow drift back to the ad hoc tool that was never fully replaced, which is exactly the kind of quiet disengagement we've covered in zombie accounts — the account stays "active" on your billing report long after it's stopped being anyone's default anything.
Three mechanisms explain why default status forms in B2B SaaS the same way it does in streaming:
1. First-opened position
The product someone opens before deciding what to do next captures every decision that follows. A CRM that's open on a rep's second monitor all day becomes the place deals get logged, not just the place they're supposed to be logged. A tool that only gets opened when someone remembers the data lives there competes with memory itself, and memory usually loses the race to a faster workaround.
2. Personalization as a sunk switching cost
Saved views, custom fields, dashboard layouts, keyboard shortcuts learned by muscle memory, Zapier or native integrations wired to other tools — none of these are retention features in the traditional sense, but all of them raise the cost of leaving in a way a price increase can't replicate. A customer who's built nine saved filters and three dashboards isn't staying because they re-evaluated your pricing against a competitor's. They're staying because rebuilding nine saved filters elsewhere is a cost nobody schedules time for.
3. Being the system other systems route through
The stickiest B2B tools aren't the ones used most often in isolation — they're the ones other tools and workflows are built to depend on. A product that other integrations, Slack notifications, and approval chains route through becomes infrastructure rather than a vendor choice, which is the same dynamic we've written about in terms of platform defensibility: what breaks for the customer at the moment they consider leaving is the real measure of how deep the default status runs.
Measuring default status without running a customer survey
You can't lift Hub's exact survey question wholesale — "which tool would you keep if forced to drop all others" is a strange question to put in a B2B NPS form, and most customers won't answer it honestly in an in-app prompt either. But three behavioral proxies get you most of the way there without asking anyone anything directly.
- Session-order rate. Of a user's work sessions in a day, what fraction start in your product versus start elsewhere and arrive via a notification or a deep link? A product that's mostly arrived-at secondhand is a utility, not a default.
- Configuration depth per account. Count saved views, custom fields, integrations, and dashboards per active user, and track the trend. A flat or declining configuration count on an otherwise "active" account is an early signal that personalization — and with it, default status — never took hold.
- Stickiness ratio, as a lagging check. DAU/MAU won't tell you if you're the default, but a rising ratio over time is consistent with it and a falling one is inconsistent with it, which makes it a useful sanity check against the other two. Our stickiness ratio calculator turns your raw DAU and MAU counts into that read directly.
None of these replace a direct relationship with the account — they're instruments for finding accounts worth a direct conversation, the same way we've described using a behavioral threshold to find zombie accounts before they cancel. An account with a falling session-order rate and flat configuration depth is losing default status months before anyone there opens your cancellation flow.
Engineering default status on purpose instead of hoping it happens
Most onboarding is built to get a user to a first success moment and stop there. Earning default status takes a second, deliberate phase after that: get the user to personalize the product before they've had a reason to compare it against anything else. Prompting a new user to build their first saved view, connect their first integration, or set a dashboard layout in week one — while there's still no competing habit to displace — converts a product from "something I tried" into "the thing I open" far more reliably than waiting for usage frequency alone to build the habit. That window closes fast; the same early period is covered in more depth in our guide to early-lifecycle churn, and it's worth treating default-status formation as its own onboarding milestone, tracked separately from activation.
It's also worth being honest about what this means for retention offers. A discount or a pause doesn't restore default status to an account that already lost it — those levers work on price-sensitive and satisfaction-driven churn, not on an account that's quietly drifted back to a spreadsheet. If a cancelling customer's real answer is "we stopped making you the first thing we open," no coupon fixes that, and a cancellation survey that only offers price and feature-gap options will never surface it. That's worth adding as its own option the next time you review what your exit survey actually asks, next to the reasons we cover in why customers cancel — because a customer honest enough to say "we just stopped opening it first" is handing you the earliest version of a warning that a satisfaction score would have missed entirely. CancelFlow is built to capture exactly that kind of specific, honest answer at the one moment a subscriber is paying enough attention to give it to you.
Frequently asked questions
What does it mean for a product to be a customer's 'default'?+
A default is the specific tool someone reaches for first, without comparing it to alternatives, for a given job — the project tracker they open before checking email, the CRM a sales rep logs into automatically rather than deciding to. It's a behavioral status, not a satisfaction score. A customer can rate a product highly on a survey and still not treat it as their default, and the reverse also happens: people keep tools as their default that they'd rate only average, simply because the switching decision never gets made.
How is default status different from high engagement or satisfaction?+
Engagement measures how much someone uses a product. Satisfaction measures how they feel about it. Default status measures whether using it is a decision they still make or one they stopped making a while ago. Hub Entertainment Research's 2026 'Decoding the Default' study found this distinction predicts retention far better than either of the other two on its own: among Disney+ subscribers who called it their default, 61% would keep it if forced to pick one service, versus just 10% among all Disney+ subscribers — a 6x gap that satisfaction scores alone don't explain.
Can a B2B SaaS product actually measure whether it has default status with a customer?+
Not directly from a survey, but you can get close with behavioral proxies. The strongest one is session-order: what fraction of a user's work sessions start with your product versus start somewhere else and route to you later. A second is personalization depth — profiles, saved views, custom dashboards, integrations configured — since default tools accumulate configuration that a comparison tool never gets. A rising DAU/MAU stickiness ratio is a weaker but easier-to-pull proxy for the same underlying habit; our <a href="/tools/stickiness-ratio-calculator">stickiness ratio calculator</a> turns raw DAU/MAU numbers into that read without a data team.
How fast can a new customer form a default habit with a product?+
There's no universal number, but the window is narrow and front-loaded. The behavioral pattern in the Hub study — 69% of respondents had kept the same default source for over two years — only happens because the default decision gets locked in early and then stops being revisited. For SaaS, that locking-in window overlaps almost exactly with the first 90 days of a subscription, the same period covered in our piece on <a href="/blog/early-lifecycle-churn">early-lifecycle churn</a>: whatever habit and personalization state exists by day 90 is close to what you're stuck with for the life of the account, for better or worse.
Stop losing subscribers today
One script tag. One function call. A live cancellation flow in under 10 minutes.
Start free trial →