[ custom builds ]
I build those. Usually for businesses between five and two hundred people, usually in India, usually where the existing software was designed for somebody else’s country and somebody else’s scale.
Procurement, production, stock, compliance and costing that match how your business actually runs — not how an off-the-shelf package assumes it does. Often this starts from SunnyERP and gets reshaped around you.
Runs a food-processing company today.
A desktop assistant that reads your email, prepares your meetings, tracks your money and remembers your commitments — across every business you run. Sensitive work stays on your machine: it never leaves for a cloud model.
I run my own businesses on mine, daily.
Agents, automations, dashboards, document extraction — the small sharp tools that remove a recurring hour from somebody’s week. Built only where AI genuinely earns its place.
Photograph a business card, get a verified company record.
[ how it goes ]
A conversation about what happens today — the spreadsheet, the WhatsApp group, the register nobody admits to keeping. No slides.
You getA written summary of the problem as I understood it, and an honest answer about whether software is the right fix.
Scope, sequence and price. What gets built first, what waits, what I would not build at all.
You getA fixed scope for phase one, with the number attached.
Building in the open. You see working software early and often, running against your real data, not a demo dataset.
You getA link you can open, from the first week.
Deployed to your infrastructure or mine, your team trained, and me still reachable when something breaks at 11pm.
You getSoftware your team uses, and a person who answers.
[ start here ]
The most useful thing you can write is the boring detail: who does what, on which day, in which spreadsheet, and what goes wrong when they’re on leave. That tells me more than any feature list.
Reply within 2 working days · from me, not an autoresponder