All Work
Case Study · AI Retrofit Planning

AI-Powered Retrofit Planning

Role
Lead UX/UI Designer
Type
PropTech · Enterprise
Timeline
May 2026
Team
1 Designer · 2 FE Developer · 1 BE Developer
Tools
Figma · FigJam
Overview

AI-Powered Bulk Retrofit Planning is a new end-to-end workflow in the BuildingMinds platform that lets portfolio managers plan, generate, and commit retrofit strategies across many buildings in a single pass, with BuildingMinds' AI Retrofit Recommender working at portfolio scale for the first time.

Retrofit planning is one of the hardest decisions in real estate sustainability, and the tools don't help.

For a single building, the planner has to weigh dozens of variables at once: climate, age, energy baseline, country-specific costs, available measures, carbon targets, budget ceilings. Most platforms hand them a blank form and expect expert-level answers. The result is either over-simplified plans that miss obvious wins, or planners spending hours per building modelling scenarios in spreadsheets.

For a portfolio of hundreds of buildings, the problem multiplies. Every building is different, no two should get the same plan, but there's no realistic way to plan each one by hand. So teams fall back to applying uniform targets across the whole portfolio — which is dishonest (a 1970s Hamburg office and a 2005 Madrid warehouse don't have the same retrofit) and produces plans the business can't actually execute.

In both cases, the underlying problem is the same: the tools force a choice between manual effort and fake uniformity, with no middle path.

Two connected features that share one trust model.

Single Retrofit Planner turns the blank form into a conversation with an AI recommender. The user frames the goal (optimisation mode, locked constraints), the AI proposes a building-specific plan, and every AI-generated value is visibly labelled so the planner always knows which numbers came from the AI, which from formulas, and which from themselves. Authority stays with the human; effort shifts to the AI.

Bulk Retrofit Planner scales that same model to portfolios. A four-step wizard lets the user set guardrails, not answers — lock must-include measures, pick one optimisation goal, cap budgets — and the AI generates a tailored plan per building, respecting every constraint. Buildings that can't be planned are surfaced honestly in a conflict panel rather than hidden behind fabricated numbers.

Together they solve the same problem at two scales: scale the user's intent, protect the user's judgment, and tell the truth about the system's limits, whether the planner is working on one building or a thousand.

01
Transition point
67% of users who start in manual mode switch to AI-suggested view at least once per session, validating the dual-mode architecture.
02
Building-level conversion
AI mode reduces time per building from 35 minutes to under 8. The remaining time is human review, not data entry.
03
Confidence flags
The AI surfaces its certainty level for every recommendation. Low-confidence suggestions are visually flagged so users know exactly where to scrutinise.
04
AI has been invisible
Users described the AI-suggested plan as "feeling like their own work." That was the goal: AI as accelerant, not replacement for expertise.
05
Audit-ready output
Every plan exports to PDF with all supporting calculations, data sources, and confidence indicators included for investment committee submission.
At a glance

Design decisions that matter

One toggle, one button, three goals
A single "Use AI Suggestions" toggle reveals AI inside the existing form, no new screen, no context switch. Three optimisation modes — High energy savings, Low investment costs, High cost efficiency — let the user set intent before the AI runs.
Visible provenance
AI-suggested fields get a coloured border that disappears the moment the user edits them. No ambiguity, no silent overrides.
Locks turn AI into a conversation
Lock buttons next to Measures, Electricity, Heating, and CapEx let users say "keep this, change that, don't touch this." The AI negotiates around the constraints.
Impact made visible
The moment a measure is accepted, the building's stranding year, energy intensity, and carbon intensity shift. The user sees what the AI's suggestion actually does.
AI that knows its limits
Eligibility is checked before the AI is invoked — disabled button with a specific fix-it tooltip, not errors after the click. Photovoltaic measures stay deterministic; the AI is deliberately silent where its data isn't strong enough.
Accountability that persists
Every saved retrofit is tagged Manual or AI in the list. Provenance follows the decision past the form and into long-term reporting.
AI reasoning tooltip showing energy savings range and explanation
The AI shows its reasoning

Hovering reveals the why

Hovering over any suggestion opens a tooltip with the AI's reasoning — an energy savings range, a cost range, and a plain-language description like "Replace existing windows with more efficient ones."

In testing, this tooltip was the single element that turned skeptical users into confident ones. Seeing a range (€290K–€430K) felt more honest than a single confident €500K.

Step 1 · Add Buildings

Start with your portfolio

Select the buildings to include in the retrofit plan. The building selector pulls from the live portfolio database, showing asset type, current energy intensity, CRREM exceedance year, and data coverage score alongside each property.

Buildings with incomplete data are visually flagged so users can decide upfront whether to proceed with estimates or pause to collect better inputs before planning.

app.proxima.com/planning/retrofit/add-buildings
Step 1: Add buildings to retrofit plan, displayed on a desktop computer monitor
Step 2 · General Information

Parameters that shape the plan

For each building, configure the planning parameters: target year for compliance, available CapEx budget, tenant constraints, and regulatory framework. These inputs define the boundaries the AI works within.

Smart defaults reduce friction for standard scenarios while leaving every parameter editable. Users who know their constraints can lock them; users who are exploring can leave them open and compare outputs.

app.proxima.com/planning/retrofit/general-info
Step 2: General information and planning parameters, displayed on a desktop computer monitor
Step 3 · Add Retrofit

Manual control or AI suggested

This is where the two modes diverge. In manual mode, users browse the retrofit measure library and configure each intervention individually, specifying scope, cost, and expected performance impact. Full control, full responsibility.

In AI-suggested mode, the platform pre-populates the optimal measure set for each building based on energy modelling, cost-effectiveness analysis, and regulatory requirements. Users review, adjust, or replace any measure before proceeding.

app.proxima.com/planning/retrofit/add-measures
Step 3: Add retrofit measures with manual and AI modes, displayed on a desktop computer monitor
Manual planning mode

Configure every measure yourself

Manual mode is for users who know their buildings well and want precise control over the retrofit specification. They can browse the full measure library, adjust installation timelines, override cost benchmarks with their own contractor quotes, and see the impact of each choice on the carbon trajectory in real time.

The planning canvas is intentionally dense: every variable is visible and editable, which suits experienced sustainability engineers who find AI pre-fills too opinionated for complex assets with unusual configurations.

AI suggested mode

Let the AI do the heavy lifting

AI-suggested mode pre-fills the optimal measure set based on the building's energy model, applicable regulatory targets, and the CapEx budget defined in step 2. The result is a complete draft plan ready for review, not a blank form waiting to be filled.

Each suggestion carries a confidence indicator. High-confidence measures appear clean; lower-confidence ones are flagged with the reason, giving users the information they need to decide whether to accept, adjust, or replace the recommendation.

app.proxima.com/planning/retrofit/manual
Manual planning mode showing measure configuration, displayed on a desktop computer monitor
app.proxima.com/planning/retrofit/ai-mode
AI suggested mode showing pre-filled retrofit recommendations, displayed on a desktop computer monitor
Final step · Review and save

The moment of truth

Step 4 is the moment of truth. Everything the user set up in Steps 1–3 collapses into one scrollable summary — a header of aggregate KPIs, a list of buildings with their individual retrofit plans, and (if needed) a conflict panel surfacing buildings that couldn't be planned.

The screen's job is to make the consequences of the user's chosen path visible at a glance. A reviewer should be able to tell, just by looking at the rhythm of the building cards, whether the plan was made manually or by AI, and whether any building fell through the cracks.

The same layout shell holds both outcomes, but the visual rhythm of the results is radically different depending on which path the user took.

app.proxima.com/planning/retrofit/review
Final review and save step showing complete retrofit plan, displayed on a desktop computer monitor
Manual planning result

One decision, broadcast everywhere

Every building card looks almost copy-pasted. The user made one decision in Step 3, and Step 4 shows that decision stamped 47 times.

What the user sees:

Key trait: repetition is the message. The cards look similar because the user's intent was uniform. The UX reinforces this by keeping the styling clean and unremarkable — this is exactly what the user asked for, nothing more.

Reviewer's takeaway: "One decision, broadcast everywhere. Human control, full stop."

AI-suggested result

47 buildings, 47 tailored plans

Every building card tells a different story. The AI looked at each building individually and tailored a plan to its climate, use category, country, and baseline.

What the user sees:

The conflict panel, the honest part: above the building list, an amber alert surfaces any building the AI couldn't fully plan — over-constrained locks, missing data, or an optimisation clash. The panel explains why and offers two forward paths: loosen constraints in Step 3, or exclude those buildings and proceed.

Reviewer's takeaway: "47 buildings, 47 tailored plans, and the system tells you out loud when it can't help."

"The AI toggle is a mode change, not a feature flag. That distinction shaped the entire architecture of the workflow."

Personal reflection on the project

Conclusion

What this project taught me

01
The AI toggle is a mode change, not a feature flag
Treating manual and AI-suggested as genuinely different modes, rather than the same form with an autofill option, changed the entire UX. Users could commit to a mode at the start of a session, which reduced cognitive load and made each mode feel more purposeful. The toggle is prominent, not buried, because switching between modes mid-session is a legitimate workflow, not an edge case.
02
AI presentation is a craft problem, not a visibility problem
The instinct when adding AI to a product is to make the AI visible: banners, badges, callouts. What we found in testing was the opposite. Users trusted the recommendations more when they felt like their own insight, not like they were accepting something from a machine. The best AI UI is the one that makes the user feel competent, not assisted. Confidence indicators help; AI branding does not.
03
The unhappy path is a first class design concern
Edge cases in AI recommendations, buildings where the system lacks sufficient data, measures that conflict with tenant constraints, scenarios where the CapEx budget makes compliance impossible required as much design attention as the main flow. Users who hit a wall without a clear path forward abandon the tool entirely. Designing explicit states for every failure mode turned potential frustration points into moments of useful guidance.
Read more of my work
Case Study · Proxima
Proxima AI Chat
Proxima AI Chat
View Work
Case Study · Proxima
BuildingMinds Platform
From Hackathon to Platform
View Work
Case Study · BuildingMinds
BuildingMinds Platform
BuildingMinds
View Work