Product →Examples →FAQ →All solutions →About →
Business problemsHow it worksRolesOrganizations
Scopeout for engagement

Get users back, and back again.

Weekly active use is the number that predicts everything else. Scopeout finds which moments bring people back, tests the ones that do, and keeps score.

Weekly active use · day-2 digest test
control · 38%variant · 46%+8 pts · promote

Habits are built one loop at a time

The way your best growth team would do it: find the moment, form a hypothesis, test it, learn. Scopeout runs that loop every week.

Find the moments that predict return

Analyze reads sessions to find what week-one users who came back did differently from those who did not.

Week-one actions that predict return in week four
Invited a teammate3.1x
Created a second report2.2x
Connected a data source1.8x
Viewed the dashboard1.1x
So the nudgetargets invites, not dashboards

Test the nudge, not the guess

Reminders, digests, in-product prompts and empty states, each tested against control on return rate.

A · reminder
B · weekly digest
C · in-app prompt

Keep the ones that work

Winners promote, losers are recorded, and the outcome library tells you what moves engagement on your product.

Engagement · this quarter
Digest on day 2+8 pts WAU
Invite prompt in week 1+5 pts
Streak badgeno change · dropped
Nextsecond-report nudge

The same loop, your metrics.

The method does not change by business model. The evidence, the tests and the number that has to move do.

B2B SaaSweekly active teams

The week-one actions that predict return, digests and in-product prompts.

E-commercerepeat purchase

Post-purchase moments, replenishment reminders, browse-to-buy frequency.

Consumer appDAU / MAU

Push timing and content, streaks and habits tested on D7 and D30.

Marketplacesessions per buyer

Saved searches, alerts and re-engagement on both sides of the market.

Built for engagement work

Return rate · by cohort
Day 764%
Day 1451%
Day 2838%
Watchedagainst baseline, per segment

Return-rate cohorts

Day 7, 14 and 28 return by cohort and segment, watched against baseline.

Aha moment, found

Invite a teammate in week one → 3.1x return

From9,400 sessions
Segmentnew teams
Test a nudge

Aha moments, found

The actions that separate retained users from churned ones, ranked by lift.

Digest
Reminder
Empty state

Nudges on your system

Digests, reminders and prompts drawn on your components and tested where users see them.

Engagement playbook
Worksdigest, invite prompt
Does notbadges, streaks
Segmentteams of 2+
Runs6

Engagement playbook

What worked for which segment, written down for the next quarter.

Start from a prompt.

Diagnose

“Which actions in week one predict a user coming back in week four?”

Run this when my batch opens →
Test

“Propose three nudges to bring dormant weekly users back, ranked by expected lift.”

Run this when my batch opens →
Review

“What moved weekly active use this month, and why?”

Run this when my batch opens →

Questions, answered.

What counts as engagement here?

Whatever you define: weekly active use, a core action per week, or time to second session. Set it once and every loop measures against it.

Can it send the nudges?

It drafts and tests them; delivery runs through your email or in-app messaging tool.

How is this different from a lifecycle tool?

A lifecycle tool sends. Scopeout finds the moment worth sending about, proves it moved the number, and records why.

Stop running the business. Start directing it.

Join the waitlist

Private beta. We onboard teams in small batches. Or contact us.