A person with proven competence in this area CAN become "notorious" for developing spreadsheet applications, which eliminate drudgery from the process of using MS Excel to handle large amounts of data. Typically, work that takes hours or days will suddenly take minutes or seconds to finish.
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.
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!
Deciding What Spreadsheet Application To Use. This would ultimately be up to you. The big "fight" has always been between Lotus 1θι and Microsoft Excel. I started out with Lotus 1θι back in 1993 and learnt Lotus Macros programming(via self_tutoring). I eventually used this skill to develop _ in my free time _ various custom spreadsheet solutions(that were formally adopted for use in the departments I worked in as a brewer/manager in Guinness), before switching to Microsoft Excel in 2001. Subsequently, I developed my Excel Visual Basic spreadsheet programming skills (also via self_tutoring), because the company had chosen to adopt MS Office during the roll over to year 2000.