Engagement and power user loops

Every product has engaged users and unengaged users. The engaged ones come back. The unengaged ones forget you exist.

This is not a small difference. It is everything.

An early-stage founder might celebrate 10,000 sign-ups. But if only 200 of them return in week 2, and only 50 return in month 2, the sign-ups are not users. They are tire-kickers. They are visitors. They will generate zero revenue, zero word-of-mouth, zero expansion potential. The sign-ups are a signal of poor activation, poor product-market fit, or both.

But a founder with 2,000 sign-ups where 400 return in week 2 and 150 return in month 2 has something real. Not because the numbers are larger (they are not), but because the retention curve is steeper. The engaged users are extracting value. The unengaged ones are dropping off fast. This founder can build on the engaged segment. The first founder is wasting time.

Engagement is the bridge between activation and retention. Activation is the first moment of value. Engagement is repeated moments of value, each one pulling the user back. Without engagement, retention is impossible. Without retention, the unit economics cannot work.

This is why engagement is not vanity. It is the canary in the coal mine.

What engagement is — and what it is not

Engagement is not a single metric. It is a compound signal: frequency × depth × loops.

Frequency: how often a user returns to the product. Daily, weekly, monthly? A user who opens the product once a year is not engaged. A user who checks in daily is.

Depth: what the user does when they arrive. Do they perform the core action (the job the product exists to do), or do they just browse? Do they create, collaborate, analyze, or build? Depth separates active users from passive visitors.

Loops: do the actions a user takes create conditions that pull them back? Does collaboration with others create notifications that drive return visits? Does data accumulation make the product more valuable over time? Do network effects make the product better as more people join? Or is each visit a standalone transaction with no compounding?

A product with high frequency but low depth has engaged users doing shallow things. A product with high depth but low frequency has powerful actions that happen infrequently. A product with high frequency and high depth but no loops will plateau: the user will hit a ceiling of value and stop returning. A product with loops grows: the more the user engages, the more the product compounds in value, the more they come back.

Example: A note-taking app where users create notes (depth) and return daily to edit (frequency) but never collaborate or build structures they refer back to (no loops) will have declining engagement over months. A note-taking app where users create notes, invite collaborators (creating network notifications), and build nested structures they reference repeatedly (loops) will have increasing engagement over months.

Same product. Different engagement shape.

Engagement metrics that matter:

• DAU/MAU ratio: what percentage of monthly users return daily? For PLG, 20%+ is good. For SLG, 5-10% is typical (daily use is not expected in enterprise). For community-led, 10-15% is sustainable. Below these thresholds, look for a product, motion, or ICP problem.
• D1, D7, D30 cohort retention: what percentage of Day 1 signups return on Day 1, Day 7, Day 30? These are leading indicators of churn. D1 > 30%, D7 > 50%, D30 > 30% (for PLG) predict sustainable retention.
• Time between sessions: for engaged users, how long do they wait before returning? A power app (Slack, Figma, Notion) has median session intervals of 1-2 days. A utility app (Stripe, Calendly) might be 7-14 days. Increasing session intervals predict churning users.
• Core action rate: what percentage of engaged users perform the core job the product solves for? Not just opening the app. Actually doing the thing. For Slack: sending a message. For Figma: editing a frame. For Stripe: making an API call. If 80% of users open the app but only 20% perform the core action, engagement is fake.
• Loop participation rate: what percentage of engaged users enter a compounding loop (invite collaborators, reference past work, trigger notifications, benefit from network effects)? If 50% of daily active users never invite a collaborator, there is no network effect. If 70% never reference past documents, there is no switching cost. Loops are not automatic. They are optional. Measure whether users actually enter them.

The diagnostic: engagement metrics by motion type

Different motions produce different engagement shapes. Comparing PLG engagement to SLG engagement is a category error. A PLG product needs high daily engagement. An enterprise SLG product needs lower-frequency but higher-depth engagement.

The diagnostic matrix:

The key insight: engagement is not a universal metric. Engagement is motion-specific.

If you are building an SLG enterprise product and optimizing for 40% DAU/MAU, you are measuring the wrong thing and making bad decisions. Enterprise teams do not use tools daily. They use tools weekly or for specific processes. Obsessing over daily engagement will push you to build the wrong product.

If you are building PLG and your D7 is below 50%, you have a real problem. PLG requires habit formation or high-value sessions. If users are not returning in the first week, the activation moment is too late or too weak.

Asymmetric contrast: what engagement looks like by product type

Engagement shapes differ radically by product category. This matters because it tells you what to optimize.

Habit-forming products (Slack, Instagram, TikTok): engagement is daily, shallow, and loop-driven.

• Users return daily because loop notifications pull them back (new messages, comments, recommendations).
• Core action is fast (send a message, like a post, watch a video).
• Each action creates a notification for someone else, pulling them back.
• DAU/MAU > 40%. D1 > 40%. D7 > 65%.
• If your product is habit-forming and your DAU/MAU is 15%, the loops are broken.

Utility products (Stripe, Calendly, Zapier): engagement is event-driven and infrequent but deep.

• Users return when they have a task to accomplish (process a payment, schedule a meeting, configure an automation).
• Core action is complex and high-value.
• There are no notifications pulling users back. The user initiates return.
• DAU/MAU < 10%. But D7 (of users who need the product in a given week) > 60%.
• If your utility product is trying to achieve 40% DAU/MAU, you are building the wrong product.

Leverage products (Figma, Notion, Datadog): engagement is high-frequency and high-depth, with strong loops.

• Users return daily or multiple times per day because they are building, collaborating, and referring back to past work.
• Core action is complex (design a frame, write a document, configure a dashboard) but deeply valued.
• Loops are strong: collaboration pulls in peers, version history creates switching costs, integrations expand use cases.
• DAU/MAU > 25%. D1 > 35%. D7 > 60%.
• If your leverage product has low collaboration loop participation, you are missing revenue (expansions) and competitive defensibility (switching costs).

Social/network products (LinkedIn, Twitter, Discord): engagement is feed-driven and loop-heavy.

• Users return daily because feed algorithms surface new content, connections drive notifications, and social rewards (likes, retweets, recommendations) pull them back.
• Core action is creating content or consuming curated feeds.
• Loops are essential: more connections = better feed = more engagement = network effect.
• DAU/MAU > 30%. D1 > 35%. D7 > 60%.
• If your network product has low loop participation (users creating content but not inviting peers), the network is not compounding.

The mistake: building a habit-forming product with utility metrics. Building an enterprise leverage product with freemium DAU/MAU targets. Building a social product without network loop instrumentation.

Power user loops: how engagement compounds

Not all engaged users are equal. Some users extract more value, expand faster, and become more loyal. These are power users.

Power users enter loops where using the product unlocks more value, creating a compounding effect.

Common power user loop patterns:

Loop 1: Invitation loop. User A creates something valuable. They invite User B to collaborate. User B sees the value, activates faster than User A, invites User C. Each invitation expands the network and increases the value for all participants. Figma, Slack, Notion all depend on this loop.

Loop 2: Data loop. User uses the product. The product accumulates data (usage history, documents, decisions, patterns). This data becomes more valuable over time. The product shows User insights that were invisible after one use but obvious after 100 uses. The user depends on the accumulated data and cannot leave. Stripe (payment history), GitHub (code history), Datadog (historical metrics) all depend on this loop.

Loop 3: Integration loop. User connects the product to other tools. Each integration increases switching costs and makes the tool more central to the workflow. The more integrations, the harder it is to leave. Zapier, Make, and API-heavy SaaS depend on this loop.

Loop 4: Reputation loop. User gains status from using the product well (becoming an expert, earning badges, publishing work, gaining followers). This reputation is portable but depends on the platform. The user is invested in building reputation on the platform and will not leave. Stack Overflow, DEV, and Twitter depend on this loop.

Loop 5: Capability loop. User learns to use the product, unlocking advanced features. Advanced features enable more sophisticated use cases. Advanced use cases create lock-in and expansion opportunity. Design tools (Figma, Adobe), productivity tools (Notion, Roam), and analytics tools (Amplitude, Mixpanel) depend on this loop.

Loop 6: Compliance/rules loop. User embeds the tool into a process, workflow, or organizational system. The tool becomes the system of record. Removing it requires process change and organizational alignment. Salesforce, HubSpot, and compliance/audit tools depend on this loop.

The key insight: power user loops are not automatic. A product can have the capability to support loops but never realize those loops if users do not enter them.

Example: Notion has the capability for data loops (accumulated documents become switching costs), integration loops (connected tools), and collaboration loops (shared workspaces). But a user who creates 1 note and stops has not entered any loop. A user who creates a 500-document knowledge base with 20 team members, 30 integrations, and heavy cross-linking has entered all loops and cannot leave.

Same product. Different loop participation.

This is why “power user” is not just a description. It is a state where the user has entered enough loops that the switching cost is high.

Founder mistakes: the three patterns that destroy engagement strategies

Mistake 1: Mistaking sign-ups for engagement.

A founder celebrates 10,000 signups. They announce it on Twitter. They present it in the board meeting. They think they have 10,000 users.

They do not. They have 10,000 people who got curious and clicked a link.

The real metric is engagement. How many of those 10,000 return in day 3? Day 7? Day 30? If the answer is “500,” then you have 500 engaged users and 9,500 tire-kickers.

This mistake cascades. The founder optimizes for sign-ups. They run ads. They add viral loops. They add referrals. They grow sign-ups to 100,000. But if the engagement rate does not improve, they still have 5,000 engaged users and 95,000 who do not care.

They have built a leaky funnel that looks big from the top and is actually tiny at the bottom. They have wasted capital on acquisition when the real problem was retention.

The diagnostic: compute your sign-up to D7 engagement conversion rate. If you have 10,000 signups and 500 are still engaged in week 2, your conversion is 5%. Your real user count is 500, not 10,000. Until this number improves, scaling acquisition is a waste.

Mistake 2: Optimizing engagement without tying it to retention or expansion.

A founder measures engagement. They see that DAU is increasing. They are happy.

But they do not check whether increasing DAU predicts lower churn. They do not check whether increasing DAU correlates with higher expansion (larger deal size, more seats, higher NRR). They have optimized a metric that feels good but is disconnected from outcomes that matter.

Example: A SaaS founder runs an experiment to increase engagement. They add daily digest emails. They add in-app notifications. They add a notification badge that reminds users of incomplete tasks. DAU goes up 15%. The founder declares victory.

But the next quarter, churn is up. Expansion is down. Why? Because the notifications are driving low-quality engagement: users are opening the app to clear the notification, not to do real work. The notifications are adding friction, not value. High engagement, low outcome.

The diagnostic: for every engagement metric you optimize, measure the correlation to churn and expansion.

• Does increasing D1 retention correlate with lower 90-day churn? If yes, optimize D1. If no, D1 is a vanity metric.
• Does increasing core action rate correlate with higher NRR? If yes, focus on core action. If no, users are not doing the job that drives expansion.
• Does increasing loop participation correlate with longer customer lifetime? If yes, build loops. If no, loops are a distraction.

Without these correlations, you are optimizing in the dark.

Mistake 3: Building power loops in a vacuum without measuring whether users enter them.

A founder has designed the perfect power loop. User A invites User B. User B invites User C. The network compounds. It is beautiful on a whiteboard.

They build it. They ship it. They wait for the network to take off.

Nothing happens.

Why? Because they never measured whether users actually enter the loop. They never asked: what percentage of users invite another user? 5%? 50%? If the invitation loop rate is 5%, the loop is not compounding. It is a feature that 95% of users ignore.

They never diagnosed where the loop breaks. Does the user not know they can invite? Are they not motivated to invite? Does the invitation flow have friction? Is the value of inviting unclear?

They assumed the loop exists. They did not verify the loop exists.

The diagnostic: for every power loop you design, measure:

1. Entry rate: what percentage of engaged users enter the loop? (e.g., % of users who invite at least one collaborator?)
2. Depth: how far into the loop do users go? (e.g., average number of invitations per user, average depth of data accumulated?)
3. Persistence: do users remain in the loop, or do they enter once and exit? (e.g., do users invite once and never again, or do they invite repeatedly?)
4. Correlation to retention: do users in loops have lower churn? If not, the loop is not creating lock-in.

If entry rate < 20%, the loop is broken. Fewer than 1 in 5 users are entering. This is a product problem (incentive, friction, or clarity) not a loop problem.

If persistence is low (users invite once and never again), the loop is not compounding. It is a one-time interaction.

If loop participation does not correlate with lower churn, the loop is not creating lock-in. You have a nice feature, not a moat.

How to design power user loops

Power user loops are not accidental. They are designed. The design has three steps.

Step 1: Identify your loop type.

What kind of value compounds as users engage? Is it network effects (more users = more value)? Is it accumulated data (more data = better insights)? Is it capability (more learning = better output)? Is it integration (more connected tools = more stickiness)?

A single product can support multiple loops. Slack has: invitation loop (growing network), data loop (message history), integration loop (connected apps), and reputation loop (workspace status).

Write down your top 3 candidate loops.

Step 2: Reduce friction to enter the loop.

For each loop, what is the minimal action required to enter it? For the invitation loop, it is “send one invite.” For the data loop, it is “create one document and reference it later.” For the integration loop, it is “connect one tool.”

Make the entry action frictionless. Reduce it to 3 clicks or fewer. Remove required data fields. Pre-fill defaults. Do not ask for permission. Just let them in.

Example: A PLG company wanted to drive the invitation loop. They had a “Team” feature that let users add teammates. But the flow required: (1) click Invite, (2) enter email, (3) set permissions, (4) confirm. Three required fields. Friction.

They redesigned: (1) click Invite, (2) enter email, that’s it. Permissions default to “collaborator.” Users can change later if they want. Friction dropped 70%. Invitation rate tripled.

Same loop. Better entry friction.

Step 3: Create notifications and incentives that pull users back into the loop.

A loop only compounds if it creates a reason for the next return visit.

For the invitation loop, the notification is: “User B accepted your invite.” This pulls User A back to see what User B is doing.

For the data loop, the notification is: “Your document was referenced in 3 other documents.” This pulls the user back to see how their work is being used.

For the integration loop, the notification is: “Your connected tool updated. 50 records synced.” This pulls the user back to see the result of the integration.

For the reputation loop, the notification is: “Your answer got 10 upvotes.” This pulls the user back to build reputation.

The notification does not have to be an email or in-app message. It can be a feature (showing referral count, showing integration status, showing data usage). It can be a dashboard (showing who joined as a result of your invite, showing who used your document, showing reputation points).

The key is: the loop must pull the user back by surfacing the consequence of their prior action.

If you invite someone and hear nothing, the loop is broken. If you create something and no one references it, the loop is broken. If you integrate a tool and there is no visibility of the integration’s value, the loop is broken.

Rules: how to think about engagement and power user loops

Rule 1: Engagement is frequency × depth × loops. If any factor is missing, you have a visitor, not an engaged user.

A user who opens the app daily but only browses (high frequency, low depth, no loops) is not engaged. A user who takes complex actions once a month (low frequency, high depth, no loops) is not engaged. A user with high frequency and high depth but no loops will plateau and churn.

Measure all three. Optimize all three.

Rule 2: Engagement is motion-specific. Do not compare PLG engagement metrics to SLG engagement metrics.

PLG requires daily engagement. SLG requires weekly-to-monthly engagement from core users. Community-led requires episodic engagement. Do not measure all three with the same metric.

Build motion-specific engagement dashboards. Target motion-specific engagement baselines.

Rule 3: Engagement is the leading indicator of churn. High engagement predicts low churn. Low engagement predicts high churn.

Before you build retention programs, retention teams, or discounting strategies, measure engagement.

If your D7 cohort retention is 60%, but your D7 engagement (users returning in week 2) is 20%, you do not have a retention problem. You have an engagement problem. Build engagement before you build retention.

Rule 4: Power user loops are not automatic. You must design them, reduce friction to enter them, and measure whether users enter them.

A loop that exists on a whiteboard but is not entered by 20%+ of users is not a loop. It is a feature.

Before you celebrate a loop, measure: entry rate, depth, persistence, and correlation to churn or expansion.

Rule 5: The engagement curve is as important as the engagement rate.

A company with 50% D1 engagement and 40% D7 engagement has a problem: users are dropping off between day 1 and day 7. Find where they drop off and fix it.

A company with 50% D1 engagement and 50% D7 engagement (no drop-off) has a real insight: the activation moment is strong and the product keeps users engaged.

Plot your engagement curve. The shape tells you whether the product is working.

Rule 6: Engagement without retention is pointless. Engagement without expansion is wasted leverage.

Measure the correlation between engagement and: (1) churn, (2) expansion, (3) NRR.

If high engagement does not correlate with lower churn, you are optimizing a metric that does not matter. If engagement correlates with expansion, you have found a growth lever. Invest there.

What happens next

Once you have built engagement and optimized power user loops, you have a new problem: how do you measure whether engagement is translating into revenue? This is where retention and churn become load-bearing. Engagement is the input. Retention is the outcome. Unit economics is the verdict.

The next chapter walks through the full economics of retention: churn, net retention, and why the shape of your retention curve determines whether the business is viable.