This last point in my opinion is ONE major benefit you must seek to extract, if you choose to engage the services of a developer. S/he should be able to help you develop (in_house) expertise needed to maintain the application AFTER s/he is gone. If you fail to ensure this, all your cost_savings from using the application might end up being spent paying the developer to maintain the application over time in the future!
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).
For the purpose of creating custom financial and business management solutions that solve your identified problems, and give you control/ownership, without burning a hole in your pocket, Excel VB offers an amazing variety of possibilities, in the hands of an adequately skilled user.
I believe the foregoing are compelling justifications for choosing Excel Visual Basic over Visual Basic.
types of spreadsheet
excel spreadsheet examples
examples of spreadsheet packages