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.
The visiting head of the technical function only needed to look at the most recently plotted point on the chart (relative to preceding ones) for a Key Performance Indicator like. Cost per Hectolitres brewed(One Hectolitre = 100 Litres), to know if the brewery had stayed within the approved upper limit of spend(plotted as a straight line target across the same period) or not. Discussions would then take place based on identified "Exceptions"(which could be "good" e.g. savings made or "bad" e.g. monetary loss due to materials over_used), and "Actions To Be Taken" to correct or maintain observed performances agreed upon.
"Over_used/Over_spent"(Losses) and "Under_used/Under_spent"(Savings) _ on a monthly basis based on data entered, the program also automatically plotted charts showing trends over a 12 month period.
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.