Where Excel fits on a long engagement.

Dismissing Excel misreads the situation. Spreadsheets encode real business logic, built by people who understood the process, and they persist because they are flexible in ways governed systems are not. A migration that ignores why the spreadsheet won will be worked around.

The risks are equally real: no version control, no test, no audit trail, and formula errors that propagate silently. Key-person dependency is the sharpest edge — a model that only one person fully understands is a business continuity risk regardless of how well it works today.

What an assigned team does with Excel.

Reading spreadsheets as data sources is its own engineering problem. Merged cells, inconsistent headers, formatting that carries meaning and manual edits between loads all break naive ingestion.

Handling that robustly, with validation that rejects rather than silently mangles bad input, is part of what assigned data capacity is responsible for under managed data services.

What we use Excel for.

  • Spreadsheet logic captured before replacement Understanding what the model does, because it is the only specification.
  • Robust ingestion from real files Validation that rejects malformed input rather than importing it wrongly.
  • Output people will actually use Exports that stakeholders can work with, rather than forcing a tool they will not adopt.

How Excel capacity is assigned.

Spreadsheet-dependent processes are assigned inside data capacity, with the reason a spreadsheet is still used understood before anything replaces it.

Tell us what your roadmap needs Excel for.

A service delivery manager replies with the disciplines we would assign, the monthly capacity and what the first month looks like.

Loading the contact form… You can also email hello@azendo.co.

We reply within one working day. No obligation, and no newsletter.