CONSUMER APP / 04User onboarding and app activation for consumer apps in India
The install was the easy part. Week one decides the rest.
User onboarding and activation get a new user to the first moment your app proves its worth, its aha moment, and bring them back the next day. We rebuild sign-up, the onboarding flow, the permission ask and the first-week journey with your product team, and measure it on activation, not downloads.
Run by Raviraj Ramavarapu, who works every account himself.
What is user onboarding and activation?
Onboarding is everything between install and the first time the app does its job: sign-up, the first questions, permissions and the first screens. Activation is the moment a user reaches that value. We design both, then read D1 and D7 by whether users got there.
Sound familiar?
Installs are up. Day 2 is empty.
- 01
Sign-up asks for everything before the app has shown anything.
- 02
The push prompt fires on first open, and most people say no.
- 03
Day-one messages go out on a timer, whatever the user did.
- 04
Nobody has agreed what first value is, so nobody can measure it.
Illustrative. We read D1 and D7 separately for users who reached first value and users who didn’t.
Downloads don’t pay. Activated users do.
The onboarding flow, rebuilt
Eight screens before value. Four after we’re done.
- 01
Ask only what changes a screen or a message.
- 02
One-time codes under your own sender name and DLT header.
- 03
First value before any permission ask, with a soft prompt first.
- 04
Day-one messages that branch on what the user did.
Every extra screen is a user you never meet.
The playbook
Six calls we make on every app.
None of this is theory. It’s what we change first, in this order, because it is where week one usually breaks.
One code, your name
OTPs go out under your own sender ID and DLT header. A code from a name nobody knows reads like spam, and sign-ups stall right there.
Ask only what you’ll use
Every onboarding question must change a screen or a message. If an answer changes nothing, the question goes.
Push after value
A soft prompt first, saying what the user gets, then the system prompt. iOS gives you one system ask. Spend it after first value, not on first open.
Activation is one event
First value is a single tracked event, agreed with product. Week one is built to reach it, and D1 and D7 are read by whether users did.
No empty screens
Empty states hand over one first step, filled in where possible, with an invite wherever the product gets better with two.
Events, not timers
Day-one messages branch on what the user did. Users who acted hear what’s next. Stuck users get the shortest way back.
What is included, end to end
The product and the journey. One owner.
Half of activation is decided on screens your CRM can’t touch. So we spec them, write them and review them with your engineers before they ship. Most agencies stop at the message. We do not.
In the product
- Sign-up with one code, from your own name
- Onboarding questions that shape every later message
- A soft permission ask after first value, not before
- First screens with one first step and an invite
- The event plan that defines first value and activation
In the journeys
- The first-week journey on push, WhatsApp, email and in-app
- Triggers on what they did, never on a timer alone
- Quiet-day nudges after three days without a key action
- Copy for every message and screen, in your voice
- A/B tests, read every fifteen days
Part of the full lifecycle engagement, or on its own if this is the only stage that leaks.
How we build it
Seven steps. One system that compounds.
The same process for every app, starting with the events underneath.
- 01
Audit
Your events, screens and every live message, read end to end against your numbers.
- 02
Capture
The one event that matters for this stage, agreed with product and tracked on iOS and Android.
- 03
Segment
Users split by what they did, not by the day they installed.
- 04
Activate
Screens specced for your engineers, and the journeys built across push, in-app, WhatsApp and email.
- 05
Automate
Journeys run on their own, with caps, quiet hours and fallbacks between channels.
- 06
Experiment
A control group from day one, so every test is read on revenue.
- 07
Compound
Winners become the default, and the next stage starts on the same rhythm.
Results that compounded.
The Healthify in-app funnel, the win-back that grew revenue 79%, and the Mygate cross-sell.
All case studies
CONSUMER APP / 04
CONSUMER APP / 02
CONSUMER APP / 06The first 90 days
Live in ninety days. Read every week.
One plan, run in the open. Every phase has one output, and you see all five numbers every month.
Audit and diagnoseWeeks 1 to 2
Repair and planWeek 3
Launch togetherWeeks 4 to 6
Run and readWeeks 7 to 10
Optimise and expandWeeks 11 to 13
The monthly report
The five numbers you see every month. Illustrative direction, not your data.
- First value reachedShould rise
- Push opt-in rateShould rise
- First key action completedShould rise
- D1 and D7 retentionShould rise
- Active users as a share of installsShould rise

Why Compound Lab
A retention agency that has run app growth.
We ran it in-house.
Raviraj led ecommerce and CRM at Healthify, where the in-app funnel and the win-back journeys were built, and ran CleverTap for Mygate.
Screens and messages, one team.
We spec the screens for your engineers and write every push, in-app and WhatsApp message around them.
Measured on revenue.
Activation, paid conversion and renewals, read against a control group, not opens and clicks.
Platforms
We work in what you use.
Platform-agnostic. We fit your stack, not the other way round. These are the ones we’ve run with revenue on the line.
Questions
Before you book.
What is user onboarding?
Everything between install and the first time the app does its job for the user: sign-up, the first questions, permissions and the first screens. Good onboarding is short, asks only what it will use, and ends in one useful action.
What is the aha moment in an app?
The first moment a user gets the value they installed for, like a first plan built or a first task done with someone else. We find it in your data, name it as an event, and design week one to reach it sooner.
What is a good activation rate?
It depends on what your app counts as activation, so we set your baseline in week one and move it from there. A number borrowed from another category tells you little.
Do you build the screens?
We spec every screen and write every word on it. Your engineers ship it, and nothing goes live until we’ve tested it end to end.
We have no CRM yet. Can we still start?
Yes. Onboarding fixes start in the product. We help you choose a CRM once the numbers call for one, and the CRM comparison tool is a good first look.
What is an onboarding flow?
The screens and messages a new user sees from install to first value. A good onboarding flow is short, asks only what it will use, and ends with the user doing the one thing the app is for.
What is user activation?
The moment a new user reaches first value, tracked as one event agreed with product. Activation rate is the share of new users who get there, usually read within the first day and the first week.
When should an app ask for push permission?
After first value, with a soft prompt that says what the user will get. See our push permission guide.
Do you work with apps outside India?
Yes. We run app retention for consumer and subscription apps in India and worldwide, remotely, with calls planned around your time zone. The work happens inside the platform you already use, such as CleverTap, MoEngage or WebEngage, so where you are based changes the channels and the rules, not the method.
Onboarding,
written down.
The first session, push permission and the numbers to read in week one.

App Retention in India: Tell Users What to Do Next
8 min read
Push Notification Permission in India: When to Ask
7 min read
App Metrics to Track: Daily, Weekly and Monthly
8 min read
Firebase or a CRM for Your App in India? When to Switch
7 min read
Rich Push Notifications: 10 Types With Examples (2026)
10 min readPaywall and trial to paid
ServiceNeed more than one stage? We run the whole lifecycle as one engagement.
See the full lifecycleBook a call
They installed. Let’s get them to day two.
Thirty minutes with Raviraj, not a sales team. Bring your D1 and D7. On the call we look at three things:
- What first value is for your app
- How many screens stand before it
- When you ask for push, and how