Case · Build (self-applied) → consumer SaaS · 8 weeks (Build-shaped, internal · 70% reused code)
Internal — Talpro Universe · Smart-doorbell QR subscription service
Build (self-applied) → consumer SaaS · 8 weeks (Build-shaped, internal · 70% reused code)
Talpro Universe (consumer brand)
Outcomes · measured
Renewal at month 6
vs ~60–70% Indian consumer-SaaS benchmark
Failed-payment recovery
vs ~15% Razorpay default · 3-touch dunning
Code reused from CVPRO
Razorpay billing + portal + admin
Narrative
01 · Problem
Problem
Jharokha launched as a thesis: an Indian household's front-door interaction was solved badly by Western smart doorbells (privacy-violating cloud video, ₹15K hardware, monthly fees in dollars). The hypothesis was that 90% of the value — ‘who's at the door, where do I tell them to go, can I let them in remotely’ — could be delivered by a printed QR code routed to WhatsApp, with no camera and no hardware purchase. The challenge: ship a Razorpay subscription billing flow (₹59/mo and ₹99/mo plans), QR generation, WhatsApp customer-onboarding sequences, payment recovery on failed renewals, and a customer portal — for a non-developer founder running this as a side product, with no margin to hire engineers. Build budget: zero rupees of new code. Reuse-first.
02 · Approach
Approach
Eight-week Build (internal) anchored on the cvpro-component-extraction skill: harvest payment + subscription + customer-portal modules from CVPRO codebase (26,429 lines, already shipped Razorpay billing). Week 1–2: extract the Razorpay subscription module from CVPRO into a stand-alone library; remove career-platform-specific coupling. Weeks 3–4: build QR generator (printable PDF with embedded routing URL), WhatsApp Business API integration for the customer-side conversation, customer portal pages. Weeks 5–6: failed-payment recovery sequences (3-touch dunning over 14 days, includes WhatsApp + email + SMS), plan upgrade/downgrade flows. Weeks 7–8: production cutover — Razorpay live mode, customer onboarding sequence, support escalation to a single founder inbox. Total new code: ~3,200 lines. Total reused from CVPRO: ~8,400 lines.
03 · Outcome
Outcome
Jharokha now serves a paying customer base with 94% subscription renewal at month 1 and 87% at month 6 — well above consumer-SaaS-in-India benchmarks (~60–70%). Failed-payment recovery sequence converts 38% of failed renewals back into paying customers (vs Razorpay default ~15%). Customer support volume has held at <5 tickets/week despite customer growth — the WhatsApp onboarding sequence answers ~80% of pre-purchase questions before the customer ever messages support. Hardware cost to customer: zero rupees (printed QR sticker). Build cost to Talpro: zero rupees of new platform code beyond the 3,200 lines unique to the doorbell domain.
04 · In their words
“The Razorpay billing logic in Jharokha is the same logic that ran CVPRO subscriptions. Reuse-first means a side-product ships in 8 weeks for zero platform-engineering cost.”
05 — Who led this engagement
Bhaskar Anand. Every first call.
Founder & CEO, CompetitorX. Pune, India. No associate-level handoff — the person who led this engagement is the person who takes your scoping call.