A consulting practice built around how businesses actually operate.
Sahaj Views is a founder-led software and systems consulting practice for growing businesses that need the way work, information, people and technology fit together to become clearer. We start with the operating reality—not a software catalogue—and use technology only where it makes the operation more connected, manageable and easier to run.
Sometimes that means improving what already exists. Sometimes it means connecting systems or building something focused. The objective is not more technology. It is a better way for the business to operate.
More than two decades working where software meets day-to-day operations.
Chetan's background spans software development, Microsoft and business platforms, information management, workflow automation, connected applications, reporting and custom systems. Over time, the recurring lesson became clear: technical capability is only one part of whether a system succeeds.
That is the thinking behind Sahaj Views. The practice combines technical depth with operational judgement—looking at the workflow, the information, the people involved, the current systems and the business outcome before deciding what should change.
The founder remains close to the problem definition, major solution decisions and review of the working result. That keeps the context behind those decisions connected from the first conversation through handover.
The gap is often not inside a tool. It is between the parts of the operation.
Growing businesses usually accumulate useful tools over time: accounting software, Microsoft 365, CRM, spreadsheets, specialist applications, messaging and reporting tools. Individually, many of those tools may be perfectly capable.
The friction appears between them. Work waits for somebody to follow up. Documents and decisions sit away from the task they belong to. People carry information from one system to another. Managers rebuild the operating picture manually.
We work on that operational layer: the structure that connects people, workflow, information, systems and visibility into something easier to understand and run.
Work moves because people push it
Follow-up, reminders and status checks are carrying the process.
Context lives in too many places
Files, decisions, history and ownership are separated from the work.
People bridge otherwise useful systems
Information is re-entered, checked and reconciled by hand.
Visibility is assembled after the fact
Leadership sees the operating position only after somebody rebuilds it.
Sahaj Views
The name reflects the kind of consulting practice we want to build: clear enough to understand, calm enough to trust and practical enough to use.
A reminder that a good operating system should reduce unnecessary effort and complexity rather than add to it.
A reminder to see the complete operating picture before deciding what should change.
Five observations that shape the work.
These are not slogans added around a technology service. They are practical conclusions from seeing what makes systems useful—or difficult to live with.
Tools do not fix unclear work.
If ownership, stages and exceptions are vague, software usually digitises the confusion rather than removing it.
Automation magnifies the process it is given.
We simplify the flow and identify exceptions before deciding what should move automatically.
Visibility should lead to action.
A useful operating view makes delays, load or exceptions visible early enough for somebody to respond.
Simpler is often stronger.
The best answer may be a better use of an existing platform, one connection or one clear workflow—not a larger build.
The client must be able to own the result.
Routine operation should not depend permanently on the consultant who designed the system.
We are not attached to a particular product—or to building something new.
The recommendation is driven by the operating need. That makes it possible to retain what already works, simplify what has become difficult, connect suitable systems or build only where a genuine gap remains.
We work across the layer beneath individual products: how the business process, information, people and systems should work together.
See the Build areasBusiness-system decisions
Clarifying what the operation needs before selecting the technical response.
Practical modernisation
Improving the current environment without assuming everything should be replaced.
Connected context
Keeping the operational reasoning visible from discovery through implementation and review.
Client ownership
Designing the result so the responsible team can understand, operate and maintain it.
The operating context stays connected to the important decisions.
Sahaj Views is intentionally founder-led. The person involved in understanding the problem remains close to the decisions that shape the response and the review of what is delivered.
That does not mean every specialist task is performed by one person. It means the business context, trade-offs and design intent do not disappear as the work moves from discussion into execution.
Clear scope, visible decisions, appropriate specialist input, user involvement, documentation and accountable handover remain part of the work.
Understand the operating problem
Business situation, workflow, people and constraints.
Shape the recommendation
Keep, simplify, connect or build.
Direct the working change
Execution stays tied to the agreed operating intent.
Review use and ownership
Confirm the result works for the people who will run it.
A good fit when capable teams have outgrown informal coordination.
The common factor is not one industry or technology stack. It is an operation that needs more structure without becoming more complicated.
We work best with businesses willing to examine how work genuinely happens, what should remain, and where focused change will remove disproportionate effort.
Several useful systems exist, but the work between them is weak.
Routine progress still depends heavily on reminders and personal follow-up.
Information exists, but people struggle to find the current context quickly.
Leadership needs earlier visibility without adding reporting overhead.
The business wants to modernise without replacing everything at once.
The internal team should be able to confidently own the result.
A clear operating problem is enough to begin.
You do not need to arrive with a technology plan. Bring the part of the business that depends too heavily on follow-up, feels scattered, lacks visibility or no longer works cleanly as the business grows.