In short: Custom software pays off when an important process in your business costs several working hours every week in reconciling, searching and correcting, when several people work with it at the same time, and when no off-the-shelf software covers your process. If only one person works with the spreadsheet and the result is right, stay with Excel and tidy it up. In between there are shared lists and industry software, which you should check first.
How can you tell that Excel is reaching its limit?
The limit is reached when the spreadsheet no longer belongs to one person and a process of the whole business depends on it. In businesses with 10 to 50 employees, several people usually already work on quotes, orders and staff schedules, but there is no in-house IT department. These are the typical signs:
- Several people edit the same file. Co-editing in Excel only works under certain conditions. According to Microsoft, the file has to be stored in OneDrive or SharePoint Online, and everyone needs a current version with a Microsoft 365 subscription. If one person opens the file with an unsupported version, the others get a message that the file is locked.
- Copies travel by email. As soon as there is a file called “Quotes_new_final2.xlsx”, nobody knows for sure which version is the valid one.
- Formula errors go unnoticed. The researcher Raymond Panko analysed audits of real company spreadsheets. In the audits from 1997 onwards, 91% of the 54 spreadsheets examined contained errors. According to the same paper, a person checking a spreadsheet cell by cell on their own finds only about half of the errors. The analysis dates from 2000, and the way spreadsheets work has stayed the same since then.
- Everyone sees and changes everything. A file has hardly any levels of access. Anyone who can open it can usually also see purchase prices and customer data.
- Nobody can trace who changed what. If a customer complains, you then have no proof.
- Data protection. Article 32 of the General Data Protection Regulation (GDPR) requires appropriate protection of personal data. The WKO (in German) describes the goal as only authorised people having access to the data, and lists measures including internal access restrictions, role-based access rules and logged sign-ins. That is hard to achieve with a customer list that is sent around as an email attachment.
When should you keep Excel?
Keep Excel as long as one person maintains the spreadsheet, the amount of data is manageable and errors do not have expensive consequences. For calculations, analyses and one-off lists, Excel is a good tool that your staff already know how to use. Tidying up is often enough. Keep the file in one single place, lock the formula cells, separate input from analysis and name one person who is responsible. According to the studies cited by Panko, this cell protection is used in only half of spreadsheets or fewer, even though it is easy to set up.
What options do you have besides Excel?
You have four options, and the most expensive one is not automatically the right one. Check them in this order, because each step costs more and ties you in more than the one before.
| Option | Strengths | Limits | Fits if |
|---|---|---|---|
| Keep Excel and tidy it up | No new costs, everyone knows it | It is still a file, errors are noticed late, hardly any access rights | one person works with it and the process is simple |
| Shared lists such as Microsoft Lists or Airtable-style tools | Everyone works on the same version. Microsoft Lists offers version history per item, approvals and permissions down to the level of individual items | Calculations and multi-step processes quickly become hard to follow, connections to other programs are limited | the job is keeping lists, such as customers, equipment or open tasks |
| Off-the-shelf industry software | Proven, quickly available, maintenance by the vendor | Your business adapts to the program, ongoing licence costs per user, special cases end up back in Excel | your process matches what is usual in your industry |
| Custom software | Covers exactly your process, with permissions, history and integration with your existing programs | Highest upfront costs, you need to plan time for coordination, dependence on the developer | the process is what your business is built on and no standard product fits |
How do you work out whether custom software pays for itself?
Compare the hours lost today with the cost of the project. For two weeks, keep track of how much time goes into entering things twice, reconciling files, asking around and correcting. Multiply those hours by what one working hour costs your business.
Sample calculation with assumed figures
The following figures are made up and only serve to show how the calculation works. Use your own values.
- Three employees each lose three hours a week, nine hours in total.
- Assume one working hour costs the business €45.
- With 46 working weeks, that comes to 9 times 45 times 46, or €18,630 a year.
- Assume an application saves two thirds of that, which is €12,420 a year.
- With an assumed purchase price of €35,000, the outlay is recovered after just under three years. This leaves out the running costs of operation. With them, it takes longer.
On the benefit side, this calculation leaves out what is hard to put a figure on, such as a wrongly calculated quote or a forgotten appointment. If you arrive at one hour a week, a project of this size is not worth it.
To put the cost side in context, here are our own figures. With us, custom software usually costs between €20,000 and €80,000, and small applications and automations start at €5,000. If you buy, the source code is yours. You can then add operation and support as needed.
What does the same example cost in instalments?
Besides buying, we offer a model with a down payment and monthly instalments. In total it costs more than buying, but it spreads the payments and includes operation, support, bug fixes and security updates. For the €35,000 example, it looks like this:
- When you place the order, you pay 20%, which is €7,000.
- In the first three months after the application has gone live for you, you only pay for hosting, meaning running it on the server. During this time you can leave without a penalty.
- From month 4 to 24 you pay 5% a month, which is €1,750. After the first three months, the contract runs until month 24.
- By month 24 you have paid 125% in total, so €43,750 instead of €35,000.
- From month 25 you pay 1% a month, which is €350 or €4,200 a year, for as long as you use the application.
Hosting comes on top in every phase. Depending on how much computing power and storage the application needs, it costs €20 to €150 a month, more if the requirements are very large. With the €12,420 a year saved in the example, this model puts you in profit after a little over four years without hosting, instead of after just under three. With hosting, it takes roughly four and a half to five and a half years depending on the amount, counted from the day the application goes live.
In this model the source code stays with Fragon Studios. You get the operated application, an export of your data and a regulated exit. If Fragon Studios ever ceases to exist and ownership of the source code does not pass to another company, the source code will be published. You and any developer of your choice can then keep working with it. Before you sign, ask to be shown how this exit is set out in the contract. The details are in our answers on pricing.
How does replacing Excel work?
Replacing Excel happens in small steps, and the old spreadsheet is only switched off at the end.
- Write down the process. Who enters what, who needs which information, where do errors happen? The spreadsheet itself is the best documentation for this.
- Define the scope. You decide what the first version must be able to do and what can wait.
- Build and show a first version. Your staff try it out early and say what gets in the way in day-to-day work.
- Migrate the data. Existing entries are cleaned up and imported. This step often takes longer than expected, because old spreadsheets have been kept inconsistently.
- Work in parallel, then switch over. For a short time both systems run side by side. After that, the spreadsheet is kept only for reference.
- Support and extend. After launch, requests come up that nobody knew about beforehand.
With us, a single tool or automation takes two to four weeks, and a business application or customer portal two to four months.
What are the most common mistakes when replacing Excel?
Most mistakes happen before the first line of code is written, namely when deciding what to build.
- Rebuilding the spreadsheet one to one. Then you have an expensive spreadsheet. What is needed is the process behind it.
- Wanting everything at once. A single process that works well is worth more than five half-finished ones.
- Not asking the staff. The people who work with the spreadsheet every day know the special cases.
- Underestimating the data migration. Duplicate customers and inconsistent spellings cost time.
- Forgetting about operation. Clarify in advance who makes the backups, who answers questions and what changes cost.
- Not checking off-the-shelf software. If a ready-made product covers most of what you need, it is usually the cheaper choice.
Frequently asked questions
How many employees do you need before custom software is worth it?
Headcount is not what decides it. What matters is how many hours a week a process costs and how expensive errors in it are. A business with twelve employees and complex staff scheduling can get more out of it than one with forty employees and simple processes.
Do we have to give up Excel completely afterwards?
No. Excel remains useful for analyses and one-off calculations. A good application can export data as an Excel file so you can keep calculating with it. Only Excel's role as a shared data store is replaced.
What happens to our existing data?
It is migrated. Before that, it is cleaned up, which means removing duplicates and making spellings consistent. The old file is kept as an archive so you can look up older records.
Where is our data stored with a custom application?
That depends on the provider and should be stated in the quote. Applications that we operate run on our own servers in Hetzner data centres in Germany and Finland. Ask every provider about access rights, backups and a data processing agreement as well.
What if our process changes later?
Then the application is adapted. That is the main difference from off-the-shelf software, where you wait for the vendor. Before placing the order, clarify how changes are billed and how quickly someone can be reached.
How do we find out whether it is worth it for us?
Track the hours for two weeks and do the calculation as in the example above. If you would like to go through the result with someone, write to us. We will also tell you if Excel or a ready-made product is the better choice for you.
Sources
- Raymond R. Panko: Spreadsheet Errors: What We Know. What We Think We Can Do. Proceedings of the Spreadsheet Risk Symposium, European Spreadsheet Risks Interest Group (EuSpRIG), 2000, published on arXiv
- GDPR: Data security through technology and privacy-friendly default settings (in German). Austrian Economic Chamber (Wirtschaftskammer Österreich)
- Collaborate on Excel workbooks at the same time with co-authoring. Microsoft Support
- Introduction to lists. Microsoft Support
