This article is meant for those individuals/businesses who sometimes experience a need to use their spreadsheets in the (somewhat "impersonal"?) manner described above, to get the results they want. That need would often arise out of their lack of requisite skills to get the spreadsheet to behave the way they want _ or limited time to devote towards incorporating necessary automation to make it do so.
The 80ᚼ Pareto principle is based on Pareto's theory that 80% of the results one gets in a particular endeavour will be mainly due to 20% of areas to which one has applied efforts. In business this principle has been found to be true. Your data, properly converted into appropriate performance indicators, will show you where your largest margins come from. You can then channel more time and effort in that direction.
Another question I ask, in answering the "Why Excel VB?" question is : "Why re_invent the wheel? ". My experiences(and those of others who favour the use of Excel VB like I do), confirm that to organise, and analyse data for (financial/management) report generation and decision making, you will save hundreds of hours using already in_built, pre_programmed Excel functions compared to a situation where you used Visual Basic proper. All the functions needed to achieve the above purposes already exist in Excel, so that you don't have to write them all from scratch as would be the case if you were to use Visual Basic. 3.It works even when you lack "In House" expertise.
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.