The real bottleneck here was never the formulas. It was the sheer, repetitive motion of opening more than 100 files every time material costs shifted. The person in this story is doing the right thing by looking for a smarter path, and the fact that they are already using basic Excel logic means they are closer than they think. This is not about learning to code or convincing leadership to migrate to NetSuite. It is about recognizing that a spreadsheet you update manually is no longer a tool. It is a tax.
What stands out is the honesty of the workflow. Multiply the case price by 1.1, divide by case weight, apply it across every customer sheet. That is a rule, not a task. And once you can articulate the rule, you can automate it. Macros are the obvious first step, but they are not the only step. Modern AI-powered spreadsheet tools can handle this kind of pattern recognition without requiring a single line of VBA. You can point the tool at a folder of files, tell it the logic in plain English, and let it process the updates while your team focuses on customer questions or order exceptions. The photo they shared shows exactly the kind of repetitive structure that these systems excel at parsing.
The resistance to changing CRM platforms is understandable. Sage 50 works, and nobody wants to rewire their entire order entry process during a period of monthly price swings. But that resistance should not extend to the spreadsheet layer. You do not need to replace your system of record to automate the busywork around it. A price sheet is just a report. Reports can be regenerated. The challenge is that this person is treating each file as a unique artifact when it is really just a template with different numbers inside. Once you see it that way, the solution becomes obvious: keep the templates, automate the updates, and let the files generate themselves.
The practical takeaway is this: start with one script that loops through all your files, applies the same percentage change, and writes the new prices back. Test it on a single customer sheet. Then run it across the whole folder. If macros feel intimidating, use an AI assistant that can write the code for you, then copy and paste it in. The goal is not to become a programmer. The goal is to stop being a human button pusher. Your team should not be working late because material costs moved. They should be reviewing the results, not calculating them. And if you can get this working for one type of change, you can scale it to handle future adjustments, price holds, or even customer-specific discounts. The only real barrier is deciding that a hundred repetitive edits is no longer an acceptable way to spend an evening.