Vivek Girotra
Frequency Is Not Loyalty
Vivek Girotra has spent years inside fintech and consumer products, building growth systems where the real work begins after the first transaction.
Most growth teams treat frequency, habit, and loyalty as variations of the same problem. Vivek has spent enough time inside high-trust financial products to know they are three entirely different challenges.
“Frequency only tells you that a behavior is happening,” he explains. “It doesn’t tell you whether there’s any real attachment or preference underneath it.” Someone might repeatedly open your app because a support ticket has been left unresolved for days. That is activity. It is not growth.
Habit is one layer deeper. The behavior has become automatic. The user no longer reconsiders. “Someone may go to the Starbucks on their way to the office and open the app because that is just what they do.” Strong behavior. But it does not prove the customer has any real affinity for the brand.
Loyalty is the layer most teams never reach. It is, in Vivek’s framing, a chosen preference under competition. When the customer has real alternatives and still picks you, that distinction shapes revenue. In high-trust categories, especially fintech, the difference is between a product people use and one people defend.
The Roots of a Customer-First Instinct
Vivek began his career at Ogilvy, where his earliest work included copywriting and proofreading. There was hell to pay if even a comma was out of place. That discipline still anchors his practice. Decades later, in an age of large language models and autonomous agents, he still returns to the same first principles. Who is the audience? What are their pain points? What is the message that creates an emotional connection? What form does that take across available touchpoints?
The sharpest illustration of that instinct came early in his career, working on a consumer electronics account in India. A manufacturer had two refrigerator lines: an older direct-cool model that accumulated ice in the freezer, and a newer frost-free model. The newer product was technically superior in every dimension. Yet in smaller cities, the frost-free units wouldn’t move.
Rather than adjust the advertising, Vivek’s planning team went directly into those tier-two towns to observe. What they discovered was something no dataset could have surfaced. Power cuts were frequent, often running four to five hours at a time. The ice that accumulated in the older freezer actually helped preserve food during outages. Customers were not being irrational. They were solving for a real constraint that the marketing brief never acknowledged.
“This is the job of a marketing professional,” Vivek says. “Going deep and figuring out things that even the best AI tools can’t yet surface on their own.” Going to where the customer actually lives, before building any system around them, is the foundation of everything that follows.
The Lifecycle Architecture: Where Growth Actually Lives
Vivek has applied this principle at scale in consumer fintech, where the product is not a transaction but an act of trust. Customers are not buying virtual gold coins at $2 a pop. They are moving money that may feed a family or cover a medical bill on the other side of the world.
In that context, the repeat behavior matters more than the first conversion. The compounding value of a well-designed product is what makes the unit economics work: convenience, confidence, and value that improve together over time.
Building the system to capture that compounding value starts with what Vivek calls hygiene. Event tracking must be set up correctly before anything else. Some events fire from the app. Some are server-side. Some occur asynchronously across payment rails. Creating the plumbing to capture all of it reliably is, as he puts it, “a non-trivial exercise that people consistently underestimate.”
Once the data foundation is sound, the lifecycle architecture can begin. His framework for getting started is deliberately simple. Define your key milestone events first. For a money transfer product, the chain looks like this: app install, sign-up, completion of Know Your Customer (KYC) verification, bank linking, and first transaction. Build the first version of the journey system against those milestones. Get data. Then go finer.
“You’ll find people who perhaps submitted a KYC, but it failed. You need a journey that sends them a deep link with correct feedback so they can retry.”
For the lifecycle infrastructure itself, Vivek’s team works with CleverTap, a customer engagement platform that consolidates event tracking, segmentation, funnel analytics, and multi-channel messaging (email, WhatsApp, and SMS) into a single system. Having a single place to track behavior and trigger campaigns removes the coordination overhead that bogs most teams down. But the platform is only as useful as the journey logic behind it.
Vivek resists the impulse to over-engineer before gathering evidence. “Lifecycle marketing is always a game of inches. You’re rarely going to make one change that gives you a 30 percent lift. It’s always going to be: I made this small change, I improved conversion by 2 percent. I added this journey, I improved the next stage by another 3 percent.” The wins accumulate. The starting point matters less than the commitment to iteration.
The Product-Marketing Handshake in Practice
The org chart draws a clean line between marketing and product. Reality does not. In Vivek’s experience, the teams that win are the ones that stop arguing about ownership and start operating on shared terrain.
His framing is precise. Marketing sets the expectation. It determines who arrives, what they believe they are getting, and what value they are mentally prepared to accept. The ad, the landing page, the app store listing: all of these shape a user’s mental model before they ever touch the product.
Product either proves or breaks the promise. If the onboarding is muddled, if the value moment arrives too late, the mismatch registers immediately. That damage doesn’t stay on the product side. It feeds directly back into growth efficiency.
The overlap zone (activation, onboarding, referral, retention) belongs to neither team exclusively. The strongest organizations treat it as a shared operating responsibility, and as Vivek frames it, everyone has to own the customer experience, not just the team whose name is on it. In practice, this has meant that lifecycle marketing teams sit within his marketing organization, not product, because retention is too central to the growth outcome to be housed anywhere else. The entire funnel, from impression to install to first and second transactions and so on, is mapped and managed as a unified system.
Brand Is Not a Logo
Vivek is pointed when the conversation turns to brand. Teams routinely reduce it to its most visible artifacts. The logo. The color palette. The tagline. His operating definition is broader. “Everything is brand. Your App Store page is brand. Your customer support experience is brand. Your onboarding flow is brand. Every time the customer touches your product or your company, they are forming a view of what your brand actually is.” In his view, consistency is built through every customer experience, not just through aesthetics.
Personalization That Actually Changes Behavior
When it comes to personalization, Vivek is precise about what the word actually means. Real personalization matches the journey, message, and timing to the user’s actual context: where they are in the lifecycle, what they are most likely to do next, and what friction stands between them and that action.
“I have never converted better because someone mentioned my name in the first line of an email.” The valuable form of personalization is contextual, rooted in the user’s actual situation.
A user who signed up and stalled at KYC needs reassurance around trust and process. An active user who has already transacted needs a different message entirely, one tied to timing or rewards or a shorter path to their next action.
“AI will make it easy to produce more variants more quickly,” he notes. “It still won’t answer the harder question of what should vary and why. Dario Amodei at Anthropic made this point about engineering: even when AI writes 90 percent of the code, the humans focusing on the remaining 10 percent become more leveraged, not less relevant. The same applies to lifecycle marketing. AI will produce the variants, but knowing which moment matters, which segment to treat differently, and when to leave something alone is where that leverage lives.”
The Distribution Problem Nobody Has Solved
As AI tools commoditize content production, Vivek is watching a common misunderstanding take hold. Distribution is increasingly confused with visibility. An entire generation of vibe coders is finding this out the hard way: building the product was the easy part. Now they’re app marketers, and they didn’t sign up for that.
“If distribution were just spraying AI spam all over the internet, we would all be multimillionaires by now.” The substance of the problem has not changed: a real distribution system requires unit economics that work, attribution you can act on, and a monetization layer that funds the next cycle of growth. The tools for executing each piece are cheaper than ever, but cheaper execution just raises the bar on everything around it.
Vivek thinks about AI adoption in three layers. The first is delegation: routine production tasks handed off entirely. His team already has all copywriting done by AI. The second is augmentation: using AI to surface deeper insights into audience behavior, predictive modeling, and segmentation that would take a human analyst weeks to assemble. The third, and the one he’s building toward, is autonomy: agents that monitor lifecycle performance, flag opportunities, and act on them independently.
That has been the through line of Vivek’s career: not the tools, but the system around them. From a freezer in a tier-two Indian town to autonomous agents managing marketing journeys, the starting point has always been the same. Go to where the customer is. Understand what they actually need. Then build the system around that.
More from Uncovered Media
 | A guest post by
|