About — Studio Inbetwn
Between craft & code
An AI-native creative technology studio, founded in Auckland. Small enough to care about every pixel. Senior enough to be trusted with the systems behind them.
The story — 01
Every era has a gap. Ours is between the businesses that run the world and the technology rewriting it.
Most agencies sell websites. Most AI consultancies sell decks. We started Studio Inbetwn because the businesses we kept meeting — dentists, accountants, physios, firms with full waiting rooms and empty websites — needed both halves working together: a digital presence that earns trust, and intelligent systems that convert it.
The name is the thesis. We sit in between design and engineering, in between agency and product studio, in between the old world and the AI one. That gap is uncomfortable for most firms. It’s home for us.
We stay deliberately small. Every project is led — and built — by the same senior hands you first talked to. When we say craft, we mean the kerning and the database schema.
What we believe — 02
Four convictions
We make things that mean something
Craft is the strategy
In a feed of templated sameness, the business that looks considered wins the click, the call and the contract. Detail is not decoration — it's positioning.
Validate before building
We'd rather ship a small thing that earns money than a big thing that earns applause. Every engagement starts with the cheapest possible test of the riskiest assumption.
AI with a seatbelt
We deploy intelligence where it compounds — and constrain it where it could embarrass you. Boring reliability beats impressive demos.
Own everything
Your code, your content, your customer data, your accounts. We build assets for your balance sheet, not dependencies on ours.
The people — 03
Founder-led. Actually.
Studio Inbetwn is founder-led — an engineering leader who spent years building products and teams before deciding the most interesting problems weren’t inside tech companies, but inside every business that isn’t one.
That background changes how projects run. Scopes are honest because the person scoping is the person building. Deadlines hold because there’s no telephone game between strategy, design and code. And the AI is deployed by someone who has shipped it in production — not someone who read about it.