The problem
A premium D2C build that looked finished on a MacBook and broke the moment a real buyer touched it.
23 issues found across founder / CEO / designer lenses. 23 fixed in a focused sprint. Then audited again — and shipped the round-two findings publicly.
Market context: Premium D2C · trust-sensitive category · ₹499–₹4,999 price points · gifting and corporate as lead channel.
Duration · 6 hours + audit cycles
See the live buildThe result · in numbers
23
Issues found via three-perspective audit
23
Fixed in a focused sprint
111 KB
Single self-contained HTML file
0
JavaScript frameworks
The brief
What the client actually needed.
A premium D2C demonstration build — 12 products across dry fruits and artisan chocolates, ₹499–₹4,999 price points, gifting as the lead channel. The stated brief was to ship a portfolio piece that proves we can build a complete premium e-commerce experience. The real brief — the one behind it — was different. Most Indian agencies don’t have a portfolio piece in this category, and the ones that do are usually polished demos with the cracks hidden. We wanted Clicknify to have one that holds up under audit. So we built the audit discipline into the engagement itself.
The problem
What was broken — in numbers.
The first draft shipped at 1,361 lines of code and looked finished. On a MacBook. It wasn’t.
- Critical issues at first-draft "done"
- 6
- High issues
- 7
- Medium / Low
- 8 / 2
- Mobile media queries before audit
- 0
The approach
What we did. Why.
Three perspectives, run in sequence — not because three reviewers found different bugs, but because each one asked a different question of the same site.
- Founder lens — will this site actually convert visitors into buyers? (Found 8 issues.)
- Agency-CEO lens — would I confidently show this in a pitch? (Found 7 issues.)
- Designer lens — where does the craft layer fail? (Found 8 issues.)
- Every issue tagged with an ID (F-01, C-01, D-01) and a severity before any rebuild work began.
The execution
Inside the work.
Audit discipline
Mobile got zero media queries. Cart died on tab close. Promo code applied visually but didn’t change the price. Weight variants didn’t affect price — a buyer could pay 250g rate for 1kg. Sort dropdown was dead UI. Checkout fired with empty fields. Eighteen jobs assigned to one shade of gold. We caught all of these before they hit a prospect’s phone.
Six-hour rebuild, ID-annotated
Every fix shipped with its issue ID embedded as a code comment — /* ═══ FIX F-02: localStorage persistence ═══ */. When a client later asks "is X handled," the answer is a code search, not a memory test. The rebuild closed all 23 issues in a single focused sprint.
Round-two audit
After the rebuild, we ran the audit again — and published the second-round findings. Fifteen new issues surfaced (1 critical, 5 high, 9 medium/low). Some were second-order — fixing the obvious ones exposed deeper questions. Some were introduced by the rebuild itself (the 674 KB file weight from base64 embedding). And some were the original case study overclaiming what was actually delivered. We published the round-two audit alongside the case study.
The outcome
What moved. And why.
Two case-study documents shipped publicly — the audit-then-rebuild story, and the honest round-two reckoning.
- 14 of 23 original issues fully resolved · 7 partially · 1 shifted to a different failure mode
- Round-two audit surfaced 15 second-order issues — published in full, not buried
- Three working principles distilled: audit before shipping · give every fix an ID · honesty is positioning
What didn’t work
Every honest case study has one. This builds more trust than ten testimonials.
The base64 image embedding strategy made the file portable but broke load performance — a 674 KB file with 533 KB of inline imagery loads in 3–5 seconds on Indian 4G, undoing a meaningful chunk of what the mobile responsive fix accomplished. Reviews coverage shipped at 17% — content for 2 of 12 products, with the other 10 falling back to identical defaults that any diligent buyer will spot. Both issues are in the public round-two audit. We published them because hiding them would have been the worse failure.
Want this audit discipline on your build? Bring it to the Clarity Call.
Book the Clarity Call
Bring one problem.
Leave with one framework.
The Clarity Audit is how every Clicknify engagement starts. 30 minutes, live, with the Founder. We diagnose one thing — a stuck channel, a leaky funnel, a brand decision that keeps slipping — and leave you with the framework to fix it. Yours to keep, regardless.
- 30 minutes · live diagnostic
- One channel, one funnel, or one brand decision
- Yours to keep — no pitch unless you ask for one
- Founder on every call
Ashwani Srivastava, Founder, on every call. Responses within 2 hours during IST business hours · same-day for international enquiries.