English Edition · Chapter 14

Chapter 13: Hard-core version of typical project case collection, using cases to build judgment and calculation capabilities

Case chapters can’t just tell stories. A truly valuable case must at least include: customer profile, billing structure, key assumptions, system boundaries, calculation logic, decision points, risk points and review conclusions. The following cases are all developed according to this structure.
14Current Chapter
5Sections in This Chapter
EnabledQuick Navigation
Chapter Introduction
Case chapters can’t just tell stories. A truly valuable case must at least include: customer profile, billing structure, key assumptions, system boundaries, calculation logic, decision points, risk points and review conclusions. The following cases are all developed according to this structure.

13.2 Case 2: Clinic/dental store, why is it a small commercial entry-level model?

#02

13.2 Case 2: Clinic/dental store, why is it a small commercial entry-level model?

Customer portrait: The business hours are stable, the load is concentrated during the day, the boss makes decisions himself, and the requirements for cleanliness of the venue are high. The bill shows obvious energy consumption during the day, so it is suitable for a self-contained roof system.

Key judgment: This type of project is more suitable for early-stage teams to accumulate small commercial capabilities than complex factories, because it combines stable load, better repayment, and case display value.

Calculation logic: First identify its Schedule category, and then estimate power savings based on business hours and TOU structure; if there is a demand fee, handle it conservatively and do not overstate the demand improvement.

[Conclusion of review]Customers such as clinics/dentists are most suitable for establishing basic capabilities such as bill analysis, construction low-interference organization, concise proposals, and monthly report output.

13.3 Case 3: Tourist villa/B&B, why the income must be ranged

#03

13.3 Case 3: Tourist villa/B&B, why the income must be ranged

Customer profile: Living part of the time, renting part of the time for short periods, obvious off-peak and peak seasons, large load fluctuations during the day. Customers often have high electricity bills and are willing to pay for good-looking and low-disruption construction.

Key Judgment: This type of project cannot promise a payback period based on a fixed monthly load because occupancy rates, rental patterns and air conditioning usage intensity will all fluctuate.

Calculation logic: Make at least three income ranges: off-season, mid-season, and peak season, so that customers know the upper and lower limits of the system value.

[Case Three Red Line]For homestay/short-term rental projects, do not promise a single point of payback period, but a range.

13.4 Case 4: Light factory/warehousing, why a big roof may not be a good deal

#04

13.4 Case 4: Light factory/warehousing, why a big roof may not be a good deal

Customer portrait: The roof area is large and the bill seems high, but the property rights, lease term, structural life, demand structure and boss's decision-making style are all more complex.

Key judgment: Teams are most likely to be attracted by "large area" and "large total price", but ignore that such projects have higher requirements on structure, demand, electricity price, repayment and contract capabilities.

Calculation logic: In addition to power saving, demand, voltage level, minimum charges, construction impact and payment ability must be taken into consideration.

[Conclusion of review]Area is not value, matching is value. If organizational skills are not prepared, a large roof project can easily swallow up the profits earned from many previous smaller projects.

13.5 Case 5: EaaS pilot, why choose the best customer first?

#05

13.5 Case 5: EaaS pilot, why choose the best customer first?

Customer portrait: stable address, stable billing, clear load, willing to cooperate with information and monitoring, and good payment behavior. The goal is not to pursue short-term contract signings, but to verify the long-term service model.

Key judgment: The value of pilot projects lies in ‘learning to do’, not ‘doing more’. If the most complex customers are selected from the beginning, the team will mix model issues with customer issues and fail to learn real experience.

Calculation logic: In addition to project savings, it also depends on monthly service fees, customer willingness to continue paying, outage response, contract termination and residual value treatment.

[Case Study Five Sentences]The success criterion of an EaaS pilot is not the number of orders signed, but whether the organization knows how to make the next order more stable.