Pirate, Architect, Designer
Earlier this year, Dan Shipper, CEO of Every, proposed a new model for engineering teams in 2026. Two people only. One pirate and one architect. The pirate vibe-codes as fast as possible to find what's valuable and ship it. The architect turns that messy, discovered surface into a reliable, structured machine. It's a sharp model. It's also missing a seat.
Speed finds value. Structure keeps it alive. But neither guarantees that a real person can open the product, understand it in five seconds, and want to come back. That's the third role. The designer.
The Pirate: Speed as a Strategy
The pirate is the founder energy in the room. They don't wait for a spec — they build, test and break things until something works. With AI, one pirate can now ship what used to take a whole team a quarter.
The pirate:
- ships features before they're fully defined
- tests ideas with real users, not slide decks
- accepts mess, because momentum matters more
What the pirate produces is proof. Proof that something is worth building. But proof isn't a product.
The Architect: Structure as a Strategy
The architect arrives once the pirate has found something worth keeping. They refactor, define boundaries, remove duplication and make the system hold under real traffic. It's slower, more deliberate work — and it's what lets a product survive its own success.
But the architect cleans up the code. Not the experience.
The Gap Between Them
Here's what happens when a team only has those two seats. The pirate ships a flow that works. The architect makes it bulletproof. And the user still gets lost on the second screen.
You see it everywhere:
- onboarding that explains nothing
- five buttons with equal weight
- forms shaped by the database, not by the person filling them in
- error and empty states nobody planned for
- an interface that looks like every other AI-generated product
Nothing is broken. Everything is technically correct. And people still leave.
AI made this gap wider, not smaller. When interfaces can be generated in minutes, every product drifts toward the statistical average. The pirate is moving too fast to notice. The architect is looking at a different layer.
The Designer: Clarity as a Strategy
The designer's job is to turn what the pirate found and the architect stabilised into something people actually understand, trust and enjoy.
The designer:
- decides what to remove, not just what to add
- sets the hierarchy — what the user sees first, second, and never
- designs the empty, error and edge states before users find them
- protects the identity, so the product doesn't look generated
- translates business logic into human language
“The pirate asks: does it work? The architect asks: will it hold? The designer asks: will anyone get it?”
How the Three Seats Work Together
This isn't a relay race where design comes last. It's a loop.
- The pirate explores. The designer sketches direction alongside, so speed doesn't lock in the wrong pattern.
- The architect structures. The designer turns the system into components, so consistency is built in, not patched on.
- The designer refines. The final touch — hierarchy, tone, motion, copy — is what makes the product feel finished.
Like the architect, the designer doesn't have to be full-time from day one. One strong designer can work across several products. But the seat has to exist. Otherwise your users are doing the design work themselves — by guessing.
Why It Matters for Startups
Users don't see your architecture. They don't see how fast you shipped. They see the interface. That's where trust is built or lost — in seconds.
A product that's fast and stable but confusing still loses to a competitor that's fast, stable and obvious. And every competitor now has the same AI tools you do. The question is no longer who can build. It's who can make it feel right.
Three Seats, One Product
Dan's model is a great starting point. The pirate finds the value. The architect makes it last. The designer makes it usable — and that's the part your users actually pay for.
At OOZE, we're usually the third seat. But we'll admit it: we also like pirating. Vibe-coding a rough prototype overnight, testing a direction before it's polished, breaking things to find what's worth keeping — that's half the fun. It also makes us better designers, because we know exactly what the pirate is chasing. We work alongside founders who move like pirates and engineers who think like architects, and we make sure what they build feels like a product people want to use.
Speed gets you there first. Structure keeps you there. Design is why anyone stays.