A spreadsheet should become an application when it is acting like a multi-user system but cannot provide dependable permissions, workflow state or data integrity.
Look for system behaviour
Multiple people, shared records, approval states, attached documents and recurring reports are signs that the file is already pretending to be software.
Identify the dangerous failure
The strongest business case is not that the sheet looks messy. It is that an overwritten formula, stale copy or unclear owner can create delay, financial error or customer harm.
Preserve useful flexibility
Do not automate every column. Understand why users added manual notes and side calculations; those adaptations often reveal requirements the formal process missed.
Migrate in stages
Define the source records, clean only what the new workflow needs, preserve a controlled archive and validate totals or counts before switching active work.
A practical checklist
- Name the business outcome in plain language.
- Map the current people, systems and exceptions.
- Separate necessary scope from attractive extras.
- Make ownership, security and operating cost visible.
- Choose the smallest next step that reduces a material unknown.
What to bring to a first discussion
Bring one real example of the current workflow, the people involved, the constraint you feel most often and what a useful outcome would change. You do not need a finished specification.