Skip to content
FREN Book a call
( Event tech · Carbon · Design system )( 03 / 08 )

Climeet

Measure the carbon footprint of an event to reduce it. An app that had to reassure without lecturing, and stay usable for event organizers who are not carbon experts.

· 2 min read · Event tech · Carbon · Design system

Climeet, an app that measures the carbon footprint of events
Climeet · Event tech · Carbon · Design systemclimeet.events

( Key facts )

Climeet is an app that measures the carbon footprint of events. In 2026, Vladimir Spalaikovitch led its art direction, Figma design system, React prototyping and marketing website.

Role
Art direction, design system, prototyping, front-end
Timeline
2026
Industry
Events, climate, SaaS
Scope
Figma design system, React app, 17-page marketing website
Stack
Figma, React, Vite

The problem

Event organizers have to measure and reduce their carbon footprint, under pressure from clients and regulation. Existing tools are built by experts, for experts: dozens of required fields, technical jargon, a constant sense of being audited.

Climeet wanted a tool any organizer could fill in, one that delivers a credible result from imperfect data and encourages progress instead of guilt.

My role

Art direction, design system in Figma, React prototypes of the key screens, then the marketing website. I worked with the founder, a UX designer in charge of wireframes, and a development team.

Key design decisions

Simplify the calculator

Client feedback on the first version was clear: too complex. We rebuilt the calculator around five data quality levels, from rough estimate to precise figure, with one absolute rule: never blocking. Organizers move forward with what they know, the tool shows how reliable the result is, and they can refine later.

Three views per category

Every emission category (transport, catering, accommodation, equipment, digital) reads through three views: total, breakdown and comparison. Same structure everywhere, so learning the first category teaches you all the others.

Gamification that doesn't cheat

Levels, badges and medals in the logo colors reward completeness and progress, not virtue signaling. A welcome popup explains the system, white blocks carry the learning content. The goal: make people want to come back and complete their data.

A design system that paid off twice

The Figma system (tokens, components, variants) was built for the app. When the simplified version was decided, the foundations stayed put: only the screens changed. The same system then fed the marketing website.

The marketing website

Seventeen statically generated pages, a full-screen hero, app screenshots staged in device frames, eighty-two client and partner logos, and photos chosen to never look like staged stock imagery. A wide container, assertive typography, and copy that explains without jargon.

Real-world constraints

  • Brand fonts missing from team workstations: a controlled, documented substitution.
  • A client changing direction after seeing the first version: that is exactly what a first version is for.
  • An app and a website that had to speak the same visual language, built by different teams.

Takeaways

  • "Never blocking" is a stronger design principle than any component.
  • A well-founded design system absorbs a change of direction without a redesign.
  • Gamification works when it rewards real effort.

See climeet.events. Expertise involved: design system, art direction, UX strategy, web design.

( Next · 05 )

Keep reading

  1. Design system

    Design system design: tokens, Figma and code components, documentation and governance, for teams that want to ship faster and stay consistent. Let's talk.Design SystemsRead
  2. Digital art direction

    Freelance digital art director in Paris: visual identity for products and websites, typography, motion and campaigns. 20 years across agencies and startups.Digital art director in Paris: identity, typography, motion, campaigns.Art DirectionRead
  3. UX strategy and product framing

    UX strategy consultant: problem framing, user research, product vision and prioritization, to decide what to design before the first screen. Let's talk.UX StrategyRead
  4. WeeFizz

    WeeFizz case study: designing a size recommendation SaaS for fashion. E-commerce widget on four CMS platforms, dashboard, back office. Co-founder and CPO.SaaS · Fit tech · AIRead
  5. Design system: where to start when you are starting from zero

    How to start a design system: the right order for foundations (tokens, type, spacing), the first twelve components, Figma and code, minimal documentation.Starting a design system: foundations, first components, Figma and code. · 3 minRead