Ask the owner of any 20–50 person business in Pune or Mumbai where their operations data lives, and you’ll get a variation of the same answer: “We have an Excel file for that.”
Inventory: Excel. Purchase orders: Excel. Attendance: Excel. Customer follow-ups: Excel. GST reconciliation: Excel. And usually, six different people have six slightly different versions of the same Excel, none of which agree with each other on a Tuesday afternoon.
This is not a criticism. Excel is genuinely impressive. Most businesses can run entirely on spreadsheets for their first few years and do it well. The problem is that Excel never tells you when you’ve outgrown it. You have to figure that out yourself, usually after something goes wrong.
What Excel actually does well
Before talking about the problems, it’s worth being honest about why Excel sticks around so long.
It’s fast to build something in. You don’t need a vendor, a contract, or a three-month implementation. You open a file, type some columns, and you’re running. The formula language is powerful enough to do real calculations. Pivot tables can answer complex questions without any training. And every employee you’ll ever hire already knows how to use it.
For a business under ten people handling a manageable volume, this is a completely rational choice. Don’t let anyone sell you software you don’t need yet.
The signs you’ve actually crossed the line
The trouble with Excel is that the problems don’t arrive all at once. They stack up slowly. By the time something breaks badly enough to notice, the root cause has been there for a year.
These are the signs we see in almost every business that reaches out to us:
1. Someone’s full-time job is copy-pasting between files. There’s a person — or a founder — who spends 2–3 hours a day moving data from one sheet to another. Inventory out of one file, purchase order into another, billing into a third. The moment you’re paying a salary to maintain a spreadsheet pipeline, the spreadsheet has already cost more than the system that would replace it.
2. You can’t answer basic questions without 15 minutes of digging. “What’s our stock of 10mm bolts right now?” “What invoices are outstanding from last month?” “How many service calls did we close this week?” If getting to a number requires opening three files, filtering two columns, and calling someone on WhatsApp for clarification — the data is there, but it’s not actually accessible.
3. You’ve had a serious mistake caused by the wrong version of a file. A quotation sent at the old price. A purchase order raised for stock that was already ordered. Payroll run on last month’s attendance sheet. These are not careless errors. They’re structural errors — the system allows multiple versions to exist simultaneously, so someone will eventually use the wrong one.
4. New hires take a month to understand “how we do things.” Because the process lives inside people’s heads and inside unnamed columns in shared files, every new employee needs a senior person to explain the workflow. That explanation happens again with the next hire, and the next. The knowledge never gets written down because there’s nowhere obvious to write it.
5. You’ve started saying “we’ll fix the data later.” Later never comes. The backlog of messy, duplicate, or missing records grows every week. At some point the spreadsheet data is so untrustworthy that people stop using it and go back to WhatsApp and memory. The Excel is still open — it’s just not the real system anymore.
If two of these are true for your business, you’re already past the point where Excel is helping more than it’s hurting.
What a custom ERP is (and isn’t)
Most people hear “ERP” and think SAP. Seven-figure implementation. Two years of consultants. Every process redesigned from scratch. That is one kind of ERP. It’s not what we’re talking about.
What we mean is a custom web or mobile application — built specifically for how your business runs — that handles the workflows your team does every day. Stock in and out. Purchase orders to suppliers. Customer orders and deliveries. Invoicing with GST. Service tickets and technician assignments. Whatever your actual operations look like.
The difference between this and a generic ERP is that a generic ERP ships with hundreds of features your business will never use, and often doesn’t have the three things your business actually needs. You end up adapting your process to the software. A custom system is built the other way around.
It also doesn’t have to cost ₹20 lakh. A focused system that handles three or four core workflows for a 30-person operation can be built, tested, and deployed in 8–12 weeks. The scope defines the cost, not the word “ERP.”
What the move actually looks like
The businesses we’ve worked with typically follow the same path.
First, we map the existing workflow on paper — or sometimes in the existing Excel files. Not to criticise what’s there, but to understand what’s actually happening versus what the official process says should happen. They’re usually different.
Then we build a minimal version: just the two or three workflows that cause the most pain. Inventory and purchase orders. Or sales orders and invoicing. We don’t try to replace everything in the first release.
The team runs both systems in parallel for three to four weeks. This is important. You don’t flip a switch. People trust what they know, and trust has to be earned by the new system before the old one is retired.
After that, we add the next set of features, based on what the team has actually asked for after using it — not what anyone predicted before.
The whole process, for a focused scope, takes three to four months from first call to the old Excel files being archived.
One thing worth knowing
The hardest part of this process is never the software. It’s getting everyone to agree on what the process actually is. Excel lets every department run a slightly different version of reality. A shared system forces a single version. That conversation — about whose version wins — is where most of the time goes.
It’s also where most of the value comes from. By the end of it, the team has a shared understanding of how the business runs that didn’t exist before.
If you’re at the point where the spreadsheets are becoming more problem than solution, we’re happy to talk through what a practical move would look like for your specific setup. Book a free 30-minute call — no pitch, just a conversation about whether a custom system makes sense for you right now.
We also build CRM systems, mobile apps for field teams, and AI automation for Indian SMBs. If the problem is bigger than one spreadsheet, we can help scope that too.