Replacing Excel with an application: MVP scope and cost

A spreadsheet does not need replacing just because it is complex. Reasons for change are specific problems: conflicting data versions, inadequate access control, manual task handovers or errors that cannot reasonably be reduced.

Identify the problem through an example

Follow one record from entry to process completion. Note who edits it, which fields are copied into other tools and where mistakes occur. If a clearer table and working rules suffice, that may be the right first step.

What should the MVP contain?

The first version should handle one complete process. For jobs, this could be creation, assignment, status changes and acceptance. An advanced dashboard is less important than correct data and permissions. Record a success criterion, such as completing the process without parallel copying.

Data before migration

• Establish which spreadsheet copy is current.
• Identify duplicates and missing identifiers.
• Separate values from formulas and comments.
• Identify archived data and required history.
• Trial migration using a representative sample.

User acceptance

Tests should cover ordinary work and exceptions: simultaneous changes, incorrect imports, revoked access and returning to an earlier stage. Compare the application result with an approved source example. Define when work in the old spreadsheet ends.

How should the application be priced?

First define roles, data objects, rules and integrations. Screen count is only part of the scope. Separate analysis, the initial version, migration, hosting and maintenance. One price cannot reliably cover every “system instead of Excel”.

Must every spreadsheet be moved immediately?

No. Start with one process and define boundaries and exchange with other tools. Staging still needs a clear source of truth for each piece of information.

Describe the process and send an anonymized data structure example. Real customer data is unnecessary for an initial conversation.