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.
At times, they would prefer to click a button that says "Print ABC", or "Print XYZ" report, instead of having to crawl all over the huge spreadsheet(and get "lost" every now and then), to highlight and print different report pages. Using a custom built data entry form to make data entries into 14 different cells in different parts of a table(at the same time/with one click) would, for them, be "heaven" compared to making the entries one at a time.
For instance if a company had five drink brands in the market but notices that Brand A, which has a profit margin of at least twice the others is in greatest demand, they could (a) focus production efforts on that brand, so that more bottles go out to trade (b) Apply Best Practice/Continuous Improvement initiatives that would result in lower costs of producing each bottle of Brand A so that even though the market price remains fixed, the company is able to earn increasing profit margins per bottle.
To elaborate further: A one_page Variable Costs Analysis report sheet automatically generated by the custom spreadsheet application I earlier described, was a powerful tool used by top management to quickly assess performances of individual breweries. Among other benefits, the report made it quite easy to realistically compare sister breweries in different locations(even across countries) based on common denominators. Apart from summarising brewing/packaging materials in two groups _