ClimateTech product design for energy software that separates readings, forecasts and targets

From live readings to yearly totals, our ClimateTech product design makes each figure clear enough to decide on and solid enough to report.

  • 2017

    Founded

  • 90+

    Projects

  • 19

    Countries with clients

What we design in ClimateTech and energy software

For teams building energy management and sustainability software, from an early idea to a suite run across many sites.

Where energy software gets hard

Energy products serve people who act within minutes and people who report once a year, from the same meters.

Readings, forecasts and targets that look alike

A meter reading, a forecast and a target can share one chart, one colour and one unit. When they look alike, people act on the wrong one. We mark measured figures apart from modelled ones, and show each scenario against a stated baseline with the changed assumptions in view.

Three roles reading one building

WhoWhat they want from the product
Facilities operator
The exception that needs action now
Finance leader
Cost and forecast
Sustainability lead
Progress against an environmental target

Building energy software UX has to serve all three. One dashboard for everyone shows too much to each of them, and a fixed dashboard per role breaks whenever a situation crosses roles.

A peak-price event is one: the operator needs the affected assets and the action tonight, and the finance leader needs the saving and its assumptions next week.

Emissions totals an assurer will question

In the EU, the largest companies report under the Corporate Sustainability Reporting Directive, whose scope was narrowed in 2026. Most emissions reporting follows the GHG Protocol, a voluntary standard with scope 1, 2 and 3 categories. Where figures are assured, the assurer asks where each one came from.

We design carbon accounting screens where every total opens onto its sources, its estimates and who approved it. Your sustainability and legal teams decide which rules apply.

Automation that acts overnight, inside limits a person set

Batteries are dispatched by software, and loads shift overnight within limits someone agreed. The design question is how people set those limits, and how they see in the morning what the system did and what it saved.

Illustration, not client work

A product plans overnight charging for a delivery company's vans. The fleet manager needs every van ready by six; finance wants the charging done when power is cheapest. On the night those clash, the product has to choose, and the fleet manager has to know it chose.

So we would design that night first: each van's charge against the price forecast, with the vans where price and readiness pull apart flagged. The fleet manager can pick before the system does. Drivers see one thing: whether their van will be ready.

What you get when Tcules designs your energy software

We design for the people who act on the numbers: operators, finance teams and sustainability leads.

Who does the work

Your energy product gets a senior product designer who leads the design and does it, while an account lead keeps the project moving. Design engineers build the coded demos, and developers join when we build the product.

What we need from you

Each role's real questions, from the operator, the finance lead and the sustainability lead. The data you have today, measured or modelled, or a realistic sample of it. Time with your data and engineering leads, and a named person who signs off product choices.

Where our part stops

Data pipelines, forecasting models and device integrations stay with your data and engineering teams. Which reporting rules apply is for your sustainability and legal teams to decide.

One misread dashboard may need only dashboard design. A direction to prove on sample data suits Coded Prototyping, and a suite users know by heart, Product Modernisation.

What clients say

  • “Tcules turned our early ideas into eight scenarios, built around the questions our operators, finance leaders and sustainability leads actually ask. Their coded demo let us see each question with its data and the digital twin in one view, before any live integration.”

    Pratik GhoshalCEO, ConnectX
  • “Our customers wanted reports that answered their own questions. Tcules researched how they used our reporting, redesigned it and gave us shared rules for filters, states and data, so new work can follow the same logic.”

    Russell MilerCOO, Ryzeo
  • “It was simply the most successful long-distance 3rd party collaboration I have seen. The company is on eye-level or above for the services they offer. Their staff were really good.”

    Roland SailerDirector of Product, Ringier Media Switzerland

Three ways to work with us

Not sure which suits you?

Tell us about the product, and we'll suggest one.

Tell us what you’re working on

Why founders and product teams choose Tcules

  • Fluent in SaaS

    Roles, permissions and data-heavy screens need no explaining to us.

  • Idea to launch

    Bring an idea or your own prototype. Designers lead it through to launch.

  • Craft people notice

    Your product stands out from lookalike software and feels effortless to use.

  • Evidence before screens

    We test your assumptions with real users before they become expensive mistakes.

  • Seen your problem before

    Senior designers who've solved problems like yours lead your product and do the work.

  • Start small

    An optional fixed-price pilot lets you try us first, and ongoing work has no minimum term.

Tell us which numbers your users rely on

Share the product, who uses it and the data you have today, measured or modelled.

Questions about ClimateTech product design

Can design start before our live data integrations are ready?

Yes. For ConnectX, Tcules made a coded demo on sample data, so the team could judge the whole product direction before connecting live systems. The same approach suits any product whose data feeds are still being built.

What does good forecast and scenario UX look like in energy software?

Each forecast and scenario sits against a stated baseline, with the changed assumptions visible. Measured figures are marked apart from modelled ones, so a reader can see what changed, what it rests on and whether anyone measured it.

Do you design carbon accounting software?

Yes. We design emissions inventories by scope, the trail behind each figure and the reports that go to auditors and boards. Your sustainability and finance specialists decide the method; we make it readable and traceable on screen.

How do you make energy data visualisation clear for non-engineers?

Each role sees the same figures at its own depth. A finance leader gets cost and forecast first, with the engineering detail one step away, and every chart says whether it shows a reading, a forecast or a target.

ClimateTech Product Design for Energy Software | Tcules