Writes about what software should do for a one-person business — and where the usual tools stop.
Suresh is a co-founder of Aasure, where he leads product, AI architecture and infrastructure. He designed the hierarchical memory structure and golden-trace training that sit behind the Aasure agent — the parts that decide what it does on its own and what it checks with you first.
He writes here about software categories: why a calendar tool stops being enough, why retail point-of-sale never quite fits a service business, and what it actually takes for automation to be trusted with a client relationship rather than just a reminder.
His published pieces follow that brief. The calendar-tool essay works through the four-fifths of running a service business — invoices, follow-ups, client history, retention — that a scheduling link never touches, and what covering the gap with separate apps actually costs each month. The point-of-sale piece asks why software built around transactions keeps mis-fitting businesses built around relationships, where the till is the least interesting moment of the appointment.
The through-line in both the writing and the product is the same question: which decisions an automated system should take alone, which it should draft and hold for approval, and how it should explain itself afterwards. For a business that runs on one person’s name and their clients’ trust, he argues, that boundary matters more than any feature list.