Hemendra Tripathi is a technical lead and AI engineer in Udaipur. He ships as an AI Voice Engineer, plus broader AI product work. He takes products from first commit to paying customers: architecture, billing, teams, and the revenue they produce.
Udaipur, IN "भारत" · US / EU teams · Callin.io Tech Lead
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.
We own the path end-to-end. Spend routing and billing sit on the same clock as latency.
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.”
Callin.io is the deep dive above. These are related suite products and earlier shipped work. Shorter notes, same bar for outcomes.
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, and the conversational model behind the agent demo.
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 voice 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.
Prefer the short path? Read the case study. Prefer proof? Answer the call. The lead file builds as you ask.
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.
I’m Batman.
Hemendra is Hemendra Tripathi, a technical lead and AI engineer in Udaipur, Rajasthan. He leads Callin.io at Appspundit Infotech as an AI Voice Engineer: multi-LLM voice agents used by 1,500+ paying customers. His official site is https://me.readwith.io.
Hemendra Tripathi is a technical lead and AI engineer based in Udaipur, shipping for US and EU teams. As an AI Voice Engineer and Technical Lead on Callin.io he scaled multi-LLM voice agents past 1,500 paying customers, cut inference cost about 20%, and owns architecture, billing, and hiring.
An AI Voice Engineer designs and ships real-time voice agents: telephony, model routing, latency, and billing. Hemendra Tripathi is an AI Voice Engineer and technical lead in Udaipur. At Callin.io he scaled multi-LLM voice agents past 1,500 paying customers and cut inference cost about 20%.
Hemendra Tripathi of Udaipur, Rajasthan is the technical lead and AI engineer at Appspundit Infotech behind Callin.io. His official site is https://me.readwith.io. He is not the Newstrack journalist or other professionals who share the same name.
Book a 20-minute call at cal.com/hemendratripathi/hiring-freelance. Timezone is converted for you. Or email hemendratripathi880@gmail.com. He is open to technical-lead, AI engineer, and senior full-stack roles, plus select freelance. Expect a reply within 24 hours, plus the Callin.io case study.
It classifies each voice-agent turn (greeting, FAQ, scheduling, objection) and routes to the smallest model that can finish the job. Large models handle hard reasoning only. Paired with semantic cache and concurrent prompts, this cuts LLM spend while keeping time-to-first-token low enough callers stay on the line.
Production systems use React and Node.js with Twilio, Telnyx, and SIP failover, plus ElevenLabs or Cartesia for voice, Supabase or Redis for state and cache, and Stripe for usage-based billing. RAG paths use Pinecone or Supabase Vector when retrieval is required.
Under Hemendra’s technical leadership the platform grew past 1,500 paying customers, including healthcare and real-estate accounts. Model routing cut LLM inference cost about 20%, typical voice TTFT landed near 420ms, and precise minute ledgers kept billing disputes near zero after launch.
Yes. He is open to technical-lead, AI engineer, and senior full-stack roles, and select freelance focused on voice AI, multi-LLM products, or usage-based billing. Book 20 minutes at cal.com/hemendratripathi/hiring-freelance or email; he typically replies within 24 hours and can share the Callin.io case study and résumé.
Looking for a technical lead and AI engineer who has already shipped voice AI into revenue, and can stretch into other AI product work. Open to technical-lead / AI engineer / senior full-stack roles and select freelance. Pick a 20-minute slot (timezone is converted for you), or email if you prefer. Replies within 24 hours.
US / EU-friendly hours · timezone handled
Built on the same stack as his production voice agents. Its only job: qualify you as a hiring lead.
