I'm going to hazard a guess based on my experience of being the one who brought it to my current employer after learning it at a previous employer: it's really hard to understand for awhile, especially coming from Excel. The paradigm required to build anything more than SUM or AVERAGE can be very unintuitive and feels almost like black magic.
It takes a lot of trial and error and patience to finally grasp how Power BI handles calculations if you are used to the freedom of Excel.
That being said, once it clicks, it feels like you are a magician, and you can do really advanced analytics on giant tables, which is great.
We pull a bunch of data out of the guts of MS Project 2010 and do a lot of custom analysis on it. It took about two years to go from scratch to a set of reports that served everyone's needs that also required minimal maintenance.
Then we got purchased by a larger company, so now the work is in rolling out a similar set of reports for the sister companies, as well as rolling them up into corporate-wide reports. It's a lot of fun.
To put things in context, our small claim to fame is anyway getting some aggregate data about lost calls and attempts that is not possible to produce in Power BI directly[1]. So it's likely that they would buy or not buy it even if it was based on Power BI itself.
It takes a lot of trial and error and patience to finally grasp how Power BI handles calculations if you are used to the freedom of Excel.
That being said, once it clicks, it feels like you are a magician, and you can do really advanced analytics on giant tables, which is great.
We pull a bunch of data out of the guts of MS Project 2010 and do a lot of custom analysis on it. It took about two years to go from scratch to a set of reports that served everyone's needs that also required minimal maintenance.
Then we got purchased by a larger company, so now the work is in rolling out a similar set of reports for the sister companies, as well as rolling them up into corporate-wide reports. It's a lot of fun.