EntreArchitect Podcast with Mark R. LePage

EA580: Jeremy Zick - "Insourcing": The Benefits of Combining Offshore Resources with In-House Collaboration

·58 min·5 clips

Remote teams cut costs in half and eliminate office space needs, while annual Colombia retreats strengthen bonds.

The conversation starts with firm potential. The focus is small firm architects who need more capacity but do not want to lose the working habits that keep projects consistent. Staffing is the pressure point. The guest keeps returning to the cost of training people from the beginning, especially when they leave before firm knowledge has time to build. That churn burns owner time. When production support keeps resetting, firm leaders have less room for advanced work, sales, growth, or broader impact. His answer is longevity. Temporary outsourcing pools can fill seats, but they can also make architects rebuild quality control and communication habits over and over. Architecture needs technical memory. Remote collaborators have to understand code, waterproofing, graphics, and the way a specific firm shows its ideas. That is more than drafting. It is a feel for standards, preferences, technical depth, and the small choices that shape the work. The model favors long term placements. The guest contrasts that with setups where a permanent quality control layer may exist, while the project staff shifts based on availability. Relationships become part of the capacity plan. Remote talent works better when people are trained into the firm ecosystem and treated as ongoing collaborators, not swappable help. The business lens stays in view. A staffing story turns into a practice management problem about where owners spend their limited attention. Production can block strategy. If the team never gets past onboarding, the firm has a harder time focusing on sales, growth, or higher level work. A separate closing promo shifts into technical delivery, with seismic bracing, base isolation, acoustic floor to floor height, and speech intelligibility.

As heard by us

A practical case for remote architecture support built around continuity, retained knowledge, and trust over time.

Remote architectural support is framed here less as a quick staffing fix than as a continuity problem for firm owners. The episode argues that the constant cycle of onboarding new help keeps teams repeating the basics, when the higher-value work sits further down the road:…

Read the full review in PlayNext →

Why you'd press play

You want remote capacity that compounds instead of making you retrain the beginning every time someone leaves.

Read the full recommendation in PlayNext →

Listen to the show on

Apple Podcasts Spotify

Play clips from this episode More from EntreArchitect Podcast with Mark R. LePage