Contents
Excel comes with Microsoft 365 Business Standard, at €12.13excl. VAT per user per month on an annual commitment in France: the license is not the problem. The real cost of a shared file is the time spent re-entering and checking data; an app at $6,800 to $22,400 (€6,000–€20,000)excl. VAT pays for itself once that time exceeds a few hours a week.
Almost every company has an Excel file that has become critical: a schedule, order tracking, a production sheet, a price list, case tracking. It is shared, edited by several people, and everyone knows it is fragile. The license costs next to nothing; what costs money is the time spent around the file. Here is how to put a number on that cost, compare it with a custom app over 3 years, and know when to keep Excel.
What Excel really costs
Excel is part of Microsoft 365. Public prices checked in October 2026 on Microsoft’s French page for Microsoft 365 Business Standard, per user per month, excluding VAT:
| Microsoft 365 Business Standard plan | Annual commitment | Monthly payment |
|---|---|---|
| With Teams | €12.13 | €14.56 |
| Without Teams (European Economic Area) | €9.34 | €11.21 |
You pay for these licenses anyway, for email and office tools. Replacing a shared file with an app does not remove them. The useful calculation is therefore about something else: time and errors.
The hidden cost of a shared file
A shared Excel file generates four types of cost that are rarely measured:
- Re-entry: the same data is typed into the file, then into the ERP, the CRM or invoicing.
- Checking: someone checks every week that formulas have not been overwritten and rows are complete.
- Competing versions: “tracking_v3_final_JM.xlsx” circulates by email, and nobody knows which one is current.
- Errors: a badly copied cell, a forgotten filter, a row deleted by mistake, and an order goes out at the wrong price.
None of these costs appear in an IT budget, but they are paid every week in salaries.
The 3-year calculation
An illustrative example, with made-up amounts to replace with your own: 10 people each spend 2 hours a week entering, checking or consolidating data around the file, at a fully loaded hourly cost of €35, over 45 working weeks a year. Cautious assumption: the app removes half of that time, not all of it. App at $13,500 (€12,000)excl. VAT, plus €2,000 a year for hosting and maintenance. Microsoft 365 licenses are the same in both scenarios and are not counted.
| Scenario | Annual cost | 3-year cost |
|---|---|---|
| Status quo: time spent around the file | €31,500 | €94,500 |
| App: remaining time (half) | €15,750 | €47,250 |
| App: development and maintenance | €2,000 a year, plus $13,500 (€12,000)excl. VAT upfront | €18,000 |
| Total with the app | €65,250 |
In this example, the app saves about €29,000 over 3 years once its own cost is deducted. With 3 people at 1 hour a week, the math no longer works: the time saved does not pay back the investment. That is exactly why you need to run the numbers with your own figures. The method is detailed in the ROI of a business tool.
When to keep Excel
Excel is still the right tool if:
- the file is used by one or two people, with no concurrent editing;
- it is used for analysis or modeling, not to run a process;
- the need is occasional or changes every time;
- an error has no consequence for a customer, an order or a payment;
- the only problem is multiplying copies: co-authoring in Microsoft 365 may be enough.
In these cases, an app would cost more than it brings back. I would rather tell you before the quote.
What the app adds
| Need | Shared Excel file | Business app |
|---|---|---|
| Controlled entry (required fields, lists, formats) | Partial, easy to bypass | Systematic |
| Role-based permissions (who sees and edits what) | Very limited | Built in |
| Change history | Limited | Full audit trail possible |
| Mobile, field and offline access | Awkward | Designed in from the start (PWA) |
| Connection to the ERP, CRM, invoicing | Copy-paste or macros | Direct connection |
| Business calculations | Fragile formulas | Tested rules |
The guide on turning an Excel file into an app covers the technical steps.
Where to start
- Pick the most critical file: the one where an error costs the most.
- Measure the time spent around it over two weeks, per person.
- A 30-minute call to check that the numbers justify a business app.
- Scoping (1 to 2 weeks): the file becomes a requirements document, with a fixed quote.
- Mockups, development in batches, data migration, then three months of support included.
Indicative budget: $6,800 to $22,400 (€6,000–€20,000)excl. VAT depending on the building blocks. The estimator gives you a range in one minute.
Frequently asked questions
Should we abandon Excel once the app is in place?
No. Excel remains the ideal tool for analysis, modeling and one-off reports. The app becomes the single source of truth for data entry and sharing; exports to Excel remain available for analysis.
Can we bring over the data from our Excel files?
Yes. Migration is planned during scoping: removing duplicates, standardizing formats, importing into the database. In my pricing, data migration is a building block of about $900 (€800)excl. VAT, more if the files are numerous or very inconsistent.
Isn’t SharePoint or Excel co-authoring enough?
They solve the problem of competing versions, not uncontrolled data entry, role-based permissions or fragile business calculations. If your only problem is having several copies of the file, co-authoring may be enough.
How long does it take to turn an Excel file into an app?
1 to 3 months for a focused business app, scoping included. A well-structured file speeds up scoping: its tabs and columns already show the data and the steps.