How do you increase user engagement without relying on notifications?
Notifications are borrowed attention — you're interrupting users rather than earning their return. The most durable engagement comes from building a product users actively want to come back to, which means solving a real problem so well that returning feels natural. Founders who obsess over push-prompt settings before fixing core value loops are optimizing the wrong variable.
Start with a product that earns the return visit
The fundamental reason users don't come back isn't that you forgot to ping them — it's that the product didn't give them a strong enough reason to return on their own. Paul Graham's point about making something people genuinely want, not just something they tolerate, is the foundation here. A flat usage graph can't be rescued by notification cadence. The question to ask is: what specific outcome does your user get from a session, and is that outcome so valuable they'd seek it out unprompted?
Practically, this means mapping your core loop ruthlessly. What happens in the first five minutes of a session? Does the user leave with something they didn't have before — an answer, a connection, a completed task, a financial transaction, a piece of creative work? If the session outcome is vague or underwhelming, no notification system will compensate. Audit your retention cohorts and find the sessions where users returned three times without being nudged. What did those sessions have in common? That pattern is your real engagement mechanic.
Use direct user contact as an engagement tool, not just a research method
One of the most underused engagement levers for early-stage founders is direct outreach — not automated email drips, but actual one-to-one communication. Paul Graham's observation in 'Do Things That Don't Scale' is that direct engagement with early users produces the highest-quality feedback you'll ever get, and that at scale you'll miss this access. What founders often overlook is that this direct contact is itself an engagement mechanism: a user who receives a personal message from a founder asking how a specific feature worked for them is far more likely to return to the product than one who receives a generic push notification.
This works because it signals that their usage matters to a real person, not an algorithm. Set up a lightweight system: when a user completes a meaningful action (uploads their first project, connects their first integration, closes their first deal inside your tool), send a short personal email from your own address. Ask one specific question. The reply rate on these far exceeds automated sequences, and the users who reply become highly activated. Track whether those users show higher 30-day retention. In most products they do.
Build habitat, not just utility
Facebook's early expansion strategy illustrates a principle that applies far beyond social networks. By creating course-specific content for each university before opening broadly, they made students feel the product was built for them specifically — not a generic tool they happened to use. That sense of 'this is my natural home' drives habitual return without any external trigger. The product itself becomes the cue.
For your product, habitat-building means asking: what would make your user feel this tool belongs to their context specifically? That might mean supporting the terminology, workflow, or integrations specific to one industry before expanding. It might mean letting users customize their workspace in ways that make it feel personally owned. It might mean building features that accumulate user-specific data over time — a history, a record, a portfolio — so that leaving the product means losing something valuable that can't easily be reconstructed elsewhere. Stickiness built on genuine accumulated value is categorically different from stickiness built on dark patterns or notification dependency.
Design sessions that end with a visible hook for the next one
Engagement without notifications requires that the product itself plants the seed for the next visit. Games have understood this for decades: end each session with an unresolved question, a visible next milestone, or a reward that requires a return action to claim. Productivity tools, B2B SaaS, and consumer apps can apply the same principle without feeling manipulative, as long as the hook is tied to genuine value.
Concretely: when a user finishes a task in your product, what do they see? If it's a blank state or a generic dashboard, you've missed an opportunity. Instead, show them the most relevant next action tied to their actual usage — not a generic upsell, but something derived from what they just did. If they just published a report, surface who on their team hasn't reviewed it yet. If they just onboarded their first customer, show the next milestone in the customer journey. The goal is to create a mental open loop that the user carries with them, so that the next session starts in their head before they've opened your app.
Measure intrinsic return rate as your north star metric
Most engagement dashboards conflate notification-driven returns with organic returns, which makes it impossible to tell whether you're building genuine habit or just successfully interrupting people. Separate these in your analytics from day one. Define 'organic return' as any session that was not triggered by a push notification, email, or in-app alert. Track the ratio of organic to triggered sessions over time. If that ratio is declining, you're becoming more dependent on external prompts even as your overall DAU numbers look healthy — a fragile position.
Founders who track intrinsic return rate as their primary engagement metric find themselves making better product decisions. Instead of asking 'should we add another notification type,' they ask 'why did users who came back organically do so, and how do we make that the default path for everyone?' That question leads to product improvements: better session endings, stronger core value delivery, more personalized content surfacing. The metric shapes the behavior. Set it up before you've built any notification infrastructure, and you'll be less tempted to use notifications as a substitute for genuine engagement.
“making students feel the site was their natural home”
— Paul Graham, source
The one thing to do
Audit your product for one concrete outcome users get from every session, then redesign the session ending to surface their most relevant next action — this builds organic return habit without a single notification.
Frequently asked questions
What's the fastest way to improve engagement without adding any new features?
Send personal one-to-one emails to users who completed a key action and ask one specific question about their experience. This alone reactivates dormant users and signals that their usage matters, often more effectively than any in-product change.
Doesn't every successful app rely heavily on notifications?
Many successful apps use notifications, but the best ones use them to surface genuinely time-sensitive value, not to compensate for weak core loops. Apps with high organic return rates — where users come back unprompted — are far more defensible than those dependent on notification permission to stay relevant.
How do I know if my engagement problem is a product problem or a discovery problem?
Look at your most activated users — the ones who return most frequently and organically. If they exist and show a clear pattern of behavior, you have a product that works and a distribution or onboarding problem. If even your best users show declining organic return, the core loop itself needs rebuilding before any other fix will hold.
Can narrowing my target market really improve engagement?
Yes, because specificity creates the feeling of belonging. A product built visibly for one type of user — with their language, their workflows, their specific problems addressed — generates far higher habitual return than a generic tool. Go deep on one segment before broadening, and let that depth compound into engagement.
Sources
- Do Things that Don't Scale — Paul Graham
- Billionaires Build — Paul Graham
- How to Raise Money — Paul Graham
- The Ronco Principle — Paul Graham
- How You Know — Paul Graham