The order sheet began as one tab. Now it has fourteen, three people keep their own copies, and one colleague is the only person who knows why column Q is yellow. Month-end means an afternoon of matching one file against another. Someone has said the business should move from Excel to custom software. Before you price anything, it is worth working out whether the spreadsheet is the problem at all.
We are a product engineering team at Infopark in Kochi. We build web applications and internal tools for businesses in India, the UAE and Australia, and a good share of the enquiries we receive begin with a spreadsheet that has grown too large. Some of those businesses need software. Others need a tidier sheet, and we say so.
The short answer
A spreadsheet is a tool for calculation and analysis. It stops working when it is used as a system: when several people enter data at once, when work has to pass from one person to the next, and when you need to know who changed what. If the sheet is a calculation that one or two people own, keep it. If the sheet is running a process, look at a packaged tool first and custom software second.
What spreadsheets do well
Excel and Google Sheets are flexible, familiar and already paid for. Anyone in the office can open one. A new column takes a second. A pivot table answers a question that would take a developer a day to build as a report. Nothing else lets a business owner model a price change or a cash position as quickly.
That flexibility is the reason spreadsheets are everywhere, and it is a real strength. A sheet imposes no structure, so it fits any business on the first day. Software does the opposite. It fixes a structure and enforces it, which is useful only when you are sure what the structure should be.
Stay on spreadsheets and stop reading if these are true. One or two people maintain each file. The sheet is used to analyse or plan, not to run daily work. A mistake in it would be noticed and corrected without cost to a customer. The process it supports is still changing from month to month. Software built around a process that has not settled will be rebuilt within a year.
Signs a spreadsheet has become a system
A spreadsheet has become a system when people depend on it to tell them what to do next, not only to tell them a number. These are the signs we see most often.
There is more than one version of the truth
The file is emailed or sent on WhatsApp, edited and sent back. Sales has one copy, the store has another, and the owner has the one from last Tuesday. A shared online sheet solves the copying problem, because everyone edits the same file. It does not solve the next one, which is that anyone can change anything.
One person understands it
The formulas, the lookups between tabs and the macros were written by one person over several years. When that person is on leave, nobody adds a product or closes the month. When that person resigns, the business discovers how much of its process lived in their head.
Status lives in colours and comments
A row turns green when the order is dispatched and red when payment is late. A column says pending, approved or hold. This is a workflow, kept by hand. Nothing moves the row forward, reminds the next person or stops a step being skipped. The sheet records what people remember to record.
You cannot say who changed what
A price was different yesterday. A quantity was overwritten. A formula was replaced by a typed number and every total below it is now wrong. Online spreadsheets keep a version history, which helps you find an old copy. It is not the same as a record that says this person approved this discount on this date.
Everyone can see everything
A spreadsheet is shared as a whole file or a whole tab. Sheets and ranges can be protected, but showing each salesperson only their own customers, or hiding cost prices from one role and not another, means splitting the data into separate files. Then the files have to be merged again, by hand.
The same data is typed more than once
An order is entered in the order sheet, again in the dispatch sheet and a third time in the accounts. Each retyping is a chance for a mistake, and the three records drift apart. The reconciliation at month-end exists only because the data was entered three times.
People outside the office need to use it
A driver has to confirm a delivery. A site supervisor has to log material received. A customer wants to see the status of an order. A spreadsheet is awkward on a phone and was never meant to be opened by a customer. This is usually the point where a business starts looking for something else.
Spreadsheet, packaged tool or custom software
There are three places for a business process to live, and custom software is the most expensive of them. The middle column is where most businesses should look first.
| Spreadsheet | Packaged or no-code tool | Custom software | |
|---|---|---|---|
| Best for | Calculation, planning and analysis by one or two people. | A standard process such as accounts, payroll, a sales pipeline or a simple form and list. | A process that is specific to your business and that many people work in every day. |
| Time to first use | Minutes. | Days to weeks. | Weeks to a few months for a first release, depending on scope. |
| Cost profile | Already paid for. The cost is the time spent maintaining and reconciling. | A recurring subscription, often per user. | A larger upfront build, then hosting and maintenance. |
| Structure | None. Any cell accepts anything. | The vendor's structure, which you configure within limits. | Your records, rules and steps, enforced by the system. |
| Who sees what | Whoever has the file sees the file. | Roles and permissions as the product defines them. | Roles and permissions as your business defines them. |
| History of changes | Version history of the file, where it is kept online. | Usually an activity log on each record. | An audit trail on each record, designed around the questions you need answered. |
| Mobile and outside users | Awkward. | Often a mobile app, and sometimes a customer portal. | Built for the people and devices that will use it. |
| Who can change it | Anyone, which is both the strength and the weakness. | An administrator for settings, the vendor for the product. | Your chosen development team. You hold the source code. |
| Main risk | Silent errors, and dependence on one person. | Bending your process to fit the product, and fees that rise with headcount. | Delivery risk, reduced by a small first scope and phased releases. |
Try the cheaper options first
A messy spreadsheet can often be repaired. Keep one master file online instead of many copies. Give each tab one purpose. Lock the formula cells. Use drop-down lists so that a status is always spelt the same way. An afternoon of tidying can put the decision off for a long while.
If the problem is a standard one, a packaged product already solves it. Accounting belongs in accounting software. Payroll for a business with ordinary pay rules belongs in a payroll product. A conventional sales pipeline belongs in a packaged CRM. We have written about where each of these runs out: Tally vs ERP, custom vs off-the-shelf CRM and whether to build or buy an HRMS.
No-code tools sit between the two. They let a non-developer build a form, a list and a few rules without writing code. They suit a small team with a simple process, and they are a good way to learn what you need before paying for a build. They strain when the rules become complicated or when the data has to connect to several other systems.
How to decide whether to move
Decide on how the sheet is used, not on how large it is. A large file that one analyst owns is fine. A small file that eight people update all day is a system in disguise. Answer these questions about the sheet that causes the most trouble.
How many people enter data into it, and how many of them work outside the office?
Does work pass from one person to another through it, with a status that somebody has to remember to update?
If a figure in it were wrong for a week, what would that cost: a correction, or a wrong delivery, a wrong invoice or a missed payment?
How much time goes into copying data between files and reconciling them at the end of the month?
If the person who built it left tomorrow, could anyone else keep it running?
Has the process behind it stayed the same for the last six months?
Does a packaged product already do this job well enough?
If few people use the sheet and mistakes are cheap, stay where you are. If a packaged product fits, buy it. If many people work in the sheet every day, the process is stable and no product fits without heavy workarounds, custom software is worth scoping. When the sheets in question hold stock, orders and purchasing together, our guide to custom ERP development explains how that kind of system is planned.
If you move: from Excel to custom software, one workflow at a time
A sensible move replaces one spreadsheet-run workflow, proves it in daily use, and only then takes on the next. Replacing every sheet in the business at once is the usual way these projects fail.
Pick one workflow. Choose the one that costs the most today, such as order to dispatch, purchase requests or job tracking.
Write down the records and rules. What is an order, what states can it be in, who may move it from one state to the next. This is agreed in plain language before any screen is drawn.
Clean the data. Customers entered under three spellings and products with no code are fixed in the spreadsheet first, so the new system starts with data people trust.
Import, then run in parallel. The existing rows are loaded, and for a short period the team keeps the old sheet alongside the new system to check that the two agree.
Keep the export. People will still want to analyse figures in Excel. A good system lets them export a report and do that, without the spreadsheet being the place where data is entered.
That is the shape of a first release on our six-stage process from discovery to growth: one workflow moved out of spreadsheets, with user roles, reports and an audit trail, and working software to look at every fortnight. If discovery shows that a packaged product or a better-organised sheet would solve the problem, we say so.
Frequently asked questions
When should a business move from Excel to custom software?
When a spreadsheet is running a daily process that several people depend on, the process is stable, mistakes in it cost money, and no packaged product fits without heavy workarounds. If any of those is missing, a cheaper option is usually better.
Is Google Sheets a good enough replacement for Excel files sent by email?
Often, yes. A shared online sheet removes the problem of several copies, because everyone works in one file. It does not add roles, steps or an approval record, so it helps with versions and not with workflow.
Can our existing spreadsheet data be moved into new software?
Yes. Rows in a spreadsheet can be imported once they are consistent. The work is in the cleaning: duplicate customers, missing codes and free-text fields that hold three kinds of information. Budget time for it, because it is the item most often left out of a plan.
Will we stop using Excel altogether?
No, and you should not try to. Excel remains the right tool for analysis, forecasts and one-off questions. What changes is that the data is entered once, in a system, and Excel reads an export of it.
Is custom software always better than a packaged product?
No. A packaged product that fits is quicker to start and costs less upfront. Custom software earns its cost only when your process differs from the standard one in ways that matter to the business.
Conclusion
Moving from Excel to custom software is the right step for some businesses and an expensive distraction for others. The test is how the spreadsheet is used. A sheet that calculates should stay a sheet. A sheet that several people work in all day, that carries status from one person to the next and that nobody can audit, is doing the job of software without any of the safeguards. Tidy it first, check the packaged options second, and build only what is left.
We are happy to look at the spreadsheets your business runs on and give a straight answer, including when the answer is to keep them. Tell us how the work moves today and we will start from there.
Human. Digital. Future.
