Why SahajViews exists — and what it actually does.
I started SahajViews because I kept seeing the same problem repeat itself across completely different industries. A business would spend money on software. It would get implemented. The team would use it for a few weeks. Then quietly — without anyone making a formal decision — they'd drift back to their spreadsheets, WhatsApp groups, and email chains.
The software hadn't failed technically. But it had failed completely in practice. And the people who sold and built it had long since moved on to the next project.
The problem was never the software. It was that the underlying work — the actual sequence of how things got done — had never been fixed before the system was built on top of it.
I've spent years working across software development, project delivery, and operational design — not as separate disciplines, but as one connected practice. A business system only works when three things are true at once: the process underneath it is sound, the people using it are genuinely enabled, and the information it relies on is clean. If any one of those is missing, the system fails.
That sounds straightforward. But most implementations skip at least one of those steps — usually because diagnosing it properly takes time, time costs money, and everyone is in a hurry. SahajViews is built around the opposite sequence: diagnose before building, fix the process before automating it, and don't call a project done until the team can run it without me.
— Chetan