Short answer: when should you replace Excel with custom software?
Replace Excel with custom software when a spreadsheet stops being an analysis tool and starts running a process that several people depend on: quotes, orders, stock, scheduling, commissions or customer records. At that point every copy, version and manual paste is a cost and a risk.
You do not always need custom code. If the process is simple and lives in one team, a no-code tool such as Microsoft Power Apps, Airtable or Google AppSheet is often enough. Custom software is the right call when the spreadsheet connects several departments, has to sync with an ERP or accounting system, or carries business rules that nobody can safely change any more.
Why do companies end up running on spreadsheets?
Because Excel is the fastest way to build a process. Someone needed to track quotes, built a sheet in an afternoon, and it worked. Then a second person needed it, then a lookup to the price list was added, then a macro, then a copy per salesperson. Five years later the spreadsheet is your operating system and nobody planned it.
That history is useful. A spreadsheet that has run your business for years is the best specification you will ever get: it shows the real fields, the real exceptions and the real rules. The goal is not to throw it away but to turn it into something several people can use at once without breaking it.
7 signs it is time to move off Excel
If three or more of these are true, a spreadsheet is costing you more than it saves.
- Version conflicts. Files named "quotes_final_v7_Maria.xlsx" exist, and people regularly overwrite each other's changes.
- Copy-paste between systems. Data is typed from the spreadsheet into the accounting system, ERP, email or a supplier portal, every day.
- One person holds the keys. Only one colleague understands the formulas or macros, and their holiday is a business risk.
- Nobody trusts the totals. Monthly reports start with an hour of checking whether the numbers are right.
- No permissions. Everyone can see salaries, margins or customer data, or you have split files just to hide columns.
- No history. You cannot tell who changed a price or a status, or when.
- It does not work on a phone. Technicians, drivers or sales staff in the field call the office to update the sheet.
The first two signs are the expensive ones. Version conflicts cost you decisions made on wrong data; copy-paste costs you hours every week and produces the errors that end up on invoices. The last sign, no mobile access, is often the one that triggers the project, because field staff calling the office is visible to everyone.
What can stay in Excel?
Not everything should move. Excel is still the best tool for:
- One-off analysis, forecasts and what-if models built by one person.
- Ad-hoc reports on data exported from your systems.
- Budgets and plans that finance owns and nobody else edits.
- Prototypes of a new process, before you know what it should look like.
The rule of thumb: if a spreadsheet is read by many but edited by one, and nothing downstream depends on it being correct within the hour, leave it. If many people edit it and other work waits for it, it is a process, and processes belong in software.
Options: keep Excel, go no-code, buy SaaS or build custom
Be honest about the process you are replacing. Most companies need a mix.
| Option | Good fit | Strengths | Limits |
|---|---|---|---|
| Keep Excel, add structure | Analysis, one owner, low volume | Free, familiar | Rules, permissions and history stay weak |
| Shared Excel in Microsoft 365 or Google Sheets | Small teams editing the same list | Co-authoring, version history | Still no real permissions or integrations |
| No-code app (Power Apps, Airtable, AppSheet) | Simple forms, approvals, one department | Fast, cheap to start, built by staff | Complex logic and integrations become hard to maintain |
| SaaS for that process (CRM, field service, inventory) | Standard processes | Ready on day one, vendor maintains it | You adapt to their workflow; per-user fees |
| Custom application | Cross-department processes, ERP sync, special rules | Fits your process exactly, no per-user licence | Upfront cost; needs a clear specification |
Our honest advice: if a standard SaaS covers 80% of the process and your team can live with its workflow, buy it. If your spreadsheet exists precisely because standard tools did not fit, a SaaS will likely just add one more system to copy data into.
How do you replace a spreadsheet, step by step?
- Inventory the files. List every spreadsheet that runs a process, who edits it, how often and what it feeds. You usually find three to five core files and many satellites.
- Map the process, not the columns. Write down the steps: who creates a record, who approves it, what happens next. Columns tell you the data; steps tell you the software.
- Decide the source of truth. For each type of data (customers, items, prices, orders, invoices) choose one owner. Usually the ERP or accounting system owns the money; the new app owns the workflow.
- Clean the data. Remove duplicates, standardise names, fix formats for dates, VAT numbers and phone numbers. This is often half the migration effort.
- Build the first phase around the most painful file. Replace one core spreadsheet completely rather than five halfway.
- Run in parallel. For two to four weeks, the new app and the old sheet run side by side. Compare totals daily.
- Switch off and lock. Make the old files read-only, keep exports available and remove the temptation to go back.
Common errors at this stage: importing dirty data and blaming the software, building every exception from day one, and letting a department keep "their own copy" in Excel after go-live.
What should the replacement do that Excel cannot?
When you brief a developer or evaluate a tool, these are the capabilities that justify the move. If a candidate does not offer most of them, it is just a more expensive spreadsheet.
| Capability | Why it matters |
|---|---|
| Roles and permissions | Sales sees prices, not salaries; technicians see their jobs, not margins |
| Audit trail | Every change to a price, status or customer has a name and a time |
| Validation | VAT numbers, dates and mandatory fields are checked when entered, not at month end |
| Workflow and approvals | A discount above the limit or an order above a value goes to a manager automatically |
| Integrations | Customers, items and invoices sync with the ERP or accounting system through an API |
| Mobile access | Field staff update jobs from a phone, with photos and signatures |
| Dashboards and exports | Management sees live numbers; anyone can still export to Excel for analysis |
The integration line is usually what separates a no-code app from a custom one. Reading and writing a few lists is easy everywhere. Keeping customers, prices, stock and invoices consistent with Business Central, SAP or your accounting tool, with error handling when the other side is down, is where custom work earns its price.
Manual vs automated: how many hours do you get back?
Here is an example for an office team of five who run quotes, orders and reporting from spreadsheets. Replace the minutes with your own.
| Task | Manual per week | Automated per week |
|---|---|---|
| Copy orders from spreadsheet into accounting | 5 h | 0.5 h (check exceptions) |
| Merge colleagues' versions and fix conflicts | 3 h | 0 h |
| Build the weekly management report | 4 h | 0.5 h (dashboard) |
| Answer "what is the status of X?" questions | 4 h | 1 h |
| Check and correct errors found later | 3 h | 1 h |
| Total | 19 h | 3 h |
Fill in your own numbers:
- Manual hours per week: ___ − automated hours per week: ___ = ___ hours saved per week.
- Hours saved × 46 working weeks × hourly cost (salary plus overheads) = ___ per year.
With the example, 16 hours a week × 46 weeks is 736 hours a year. At €30 an hour that is roughly €22,000 a year, before you count the cost of errors such as an invoice never sent or a wrong price quoted. If your number is small, a no-code tool or a cleaner spreadsheet is the better investment.
What does it cost to replace Excel over 3 years?
All figures are estimates for a team of 10 users. SaaS and no-code prices vary by vendor, plan and region and change often, so treat them as ranges and check the vendor's page. Custom figures are typical market ranges, not a Raao price list.
| Option | Year 1 | Years 2–3 | 3-year total (estimate) |
|---|---|---|---|
| Shared Excel (existing Microsoft 365) | €0 extra | €0 extra | €0, but manual hours stay |
| No-code app, 10 users | €1,000–4,000 licences + build time | €1,000–4,000 / year | €3,000–12,000 + staff time |
| SaaS for the process, 10 users | €2,000–12,000 + setup | €2,000–12,000 / year | €6,000–36,000 |
| Custom application, first phase plus hosting | €10,000–25,000 build + €1,100–3,600 hosting | €1,100–3,600 / year + changes | €13,000–36,000 |
The custom row assumes a focused first phase: one or two core spreadsheets replaced, a few roles and one accounting or ERP connection. A multi-department platform with two-way ERP sync is a bigger job, typically €20,000–45,000 for the first phase on the same estimate basis.
Two things the table does not show. The no-code row hides the time of the person who builds and maintains the app, often your most expensive operations person. The custom row has no per-user licence, so hiring ten more people does not change the bill.
At Raao we keep the risk low. A free 30-minute call tells you whether custom makes sense at all. If it does, a paid discovery workshop maps your processes and spreadsheets and produces a written specification, architecture and a fixed quote that are yours to keep. The build then runs in phases, each priced and approved separately, with the first usable module live in weeks. You pay 30% upfront and the rest on milestones, with no licence fees, and hosting and maintenance starts from €89 a month. See how we approach it on the custom software page.
If your spreadsheet is mainly a quote and invoice tracker, read quote to invoice software. If it is really a CRM in disguise, compare custom CRM vs HubSpot.
How we did it for xcrm
xcrm, the CRM and ERP hub we built for a multi-company retail group, replaced exactly this kind of patchwork. Several companies shared one ERP but managed leads, quotes, projects and marketing data in separate tools.
- Opportunities, pipeline stages, contacts, quotes, contracts and projects in one application.
- Fast access to Business Central items, orders, invoices, stock and vendors for the sales team.
- Meta Lead Ads captured straight into the CRM, instead of exported lists.
- Marketing reporting from GA4, Google Ads, Meta Ads and TikTok Ads in one view.
- Webshop orders pushed to Business Central automatically, plus Microsoft 365 mail and Planner integration.
The result is one place for sales, marketing and operations data, and faster answers for sales and management teams.