A spreadsheet can be a good place for an initial product list, price calculation or sales analysis. Difficulties arise when several stages of work depend on a single file. The same table is expected to describe the product, check option compatibility, store customer agreements and supply order data. At that point, it is worth examining what actually needs to change: the data structure, the rules for collaboration or the tool itself.
The warning sign is how you work, not the file size
A large number of rows alone does not mean a system needs to be implemented. Dependencies between information and responsibility for keeping it current matter more. A small price list can cause problems if every salesperson uses a separate copy and changes are shared in messages. A complex analytical spreadsheet, meanwhile, may still serve its purpose well if it has a defined data source and owner.
Pay particular attention to moments when someone stops work to confirm a price, find a document version or ask about an exception. Record why they stopped and what information they needed to continue. This identifies a specific problem to solve instead of a general feeling that “Excel is no longer enough”.
A short audit of the quoting process
Choose a few completed cases and trace the path from enquiry to order handover. For each question, record the answer and an example of a document or action that supports it.
- Data source: where does the salesperson get the price, and how do they know it applies to this product and market?
- Responsibility: who approves a price list change, who publishes it and how does the team learn about the update?
- Rules: where are option dependencies recorded, and could someone else use them to prepare a valid variant?
- Re-entry: which fields are copied manually into quotes, messages and orders? Where must the same information later be corrected?
- History: can you reconstruct the exact scope of a sent quote, its price and the agreements it was based on?
- Handover: does the person taking over know what has been agreed and which decisions remain open?
There is no need to create a numerical company maturity score. Identify where missing data blocks work or causes discrepancies. Also separate errors in the data itself from problems in how it is passed on. A new form will not fix an outdated price list, and tidy folders will not replace a missing equipment selection rule.
Hypothetical example: one change across several documents
Imagine a company offering a device with an optional control module. The product owner updates the module's price in the master file. A salesperson, however, prepares a quote using an older copy saved on their computer. After talking to the customer, they add new equipment directly to the document, while the fulfilment team receives the original spreadsheet. Everyone works with information they believe is correct.
This example requires three decisions: where the current price list is maintained, how the sent quote version is preserved and which dataset goes to fulfilment. Only once these are documented is it worth choosing how to support the process. Better organisation around the existing tool may solve part of the problem. Another part may require a shared catalogue or an application supporting successive stages.
Moving in stages
Start with one product family and one quoting path. Standardise names, identifiers, units and field meanings. Assign a data owner and a change approval process. Separate the current catalogue from historical quotes so that a price update does not erase the record of what the customer previously received.
Next, describe the rules using real examples, including unusual ones. Test a pilot with the people who prepare quotes and receive orders. Compare the time spent searching for information, the number of manual transfers and the clarifications required before and after the change. These observations will help you decide whether to extend the scope.
Before switching over, set a date to stop editing old copies, decide where to archive them and define how to report missing information. Spreadsheets can remain useful for analysis. What matters is that everyone knows where the authoritative data for daily work is created and who is responsible for its quality.