NOVA. is a studio in Moscow making the kind of site you build once and never apologise for. Slow, expensive, and on time. Premium showcases, considered commerce, and bespoke products for clients who can tell the difference.
Almost every project is under NDA or still in flight — we describe the thinking, not the screens. The one card with a pink badge is the sample case study, open it to see how we publish work when we can.
A bespoke marketing site for a Frankfurt-based investment firm. Daily-updated commentary, a quarterly publication, and a private dashboard for LPs — all on one Payload instance, all under one weight.
View case study →An Oslo workshop's first dedicated e-commerce site. Built around editorial lookbooks instead of category grids; checkout in three steps; lead-time transparency on every product.
Read notes →A practice site for one of Germany's most quietly serious architecture studios. Three hundred projects, two languages, one Payload schema — and a press archive that finally renders on phones.
Read notes →Every engagement starts as one of these five. Hourly work and retainers are politely declined — we price by outcome and scope, not by the calendar. Open any line for what's included.
Total elapsed time ranges from 8 to 16 weeks depending on scope. Every stage ships an artefact — there's no black box in this studio. The document you'd be reading at Stage 02 is the studio's design-system spec.
An intro call, a working session, and a signed brief. We name the thing that's broken, the audience that matters, and the budget that exists — in plain sentences, no jargon.
A 12–20 page document like the studio's design-system spec: naming, tokens, references, risks. The studio's bet on the brand before a single component is drawn. Signed off in writing.
Two rounds of high-fidelity design. Round one is the direction; round two is the resolution. We design in the browser when we can, in Figma when we must. Motion is prototyped, not described.
Production build on the studio stack. Code review on every PR, a private staging URL from week one, performance budget enforced in CI. Same hands as design — there is no handoff.
DNS at 10:00 MSK, never on a Friday. Three weeks of post-launch support included. After that, the client owns the codebase and the studio is on a phone-call basis for as long as the site is live.
Long-form essays on craft, process, and the economics of premium. Quarterly, unsponsored. The two most recent are below.
The site goes live, the team takes a screenshot, the client posts on LinkedIn. We stay quiet. A defence of the cooling-off period, and what we do during it instead.
A field note on the rules we keep — what we let assistants do, what we never let them touch, and why the boundary keeps moving. This site is the proof.