It's a challenge for every company with a software "solution" for sale: it's a solution, but for what? Are customers looking for an all-encompassing solution to a big problem, or a targeted solution for a small problem? Do they want an interconnected suite of software modules, with a common data model, common look-and-feel, and discounted price tag, or a small-bore program that will automate a currently manual process?
For the suppliers of enterprise carbon and energy management (ECEM) software, this age-old problem is especially challenging since the range of potential functionality is so broad, and the array of potential stakeholders, influencers, and buyers is so wide.
Consider the "word cloud" depicted in Figure 1 below, which shows a subset of the labels for such software.
And in parallel, the motivations of potential buyers of ECEM shown in Figure 2 below:
Since most companies do not face cut-and-dry regulatory requirements for emissions reporting, matching up the motivations of the buyers with the functional scope of the product sellers is a time-consuming exercise of workshops, pre-sales consulting, assessments, and, inevitably, drilling a lot of dry holes.