Why We'll Never Become a Big Agency (And Why That's the Point)

A few years ago we responded to an RFP from a restaurant group. Interesting brand, real budget, a project that would have been good for the portfolio. In the process of putting together our response, we had an internal conversation about whether we were the right fit. Not the typical “do we want this client” question, but a more honest one: “is this an opportunity to take on more than we can do well, or is this an opportunity to get better as a team?”

We decided it was the latter. We responded with a proposal for a framework we thought was the right technical choice for their needs, even though it wasn’t what they’d asked for in the brief. We explained our thinking clearly. We didn’t get the project. I don’t know if we lost it because of the technical counter-proposal or something else. What I do know is that writing that proposal, taking the time to think through the right answer rather than the easiest answer, made us better at the next one.

That’s the version of agency growth we care about.

What “senior-only” means in practice

The phrase “senior-only team” appears in a lot of agency marketing. Most of the time it means the account manager is senior and the developers are mid-level. Or the director who sells the work is experienced and the execution team is not.

What we mean by it is more literal: the person who scopes your project is also one of the people building it. The developer making architectural decisions on your store has been doing this for 10+ years. There’s no hand-off from the person who understood your brief to a junior team member who’s implementing from a spec document.

This has a real operational consequence: we can’t take as many projects at once as an agency with a pyramid structure could. A large agency can staff one senior person per several junior people and spread their capacity much wider. We can’t do that and maintain the quality level we’re committed to.

That’s not a limitation we’re trying to solve. It’s a constraint we’ve chosen to keep because it keeps us honest about what we can actually deliver.

The compounding value of long relationships

Some of our client relationships have run for many years, long past the project that first brought us together.

Those relationships change the nature of the work in ways that are hard to articulate but immediately obvious in practice. We know the business, the industry, the internal politics, the specific person we’re talking to and how they think. We know which stakeholder has strong opinions about the checkout flow and which one just wants it to ship. We know what’s actually a priority and what sounds like a priority.

That institutional knowledge is worth something. Not just to us. To the client. When a new agency takes over a project, there’s a period of months where they’re making decisions without context. They’re building mental models from documentation and discovery calls rather than from watching the business evolve. Some of that is inevitable. But the shorter that period is, the less the client pays for it.

Long relationships also change the honesty dynamic in useful ways. When you’ve worked with someone for a long time, you can say the uncomfortable thing more easily. “I don’t think that’s the right call” lands differently when it comes from someone who’s been right with you before than when it comes from a vendor who’s been on the account for 90 days.

What clients get from boutique vs. large agency

The large agency pitch usually emphasizes scale: more resources, more specializations under one roof, more capacity. If you need something done simultaneously across 40 markets or you’re running a massive content operation that requires 30 writers, that scale matters.

For most growing ecommerce brands, it doesn’t. What they need is:

Direct access. On boutique projects, you talk to the person doing the work. Not a project manager relaying messages to a development team you’ve never met.

Faster decisions. When the person you’re talking to has the authority to make a call and the context to make it correctly, decisions happen in minutes rather than requiring a ticket, a sprint planning meeting, and a change order.

Honest recommendations. Large agencies have a financial incentive to recommend larger scopes. The business development person is compensated on deal size. We’re compensated on doing good work that clients want to continue. Those incentives are not identical, and they produce different recommendations.

Someone who will tell you no. When a client is about to make a decision we think is wrong (the wrong platform, the wrong prioritization, a change that will hurt their SEO), we say so. Directly, with our reasoning. A vendor who needs to protect a large account has reasons not to push back on the client. We don’t have that problem.

The honest trade-off

Boutique has a real limitation: we can’t take every project, and we can’t grow every client relationship simultaneously at full intensity.

There are projects that are wrong for us: too large, too resource-intensive, requiring specializations we don’t have. There are clients who need more than we can give and would be better served by a larger partner. We turn those opportunities away. That’s not a comfortable thing to do with a real project in front of you, but it’s the decision that keeps the quality of the work we do take at the level it needs to be.

The filter is: can we do this work well? Not: is there a way to take this project? If the answer to the first question is yes, we’re interested. If it’s not, we’ll tell you that and try to point you in the right direction.

That’s a harder business to operate than one that says yes to everything and figures out the staffing later. It’s also a better one to be a client of.

If you want to understand what working with us actually looks like, the case studies are the best place to start. They’re real projects with real clients, not sanitized portfolio pieces. Or just get in touch and we’ll have an honest conversation about whether we’re the right fit for what you’re trying to do.

Last Updated: July 2026