The visiting head of the technical function only needed to look at the most recently plotted point on the chart (relative to preceding ones) for a Key Performance Indicator like. Cost per Hectolitres brewed(One Hectolitre = 100 Litres), to know if the brewery had stayed within the approved upper limit of spend(plotted as a straight line target across the same period) or not. Discussions would then take place based on identified "Exceptions"(which could be "good" e.g. savings made or "bad" e.g. monetary loss due to materials over_used), and "Actions To Be Taken" to correct or maintain observed performances agreed upon.
It's not enough to have a professional with the technical skills to solve your problem. s/he also needs to have the right attitude and background/experience _ else the relationship will not work. This is where an Excel VB resource is more likely to add value to you. Most Excel VB Developers have backgrounds in management, accounting, engineering and other fields, which further equips them to be useful to you in "thinking up" better ways to apply your spreadsheet automation to get the most value for your business. You therefore need to choose the right developer, with the appropriate background to match your needs.
Why Excel Visual Basic _ and NOT Visual Basic? I always answer this question by asking the following question: What would be the point of "Killing A Fly With A Hammer"? Let me elaborate. If a method is available that allows us to achieve the same desired result(s) at LOWER cost, with LESS effort and in LESS time, why should we fail to adopt it? Certain IT persons insist that developing executable applications using the standalone Visual Basic programming language is "better" as it does not limit the user to a particular user application software environment. I concede that this might be a valid point under certain conditions. However, I point out that there are many users who have peculiar needs that do not necessarily require complex solutions. A lot of people today simply want to get their data recording, (re)organisation, and analysis for decision making done quicker and with less effort. They also want to spend as little money as possible to do this. In other words, they want a cost_effective solution that gives them independence from the solution provider in the long term _ without requiring them to undertake laborious skills acquisition immediately. This category of everyday users of technology described above are the ones I believe need Excel VB solutions of the type I describe. One expects that some of these users will over time develop an interest in acquiring advanced skills needed to develop their own solutions in future _ which is why I also encourage them to do so, possibly via self_tutoring, like I did.
In effect what I am saying is that companies which get the most value from spreadsheet automation(including using it to avoid expenditure on less adaptable commercial off the shelf applications) will be those which empower their users to routinely generate "in house" solutions. In such companies, you will find that only when the requirement becomes considerably specialised or complex, does the IT department get called upon to develop or purchase software solutions for user departments or functions with significant data recording and analysis needs.