Home
Our Approach

How our business consulting worksThe SAI Consulting Approach

A consulting engagement is not a project with a fixed deliverable. It is a process of building capability — in the systems and in the people who run them. Here is exactly how that process works.

Phase OneFirst Conversation

Understanding Before Proposing

Every engagement begins with a conversation — not a sales presentation. We want to understand your business, your situation, and your goals before we propose anything. This is not courtesy — it is methodology. An engagement designed without this understanding will solve the wrong problems.

We listen to how you describe the challenges in your business — the language matters as much as the content
We ask about what has been tried before and why it did not hold
We are honest about whether we are the right fit — not every business needs every service, and we say so
If the conversation suggests a diagnostic is warranted, we propose one — a structured visit before any engagement is designed

1 to 2 hours · No obligation

Phase TwoDiagnostic Visit

Seeing the Business From the Inside

The diagnostic is where we form our actual understanding of the business. We spend time on the floor, in the departments, and with the people — not just in the owner's office. What we observe and what we are told are often different, and that difference is where the real problems live.

We observe production flow, team interactions, and management practices in real time
We review existing reports, SOPs, and systems — whatever exists
We speak with managers, supervisors, and operators — at their level, in their language
We identify the gap between how the business is supposed to work and how it actually works
We document findings in a structured report with clear priority areas

1 to 3 days on-site · Structured MOM delivered

Phase ThreeEngagement Design

A Programme Built for Your Business

Based on the diagnostic findings, we design a consulting engagement that is specific to what your business needs — not a template programme applied uniformly. The scope, timeline, and structure of the engagement are agreed before any work begins.

Priority areas are sequenced logically — foundational systems before advanced ones
Timelines are realistic — we do not promise transformation in 30 days
The engagement is designed as a programme, not a series of one-off visits
Roles and responsibilities on both sides are agreed in advance — what we do, what your team does
A formal proposal and engagement agreement is provided before work begins

Proposal delivered within 5 working days of diagnostic

Phase FourImplementation

Building Alongside Your Team

This is where most consulting engagements fail — and where SAI is most different. We do not design systems and hand them over. We build every system alongside the people who will run it, so that ownership transfers from day one of implementation, not at the end.

Regular on-site presence — not monthly check-ins from a distance
Systems are built in working sessions with the actual team, not prepared offline and presented
Problems that surface during implementation are solved in real time, on the floor
Accountability is held — actions are tracked, follow-through is expected, and drift is corrected
Every tool, format, and system is tested in the actual environment before it is finalised
The PDCA discipline — Plan, Do, Check, Act — is embedded into every system and every review

6 to 24 months depending on scope · Regular on-site presence

Phase FiveHandover & Independence

Leaving When the Team Is Running It

The goal of every SAI engagement is for our involvement to become unnecessary. We measure success not by what we delivered, but by whether your team is running the systems we built together — independently, consistently, and with genuine understanding of why each element exists.

Handover is planned, not abrupt — we reduce involvement gradually as team capability increases
We verify independently that systems are running correctly before stepping back
A post-engagement review is conducted to confirm sustainability
Ongoing support is available if new challenges arise — but it should be the exception, not the norm
The measure of a successful engagement: three months after we leave, the systems are still running

Structured handover · Post-engagement review at 90 days

What we believe

The Principles Behind the Approach

Diagnosis Before Prescription

We never arrive with a solution. We arrive with the discipline to understand the problem correctly before recommending anything. A wrong diagnosis wastes time, money, and trust — all three of which MSME owners have in limited supply.

Presence Over Reports

A consulting report is only as valuable as what changes because of it. We measure our work not by the quality of the documents we produce, but by the changes we observe on the floor over time. That requires presence — not remote advisory.

People Are Not the Problem

When things go wrong in a business, the instinct is to blame people. In our experience, the root cause is almost always structural — unclear roles, fragmented information, absent systems. Fix the structure, and the people perform.

The Check Step Is Non-Negotiable

Plan, Do, Check, Act. The Check step is the most consistently missing element in MSME management discipline. Without it, actions are taken, but whether they worked is never verified. We build the Check into every system we design.

Independence Is the Outcome

We do not build businesses that need us to function. We build businesses that can function without us — and call us when they want to go further. Dependency on a consultant is not a result. It is a failure of the engagement.

The Human Layer Is Not Optional

Every framework needs two layers to work: the structure — SOPs, KPIs, reporting formats — and the human layer — how people speak, behave, and connect their work to purpose. Most consultants build the first. We stay for both.

“We build the framework. We stay until the people inside it are running it themselves.”
Deepak B. Gondkar

Start a Conversation