Type: Independent product-strategy case study (self-initiated exercise, not a client engagement) · Domain: Micro-drama streaming · Retention & monetization design · Growth loops
Company context: KuKuTV is a serialized micro-drama streaming app inside the KuKu FM ecosystem, competing in India's Tier-2/3 mobile-first micro-drama market against Story TV, ReelSaga, Moj/QuickTV, Amazon MiniTV, and attention-competitors like YouTube Shorts and Pocket FM.
The brief: turn first-episode intent into habitual, monetizable engagement. Baseline: 12% multi-show engagement, ₹600 realized LTV/cohort user, 15 daily active minutes — target 30% / 2-3x ARPU / 45 minutes.
Three compounding failures, all traced to one root cause — post-episode, users lack a low-friction, high-relevance next action:
Economics: CAC ₹65–80, realized LTV ₹600, LTV:CAC ~7.5:1 (target 10:1), CAC payback >6 months (target <6).
JTBD (primary): "When I finish an episode and I'm still emotionally engaged, I want the platform to surface the most compelling, low-friction next thing — without cognitive friction or payment distrust."
Three strategic pillars, each mapped to a RICE-scored initiative:
| Pillar | Initiative | RICE | Expected Impact |
|---|---|---|---|
| Continuity UX | 4-option end-of-episode modal (Preview / Watch-with-ad / Ad-Lite trial / Save-Share) | 224 (highest) | +25–30% second-show starts |
| Smart Monetization | Freemium → Ad-Lite (₹39/mo, regional floors ₹29–99) → Premium ladder | 63 | Free→paid conversion 15%→35% |
| AI-Powered Discovery | Embedding-based narrative-similarity engine (not genre tags) | 30 (long-term bet) | Sustained multi-show engagement growth |
Prioritization used MoSCoW (Must: Continuity Modal, Layered Monetization, AI Discovery) layered on top of RICE, plus an Impact-vs-Effort matrix confirming the Continuity Modal as the highest-priority, lowest-effort move.
Experimentation framework (pre-registered, three parallel tracks):
Instrumentation: a canonical event schema (install → episode_start → episode_end → modal_action → conversion) feeding Kafka/PubSub → BigQuery/Redshift, because none of the above is measurable without it — this shipped in Week 1, before any experiment launched.