Skip to content
Nitesh Tiwari
Back to Work

Fixing the path to first value

Only 12% of new users played a game on day one.

Onboarding Funnel Redesign · Witzeal Technologies · Real-money gaming · Product Manager · May 2022 – Mar 2023

A 12.2% Day-7 number looked like a retention problem. The funnel said activation. Five changes to the first 60 seconds, tested against a 30% control.

Day-7 retentionMeasured

12.2%control25.4%treatment

+13.2 percentage points

~50K users · ~3 weeks · 30/70 controlled rollout

The redesigned onboarding arm recorded 13.2 percentage points higher Day-7 retention than the concurrent control.
  • Five onboarding changes shipped together, including a ₹15 free-game incentive; causal isolation was limited.
  • Day-7 definition and statistical significance were not recorded.
How it was measured: Day-7 retention

Controlled rollout · 30/70 · ~50K users · 3 weeks

Definition not recorded: the original experiment record doesn't capture the denominator.

Control (existing onboarding) against treatment (redesigned), concurrently. The treatment bundled five changes, one of them an incentive, so the lift belongs to the bundle. Statistical significance wasn't recorded.

D0 gameplay · supportingReported

12% to 33%

Comparison basis not recorded.

12% is the pre-redesign baseline; whether 33% was read against the concurrent control is not recorded.

01Context

Growth for a real-money gaming platform.

I owned growth, onboarding, monetization and lifecycle. On this problem: the call to read it as activation, the funnel analysis and CleverTap dashboards, and the product and technical diagnosis of the OTP and API friction.

Company
Witzeal Technologies
Role
Product Manager
Period
May 2022 – Mar 2023
Tools
CleverTap funnels and dashboards

02Signal

Two numbers, both around 12%.

Read quickly, a 12.2% Day-7 number is a retention problem, and it points toward reminders, rewards and re-engagement.

  • 12%

    of new users played a game on day one (D0). Reported

  • 12.2%

    Day-7 retention. Measured

03Diagnosis

The drop wasn't motivation. It sat before the first game.

I traced it through the onboarding funnel and through the OTP API's success and failure rates and delivery time. Most new users were lost before they ever reached a game, in signup and OTP verification: an activation problem, not simply a retention one. Step-level drop-off rates weren't kept in the record, so none are shown.

  1. Read as retention

    Where the loss is
    Players drift away over the first week
    What you build
    Reminders, rewards, re-engagement campaigns
  2. Read as activation· What the funnel showed

    Where the loss is
    Only 12% of new users play on day one
    What you build
    Time to the first game, in the first session
The numbers are documented; the contrast between the two readings is product reasoning.

04User insight

Product reasoning

Players weren't rejecting the game. Most never reached it.

There are no user interviews behind this case, so the insight comes from behavior: the value moment was the first game, and only about one in eight new users got there on day one. Everything before it was cost without value.

05Hypothesis

Product reasoning

Get new players into a game faster, and more of them come back.

If
new users reach their first game faster, with less signup and OTP friction
Then
more of them play on day one and are still around on Day 7
Measured by
D0 gameplay and Day-7 retention, treatment against a control on the existing onboarding

06Options

Product reasoning

Pay to bring them back, or get them to the game.

  1. Option A

    Bring players back later

    Works because

    Familiar levers: reminders, rewards, re-engagement campaigns.

    Falls short because

    Pays to re-engage people who never reached the product's value.

  2. Option B

    Get players to a game before they leave

    Chosen

    Works because

    Removes the cost before the value moment, in the first session.

    Costs

    Needs product and API work, not just a campaign.

07Decision

Five changes, all aimed at the first game.

Fix the first 60 seconds before paying to bring players back.

The path to a first game, and what changed at each stepDocumented
  1. 01

    Signup & login

    Simplified

  2. 02

    Email

    Fetched automatically

  3. 03

    OTP

    Auto-read

  4. 04

    First games

    First 3 free

  5. 05

    Gameplay

    Live tutorial

08Trade-off

Free games as a bridge to first deposit, not an open-ended discount.

The goal was to extend early engagement toward Day 7 and drive at least 5 game plays. The free games were bounded: three entries, then the first deposit.

Onboarding bonus per user
₹15
Onboarding bonus per user
₹5 free entry × first 3 games
Minimum first deposit
₹20
Minimum first deposit
Game plays: the early-engagement goal
5+
Game plays: the early-engagement goal
The economics are the design; deposit conversion wasn't measured in the original analysis.

09Experiment

30% kept the old onboarding. 70% got the new one.

10Result

More new players in the treatment arm were still playing on Day 7.

The redesigned onboarding arm recorded 13.2 percentage points higher Day-7 retention than the concurrent control. The positive direction continued into the first month (M0); later figures aren't available, so none are shown.

The figure at the top of this page carries the full evidence: control and treatment, both caveats, how it was measured, and D0 with its unrecorded comparison basis.

11Business link

Activation was measured. The money it should lead to wasn't.

In a real-money game, a retained player only pays off once they deposit. The test measured the first two links of that chain.

  1. Measured

    D0 gameplay

  2. Measured

    Day-7 retention

  3. Not measured

    First deposit

  4. Not measured

    Net gaming revenue

The experiment measured activation and retention; the original analysis did not establish the downstream revenue impact.

12Limits

One thing the test could not isolate.

The rollout shipped five changes together, and one of them was an incentive: ₹15 of free games per new user. The test shows the bundle worked. It cannot show how much of the lift came from removing friction and how much from the free games.

That distinction matters, because the argument of this work is to fix the product before paying for engagement. Shipping the bundle was the faster path to a result; the price was attribution.

  1. Friction

    • Simpler signup and login
    • Email fetched automatically
    • OTP auto-read
  2. Incentive

    • First 3 games free (₹15)
  3. Guidance

    • Live gameplay tutorial
The five changes, by the lever each one pulls. They shipped as one treatment.

13Isolate

Product reasoning

What I would isolate today.

A proposed design, not a test that was run. Each arm answers one question the bundle couldn't.

  1. ControlNo changes

    The baseline, on the existing onboarding

  2. AFriction fixes

    What removing friction does on its own

  3. BFree games

    What the incentive does on its own

  4. CFriction fixes + Free games

    Whether the incentive adds anything once friction is gone

  5. DFriction fixes + Free games + Tutorial

    The shipped bundle, as the reference

Signup, email and OTP stay one arm because they act on the same step. Every extra arm needs its own sample, which is the trade-off against the speed of shipping the bundle. If arm A holds most of the lift, the free games can shrink.

14Learning

Retention is won before the retention metric.

Retention work often starts upstream of anything labelled retention: in the first session, and sometimes in OTP verification.