Back to all blog posts
Jeremy Zick | 15 April 2026You tried offshore once and it burned you. That doesn’t mean the model is broken. It means you tried the wrong version of it.
There’s a moment in almost every conversation I have with architecture firm owners where something shifts. It usually happens right after they tell me about the outsourcing thing they tried before.
It went something like this: they heard about a firm overseas (India, the Philippines, sometimes Vietnam) that could produce Revit documentation for a fraction of what a US hire costs. They were skeptical but desperate. A couple of big projects landed at once, their one reliable production person was maxed out, and they couldn’t afford to hire local. So they gave it a shot.
And it was a disaster.
The drawings came back wrong. Not a little wrong. Fundamentally wrong. Centerline dimensions instead of face-of-stud. Details that looked professional but didn’t match their standards, their jurisdiction, their project type. They spent more time redlining and re-explaining than they would have just doing it themselves. The communication loop had an 11-hour delay baked in. The cultural context around US construction documentation was just missing.
They burned weeks. Maybe lost a client’s confidence. Definitely lost their own confidence in the idea of ever outsourcing again.
And here’s the part that gets me: they walked away thinking the model itself was broken. That outsourcing AEC production just doesn’t work.
That conclusion is wrong. But I understand why they land there.
The offshore model those firms tried was built for cost arbitrage, not integration. You send a batch of files, someone processes them against a checklist, and you get something back that technically resembles architecture. There’s no relationship. No context. No one on the other end who’s spent years immersed in US building codes, US contractor expectations, US design culture. And no path to building the kind of working relationship where someone starts to anticipate what you need before you even ask.
That’s not a people problem. That’s a model problem.
I started WeCollabify because I kept seeing the gap between what the offshore model promised and what architecture firms actually needed. The firms I talk to aren’t looking for cheap bodies to push geometry. They’re looking for someone who can jump into their Revit template on Monday morning, understand why the door tags work the way they do, ask smart questions in real time, and still be available at 3pm when the GC calls with a question about a detail.
That person exists. She’s in Medellín. He’s in Bogotá. They trained at universities that rival anything in Latin America, many have worked inside firms with US project exposure, and they’re in the same time zone as you, or close enough that a Slack message gets a reply before you’ve finished your coffee.
I’ve seen this play out recently in two ways that illustrate exactly what I mean.
A design-build contractor in the mid-Atlantic, solid business, loyal commercial developer clients, strong pipeline, tried to solve a capacity crunch by bringing in an outside drafting firm. The work came back wrong. Dimensions off. Detail language that didn’t match their construction methodology. They had to redo significant portions of the drawing set, which delayed the project and strained the client relationship. Their in-house project manager was drowning, and they were about to call clients to tell them projects couldn’t start for four to six months.
When we talked, he didn’t need convincing that outsourcing could work. He needed convincing it could work right. That there was a version of this where the person on the other end understood US construction, could work within his systems, and would be a long-term partner rather than a transaction. Once he understood that’s what nearshore actually looks like, the conversation turned.
Another situation: a solo architect in the Southeast grinding through hotel projects, doing wall sections he hated at 11pm because there was no one else to do them. He’d heard about offshore services, tried one, been burned, and wrote off the whole category. Then someone handed him our information at a conference. He called skeptical. He left asking how quickly we could start.
What changed? He understood that the failure wasn’t with outsourcing as a concept. It was with outsourcing to people who didn’t have the context, the training, or the incentive to care about his specific workflow. Colombian architects who are integrated into your firm, treated as long-term team members, paid well relative to local market rates. Those are people who want to stay and get better at serving you. That’s a fundamentally different dynamic than sending files to an anonymous queue.
The cost math is also worth being honest about. A mid-level architect in your market costs $75,000 to $95,000 in salary alone, before benefits, payroll taxes, software licenses, and the three months it takes them to get up to speed, if you can find one. Firms across the country are posting jobs and getting crickets, or getting applications from people who need two years of mentorship before they can be trusted with a drawing set.
Nearshore doesn’t mean cheap. It means the cost structure actually makes sense for a 5-15 person firm. You get real talent, real integration, real relationship, at a rate that lets you grow instead of just survive the next deadline.
If you tried offshore before and it failed, I’m not asking you to ignore that experience. I’m asking you to consider that you tried the wrong version of this.
The right version looks like a Colombian architect who joins your Monday standup, knows your Revit standards better than your last local hire did, and is still there two years later because the relationship works for both of you.
If that sounds like what you actually needed the first time around, I’d like to have a real conversation about it, no pitch deck, no pressure. Book a free strategy call here.
WeCollabify places vetted Colombian architects and designers with US AEC firms. Nearshore, not offshore. Working hours, not overnight batches. Real relationships, not vendor transactions.