Opinion
Field Notes
The handoff is the product
A system you can’t run without us isn’t an asset — it’s a dependency. We’d rather build something you own outright.
TAGS
OWNERSHIP
HANDOFF
DOCUMENTATION

Marco Vieira
FOUNDER
10 Apr 2026
4 minutes
ON THIS PAGE
01 Lock-in is a business model, not a feature
02 What handoff actually includes
03 Build it so it can outlive us
There’s a version of agency work where the deliverable is a black box, and the real product is your continued dependence on the people who built it. We think that’s a bad deal, and we don’t build that way.
Lock-in is a business model, not a feature
When a system is undocumented and only its builders understand it, every future change has to go through them. That’s great for the builder’s retainer and terrible for you. You end up renting access to your own software.
We’d rather lose the lock-in and keep the trust. A client who fully owns what we built is a client who comes back because they want to, not because they’re stuck.
What handoff actually includes
A real handoff isn’t a zip file and good luck. It’s documentation written for the people who’ll maintain it, runbooks for the things that go wrong, and training so your team can run, extend, and trust the system after we leave. We’re not done when it works. We’re done when you can keep it working.
Build it so it can outlive us
The mark of a good engagement is that, six months later, the client has changed things we never touched — and it still holds together. That only happens if the system was built to be understood and handed over from day one.
We build it. You own it. That’s the whole point.
archivio { 1 }
OTHER POSTS
Read related content
Read our posts on strategy, engineering, process, opinion and field notes.
RELATED INSIGHTS
All
Strategy
Engineering
Process
Opinion
Field notes

Context windows aren’t memory
Stuffing everything into the prompt feels like memory, but it isn’t. Real systems decide what to retrieve, when, and what to forget — here’s how we think about it.
Inês Carvalho
6 minutes
Read post

Most "AI problems" aren’t AI problems
Before you build an agent, it’s worth asking whether the bottleneck is the model — or the broken process around it. Usually it’s the process.
Sofia Almada
5 minutes
Read post

What "production-grade" actually means for an AI agent
A demo proves an agent can work once. Production means it works on the thousandth strange input, at 3am, when nobody’s watching. Here’s the gap between the two.
Inês Carvalho
7 minutes
Read post

Why we ship in weeks, not quarters
Long timelines hide risk. Short ones surface it. Here’s how a six-week engagement stays honest from kickoff to launch.
Marco Vieira
5 minutes
Read post

Agents vs. wrappers: a field guide
“We added AI” can mean a thin wrapper around a chat box, or a system that does real work end to end. The difference matters more than the label.
Inês Carvalho
6 minutes
Read post
