The site that has to explain the platform.

The problem

Gamelu sells into a market that does not think of itself as buying software. The buyer is a company that currently manages safety compliance with a spreadsheet and does not necessarily believe a platform would help.

That makes the marketing site do more work than a typical product page: it has to describe an obligation the visitor already has, show that the obligation is being handled badly, and only then introduce the product.

What we built

A Next.js site with the App Router, statically exported so every page is a CDN-served HTML file — no server to run, and no cold start between an ad click and the first paint.

Localisation runs through next-intl with Croatian and English message catalogues, so both language versions share one component tree and one deployment rather than being maintained as separate sites.

The contact route posts through Resend, giving enquiries a real delivery path with logs, instead of a mailto link that depends on the visitor having a mail client configured.

Design decisions

The page is ordered around the deadline problem — the thing the visitor recognises — rather than around a feature list. Modules are introduced as answers to a specific compliance obligation.

The primary call to action is the trial rather than a demo request, because the product is self-explanatory once someone is inside it and a booked call is a heavier ask than the buyer wants at that stage.

Where it stands

Live at gamelu.hr and feeding signups into the platform. The site and the app are developed together, so a change in the product can land on the marketing page in the same pass.