jagnani73P.03
[the record]STATUS: NTU SINGAPORE — AUG 2026

NudgeLab

HACKRX 3.0 · DARK HORSE
no-code in-app nudges — design, configure, and ship guidance without touching the product codebase
fig. 1 — a no-code nudge, configured once, delivered into a live productCDN · campaign
app.yourproduct.xyz
SearchDashboardAnalyticsPublish
New — multi-chain analytics is live. Take a look →
no deploy · pushed from the admin panel
01THE PROBLEMevery nudge is an engineering ticket

Onboarding flows, feature announcements, contextual prompts — each one traditionally means another engineering ticket, another deploy.

NudgeLab is a no-code, platform-independent nudge management service. Wrap any product with a lightweight SDK script tag, and a self-serve admin panel lets teams design, configure, and deploy in-app nudges — no codebase changes, no deploys. Built at HackRx 3.0, Bajaj Finserv's national hackathon, where it won the Dark Horse and Power & Pace awards.

02THE ARCHITECTUREtwo delivery modes · backend-owned

Two delivery paths. Campaign nudges are pushed to a CDN edge and fetched by the client SDK on load — no per-user server roundtrip. Trigger nudges run through HTTP polling: the backend SDK intercepts API calls, injects an event_label into a message queue, and the client polls for matching responses.

01

CONFIGURE

design a nudge in the admin panel

Next.js admin

02

DISTRIBUTE

campaign → CDN edge, cached

CDN · Client SDK

03

TRIGGER

event_label into a message queue

Backend SDK · queue

04

DELIVER

client polls + renders the nudge

HTTP polling

STACK — Node · Express · Next.js · CDN delivery · message queue
03WHAT I BUILTbackend · both SDK layers

My work was entirely backend — both SDK layers, the queue pipeline, and the CDN mechanism. The subtle part was cache invalidation: making nudge updates propagate reliably without stale content reaching users:

01

client + backend SDKs

one script tag wraps any existing product

02

CDN distribution

static configs at the edge, no per-user roundtrip

03

message queue

event_label routing for trigger-based nudges

04

cache invalidation

config serialization so updates never go stale

04IN THE WILDplates 01–06 · the admin panel