Excel is not the problem — giving it the wrong job is
A spreadsheet is excellent for analysis, temporary models and simple price lists. The problem starts when one workbook becomes the only source of truth for hundreds of products, dozens of surcharges and rules understood by only a few people. At that point it is no longer just a document; it is a business application without business-application controls.
The symptoms are familiar: files named “price_list_final_v7”, hidden columns, protected cells with forgotten passwords and formulas nobody wants to touch. The company still works, but reliability depends on individual discipline.
Versions multiply faster than products
A price list is emailed to sales. One colleague updates purchase prices, another keeps the old copy, a third adds a personal discount column. A month later the company officially has one price list and operationally has five. The discrepancy is discovered only after a quotation reaches a customer.
A central configurator does not magically improve bad data, but it does solve distribution of the active version. One price or rule change becomes available from one controlled place with a clear date and owner.
A formula does not know whether a combination is technically valid
Excel can calculate almost anything, but a formula is not automatically a domain model. Is this hardware allowed for that sash weight? Does a dark colour require different reinforcement? Is this opening type compatible with a two-track sliding profile? Over time those questions become complex IF statements or stay in the salesperson’s memory.
A configurator can separate pricing from compatibility rules. The user is not offered an impossible combination instead of being expected to remember a note on the third worksheet.
The largest risk is dependency on one person
If only one person understands the calculation, that person’s absence becomes an operational risk. New employees then learn by copying old quotations and verbal rules, which means errors can be reproduced together with the knowledge.
Digitalisation becomes valuable when it turns implicit knowledge into visible structure: products, options, formulas, price items, constraints and test cases. The system becomes documentation that can actually execute.
When a spreadsheet is still perfectly adequate
If a company sells a small set of standard products, prices rarely change, conditional surcharges are limited and one trained person prepares quotations, a good spreadsheet may still be the most efficient solution. There is no reason to automate simplicity merely because automation is possible.
The trigger for change is not the number of spreadsheet rows but the number of decisions users must remember. When quotations depend on many connected choices, several people work in parallel or mistakes become expensive, a configurator stops being a luxury and becomes process control.
