Projects

Work

Each case with the problem, what we built and what changed.

01 · 2025

GymManager

The problem: A gym runs on a notebook, a spreadsheet and three apps that never talk to each other. Renewals slip, payments get chased by hand, and nobody knows how many people came in yesterday.
The insight: The problem was not a missing tool: it was that each one solved a slice and none shared its data. Members, payments and access are the same data seen three ways.
The solution: A web platform — installable on the phone as a PWA — where members, plans, recurring payments, routines, QR check-in and reports live together. One place, several locations.
The result: It is a product in production, used daily by paying customers. You can open it and look around.

02 · 2026

The problem: An internet provider with three sites — the landing page, the blog and the research site — where changing a paragraph meant opening a ticket and waiting for a developer to have a spare moment.
The insight: They did not need a new site: they needed to stop depending on us to publish. The improvement worth making was not visual, it was who holds the key.
The solution: The blog became self-managed: the team writes, edits and publishes without opening a ticket. On the same principle, we are now working on the landing page and on improving the research site.
The result: The Ixfo team publishes and edits its blog without going through development.

03 · 2026

The problem: Orders arrived as messages and were typed into a spreadsheet by hand. Every order was written twice, and the second time was where the stock errors appeared.
The insight: An order never needed to be written twice. If it is entered once and travels with its status, the kitchen and the back office read the same data.
The solution: A full platform on one foundation: catalogue and orders on the web, a mobile app for the customer, and an admin panel with statuses and reports.
The result: An order is entered once and reaches the kitchen without being retyped.