We built Mistaek to make ourselves unnecessary
Six months in, the problem is better. Not solved. This piece explains why that is structural to the retainer model, and what Mistaek built instead.
Posted on:
Jun 26, 2026
Team:
André Sequeira
Categories:
Studio
You hired someone to solve a design problem. The problem is better. Six months in, it should be solved. Every time you think about ending the engagement, there is a reason it is not quite time yet. The system is almost done. The component library needs one more round. The new hire should probably be onboarded into the workflow first.
This is not a failure of any individual agency or designer. It is what the retainer model produces when you follow its logic all the way.
When staying needed is the business model
A studio that charges by the month measures success in recurring revenue. When recurring revenue is the goal, churn is the enemy. And when churn is the enemy, the incentives point in one direction: toward being needed. The incentive to make you capable points in the opposite direction and has no mechanism to reward it.
This does not require anyone to make a cynical decision. The model creates its own gravity. A studio that keeps you involved in decisions that should eventually be yours to make is a studio working exactly as designed. The relationship continues as long as you need them. They stay needed by staying close to decisions that should already be resolved.
The result is a specific kind of slowness that is hard to name while you are inside it. Design debt does not disappear. It gets serviced. The system never quite becomes yours because it was never built to be.
What changes when the goal is to leave
Every Mistaek sprint has a defined end date. The system gets handed over. We leave. That is not incidental. It is the whole structure.
Sprint-based work sets a higher bar on what gets built. If permanent ownership is the outcome, then the documentation has to explain the reasoning behind each decision, not just the output. The training has to be real, not a thirty-minute walkthrough at the end of a call. The governance framework has to be something a designer who joins six months from now can pick up without calling us.
The trade-off is real: you cannot call Mistaek for every small decision. That is exactly why the system has to be solid enough not to need us.
What this model costs, honestly
Sprint-based work with a clear handoff means Mistaek does not benefit from being the ongoing answer. A design system that produces recurring dependency for us would be a system that failed at its job.
That is a different kind of pressure than a retainer studio carries. Every decision in the build gets tested against one question: will your team still be using this in six months without us in the room?
The Diagnose sprint exists because of that question. Before any full engagement, one week to audit what is there, name what is missing, and confirm whether a sprint is actually the right next step. The report is honest. If the answer is not yet, the report says so. The EUR 1,500 is credited against a full sprint if you proceed.
When a retainer is genuinely the right answer
Not every company is at this point. Some have no design capability and no plan to build it. If ongoing support is the actual need, a retainer from a studio built for that work is the honest fit.
Mistaek will say this in the first call rather than take an engagement the model is not built to serve. The sprint model works when the goal is independence. If the goal is something else, that deserves a direct answer, not a repackaged version of the same thing.
What permanence looks like in practice
The goal is a system your team owns permanently. When we leave, the work compounds. The team builds on what exists rather than calling us to extend it.
A new designer joins six months from now, reads the documentation, and understands why each decision was made. They build on the foundation without needing to reconstruct the reasoning. An enterprise client opens the dashboard and sees something built with intention. The credibility was already in the product before they arrived. That is permanent ownership: a system the team uses because it was built for the people who inherit it.
If you are at Series A and design is starting to slow your team down, a 15-minute call is the right starting point. We will tell you honestly whether a sprint makes sense for where you are. If you already know the problem but not the scope, the Diagnose sprint answers that in one week.
