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!
One Possible Application: Plotting a pie chart based on income contributions from all your products and services(daily, weekly or monthly), and reviewing the automatically computed percentages/visual pie slices, can give very illuminating insight.
The savings _ from using your "in house" expertise _ in terms of money and man_hours alone, will quickly justify the investment you make in "developing the needed skills" _ especially, when you compare what you spend with the cost of purchasing a commercial software application _ or even engaging the services of an Excel VB developer.
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).
excel budget templates
examples of spreadsheet packages
what is a spreadsheet used for