The saving estimate gets the strongest visual weight because it answers the owner's first question.
Self-initiated / Product strategy, UX, UI and build / 2026
meterroom
Energy bills finally explain themselves.
Meterroom turns a month-end cost into one clear operational decision for independent hospitality teams.
Meterroom / working prototype Sample data live
Venue type
Estimated avoidable monthly spend
£386£4,632 over a yearFirst action
Separate extraction and refrigeration from the overnight base load.
00:0006:0012:0018:0024:00
Illustrative product output using sample assumptions. It is not an energy audit or financial advice.
01 / ProblemA month-end bill shows the cost, not what to change next.
02 / ThinkingRecommendation first, evidence second, one action last.
03 / BusinessSpot avoidable spend before the next energy bill arrives.
04 / UsersCafé, bar and restaurant owners and shift managers.
05 / ConstraintsSample data, plain language and one short session.
06 / OutcomeA working responsive calculator that makes the recommendation, evidence and next action usable.
The product decision
Do not give a busy owner another dashboard to study.
The useful question is smaller: where is money leaking this month, and what can the team change before the next bill?
I designed the product around a recommendation first, then placed the evidence close enough to earn trust. The interface uses plain language, a visible estimate and a single next action.
Interface system
A control room with the panic removed.
Charts explain a recommendation. They never compete with it.
Every diagnosis ends with one operational change, written for a shift manager rather than an analyst.
What this proves
I can turn an unfamiliar business problem into a calm, usable product.
Positioning, naming, information architecture, interaction design, responsive UI and front-end implementation were all handled as one system.
Next proof piece: Again, Please →