AI that earns its place
Assistants, extraction, search and automation built into the workflow your team already uses, scoped to a measurable outcome, not a demo.
Hours saved weekly↗
Software Engineer • AI Consultant • Product Builder
I build software that makes a business measurably easier to run.
Sixteen years of it, across India and the US. Today I'm building Weavzi for the textile industry, while taking on client work alongside it.
First call is free and takes thirty minutes. No deck, no pitch. Prefer WhatsApp? Message me directly.
Years building software products
Startups & scale-ups across India and the US, from founding engineer to eBay
Production systems built solo: one enterprise, one consumer
What I do
Most engagements start with one of these. If your problem doesn't fit neatly, that's usually a sign it's worth a conversation.
Assistants, extraction, search and automation built into the workflow your team already uses, scoped to a measurable outcome, not a demo.
Hours saved weekly↗Operations, inventory, quality and reporting tools that replace the spreadsheet sprawl teams quietly build around.
One source of truth↗Rebuild or wrap ageing systems without stopping the business. Incremental migration, no big-bang rewrite.
Lower risk, faster change↗Manual handoffs, approvals and data entry turned into reliable pipelines with clear audit trails.
Fewer manual steps↗From zero to a shipped product: architecture, backend, interface and the judgment calls in between.
From idea to live↗A second opinion on architecture, hiring, build-vs-buy and where AI actually pays off for your business.
Clarity before spend↗Selected work
One runs a factory, one runs on the public internet with paying customers. Both are complete systems rather than features. I built both solo, from architecture to interface.
Solo build: architecture, backend, interface
A textile ERP and factory operating system for garment manufacturing and job-work factories. Not a dashboard bolted onto spreadsheets. The whole operation, from a sales order through supplier movement and the shop floor to the ledger, running as one system. Built in Coimbatore, in the middle of the industry it serves.

Solo build: chart engine, backend, interface
A full consumer SaaS. A classical Jyotish engine computes the real chart; AI writes it up in plain language and cites the exact placement behind every answer. Accounts, memberships, payments and PDF export underneath.

How we'd work
You should know within one conversation whether this is worth your time, and see working software long before the invoice feels large.
Thirty minutes on what you're trying to change and what's in the way. No deck, no pitch. You leave with a straight answer on whether I can help.
Free · 30 minA written proposal: what gets built, in what order, what it costs and what it should change for the business. Fixed scope for the first milestone.
Within a weekWorking software in your hands early and often, with a weekly rhythm of demos and decisions. No six-month black box.
OngoingI work directly with you to design and build the thing. When a project needs it, I bring in designers or engineers I've worked with before. You still deal with me, and I still own delivery.
Experience
Sixteen years across AI products, large-scale backend systems, consumer software and internal enterprise tools, built for companies in India and the US, which is mostly useful because it means fewer surprises.
Early Engineer
AI product · 0→1Early Engineer
Consumer · AI mediaEngineering
Mobile infrastructureEngineering
Systems at scaleBefore you write
If something here is still unclear, that's a good enough reason to get in touch on its own.
It depends on what you're building, but you won't be surprised. The first conversation is free, and you get a written number for a defined scope before any work starts. If your budget and the problem don't match, I'll tell you early rather than after you've spent.
Small is fine. Some of the most useful things I've built started as one annoying process someone finally wanted to stop doing by hand. If it's genuinely too small to be worth hiring me for, I'll say so and point you at a cheaper way to solve it.
That's normal, and it's most of what the first conversation is for. You don't need a spec or a document, just the problem as you experience it. Working out what to build is part of the job, not a prerequisite for starting.
No. You need to understand your business, which you already do. I'll explain the trade-offs in plain language and won't ask you to make decisions you don't have the context for.
Most first milestones land in weeks rather than months, and that's deliberate. You should see working software early enough to change your mind while changing it is still cheap.
Yes. It's some of the work I know best. Weavzi is a full production system for textile and job-work factories, built here in Coimbatore, so terms like job-work billing, subcontractor movement and shop-floor tracking don't need explaining from scratch.
Then I work with them, not around them. Sometimes what's needed is an extra pair of hands; sometimes it's a second opinion on architecture, or a review before you commit to an expensive direction.