THE FORK IN THE ROAD
Every software studio that gets traction reaches the same decision point: grow or focus.
Growing means hiring, adding accounts, building a sales function, delegating delivery, and gradually shifting from "people who build things" to "people who manage people who build things." It means higher revenue, more overhead, and a business model that depends on utilization rates and project margins across a team of people with varying skill levels.
Focusing means staying small, taking fewer projects, charging more for each one, and keeping the people who talk to clients as the same people who write the code. It means lower revenue ceiling but higher margin, and a product — the work itself — that stays consistently excellent because the same people are accountable for it from kickoff to launch.
We chose to focus. Here's why.
THE AGENCY PROBLEM
Most software agencies are structured around a fundamental tension they never fully resolve: the people selling the work are not the people doing the work, and the people doing the work are not invested in the outcome the way a founder is.
This creates predictable failure modes. Scope is oversold in pitches because the salesperson's incentive is to close deals, not to scope accurately. Work is under-resourced in delivery because the margin lives in the gap between what's billed and what's spent on labor. The senior engineers who pitched the engagement move on to the next sale while the project is handed to whoever's available.
Clients know this. They've been burned by it. And they're right to be suspicious when a "senior-led engagement" turns out to mean a senior person was in the room for the pitch.
WHAT BOUTIQUE ACTUALLY MEANS
Boutique doesn't mean small because we couldn't grow. It means small by design, because size is the mechanism that delivers quality.
At Barrio 40, the people you talk to in the first conversation are the people who build your product. There's no handoff to a delivery team. There's no junior engineer doing 80% of the work while a senior reviews PRs. The work is done by the people who understand the problem and who have personal stake in it being right.
This matters more than most clients initially expect. The difference between a developer who's executing a spec and a developer who's thinking about whether the spec is right in the first place — that gap shows up in every product we've seen. Specs are always incomplete. Requirements always have gaps. The question is whether the person filling those gaps is doing it thoughtfully or just making the minimal interpretation to stay on scope.
THE ECONOMICS WORK DIFFERENTLY
The boutique model is often misunderstood as a constraint. It's actually a different economic structure.
Agencies compete on capacity and price — they can staff up for large projects and absorb them at scale. Boutiques compete on outcome quality and speed-to-value. The rate is higher per person, but the total cost of a well-scoped project is often lower because there's no overhead, no coordination tax, no rework from miscommunication between the person who understood the problem and the person who wrote the code.
The clients this model attracts are the ones who've been burned by the alternative — who've paid an agency for six months and gotten something that mostly works, then spent another three months fixing what the agency built. They know what bad delivery costs, and they're willing to pay for the kind that ships on time and actually works.
THE CONSTRAINTS ARE FEATURES
Staying small means we say no more than yes. We can't take every project, and we don't try. If a project needs a team of fifteen developers, we're not the right fit and we'll say so.
But constraints force clarity. Because we can only take a few projects at a time, we're careful about which ones we take. We look for problems we can actually solve well, clients who have thought through what they need, and projects where shipping something sharp is the goal rather than shipping something big.
That filter produces a portfolio of work we're proud of and clients who come back. Not because of a retention strategy, but because the last thing we built for them worked.
THE ACTUAL REASON
There's a practical case for the boutique model. But the real reason we chose it is simpler: we like building things. The agency growth path leads away from building and toward managing. We're not interested in that trade.
The studio stays small so that the people running it can keep doing the work. That's the whole answer.