TL;DR:
- Dezerv leveraged Digia Engage to decouple UI updates from app releases.
- Growth teams shipped experiments independently, without engineering tickets.
- A single SIP-screen bottom sheet generated $250K+ in digital collections.
- The experiment was built and launched entirely from Digia’s dashboard.
- No app release was required to deploy the nudge.
- The case explores what changed, why SIP screens worked, and how fintech teams can overcome dev-queue bottlenecks.
- All figures and quotes are sourced from Digia’s published content, with no unsupported details added.
About Dezerv
Dezerv brings mutual funds, stocks, NPS, and fixed deposits into a single wealth dashboard, offering a real-time unified view of a user's assets alongside expert-led portfolio review, and the platform is fully licensed by SEBI, APMI, and AMFI, with bank-grade security and ISO 27001 certification. This regulatory context matters directly for the story that follows: a wealth management app operating under SEBI's compliance regime cannot treat in-app changes casually, which makes the specific problem Dezerv's growth team faced, and the specific way it was solved, more consequential than it would be for a lower-stakes consumer category.
The Problem: A Growth Team Blocked Behind a Release Cycle
Digia helped Dezerv modernize its PMS app by decoupling the UI from release cycles, enabling faster updates. Before this change, any in-app experiment, a new nudge, a new message, a new placement, required the same engineering path as a core feature build: a development ticket, a review cycle, and an app store release before anything could reach a single real user.
As Sripad Panyam at Dezerv put it: "We're not as blocked by the dev team for small experiments anymore, so we're able to move faster and try things out more often." The word "small" is worth sitting with. The problem was not that Dezerv's engineering team was slow or unwilling. It was that the release pipeline treats every UI change identically, regardless of size, which means a two-line nudge and a major feature rebuild were both queued behind the same review and release process. For a growth team, this means the cost of testing a small idea is functionally the same as the cost of shipping a large one, which in practice means most small ideas never get tested at all.
The Solution: Server-Driven UI on a Regulated App
Dezerv accelerated experiments and growth using Digia's Server-Driven UI, enabling faster updates and smoother user experiences. Server-driven UI means the app's in-app screens, messaging, and placement logic are controlled from a backend rather than compiled into the app's binary, which is the specific architectural shift that let Dezerv's growth team build and modify in-app experiences directly, without each change requiring a new build submitted to app store review.
For a SEBI-regulated fintech app specifically, this is not a trivial technical detail. It means compliance-relevant screens and disclosures can still be reviewed and controlled with the same rigor a regulated product requires, while the day-to-day experimentation layer, testing a specific nudge's copy, timing, or placement, operates on a faster, independent cycle that does not force every small test through the same review gate as a core product change.
The Result: A Single Nudge on SIP Screens
Dezerv drove $250,000 or more in new digital collections from a single bottom sheet nudge placed on SIP screens, built and shipped from the Digia dashboard without an app release. This is the specific, headline result publicly documented for this engagement, and it is worth being precise about what it actually demonstrates, beyond the raw figure.
Why the SIP screen specifically. A Systematic Investment Plan screen is where a user is either actively setting up or actively reviewing a recurring investment commitment, which means it is a moment of genuine, active financial decision-making, not a passive browsing screen. A bottom sheet nudge placed here is not competing for attention against an unrelated task. It is appearing at the exact point where a user is already thinking about the specific category of decision the nudge is meant to influence, which is the same contextual-placement principle documented across other case studies in this series: a message that arrives when a user's own behaviour has already signalled relevant intent consistently outperforms the same message shown to a broader, less targeted audience.
Why a bottom sheet specifically. A bottom sheet is a non-blocking overlay that a user can dismiss with a downward swipe, distinct from a full-screen interstitial that demands an explicit action before the user can continue. For a regulated financial product specifically, this format choice matters: a nudge a user can easily ignore respects the trust constraint that governs financial apps generally, since an element that cannot be easily dismissed reads as pressure rather than assistance, particularly on a screen where a user is making a genuine financial commitment.
What "built and shipped without an app release" actually means here. The nudge's existence, its placement, its copy, and its timing were all configured through Digia's dashboard rather than requiring a developer to write and ship new code for this specific experiment. This is the direct, concrete payoff of the server-driven architecture covered above: the $250,000 result was not produced by a fundamentally new capability the app didn't already have access to. It was produced by removing the engineering bottleneck that had been preventing the growth team from testing this specific idea, and presumably others like it, in the first place.
What This Case Demonstrates More Broadly
The Dezerv result is a useful illustration of a principle that generalises well beyond this one nudge: in a regulated, high-trust category like fintech, the highest-leverage in-app experiments are often not complex. They are simple, well-placed, and well-timed messages that would never have justified a full engineering sprint on their own, but that collectively represent meaningful, testable value once the cost of testing them drops close to zero.
This is also consistent with the broader activation and retention research on Indian fintech apps generally: most neobanks lose a significant share of users between account setup and their first meaningful transaction, and the specific interventions that close this gap tend to be small, contextual, and tied to a moment the user is already in, rather than large, disruptive redesigns. A bottom sheet nudge on a SIP screen fits exactly this description: small in engineering scope, large in relevance to the specific moment it appears in.
Why the Trust Constraint Makes This Result More Notable, Not Less
Financial apps carry a specific evaluation ordering that most other categories do not: every in-app element is read as a signal about whether the institution can be trusted with money, evaluated for credibility before it is evaluated for relevance, which means a technically well-targeted nudge can still fail if its format or tone reads as commercially aggressive. A $250,000 result from a single nudge on a wealth management app is a more demanding outcome to produce than the equivalent figure would be in a lower-trust category, precisely because the nudge had to clear this credibility bar before it could do any persuasive work at all. A user reviewing their SIP is not simply deciding whether an offer is relevant. They are continuously, if implicitly, asking whether the platform showing them anything at that moment can be trusted with their money, and the nudge's placement and dismissible format are best read as the specific design choices that let it clear that bar rather than trip it.
What the Regulatory Backdrop Implies About How This Nudge Was Likely Built
SEBI's proposed Common Advertisement Code, under consultation through 2026, requires advertisements to be true, fair, accurate, and unambiguous, avoiding technical or legal terminology that may mislead, with short-format messaging specifically permitted to use a hyperlink to a full disclosure page where character limits prevent a complete disclaimer. A SIP-screen nudge for a SEBI-regulated platform operates inside this framework by necessity, which means the specific messaging Dezerv's growth team was iterating on was very likely constrained to genuine, non-exaggerated framing rather than an urgency-driven or FOMO-style prompt, the category of messaging regulators have specifically flagged as a concern in financial contexts. This is a useful detail for any team assuming a nudge's effectiveness comes primarily from persuasive intensity: in a regulated category, the nudge's performance had to come from placement and timing precision instead, since the content itself operates under real constraints on how persuasive it is allowed to be.
The Measurement Discipline This Kind of Result Requires to Be Trustworthy
A $250,000 figure attributed to a single nudge is only a credible number if it was measured correctly, and it is worth naming the specific methodology this category of claim depends on. The correct approach for attributing revenue to an in-app surface is a randomised holdout: a portion of the qualifying audience is withheld from seeing the nudge, and the resulting behaviour of the treated group is compared against that holdout over the same window, which isolates the nudge's actual causal contribution from the fact that users who are already reviewing their SIP are, by definition, already higher-intent users likely to take some action regardless of any nudge. Without this structure, a headline collections figure risks simply describing what SIP-reviewing users were already going to do, rather than what the nudge specifically caused them to do. This is a general discipline this article recommends any team apply to their own in-app results, not a claim about the specific measurement approach used for the Dezerv figure, which this article has not independently verified beyond what Digia has published.
Why "Small Experiments" Compound Into a Meaningfully Different Growth Motion
The Sripad Panyam quote, "we're not as blocked by the dev team for small experiments anymore, so we're able to move faster and try things out more often," describes a change in cadence, not just a change in cost per experiment. A team that can only justify testing an idea once it clears a certain engineering-cost threshold will, over a year, test a small number of large ideas. A team where the threshold drops close to zero tests a much larger number of small ideas across the same period, and the $250,000 SIP nudge is best understood as one visible result surfaced from within that larger, less visible pattern of increased experimentation volume, not as an isolated, one-off success unconnected to everything else the team is now able to try.
Topics Not Directly Documented in Public Sources, Worth Asking About
Two questions a reader evaluating this result seriously should ask, that this article cannot answer from publicly available material alone. What was the SIP nudge's actual conversion rate, not just the total collections figure, since a large absolute number can come from either a modest conversion rate applied to a large audience or a strong conversion rate applied to a smaller one, and the two describe very different underlying mechanics. And over what specific time window was the $250,000 figure measured, since a result attributed to "a single nudge" without a stated measurement period is harder to compare against other growth investments with a defined return timeline. Neither of these details is currently published in the sources this article was able to access, and a team seriously evaluating whether a comparable result is achievable for their own app should ask a vendor directly for this level of detail before drawing conclusions from the headline figure alone.
Key Takeaways
Dezerv's growth team was blocked not by a lack of ideas but by a release pipeline that treated every UI change, regardless of size, as requiring the same review and app store process as a core feature build, which meant small experiments rarely got tested at all.
Server-driven UI, decoupling in-app screens and messaging from the app's release cycle, is what let Dezerv's growth team build and modify experiments directly, while still operating within the compliance expectations a SEBI-regulated wealth management app requires.
The headline result, over $250,000 in new digital collections from a single nudge, came from a deliberately small, well-placed intervention: a dismissible bottom sheet on the SIP screen, appearing at the exact moment a user was already engaged in the specific financial decision the nudge addressed.
The format choice, a non-blocking bottom sheet rather than a forced interstitial, reflects the same trust-first design discipline that governs financial apps generally, where an easily dismissed nudge reads as assistance and a hard-to-avoid one reads as pressure.
Because financial apps evaluate every in-app element for credibility before relevance, a nudge's performance in this category has to come from placement and timing precision rather than persuasive intensity, particularly given that SEBI's evolving advertisement code specifically constrains urgency-driven or exaggerated messaging in financial contexts.
Any headline revenue figure attributed to a single in-app surface is only trustworthy if measured against a randomised holdout group, since users who are already engaging with a high-intent screen like a SIP review are likely to convert at some rate regardless of any nudge, which makes the holdout comparison the only way to isolate the nudge's actual causal contribution.
The broader principle this case illustrates: once the cost of testing a small in-app idea drops close to zero, a growth team can pursue the category of experiment, contextual, well-timed, low engineering scope, that produces meaningful results precisely because it was previously too small to justify the standard release process, and a single visible result like the SIP nudge is best understood as one output surfaced from a larger increase in overall experimentation volume.
Further Reading
From Digia Engage:
- In-App Experiences for Fintech and BFSI Apps in India — the trust-constraint and RBI/SEBI regulatory framework referenced in this article's broader analysis
- How Groww Uses In-App Surveys to Build Risk Profiles Without Feeling Like KYC — the SEBI, APMI, and AMFI regulatory detail this article draws on for Dezerv's own licensing context
- How Indian Fintech Apps Drive User Activation: 8 In-App Patterns — the broader activation-gap research this article's pattern-matching section is built on
- The ROI of In-App Engagement: Business Case for Leadership — the holdout measurement methodology this article's measurement-discipline section is built on
- In-App Nudges: The Complete Guide for Mobile Growth Teams — the format taxonomy behind the bottom sheet choice discussed in this article
Explore Similar Case Studies
- The EleFant — scaling from one contextual upsell to 10 live in-app experiences in 30 days
- Probo — shipping feature rollouts and in-app experiments without app store dependencies
- BBlunt — a full e-commerce app launched with native in-app experiences built on Digia
- Datamuni — a growth team running experiments independently with no dev queue for in-app changes
Want your growth team running in-app experiments the same way, without waiting on a dev queue? Book a demo or read how in-app nudges work end to end.