Work

Proof, not promises.

We'd rather show you than tell you. Below are sites and products we've actually shipped — live, clickable, and built to be owned, not rented. Each one links straight to the real thing.

Selected work

Gasthaus Löwen · Siglistorf, CH

Babas Büezer Beiz

A Siglistorf Gasthaus that runs its entire online presence itself. Self-updating weekly lunch menus, reservations, plus candle sales and apartment rentals — several businesses under one roof, on one site the owner controls from her phone.

Why not a template

Built to be owned, not rented — no monthly platform fee, no template lock-in, and it loads fast. The weekly menu changes without anyone touching code. A template would have meant paying rent forever for a site that still couldn't do half of this.

Visit site

What we're building

Launching 2026

MiseEnKit

Your food. Your voice. Posted.

The fastest path from a phone photo of tonight's special to a posted, on-brand social update — for independent restaurants and cafés with great food and no time for design tools.

Visit site

Systems we run ourselves

0:40

Assistant

Fleet

One front door to thirty running projects, email, travel, a product pipeline and the accounts. Ask what needs you today and it answers out loud, in about forty seconds.

What it takes

An assistant is only as good as what it can see. George doesn't know anything. It reads systems that do — so what it can tell you, how complex it gets, and what it costs are decided by that infrastructure, not by the assistant sitting on top. Where those systems already exist, we connect to them, and that means real access to them; the access is most of the work. Where they don't exist yet, building them is its own engagement, and a larger one. The design and the personality are entirely yours — we'll work with you to shape both to your taste and the way you work. That part is flexible, and it's the cheapest part of the build.

Talk about building one Read how it was built

Agent workforce

Moya

A coordinated workforce rather than a pile of separate tools. One orchestrator takes the request and routes it to the specialist that should handle it — research, build, content — each working in its own lane and reporting back through a shared control repo. This is the layer an assistant reads from.

Audit

Aeryn

A standing audit pass over architecture, code quality, security and dependencies, run read-only and deliberately separate from whoever built the thing. Findings land in the repo with severities that gate the work until they're addressed or knowingly overridden. The session that built something is the worst judge of it.

Want something like this?

Start a conversation