How Hygibox went live in under a week and increased conversions by 200% with doubled frontend performance

HYGIBOX does not sell the way a shop sells. In Germany, anyone with care level 1 or above who is cared for at home is entitled to care aids worth up to €42 a month, covered by their statutory care insurance fund with no copayment. So the order is not really a purchase. It is a claim: the customer configures a box, then files a cost-coverage application with their care level, their insurance fund and the details of the person being cared for, and hygi.de settles the invoice with the fund afterwards. That logic already worked. It sits in systems hygi.de built itself and has run for years. What did not work was the layer in front of it.

The existing frontend had reached the point where every visible change was an engineering task. A campaign landing page, a new product area, a seasonal banner: each one meant a ticket, a queue and a wait, and in a business whose ordering season is driven by campaigns, that waiting time is expensive. The audience raised the bar further. The people ordering are care recipients and the relatives who care for them, often older, usually ordering under time pressure, and rarely willing to work through a dense interface. Every extra step, every unclear label, every field that asks the same thing twice costs a completed application.

Replacing the commerce system was never on the table. The order logic, the product data and the insurance settlement were fine. HYGIBOX needed a new frontend, not a new platform, and it needed it in days rather than in a project cycle measured in quarters.

Laioutr went on top of the existing stack as a frontend layer. The commerce system, the product data and the insurance settlement stayed exactly where they were: nothing was migrated, nothing was replatformed at the back. The entire storefront UI was then built in Laioutr, from the box configurator through product and category views to content pages and the responsive layout. Components come from the Laioutr library and are composed in Laioutr Studio, so a page is a composition rather than a template a developer has to open.

The checkout is where the custom work went. Laioutr connects to HYGIBOX's own checkout through a custom integration, so the ordering process for a care-aid box (configuration, cost-coverage application, submission) starts and runs inside the storefront and hands off to the systems that file the claim and bill the fund. The customer moves through one flow. Behind it, the existing logic keeps running unchanged.

Alongside the build, Laioutr advised the team on how to structure the frontend for the years after launch: which parts belong in reusable components, how pages are cut into sections, and how the team administers all of it in Laioutr Studio afterwards, without going back through engineering for a banner, a landing page or a campaign. From project start to live storefront took under a week.

The storefront went live in under a week. That is the number the team notices first, but the one that matters more came afterwards: conversions have grown by 200% since go-live. Two things drove that. The ordering process is now one path rather than two, so configuring a box and filing the cost-coverage application no longer feel like separate systems to the person ordering. And the interface was built for the people who actually use it: few steps, plain language, large targets, nothing to interpret.

Day to day, the frontend now belongs to the team that runs it. Content, product areas and campaign landing pages are edited in Laioutr Studio by the people responsible for them. Engineering is involved when something needs to be built, not when something needs to be changed.

And because the storefront sits on top of the existing commerce system instead of replacing it, the two can move separately. The backend can change without a frontend rewrite; the frontend can change without a release train.