Case · Forge (self-applied) · 5 weeks (Forge-shaped, internal)
Internal — Talpro Universe · Cross-product billing orchestration
Forge (self-applied) · 5 weeks (Forge-shaped, internal)
Talpro Universe (cross-product billing)
Outcomes · measured
Month-end close time
CFO reconciliation across 4 products
Failed-payment recovery
unified dunning across products
Webhook lag detection
Telegram alert on first lag spike
Narrative
01 · Problem
Problem
By March 2026 Talpro Universe had four products charging customers — CVPRO, Jharokha, HCI Talks, internal Talpro India invoicing — each with its own Razorpay integration, its own webhook handler, its own dunning logic, and its own failure-mode debugging. A failed payment on Jharokha would land in one Slack channel; a CVPRO churn would land in another; an HCI Talks renewal-failure would email a single inbox monitored sporadically. Refunds were processed manually. Tax invoices generated by hand. When the CFO asked ‘what’s our gross-payment-volume this month across all four products?’ the answer required pulling four spreadsheets and reconciling for 90 minutes. Worse: when one product's webhook fell behind (Jharokha lost 6 hours of webhooks during a Razorpay TLS migration), nobody noticed for three days because each product was monitored in isolation.
02 · Approach
Approach
Five-week Forge to build Maitro as the single billing orchestrator. Week 1: cross-product audit — map every payment surface, every webhook, every dunning sequence into one canonical model. Weeks 2–3: ship a unified Razorpay webhook handler that receives every event from every product, persists to one Postgres ledger, fans out product-specific actions. Weeks 4–5: dashboard (gross-payment-volume by product / month / customer / failure-mode), automated tax-invoice generation, unified dunning engine reused across all four products. Telegram alerts on webhook lag >15 min, on failed-payment-recovery rate dropping below threshold, on refund volume spike.
03 · Outcome
Outcome
CFO month-end revenue close dropped from 90 minutes of spreadsheet reconciliation to 4 minutes (open dashboard, screenshot). Failed-payment-recovery rate rose from 22% (per-product avg) to 41% — the unified dunning engine compounds product-level retry data into a smarter cadence. Webhook lag detection went from 3 days to 15 minutes. The April 14 Razorpay TLS migration that previously cost Jharokha 6 hours of lost events was caught at 17 minutes lag, recovered before customer impact. Tax-invoice generation went from manual (~3 hours / month / product) to zero human time. Maitro now powers every Talpro Universe billing flow and is the eval ground for the Sales-Dev Agent Army's upcoming ‘billing reconciliation as a service’ offering.
04 · In their words
“Maitro is what every CFO building a multi-product company eventually wants. We built it for ourselves first because we needed it before anyone else did.”
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.