At LiveKeeping, PRO+ users generated E-Way Bills in Tally rather than in the app — a 17:1 adoption gap hiding in white noise. A deep-dive diagnosis mapped the real workflow and produced a C-suite narrative so clear it changed the product roadmap.
A compliance SaaS with 50K+ Indian SMBs lives or dies on where merchants actually do bookkeeping. If a critical transaction gets generated in Tally, a native feature is silently dead — and the negative is invisible in a happy-path dashboard.
The set-up
- Native e-way bill generation exists; it's a top-of-funnel "PRO+ feature"
- Analytics showed usage, but nothing about substitute behavior
- Support tickets hinted at Tally; nobody quantified it
The two-step diagnosis
Step 1 — Workflow tracing. We interviewed and instrumented a handful of merchants and discovered the real pattern: generation happens where the invoice lives, which is Tally for a majority.
Step 2 — Quantify the gap. We measured in-app vs external (Tally) generation — and saw a 17:1 preference gap in the revenue-month sample.
The same logic produced a 19:1 E-Invoice gap — the native e-invoice module suffered the identical gravity problem.
What the executive narrative changed
- The roadmap pivot. If adoption is a workflow problem, not a feature problem, the fix is middleware (data flows via Tally natively) — not a principed sub-release.
- C-Suite escalation. The narrative (17:1, 19:1) got an audience in a week; data cut through.
The result
- 17:1 technical-use gap uncovered and reported
- 19:1 e-invoice gap in the same study
- C-Suite escalation funded a different path to adoption
- −58% rejection rate in the reopen era as rejection reasons were tracked
What I'd do differently
- Run the workflow trace before the honeymoon. We found Tally-origin volume after the feature demo.
- Report the two numbers together. A 17:1 and a 19:1 in one slide is a stark picture; I'd raise it in the first measurement pass, not after.
Read the whole story in the compliance gap case study. For more on metrics that matter in this exact problem space, see my notes on product management metrics.