A small studio. A single brain.
We're a senior studio building production systems for ambitious teams. This page is who we are, where we're going, and the rule that decides what we'll do.
Where we're going.
To be the small studio that ships the most-loved products of the next decade. Compact teams. Decade-long thinking. Weekly proof of work.
We're optimising for a long career, not a quick win. The work we ship in 2026 is the foundation for the work in 2036. Senior craft compounds — we want every project we take to make the next one easier.
Posture
Slow on intake. Fast on shipping. Picky on partners. Generous with referrals when the fit isn't us.
What we do every day.
We pair design, code, and AI agents to ship production systems for ambitious teams. Small senior teams. Weekly demos. End-to-end ownership.
Every project ends with three things: a deployed system in production, a runbook that fits on one page, and a team that can run the system without us. If any of those three are missing, we haven't finished.
How we measure
- · Did it ship? (binary)
- · Does it run? (production parity)
- · Can they run it? (handover < 1 hour)
- · Would they hire us again? (NPS)
Daily rhythm
09:00 standup async · 14:00 review · weekly demo Thursday · monthly retro · quarterly re-scope.
One rule. Three words.
Ship products, not slides. It's printed at the top of every project brief, every contract, every weekly demo agenda. If the deliverable can't be deployed, it's not the deliverable.
The motto is also a filter — if a project requires us to spend more than 20% of the time on artefacts that don't ship to production, we either re-scope or pass. It saves both sides a slow-motion failure.
Where you'll see it
- · Top of every project brief
- · Footer of every contract
- · Header of every weekly demo
- · Pinned on every team Notion
Why three words
If we can't say it in three words, we can't expect a client to use it as a decision filter at 4pm on a Tuesday.
From the studio.
We started VIZULABS because the studios we used to work with all ran the same play — big teams, big decks, big invoices, slow shipping. Then somebody else inherited the system.
We wanted to run the opposite play: one or two senior people, one shared brain, one shipped system at the end. Same people from first call to last commit. Door's open.
If we're the right fit
- · You'd rather have a shipped v0.1 than a perfect v1.
- · You read code reviews carefully.
- · You can write a tight one-page brief.
- · You like working with people, not departments.
If we're not
You need 40 hands on a 12-month strategy engagement. You want a single junior contractor for a year. We'll refer you to a peer that fits.