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!
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 _
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).
So, (when considering the automation I speak about) do not think about spreadsheet documents containing one or two click_able buttons that allow a user print a page or copy some cells from one sheet to another. Instead, I want you to picture an application(or Entreprise Information System) that customises the appearance of your spreadsheet workspace(to take advantage of maximum screen capital available on your PC), and offers you custom "floating" data entry forms.
blank spreadsheet templates
examples of spreadsheet packages
uses of spreadsheet