Embedded, not outsourced

There’s a moment in most outsourced projects that nobody puts in the contract. It happens a few weeks in, when the agency asks a question your intern could answer. Something about how your approval process works, or who actually owns the product roadmap, or why the last redesign got shelved. And you realize: they don’t know you. They know the brief. Those are different things.

We’ve watched this play out from both sides. The deliver-and-disappear model is the industry default for a reason. It’s tidy. Scope goes in, deliverables come out, everyone shakes hands, and the agency moves on to the next logo for the portfolio page. The work might even be good. But it was made about you, not with you, and that difference is visible in the final product the way a stock photo is visible on a landing page. Something’s off. You can’t always name it, but your customers can feel it.

So we do it the slower way.

What embedding actually looks like

It’s not a metaphor. When we start with a client, we spend real time learning how they operate before we make much of anything. We sit in on the meetings where decisions actually get made, which are rarely the meetings on the calendar labeled “decision.” Which Slack channel is the real one, who has to be convinced, who has veto power they never use, who quietly runs the whole place from a role three boxes down the org chart. We learn all of it.

We learn the workflows, too. Not the documented ones. The actual ones. How content really gets approved. What happens when legal gets involved. Which tools the team loves and which ones they tolerate because someone bought a three-year license. If we’re building you something your team has to live inside every day, we’d better know what their day looks like.

And we learn the goals behind the goals. Every company has the stated objective and then the real one underneath it. “Increase conversions” often means “prove to the board that this channel works.” Those call for different decisions. You only find the second one by being around long enough to hear it.

Why it matters for the work

Here’s the practical payoff: work that’s embedded doesn’t need a translation layer. When an outside vendor hands you a deliverable, someone on your team has to adapt it, explain it, and defend it internally. That person becomes the unofficial project manager of the agency relationship, which is a job nobody applied for. When the work is made from inside your context, it arrives already speaking your language. Your team doesn’t have to convert it into something usable. It just fits.

It also means we catch problems earlier. An outsourced team finds out about the reorg, the budget shift, or the strategy pivot when the deliverable bounces. We find out in the standup, because we’re in the standup. Course corrections that cost a conversation instead of a change order.

And it changes how feedback works, which might be the most underrated part. When a vendor presents work, feedback arrives formal and filtered, three rounds of consolidated comments in a shared doc, everyone performing politeness. When you’re embedded, feedback sounds like a colleague leaning over and saying “that’s not how our customers talk.” Ten seconds, no ceremony, and the work gets better on the spot.

Filtered feedback protects feelings. Unfiltered feedback protects the project.

There’s a line we use often enough that it’s basically on our letterhead: we embed with your people, learn how you operate, and deliver like we’ve been there from day one. The point isn’t proximity for its own sake. The point is that good decisions require context, and context doesn’t transfer through a creative brief. It transfers through time spent.

The part where we admit the catch

This model is worse for us in some obvious ways. It’s slower to start. It doesn’t scale like a production line. We can’t take on forty clients at once, and we’ve stopped pretending we’d want to. Embedding requires us to actually care about your business, which is not a renewable resource we can fake indefinitely. It only works when we do fewer things, more deeply.

We’re fine with that trade. Colony was built by independent people who chose to work together because proximity made the work better. Extending that logic to clients wasn’t a strategy decision. It was just consistent.

The test we hold ourselves to is simple. Six months after launch, when someone new joins your team and looks at what we built, they shouldn’t ask which agency did it. They should assume it came from inside the building.

Because in every way that matters, it did.