Delhi NCR projects tend to start with a harder question than most cities ask upfront: who exactly is this for, a procurement committee, a first-time citizen user, or a startup’s early adopter, because the answer changes almost everything about how we approach the work. So before any screen gets touched, we spend time figuring out where the current product actually breaks down, using heuristic review, real usage data, and direct interviews with people who match your specific audience, not a generic panel.

Once that’s clear, the work moves through information architecture and wireframes, then visual design and a component system built to scale across however many stakeholders need to sign off, and finally developer handoff: annotated Figma files, interaction specs, and a live call with your engineering team rather than a file dropped over email.

Turnaround depends heavily on which of the three groups you’re in. A UX audit for a SaaS product usually wraps in one to two weeks. Full builds run six to ten weeks for most SaaS and enterprise work. Add formal procurement or a multi-department sign-off chain, and it runs longer still, so we ask about approval structure on the very first call instead of finding out halfway through.