All case studies
SuperApp Architecture · Conversational AI
Wiiv (Winners)

A super-app blueprint — architected in two weeks

SuperApp · Grocery · Loyalty · Payments · One member. Nine sections. Four partner tiers.
Strategy & Advisory
Wiiv (Winners)
SuperApp · Grocery · Loyalty · Payments
Delivered surface below ↓
The challenge

Super-apps live or die on whether the platform — not any single partner mini-app — carries the complexity. Wiiv (built for Winners, one of the country’s largest grocery retailers) needed one member identity resolvable by every mini-app, one loyalty ledger spanning every partner, and one payment layer settling across every rail — so that a grocery customer and a pharmacy customer were recognisably the same person, wallet and points balance. Nine sections, four partner tiers, one wallet, one loyalty ledger and one payments rail — all sitting behind a single mobile shell — is a lot of surface area for a first-time user to navigate alone.

The solution

A two-week architecture direction engagement. We defined the target system, top-down: everything a member touches flows through one shell, one gateway, and a set of partner-specific integration layers — all backed by shared core services and a single behavioural data spine. Then we conceived a conversational concierge and scoped it inside the core architecture, not as a future add-on. The principle was simple: the concierge inherits every partner connection the platform already has, so no separate integration path is needed.

Proof of work

What the customer actually experiences.

Reference imagery drawn against the same brand system the programme ships against — not a client screenshot, but a faithful reading of the surface.

9:41wiivPCWiiv WalletRs 366Roupies balance · Rs 4,280Go to Wiiv WalletEXPLOREWinnersHealthFuelEventsStaysPayDealsConciergeMoreHomeRewardsPayWiiveeMe9:41wConciergeReordering last week’s groceriesWinnersReview & PayConfirmedWinners · 22 itemsBread · Loaf×2Rs 90Milk · 1L×3Rs 165Eggs · Dozen×1Rs 130Chicken · Boneless×1Rs 420Order totalRs 1,240Free delivery on this orderTIER 3 · 30-SEC UPLOADComplete your verification
DELIVERED SURFACE
One shell. One member.
Reference imagery drawn from the delivered surface — original artwork, not a client screenshot.
The concierge rides on the same downstream APIs the mini-app UI uses. Every partner it needs to reach is already connected.
2 wks
Architecture direction engagement, end-to-end
The direction we took

Where we pointed the work.

A single diagram, drawn from the programme, showing how the strategy actually lines up — where it converges, where it stays plural.

How we shaped the work.

Step 01
One shell, many mini-apps
A single member-facing client — mobile and web — hosting every mini-app and the conversational layer. Traffic passes through a unified gateway with consistent auth and routing rules for every partner.
Step 02
One identity, one ledger, one wallet
A shared member profile, a single loyalty ledger and a multi-rail payment orchestrator become the platform’s spine. Every partner reads and writes to the same state — no siloed balances, no split identity.
Step 03
Four partner tiers, repeatable onboarding
From full native integration for the anchor partner to a lightweight embedded web layer for late-stage additions, each tier gives a partner a defined path in — matched to how much of the experience they want to control.
Step 04
A conversational layer, not a future project
The concierge sits over the existing UI without altering its visual system, turning a member’s intent into a completed journey across partners. Because it uses the same downstream APIs the UI does, it inherits every partner connection the moment they’re onboarded.
Step 05
Handed over, ready to build
A complete architecture package plus a conversational AI concept mapped into a small set of cross-module member journeys. Delivered to the build team at the end of the engagement.
Outcomes

What reached production.

Blueprint
A platform architecture the build team could ship against on day one
Concierge
A first-class conversational layer scoped inside the core, not bolted on
2 weeks
From engagement start to a full, buildable architecture package
AI-native, today

A conversational layer, inheriting every partner connection it needs.

The concierge does not need its own integration project. Because it rides on the same downstream APIs as the mini-app UI, every future partner arrives already speaking to it. That is why the concierge sits as a first-class layer inside the platform, not as a hopeful add-on for later.

Start here

Start with one thing that works.

A 60-minute working session with two of our engineers. You bring a delivery problem. You leave with a written assessment of where AI would help, where it would not, and what it would take to find out.

No pitch deck. No obligation.