02 Work

Selected work

Four projects, explained in full: what the problem was, what I built and where it stands today.

01 Online store for a heating equipment distributor

Rotherm B2B

A custom store that replaces a rented platform: public catalog, partner accounts with their own prices, a Google product feed.

Role
Design and full-stack development
Year
2026
Where it stands
Launching November 2026

The problem

Rotherm sells boilers, heat pumps and air conditioning to both homeowners and installers. The store ran on a rented platform that could not show an installer their negotiated price, and every price change from a supplier meant editing products one by one.

What I built

I designed and built the store from scratch: the interface in Next.js, the server and database in FastAPI and PostgreSQL. Around 650 products, with categories, brands, specifications and documents, were moved from the old platform. The same site serves two audiences: visitors see public prices, while installers log in and see theirs.

How it works

  • Three price levels: public list, company list with discount, price negotiated per product
  • Partner accounts for installers, with a sign-up request reviewed by the team
  • Catalog with filters, brand pages, service pages and a blog
  • Product feed for Google Merchant Center, generated from the catalog
  • Product images and documents served from cloud storage, so pages stay fast
  • Every update is checked automatically before it goes live, so a change to prices cannot break ordering

Where it stands

The store is on a test address and replaces the old platform in November 2026. The remaining steps are the 301 redirects from the old addresses and adding the feed to Merchant Center on the final domain.

Screens

Stack: Next.js · React · TypeScript · Tailwind CSS · FastAPI · PostgreSQL · Vercel · Railway

02 Back-office for products, prices and orders

Rotherm ERP

The admin side of the same platform: supplier price imports, product pages filled in with AI, competitor prices, and the order flow from stock check to invoice.

Role
Process analysis, UX and full-stack development
Year
2026
Where it stands
In development · catalog modules in use

The problem

Behind the store, the work was spread over spreadsheets, the invoicing program and email: supplier price lists arrived as PDF or Excel, stock was kept in two cities, and nobody could see in one place where an order stood.

What I built

I wrote the specification together with the team, drew the screens, then built the back-office inside the same platform as the store, so there is a single source for products, prices and orders. It grows module by module: the catalog side came first, the order flow follows.

How it works

  • Price import: a supplier's PDF or Excel list is uploaded once, matched by product code, and prices and discounts are recalculated
  • Product enrichment: description, specifications and photos are pulled from the manufacturer's site and arranged with AI, then checked by a person
  • Competitor prices: checked every night, matched by code and shown next to ours, product by product
  • Sales channels: the fields Google and marketplaces ask for, with a check that shows what is missing on each product
  • Suppliers, brands, product variants and a review queue for imported products
  • Order flow, designed screen by screen: stock allocation per warehouse, split deliveries, pick-up with serial number scanning, courier shipping, proforma and invoice through the invoicing provider

Where it stands

The catalog modules (products, price import, enrichment, suppliers, brands, channels, competitor prices) are in use for preparing the launch. The order flow is designed and specified, and is being built next.

Screens

The screens are the UX mockups for the order flow, with sample data.

Stack: Next.js · TypeScript · FastAPI · PostgreSQL · Claude API · Python

03 Health app (PWA)

Moveat

An installable app connecting meals, running and the menstrual cycle in one daily view, with Strava sync.

Role
Concept, design and development
Year
2026
Where it stands
Live · version 2.0
Live site ↗

The problem

Meal plans, running plans and cycle tracking usually live in three separate apps that know nothing about each other. Yet what you should eat or how hard you should train depends on all three.

What I built

A web app that installs on the phone like a native one and opens even without internet. It has four tabs: Today, Meals, Sport and Cycle. The Today screen gathers everything into one picture of the day. Runs come in automatically from Strava.

How it works

  • Sign-in with a link sent by email, no password to remember
  • Meal plan with calories and macros for the day
  • Training plan and runs synced from Strava
  • Cycle phases, with recommendations adapted to each phase
  • Onboarding, consent, settings, data export and account deletion
  • Works offline and adapts to phone, tablet and desktop

Where it stands

Version 2.0, with a new, colourful design, is live. I use it every day, which is also how I find what to improve next.

Screens

Stack: JavaScript · PWA · Supabase · Strava API · Vercel

04 A planner that an AI assistant can read and edit

Agenda MCP

Tasks, calendar, notes and daily goals exposed to Claude as 24 tools, plus a web app over the same data.

Role
Concept, design and development
Year
2026
Where it stands
Live · private

The problem

An AI assistant is only as useful as the data it can reach. Without access to your planner, it can give advice about your day but cannot see it or change it.

What I built

A server that speaks MCP, the open protocol through which Claude connects to outside tools. It gives the assistant 24 actions over tasks, calendar, notes and goals. On top of the same database there is a web app, so the planner can also be used by hand, on phone, tablet or laptop.

What's on today?
daily_briefing()
3 tasks, a call at 14:00 and 6 of 10 on your daily goal.
Move the course to Thursday at 17:00.
update_event()
Done: React course, Thursday 17:00–19:00.

How it works

  • Tasks grouped by project, with categories, priorities and due dates
  • Seven-day calendar with events and work blocks, each in its own colour
  • Text notes and a handwriting board for a stylus
  • Daily goals with progress and history, and a morning briefing
  • Its own accounts and sign-in, so each user only reaches their own data
  • Whatever the assistant changes appears in the web app at once, and the other way round

Where it stands

It runs non-stop and I plan my days with it. The same approach works for a business: an assistant connected to orders, stock or customers instead of a planner.

Screens

The screens show the real app with sample data.

Stack: Python · MCP · PostgreSQL · Claude · Railway

Have a project?

Let'stalk.