What Implementation Teams Miss Without Spreadsheet Discovery

Ask any ERP or CRM implementation consultant where projects go wrong, and you will rarely hear “during build” or “during testing.” You will hear the same answer again and again: discovery. Discovery is the phase where the implementation team is supposed to learn what the client’s current systems and processes actually do. And when critical business logic lives in spreadsheets — pricing models, forecasts, approval calculations — that phase has a blind spot most teams never close. This article breaks down exactly what gets missed without structured spreadsheet discovery,

why it costs so much when it surfaces late, and how leading implementation teams are closing

the gap.

The Blind Spot in Every Discovery Phase The discovery workshops go well. Stakeholders describe their processes. Requirements get documented. The scope is signed off. Then, six weeks into the build, someone opens the client’s master workbook and finds:

• A nested pricing formula referencing three other sheets nobody mentioned
• A manual override rule that exists nowhere except in one cell’s IF statement
• A broken external link that has been silently returning stale data for two years
• Logic that contradicts what stakeholders described in the workshop — because the

spreadsheet, not the description, is what the business actually runs on None of this is the team’s fault. It is what happens when discovery relies on interviews and manual inspection of workbooks that took years to grow.

The 5 Things Teams Consistently Miss

• Hidden cross-sheet dependencies

A single formula cell can pull from a dozen other locations across multiple worksheets. Manual tracing catches the obvious ones. It rarely catches all of them — and the ones it misses are exactly the ones that break in UAT.

• Undocumented business rules

“Why does this formula add 4% here?” Nobody knows. The person who built it left in 2021. That rule might be a regulatory requirement, a legacy workaround, or an outright error — and you cannot migrate what you cannot explain.

• Key-person dependency

Often one person — maybe the Finance Director — is the only human who understands how the workbook holds together. Without discovery, this risk stays invisible until that person is on holiday, has resigned, or is simply too busy to answer questions during build.

• Data quality landmines

Hardcoded values inside formulas, inconsistent units across sheets, circular references, and broken external links. Each one is a small problem. Migrated blindly into a new ERP, they become systemic errors with a business-wide blast radius.

• The gap between described process and actual process

Stakeholders describe the process as they believe it works. The spreadsheet encodes how it actually works — including every exception, workaround, and quiet fix accumulated over the years. Migrating the described process instead of the actual one is how you get a new system the business refuses to trust.

Why Late Discovery Is So Expensive

Every missed item follows the same costly pattern:

• It surfaces in UAT — the most expensive possible moment
• The business blames the new system; the system team blames the requirements
• Scope changes trigger rework; rework triggers deadline slips
• Confidence in the project — and in the implementation partner — erodes

Budget overruns and timeline slips in ERP and CRM programmes are rarely caused by bad building. They are caused by building on a foundation nobody fully inspected.

What Structured Spreadsheet Discovery Looks Like

Structured discovery treats the workbook itself as the primary source of truth and analyses it systematically, before requirements are written:

• Upload the workbooks exactly as they are — no cleanup, no preparation
• Analyse the complete structure: every formula, dependency, and cross-sheet link
• Extract every embedded business rule into a plain-language register
• Review each rule with stakeholders, classified by risk and migration readiness
• Map validated rules to the target system’s fields, workflows, and entities
• Evidence — package everything for workshops, UAT planning, and governance sign-off

The output is an Evidence Pack: a validated blueprint that lets implementation teams quote accurately, build confidently, and walk into workshops already knowing where the risks are.

What This Means for Implementation Partners

For consultancies and implementation partners, structured spreadsheet discovery is not just risk reduction — it is a commercial advantage:

• Faster, more accurate scoping — quote from evidence, not estimates
• Shorter discovery phases — analysis measured in hours, not weeks of manual tracing
• Fewer UAT surprises — hidden logic surfaced before build, not during it
• Reusable intelligence — the same approach applies across every client with

spreadsheet-driven logic IC-Flow is a Spreadsheet Migration Intelligence Platform built for exactly this. It is validated on live migration projects, with paying SaaS customers and UK patent applications filed — and partnership discussions with ERP, CRM, Power Platform, Zoho, and Salesforce consultancies are welcome, with no minimums and no lock-in.

Close the Gap Before Your Next Project

The spreadsheets your clients depend on are not going to explain themselves. Every migration that starts without understanding them is carrying risk that will surface — the only question is when, and at what cost. See how IC-Flow’s discovery workflow works or watch the 2-minute demo — and if you are an implementation partner, get in touch about working together on your next migration.