The Growth Gap is a practical book for owners of Indian businesses growing from 20 to 150 people. It shows why things start slipping as you grow, and how to fix the right process first.
₹399 · Paperback · 18 chapters · About a 2.5-hour read · First published October 2026
About the book
At eight people, you knew everything. A customer called, and you knew the customer. An order was delayed, and you knew why.
Now you’re at forty, or eighty. The same questions come back to you every day. How many leads came yesterday? Which salesperson is performing? Why did sales drop? And too often the answer is: “I’ll check and get back to you.”
That gap is where many growing businesses start struggling.
Most businesses don’t have a people problem or a software problem. They have a Growth Gap: the business has outgrown the way it is being run, and nothing has been built to replace the owner’s memory.
The Growth Gap shows you how to find where information gets stuck, fix the process first, and only then decide whether automation, AI or a better workflow is the answer.
Drawn from 50+ automation projects across 28+ businesses. Client names are kept confidential.
It knew its annual profit, but not which projects made money. Project-level costing showed that several projects it believed were profitable were quietly losing three to five percent.
It asked for one consumption report. The real problem was inventory, and the fix became stock tracking that flags items nearing expiry and fast-consuming products.
It had plenty of customer data, stored in many places and connected nowhere, until every source fed one sales process.
It replaced its telecallers with voice AI agents. Technically, it worked. But the AI cost more than the people it replaced, and the project was eventually pulled.
The last one is the most useful story in the book. Knowing when not to automate matters as much as knowing how.
This book isn’t about buying more software. It isn’t about collecting automation tools. It isn’t about putting AI into every department.
The first question should always be: what business problem are we trying to solve? Intelligence comes last, once there is a process worth making smarter.
The book’s REPETITION Test decides which processes deserve automation, and which don’t yet. Ask it of any process you’re considering.
The easiest process to automate is not always the best process to automate first.
A business owner once asked us to automate an entire process. The more we questioned it, the more we found: unnecessary steps, approvals that existed only out of habit, information entered twice.
If we had automated it exactly as it was, we would have created a faster version of the same inefficiency.
Prediction helps us deal with what we don’t know yet, but can estimate from patterns. If you have a clear rule, when X happens do Y, there is often no reason to add AI.
Neither replaces human judgement. Both can make human judgement more effective.
The price of an automation project is visible. The cost of a bad process is often scattered across the business: employee hours, rework, errors, missed opportunities, customer loss, management time and delayed decisions.
Ask not only “How much will this cost?” Also ask “How much will it cost us to continue doing this the current way?”
“Don’t automate because you can. Automate because you should.”
From The Growth Gap
How a growing business quietly loses sight of itself, and why the problem is almost never the people.
How to decide what deserves automating, what to leave alone, and how to build the first one properly.
What automation is worth, how to run the first project, and what changes once there is more than one.
“Automation starts when you stop accepting repetitive problems as ‘just the way things are done.’” From The Growth Gap
I come from a technology background. I spent around 14 years in web application development. For a long period, my world was software, applications and technology.
Then I moved towards agriculture. Irrigation depended on people being available at the right time, so I kept asking why I should keep doing the same thing manually when the problem kept repeating. That led to drip irrigation, then automatic motor starters, then mobile-based control.
Instead of thinking only about the task, I was thinking about the system around the task. That shift is the whole of this book.
At a farmers’ summit, a farmer of around 70 heard that I had left IT for farming. He asked me:
You have all studied IT. If you can’t find a way to solve our problem, and you turn up carrying a spade just like us, then what is the meaning of it?
That question pushed me towards marketing. We could generate leads for businesses, but many of those businesses struggled to follow up with them properly. The problem was rarely a lack of leads. It was what happened after the lead arrived.
That’s what pulled me from marketing into systems, and eventually into automation. Across more than 28 businesses and 50 automation projects, the industries changed but the problem rarely did.
Winner of AITHON 25, Coimbatore
Winners of the GEN AI Architect Buildathon
Revenue Rockstar Award
Eagle Award
TN Digital Summit 2025
DigitAll Sangamam 2025
“A good employee inside a bad process can look like a bad employee.”
From The Growth Gap
No. There is no code in this book and no particular tool you have to know. What you need is a willingness to look at a process you have stopped noticing.
Partly. It explains where AI genuinely helps, and where a simple rule or a better process does the job better and cheaper. If you have a clear rule, when X happens do Y, conventional automation may be ideal.
No. It helps you decide what to fix and why. Choosing tools comes after that, and the book shows you how to decide whether to build, buy or connect what you already have.
Yes, if you’re feeling the strain of growth. The ideas apply most directly to businesses of 20 to 150 people, where the gap is widest.
Pick one process. Not the biggest one. One that happens every day and irritates you. Then run it through the REPETITION questions: is it repeated, easy to explain, predictable, error-prone, time-consuming, information-based, trigger-based and impactful?
Because automating a process exactly as it is creates a faster version of the same inefficiency. Understand it first, remove steps that add no value, simplify and standardise, and only then automate.
About two and a half hours. Most chapters end with a short exercise you can try on your own business.
Yes. Use the bulk order option in the Get your copy section, or message Sivaraj on WhatsApp.
₹399 · Paperback, first edition. Delivered across India.
Buying for your team? Ordering 10 or more copies for your managers? Ask about a bulk order.
Request a bulk orderMost of this book you can act on yourself. But some problems are hard to see from inside the business. If you’d like a second pair of eyes, I’m not difficult to find.