Nuttifox manifesto

Four people, one team, no hand-offs.

Nuttifox is a small studio — not an agency machine. We take on a handful of projects, so the people you meet are the people who design and build the thing.

Established2009

Team4 people · remote

WorkingEMEA · US · APAC

AvailabilityQ4 2026

/01

Origin

est. 2009

origin.txt

We started as one designer taking on work that needed building, not just drawing.

The studio has been running since 2009. It grew the way good studios do — slowly, by keeping clients rather than chasing them, and by adding people only when the work genuinely needed a new pair of hands.

Along the way the tooling changed completely. Framer replaced static mockups. Lovable, Replit and Claude collapsed the distance between a prototype and a real product. n8n turned the boring parts of a business into something you configure once.

What didn’t change: a small senior team, one thread of accountability, and a bias toward putting something real in front of people early.

/02

What we believe

four positions

Same people, start to finish

The team that scopes your project is the team that ships it. No account layer, no hand-off to a junior pod once the contract is signed.

Taste and engineering aren't in tension

Design and build run as one job, not two departments passing files. Nothing gets lost in translation, because the person drawing it is in the same thread as the person shipping it.

Shipped beats presented

We're only doing our job if the thing we build makes your business move faster. Fewer decks, more work in production.

AI is a tool, not the pitch

Claude, n8n, Lovable and Replit are in the pipeline where they make the work faster or better — and we say so plainly when they don't.

/03

How we work

scope → ship

01
Scope
A short call, then a written scope: what we're building, what we're not, and what it costs. No discovery theatre.
scope doc
02
Design in the open
Work lands in a shared channel as it happens — you see the real thing early, not a reveal in week three.
shared channel
03
Build together
Design and engineering run in parallel, not in sequence. Framer, React, or a mix — whatever the build needs.
staging build
04
Ship, then iterate
We launch, watch how it behaves, and keep going — retainer or flexible support from there.
in production