“Only Ramesh knows how that works”
A process lives in one person’s head. When they’re on leave, part of the business quietly stops.
Digital Transformation
This is the service for businesses that don’t have a brief — just a nagging sense that things take too long, too much depends on one person, and everyone else in the industry seems to have figured something out.
Sound familiar?
A process lives in one person’s head. When they’re on leave, part of the business quietly stops.
Orders, stock, attendance or payments recorded on paper or in a book. Finding last quarter’s numbers is an afternoon’s work.
None of them talk to each other, so someone types the same information into each one and the three copies disagree.
It works, sort of, on one machine, and nobody dares update it. Adding anything new is quoted in months.
Because there’s no way for them to check anything themselves, every status question becomes a phone call.
The data exists somewhere. Turning it into a decision takes long enough that most decisions get made on instinct.
The work
Not a strategy document that sits in a drawer. A sequence of specific, buildable changes, in the order that causes the least disruption.
How we run it
Transformation projects fail when they try to change everything at once. We sequence the work so the business keeps running and each phase pays for the next.
A short, paid engagement where we learn how the business really works — including the parts nobody documents because “everyone knows”.
A written plan: what to change, in what order, what each phase costs and what it should return. Yours to keep, whether or not you build it with us.
We start with whatever hurts most and can be fixed fastest. Early visible wins are what keep a team on side for the rest of it.
Old and new in parallel until the new one has earned trust. Nobody is asked to bet the business on a system they saw for the first time on Monday.
The people using it every day get taught properly, in their language, with something to refer back to.
Then we take the next item on the list — reprioritised, because six weeks of reality always changes the plan.
Why we’re suited to this
Our own products came from watching small Indian businesses work. A licence tracker, because owners genuinely don’t know when their trade licence expires. A tool that reads WhatsApp history, because that’s where the customer relationship actually lives.
That’s the instinct we bring to transformation work: start from how people already behave, not from how a textbook says they should.
See what we’ve builtRenewal tracking for 12 common Indian business licences, with live countdowns and calendar export. Built because nothing warns you before a licence lapses.
Turns years of WhatsApp chat into the customer list a business already had but couldn’t see. English and Hindi, nothing uploaded.
Questions
Only if we design for them, which is most of the job. That means fewer fields, obvious buttons, working on the phones they already have, and often in the language they actually speak. Adoption is a design problem long before it’s a training problem — if people go back to the register, we built the wrong thing.
You shouldn’t have to. We run new systems alongside existing ones until they’ve proven themselves, migrate in stages, and always keep a way back. No project of ours has a single day where everything changes at once.
Then you’re exactly who this page is for. Come with the symptoms — slow, manual, error-prone, dependent on one person — and we’ll do the work of turning those into a plan. That’s the service, not a prerequisite for it.
We think so, and you can take the output elsewhere — it’s your document. Being paid for it is what lets us give you an honest answer, including “this doesn’t need software, it needs a different process”, which free proposals never say.
It comes with you, and we reconcile it rather than assuming it’s clean. Real business data is always messier than expected — duplicate customers, three spellings of the same supplier, missing dates. We report what didn’t match instead of quietly dropping it; that problem is exactly why we built Tessera.
Start there. You don’t need to know whether the answer is an app, an integration or a different process — that’s the part we’re for.