Callin.io
IN PRODUCTIONAI voice-calling SaaS scaled to 1,500+ paying customers and enterprise accounts. Low-latency telephony, multi-LLM orchestration, and minute-based billing with negligible disputes since launch.
Hemendra Tripathi is a technical lead for AI voice systems who takes products from first commit to paying customers — architecture, billing, teams, and the revenue they produce.
As Technical Lead I owned the architecture, vendor spend, and billing system for an AI voice platform that grew past 1,500 paying customers — including medical and real-estate enterprise accounts — while cutting LLM cost 20% and keeping billing disputes near zero.
callin.io ↗Classify each turn — greeting, FAQ, scheduling, objection — and route to the smallest model that can finish the job. Large models only for hard reasoning.
Cache high-frequency intents; fire retrieval and response scaffolds in parallel so time-to-first-token drops before the caller notices silence.
Twilio + Telnyx with SIP fallback. Fail over without dropping the call; keep audio streaming over WebSockets under load.
Minute tracking with rollover ledgers precise enough that disputes became rare. Stripe subscriptions wired to actual usage, not estimates.
“Hemendra is the rare engineer who can rewrite the voice pipeline before lunch and close an enterprise prospect after dinner. He treats infrastructure cost like product debt — and it shows in the margins.”
AI voice-calling SaaS scaled to 1,500+ paying customers and enterprise accounts. Low-latency telephony, multi-LLM orchestration, and minute-based billing with negligible disputes since launch.
AI agents that sort, draft, and auto-reply across providers. Live with early adopters — including high-volume Amazon sellers running inbox workflows on it.
Connects lead sources, builds a business profile, and places AI qualification + follow-up calls for property leads. Final beta ahead of release — the conversational model behind the demo below.
Pan-India farm management with field-to-warehouse sync, plus a financial dashboard with automated reconciliation — 30% fewer accounting errors, 15+ staff-hours saved weekly.
I build AI agents that make real phone calls for a living. This one runs on the same conversational patterns as production voice agents — except its lead-qualification target is you.
Answer the call. Ask about numbers, stack, or why hire him. The lead file builds the way Realead qualifies property leads in the field.
Built on the same stack as his production voice agents. Its only job: qualify you as a hiring lead.
In voice AI, silence is a bug. Every architectural choice — caching, routing, carrier failover — exists to keep the human from hanging up.
A confirmation doesn't deserve a frontier model. Route by complexity. Your CFO will notice. So will your p95.
If customers argue about invoices, the product is unfinished. Usage ledgers should be boringly correct.
Architecture without vendor spend ownership is theater. I hire, I ship, and I know what the infra bill was last Tuesday.
“We evaluated three voice vendors. Callin's agents were the only ones our clinic staff didn't hang up on — and the only ones whose invoices we didn't audit line by line.”
“He hired half my eng team, set the roadmap, and still jumped on customer calls. That's not a contractor. That's an owner.”
“Curriculum he redesigned moved our placement rate up over 40%. Students left knowing how to ship, not just pass exams.”
Based in Udaipur, shipping for the US and Europe. I got here by teaching 150+ students to code, freelancing across four frameworks, and rebuilding a voice-AI platform until 1,500 companies paid for it. I like systems that are boring, fast, and profitable — and teams that own what they build.
Looking for a technical lead who has already shipped AI products into revenue — not someone who will learn voice AI on your dime. Open to technical-lead / senior full-stack roles and select freelance. Replies within 24 hours.