Excel is not the enemy. A spreadsheet is useful for analysis or a temporary overview. Problems start when the same file has to serve as a schedule, customer database, approval process and invoice source at once. The question is not whether your company is big enough for custom software. It is whether the current way of working remains dependable.
Look for friction in everyday handovers
Watch what happens between people. Someone copies an order from an inbox, a colleague creates another version and a third person asks which column is correct. These are concrete signs of process friction. A slow workbook alone does not justify a rebuild: clearer agreements, a simpler model or an integration may be enough.
Separate calculation from collaboration. A specialist may continue using a complex pricing workbook. File status, access permissions and handovers to another department may belong in a shared application. You do not need to replace every spreadsheet.
Follow one workflow from start to finish
Take a recent enquiry and follow it through to invoicing. Record where information is re-entered, who checks it and what happens when something is missing. Include an exception: a cancelled job, partial delivery or changed address. These examples reveal what future software actually needs to support.
Illustrative scenario: an installation business schedules work in a spreadsheet. Its biggest difficulties are missing photographs and unclear job-sheet status. A small field app connected to the schedule could be the right first step, rather than an entirely new ERP.
Define a focused first version
- Choose one process owner who can make decisions.
- Agree which system is the authoritative source for each field.
- Define who may read, change and approve information.
- Describe three ordinary situations and three exceptions.
- Pick one measure, such as correction work per completed job.
A list of screens is not a project scope. Describe what a team member must be able to complete independently after launch. Test that with safely prepared representative data before adding more features. Keep the first release small enough that users can review the entire workflow.
Move the data with a recovery plan
Clean up duplicate customers and ambiguous statuses before importing. Keep an export of the starting point, run a trial import and compare record counts alongside a sample of files. Agree when the old workbook becomes read-only and who investigates discrepancies. Letting everyone edit both systems indefinitely makes mistakes hard to trace.
Start with a short process review involving the people doing the work. Explore custom software, or compare custom and off-the-shelf software. A targeted improvement may be enough; complete replacement is not a goal in itself.
Practical guidance by Codewera. Examples are illustrative; the right solution and investment depend on your situation.