Notes on bringing AI to an MSME

WhatsApp, paper ledgers, Tally, and a few spreadsheets. What actually moves the needle, and what doesn't.

The textile distributor I spent time with last year wasn't running his business badly. He was running it the way it works — WhatsApp threads with buyers and suppliers, paper ledgers for stock, Tally for the accountant, a few shared spreadsheets for the delivery schedule. Every piece of that system represents a decision that worked well enough to survive. The implicit argument for AI has to reckon with that.

The most common mistake in bringing AI to a business like this is treating the current system as a problem to be replaced. It isn't. It's a pragmatic equilibrium built on trust relationships, cash-flow timing, and muscle memory. An AI that demands new behavior in exchange for its benefits doesn't get adopted — the cost of the behavior change is too high and too immediate, while the benefit is too abstract and too uncertain.

What does earn its keep: removing typing, removing memory load, and removing the gap between what happened and what got recorded. Order capture by voice or photo, where the AI handles transcription and structuring, fits that pattern. Reconciliation assistance — "here's what the ledger says, here's what WhatsApp says, here are the two discrepancies" — fits it too. Summarization over the operator's own data, not over some generic knowledge base, fits it most naturally of all.

What doesn't earn its keep, at least not yet: autonomous decisioning on contested transactions. When a buyer disputes a quantity or a supplier adjusts an invoice, the resolution is relational, not informational. The operator needs to be in that conversation. An AI that tries to close it will get turned off.

Neev is where this thinking is landing — a modular operations platform for MSMEs, starting with textile distribution. The design constraint is that nothing in the workflow should require the operator to learn a new mental model. That's harder than it sounds.