In addition, an Excel VB developer( who in many cases will tend to be a user turned developer, and is therefore likely to easily see things from your perspective) _ unlike a programmer _ is more likely to be positively disposed to working with you to ensure the application meets your practical needs. S/he will readily understand that the final application is meant to help solve a real problem(s), and will therefore build it to match those expectations.
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).
Variable Costs Control/Reduction was a strategy that worked extremely well for the company. Most memorable for me as a brewer, was the manner in which huge monetary savings/profit gains were made by successfully implementing variable cost reduction initiatives. For instance, a brewing ingredient switch was made to a more readily available local alternative which was many times cheaper, resulting in phenomenal savings and progressively increasing profit earnings even though the price of beer produced was not raised. This practice was routinely applied across the brewing and packaging processes in line with a well thought out plan.
I believe using either of these two applications should not pose any problems for implementing your spreadsheet automation ideas. This is because both have always been "friendly", towards making it easy for users to get more functionality out of them by way of custom programming.
what is a spreadsheet used for
spreadsheet templates for tracking
what is spreadsheet in excel