How GuusLab works, in six lines.

A short operating manual for a one-person studio. Read it in under a minute.

Principles

  1. 01

    One person, full stack.

    Design, code, and infrastructure are one conversation. No handoffs, no interpretation loss. The person drawing the pixel is the person shipping the pixel.

  2. 02

    Ship things, not decks.

    Every week should produce something a real person can use. A moodboard is a warm-up; a working prototype is the work.

  3. 03

    Taste is a technology.

    Choosing what to leave out is harder than choosing what to add. The studio optimises for the feeling you get on second use, not first glance.

  4. 04

    Own the whole seam.

    From brand to database. If GuusLab is responsible for a product, GuusLab is responsible for every edge of it.

  5. 05

    Small, not scaled.

    The studio stays one person on purpose. The unit of scale is quality per shipped surface, not headcount.

  6. 06

    European by default.

    Files, servers, and jurisdiction in Europe. GDPR isn't a constraint; it's the baseline.

How a project runs

A typical GuusLab project moves in four overlapping phases, not stages: shape, make, ship, polish. The first three happen in parallel almost from day one. Polish never really stops. It's what separates a product from a demo.

What the studio is currently building

All of GuusLab's attention is on Nemi right now, an all-in-one file platform. Alpha is live internally. Invite-only beta opens in Q2 2026, with public beta rolling out between Q3 and Q4 2026.

Work with GuusLab

GuusLab occasionally takes on a single external project per quarter. If that sounds like yours, get in touch via the contact page.

© 2026 GuusLab. Built in the Netherlands.