How a Hidden UX Flaw Was Poised to Wipe Out 60% of a Startup's Launch Revenue.
A 3-day UX audit that prevented catastrophic user drop-off for a pre-launch C2C property platform.
- Deal Direct is a subscription-based C2C property platform — owners pay ~₹999 per listing to reach buyers and renters directly, no broker.
- Two weeks before public launch, I ran a 3-day strategic UX audit on the listing and filtering flows. 63 issues across 17 findings.
- Aadhaar verification rejecting every valid ID — a 100% block at the final trust step. Drop-off projected to hit 40-60% at launch.
- Delivered an 8-week roadmap with severity tags, effort estimates, and ROI per fix. Critical fixes mapped to ~₹1-1.5L MRR recovered, ~300% ROI in month one.
The launch-killer
Three days in, working through the Property Adding flow. Last step — Aadhaar verification.
The 12-digit number was correct. The page rejected it with: "OTP generated... try after 45 seconds." I waited. Tried again. Same error. Tried a different valid number. Same error.
Aadhaar isn't onboarding. It's the activation step — the moment the user commits a real listing to the platform. A 100% rejection at activation isn't a bug. It's a launch blocker on a subscription product. Users don't pay ₹999 for a flow that ends in a confusing error.
The price filter. Default range went from ₹1000 to ₹10 Cr — a sales-scale slider. Anyone searching the rental market couldn't move the handle into a usable range without overshooting. Half the search traffic was filtered out before it started.
What broke
The platform had a client, a launch stage two weeks out, and 63 critical usability issues across 17 major findings — four key symptoms the in-house QA process hadn't flagged.
How the audit was structured
Three days. Two user paths — residential and commercial. Heuristic evaluation across both flows, benchmarked against three leading platforms (MagicBricks 8.5/10, 99acres 8.0/10, Housing.com 7.5/10), severity-classified findings with ROI per fix.
Mobile, the dashboard, and the incomplete Figma files were out of scope — the deliverable had to be shippable in two weeks, not a wishlist.
The five P0-P1 blockers
Five issues that would have killed activation on day one — the price filter, commercial form fields, Aadhaar verification, the rental period selector, and the future-date picker. Each tagged with severity, effort, and projected revenue impact.
The full bug tracker — 63 issues, screen recordings, annotated screenshots — lives in the audit report handed to the team.
The roadmap
Four phases, severity-ordered. Week 1 alone — the date picker, the rental period selector, label fixes, Aadhaar — projected to recover 100-150 paid subscribers a month. ~₹1-1.5L MRR. ~300% ROI in month one.
Each fix had a number against it. Nothing was a wishlist.
Projected impact
A projected 3x lift in user activation, bringing the platform from 15% to industry-standard completion rates. ~₹1-1.5L in monthly recurring revenue recovered. The bug tracker was delivered as a live, filterable database — screen recordings, severity tags, fix recommendations handed directly to the dev team.
What this proves
Three days. Two user paths. A pre-launch QA list the in-house team had already cleared.
A founder doesn't need an audit to find the easy bugs. They need someone who can find the launch-killer before launch — and tell them which fixes pay back fastest.
If you're weeks from launch and something feels off, let's talk.