refinq GmbH

From a pitch deck to a funded product.

I turned existing research and founder input into an interactive prototype for the FFG funding process, plus a design foundation the team could develop after the funding decision.

0→1 Product DesignProduct StrategyDesign SystemsRapid PrototypingStakeholder Alignment

RoleProduct Designer and Product Consultant
TimelineJune to September 2023 · 4 months
ProductB2B platform for climate and nature risk
ResultInteractive prototype for the FFG funding presentation, plus a design system foundation
refinq open on a MacBook: the Locations panel beside the risk map of Europe, standing on a pale green ground

Impact

  • €480KFFG research grantThe prototype was presented as part of the funding case.
  • 6 → 1Product directions to one journeySix valid ideas were organised around one shared unit.
  • 40+Components designed and documentedThe design foundation for the product.
  • 4Product areas designedMap, list, risk detail and report overview dashboard.

Overview

Context

refinq assesses climate and nature risk for company locations.

Task

Create a credible interactive prototype for the FFG funding process.

Starting point

Existing research, analyses, reviews and founder feedback.
No product interface, structure or component library.

Outcome

One location-based journey, with the system underneath it.

  1. An interactive prototype with user flows.
  2. A design foundation the team could develop after the funding decision. The core structure remains in the later product.

01 · The starting point

Product StrategyRapid Prototyping

Design started at zero

refinq had validated climate models, existing research and several valid product directions.
Development had not started, because the funding decision had to come first.
No product design, no wireframes, no screens, no design system.
I was the only designer.

The prototype therefore had two jobs.
It had to make the proposed product concrete in the funding room. It also had to leave behind a structure the future team could develop.

The main constraint was scope.
Six directions could not become six products in four months. A clear first product had to be defined without closing the door on later use cases.

The product design had to be specific enough to fund and broad enough to grow.

existing research and analyses
six valid product directions
wbgt_max_rcp85.csv
lat,lon2030205046.76,15.1927.928.350.11,8.6826.427.140.41,-3.7031.232.641.90,12.4930.131.4
the data existed: it just had no interface
Research and directionsthe starting point
A design foundationsection 04
An interactive prototypesection 03

02 · Product strategy

Information ArchitectureStakeholder Alignment

Challenge: Six directions → one product

What did the six directions actually have in common?

The founders’ ideas ranged from supply chains to scenario planning.
All of them were valid, but we had to set priorities in order to create an MVP.

What every direction shared was a starting point: company location.
That decision created four connected areas: map, locations, risk and financial impact.
It also created one complete journey: sign in, add a location, understand the risk, compare the financial effect, and export a report.

Instead of comparing six futures in the abstract, the founders worked through one product they could see, and each direction either found its place in it or moved to later.

Six directions became one journey without removing the future options.

03 · Interaction and data visualisation

Interaction DesignData Visualisation

Decision-makers need the conclusion first. Specialists need the evidence behind it.

The product had to support two levels of use.
Specialists needed traceable climate data, models and scenarios.
Corporate decision-makers needed a clear answer at portfolio level.

I built every screen around one rule: show the answer first, keep the evidence one interaction away.
A risk score appears in the main view.
The scenario matrix, source and model details can be opened when they are needed.
The journey ends in financial impact, which translates hazard data into an interactive report that supports business decisions.

A single unexplained summary score was avoided.
In climate risk, a number that cannot be traced is not useful.

The interface reduced complexity without hiding where the result came from.

Station 1 · Sign in. Click Login to start the journey.Station 2 · Map. Decision 1 · two tabs, Coordinates and Address, plus NACE code and reporting period.Station 3 · Location Details. Decision 2 · the score up front in a coloured chip, source and model open on demand.Station 4 · Data Layers. Risk is a layer you switch: heat stress, flood, Natura 2000.Station 5 · Report. Decision 3 · two risk types, one euro figure each, the bigger risk as the bigger circle.

refinqKey visual: stacked translucent diamond planes in green and blue
Locations
Your Locations
8541 Schwanberg60310 Frankfurt am Main28001 Madrid00010 Rome
Data Layers
Choose Data Layer
Location Details
Your Locations
Mitigation Strategy
Avoidance
Minimisation
Rehabilitation and Restoration
Compensation or Offsets
Protected Areas4Dependencies2Impacts8
Satellite view of the Schwanberg site
Nace Code: B8.1.2High PriorityAdaptation Solutions NecessaryMitigation Measures Necessary
Austria8541 Schwanberg46.76356, 15.19284
RCP 2.6RCP 4.5RCP 6.0RCP 8.5WAVGStartMaxEnd
Heat Stress
Water Stress
River Flood
Coastal Flood
Rainfall
Snowfall
Hail
Wind
Cyclone
Landslide
Wildfire
Heat Wave Days
Cold Spell Days
Frost Days
Ice Days
Drought
Crop Failure
Soil Erosion
Location Overview
Your Locations
Filter By
Filtered: Nace B8.1.2 · 4 locations
Views
721K+11.01% ↗
Visits
367K-0.03% ↘
New Users
1,156+15.03% ↗
Active Users
239K+6.08% ↗
Potential Financial Impacts
30.000€Biodiversity & Ecosystems
120.000€Physical Climate Risks
Development
SchwanbergFrankfurt am MainMadridRome
01.0101.0201.0301.0401.05
Risk Mapping
High Physical Climate Risks38.6%
High Dependencies22.5%
High Impacts30.8%
Other8.1%
Asset Austria · Components
scroll for all 18
WAVGStartMaxEnd
Heat Stress0.361528.718528.342128.3421
Water Stress0.16360.05690.07260.0726
River Flood0.00000.00000.00000.0000
Coastal Flood0.00000.00000.00000.0000
Rainfall0.76961034.6351204.8911048.546
Snowfall0.301154.4663116.774563.2159
Hail0.36500.07750.07680.0759
Wind0.192366.774166.910666.4593
Cyclone0.00000.00000.00000.0000
Landslide0.00000.00000.00000.0000
Wildfire0.07960.00210.01610.0053
Heat Wave Days0.42683.38747.22247.2224
Cold Spell Days0.00000.00000.00000.0000
Frost Days0.4179123.6667152.3333112.0000
Ice Days0.244523.000069.666718.6667
Drought0.12280.05800.21740.0000
Crop Failure0.05600.00390.01700.0000
Soil Erosion0.48901416.2021820.5041820.437

04 · Design foundation

Design SystemsAccessibility

The design foundation was built at the same time as the product.

Material Design 3 provided the base. I extended it with the patterns refinq needed: severity chips, scenario matrix, financial impact visualisations and ESRS reporting table.

Each component included its states and its information logic, not only a default screen. Severity was communicated through colour, label and score, so it remained readable in greyscale and for people with colour vision differences.

The library was documented so engineering could start from a defined product structure instead of reverse-engineering it.

The prototype showed what to build. The foundation showed how to continue.

Design Foundation
Tokens
Forest#24473C
Leaf#8CC63F
Teal#014751
Blue#1E5EE4
Green#00D37F
Lime#DAFEA4
SurfacesRail · Panel · Card
Panel title 26Card title 20Label 13
Component library · live states
Button· property: variant (4) × state (4) · the Enabled column is live
EnabledHoveredPressedDisabledFilledLabelLabelLabelOutlinedLabelLabelLabelText+ Label+ Label+ LabelTonalLabelLabelLabel
Button· product instances
Finished
Button· on dark
Text field· live · click and type
Underline field · label, input, validation.Latitude must be between -90 and 90.
Text field · Underline· states
Text field · Outlined· states
LatitudeInput
LatitudeFocused
LatitudeError!
Date picker · Docked· live
‹ Aug ›‹ 2023 ›
SMTWTFS
CancelOK
Date field· wired to the picker
Date08/17/2023
MM/DD/YYYY. The reporting period on the Add screen uses a range of two.
Radio· states
UnselectedSelectedDisabled
Instance: the "Your Locations" list, one active site.
Checkbox· states
UncheckedCheckedDisabled
Instance: the Country filter, "Remember me".
Tab· states
CoordinatesAddress
Badge· states
Protected Areas4Dependencies2Impacts8
Modal· live · every score opens its evidence

The chip carries the answer. The modal carries the method: definition, data sources, scoring, the same pattern behind the info dot on every hazard row.

Severity chip· anatomy
+Label+0.3609→0.3609

Colour + label + score, all three, always. Readable without colour: flip the Greyscale toggle.

Severity scale· the four levels
Low · 1Medium · 2High · 3Very High · 4

05 · Outcome

Company OutcomeProduct Handover

The founders could show one product instead of explaining six ideas.

The interactive prototype was used in refinq’s FFG funding presentation. refinq subsequently received €480,000 in research funding from the Austrian Research Promotion Agency FFG.

My contribution was a complete product direction and a documented design basis. I made the intended product visible, testable and concrete enough to be discussed as a product.

The founders could align around one interactive product rather than separate descriptions. Engineering could begin with a defined journey, data hierarchy and documented components.

After handover, the team continued with the location-based journey, the risk scale, the scenario logic, the financial impact visualisation and the design foundation.

Read the coverage on brutkasten ↗

06 · My contribution

Product strategySynthesised existing research, analyses, reviews and founder feedback into the first product scope.
Product designDesigned the complete journey and every screen of the interactive prototype.
Data visualisationTranslated climate scenarios into risk, portfolio and financial impact views.
Design systemsCreated and documented a Material Design 3 foundation with more than 40 components.

More projects

What else I have built.