Product teams constantly struggle to surface the right guidance to users at the right moment. Onboarding flows, feature announcements, and contextual prompts traditionally require engineering effort every single time. NudgeLab is a no-code, platform-independent nudge management service that cuts out that bottleneck. It wraps over any existing infrastructure through a lightweight SDK script tag, giving teams a self-serve admin panel to design, configure, and deploy in-app nudges without touching the underlying product codebase.

The platform supports two distinct delivery modes. Campaign-based nudges are scheduled and distributed via a CDN-backed delivery architecture: static nudge configurations are pushed to a CDN edge, and the Client SDK fetches them on load, keeping delivery low-latency and scalable with no server roundtrip per user. Trigger-based nudges work through HTTP polling, where the Backend SDK intercepts API calls, injects event_label identifiers into a message queue, and the client polls for matching nudge responses in real time. Administrators authenticate, create projects, generate SDK scripts, and configure nudges entirely through the dashboard, with no deployments required on the client side.

My work on NudgeLab was entirely backend: I designed and built both SDK layers, the message queue pipeline, the CDN distribution mechanism, and the HTTP polling system for event-driven nudges. The CDN delivery approach required careful thinking around cache invalidation and configuration serialization to make sure nudge updates propagated reliably without stale content reaching end users.

NudgeLab was built at HackRx 3.0, Bajaj Finserv's national hackathon, where it won the Dark Horse and Power & Pace awards.

Built using: