Designing the platform architects use to understand climate.

Product Design· UX Research· AI-Assisted Design· Product Communication
infrared.city — Sky View Factors
Product infrared.city

One year as the only designer at a climate tech startup. My job was to understand what users actually needed and design a product that delivered it.

Details
Role
Product Designer
Scope
UX Research · Product Design · Communication
Type
B2B SaaS · Climate Tech · AI Tools
Duration
2025–2026
Problem A powerful platform with real UX gaps

The platform had strong technical foundations but had grown without dedicated design input. Onboarding, navigation, and data presentation had room to improve.

Solution Research-led design, end to end

I ran usability studies, redesigned key platform features, built the plugin icon system, and led the audience research and communication strategy.

Result A platform users can actually use

1,300+ projects optimized, climate reports in under 5 minutes, measurable performance gains, and a design foundation the team can build on.

Deliverables End-to-end — research, design, delivery
6
Usability Sessions
6 sessions · new users · task-based
3
Design Audits
website · software · platform
9
Onboarding Steps
Product Fruits + Figma
~30
Icons Designed
Revit + Grasshopper plugins
2
Features Rebuilt
reports + comparison
4
Landing Pages
2 audiences + pricing
4
Platforms
app · SDK · interior · integrations
1
Full Website
infrared.city from scratch

From 3 days to 3 seconds.

80% of buildings have no climate assessment. Traditional simulations require specialist software, weeks of setup, and budgets of tens of thousands, putting climate-informed design out of reach for most projects.

infrared.city changes that: AI-powered simulations for wind, solar, thermal comfort, and heat stress, directly in the browser, for any project, at any scale.

<1s
per simulation
500K+
simulations in training data
0.1%
of traditional cost

Design. Simulate. Iterate.

Here's how a project actually moves through the platform, from an empty map to a shareable climate report.

01Create
Pick a location. Climate and weather data loads automatically.
02Edit
Add buildings, trees, and ground materials to the 3D scenario.
03Simulate
Run wind, solar, thermal or daylight models — 8 types, results in <1s.
04Compare
Save a snapshot, then compare two scenarios side by side.
05Report
Generate a client-ready report or share via public link.
infrared.city platform — thermal comfort simulation

infrared.city platform — thermal comfort simulation overlaid on a 3D urban model.

I was designing a platform for architects.

I'm not only a product designer.

I'm also an architect.

My architecture background gave me two perspectives at once. As a potential user, I understood the workflows, the project pressure, and where a confusing interface costs real time. But because I wasn't part of the team that built the product, I could also see it with fresh eyes, recognising what wasn't working without the assumptions that come from being too close to something.

Who is this actually for?

infrared.city could serve architects, students, researchers, city planners, and more. Trying to speak to all of them meant speaking clearly to none. I ran competitor analysis, drafted personas, and used direct observation through usability sessions and a user survey to understand who they were and how they actually used the product.

Potential user types identified

Sustainability Architect
Architecture Student
Urban Planner / City
Freelancer Architect
Technical Integrator
Sustainability Consultant

Meet Anne and Louis.

Two personas built from the usability study and internal feedback, representing the two most differentiated user types on the platform.

Anne Fitcher — Sustainability Architect
Anne Fitcher
Louis Bernard — Architecture Student
Louis Bernard

I watched four architects get stuck in the same place.

Before designing anything, I needed evidence. I combined task-based usability testing with semi-structured interviews to understand where the product was failing and why. Each finding mapped to a real user struggle, not an assumption.

Methodology

6participants
6sessions
New users only
Task-based testing
Post-session interviews
Findings documented

"Where do I create a project?"

Onboarding task

"I just need the basic information when I create a project."

Post-session interview

"Is the wind stronger when it's red? Or when it's blue?"

Climate section task

From findings to design decisions

The research made it clear where to start. Each design response maps directly to a finding. Nothing was designed speculatively.

Onboarding & Navigation clarity

The biggest friction point was the first 60 seconds. I benchmarked 8 B2B SaaS products, then designed a 9-step contextual quick tour using Product Fruits, each tooltip mapped to a specific panel, guiding users in context. I proposed always keeping one mode active (navigate or edit) so users always know where they are. I also surfaced "Create new project" to the top of the dropdown, making the primary action immediately visible.

Benchmarking research — 8 B2B SaaS products
8 products benchmarked
Esri, Mapbox, Autodesk Forma, CARTO, Giraffe, UrbanFootprint, DroneDeploy, Nearmap
Quick tour — 9-step onboarding
9-step onboarding designed with Figma and Product Fruits

New features kept appearing. I designed every icon.

As the Revit and Grasshopper plugins evolved, new actions kept emerging. I designed the full icon set from scratch, using colors outside the main brand palette so plugin icons are immediately recognizable inside those environments. Low effort, high impact.

Reports.
The only deliverable that leaves the platform.

The reports feature was the most critical part of the product. It is what architects share with clients and planning authorities. If it was broken, the platform's value did not reach the end of the chain. It was also the feature furthest from production-ready.

I used Lovable alongside my own UX direction to prototype and rebuild the reports system in Figma. The before and after shows how dramatically the experience changed.

Before
Reports — before redesign

No information hierarchy, no audience targeting, no AI writing support. Sections were visually uniform and navigation made it hard to orient.

After
Reports — after redesign

The new system has structured navigation by section, audience selection that adapts content density, AI writing integrated per section, key metrics in the summary, and a clear management dashboard with status and filters.

Key features

01
Audience targeting
Reports adapt their text density and chart complexity based on whether the audience is a client, technical team, or mixed. One platform, multiple outputs.
02
AI writing per section
Each report section has an integrated AI writing tool that generates climate summaries from simulation data. The designer defines the structure. AI fills the content.
03
Snapshot management
Reports are built around simulation snapshots. Users select a main snapshot and comparison scenarios. The report structure follows from the data, not the other way around.

Comparison.
Side by side, finally.

The comparison feature lets users evaluate different design scenarios side by side: baseline vs. more trees, baseline vs. higher density, for example. The original version made it difficult to understand what was being compared and why the numbers differed.

I rebuilt this page in parallel with the reports system, establishing a consistent visual language between the two features.

Before
Comparison — before redesign

No customization, no way to adjust what was being shown or how.

After
Comparison — after redesign

Adjustable panel sizes, empty states guiding each step, and a clearer data hierarchy.

The AI built it. I fixed it.

The team rebuilt parts of the platform with AI assistance. Using Claude Code, I reviewed the output systematically: checking for hierarchy issues, inconsistent component usage, broken flows, and copy that did not match how real users actually spoke.

AI can produce interfaces that look correct but fail on usability. My role was the design judgment layer between AI output and the finished product.

4
areas reviewed
18
issues found
6
quick wins
3w → 3d
with Claude Code

4 areas reviewed

I organized all 18 findings across four categories, then prioritized 6 as quick wins: low-effort, high-impact changes.

01
Analyze
02
Integrations
03
Code & API
04
Overall UX

Quick wins

6 issues flagged for immediate resolution, prioritized by impact and effort

Effort / Impact matrix

Fast prototyping with Claude Code

Claude Code became a constant tool across the entire process: meeting transcription, brainstorming, audit organization, and systematic design review. Work that would normally take 3 weeks was completed in 3 days.

Claude Code mascot

Taking the product to the right people.

Beyond product design, I led the communication strategy: mapped audiences, ran a user survey, defined channels, and designed two distinct landing pages for the two most different user profiles.

Audience research delivered as a full communication strategy deck

Audience segmentation map
Audience segmentation — Strategic · Target · Opportunity
Primary target and channel strategy
Primary target profile + channel strategy
User survey data
User survey — professional background & experience
Communication action plan Aug–Oct 2025
Action plan Aug–Oct 2025 — Instagram · LinkedIn · Google Ads

Landing pages: two audiences, two distinct messages

Two versions targeting the two most differentiated user profiles: non-technical architects who need fast sustainability reports, and technical teams looking to integrate simulation into their stack.

Landing page — non-technical audience
Non-technical architects — sustainability reports, fast outputs, no setup required
Landing page — technical teams
Technical teams — API access, simulation pipeline integration, developer-first messaging
Visual system · color tokens
Urban Teal
#2B7C85
Verdant Breeze
#53AB85
Sky Mist
#D4F0FC
Ocean Depth
#175873
Midnight Blueprint
#142063
Soft Cloud
#F3F3F3
Deep Onyx
#171616

These color tokens were part of infrared.city's existing brand palette. I used them as a foundation and introduced gradients between the tones to bring a more contemporary feel to the visual system.

What a year as the only designer taught me

01
Domain fluency sharpens what you see
My architecture background made me a better analyst. I could read the gap between what the interface assumed and what architects actually needed.
02
AI output needs human editorial judgment
Consistency, tone, and usability don't come from a prompt. My role became the layer of judgment between AI output and the finished product.
03
Document the reasoning, not just the result
Every design decision in a startup has downstream consequences. Documenting the reasoning made collaboration faster and gave the team something to build on.

Like what you see?

Let's Connect!

✉ marisouzaarq@gmail.com

Designed and built entirely by Marianna de Souza · Built with Claude Code