Custom spreadsheet solutions which survive long after the developer has "left the scene", are often those which users accept because they discover it _ among other benefits _ makes their work quicker and easier to do. That is why the best person to develop such solutions tend to be one who works in that area, and is therefore familiar with the way the manual system operates. S/he would have an "insider's" perspective of the best way to introduce automation other users will readily adopt _ even as it solves the identified problem(s).
VBA is therefore different from the Standalone Visual Basic program used(by professional programmers) for developing commercial quality software applications _ though it borrows many of the latter's features. Think of Excel VBA as being the standalone Visual Basic software, built into Excel for the benefit of Excel users who are not necessarily programmers, but who are keen to exert more control over the application. So, Excel VB offers any interested users the necessary tools to make the application deliver more functionality. The final product is still an Excel document, but with extra functionalities added using VBA.
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.
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.