The Org Chart Doesn't Look Like It Used To
For most of the last decade, bringing on an external team meant something had gone sideways. You were short-staffed, or a deadline was closing in, or someone had just walked. The call came in as a patch, not a plan.
That's not really true anymore.
Talk to studio leaders right now and you'll hear some version of the same story. Thousands of roles gone across studios of every size. The people still in the building are doing more, covering wider ground, against a roadmap that didn't get any shorter just because the team did. I want to be careful here — this isn't a piece about layoffs being some hidden opportunity. They're not. Behind every one of those numbers is a person, a career, a team that used to exist, and we don't treat that lightly.
But something has changed underneath all of it, and it's worth naming.
External partnerships used to be a stopgap. Now, for a lot of studios, they're just part of how the org chart works.
The flexibility argument was always there.
A lean internal team can't flex up for a vertical slice, or a platform port, or a feature crunch, without pulling people off everything else that still needs to ship. An outside team can scale in for exactly the window you need, then scale back out, without the six-month hiring process on one end or the hard conversation on the other. That math hasn't changed in years.
What's changed is who's doing the math.
It used to be a producer's problem to solve quietly. Now it's a leadership conversation happening in the open, because the alternative — rebuilding a team you just spent a year trimming — isn't really on the table anymore.
Here's the part I think gets missed.
The value of a good partner was never really about being cheaper than a hire, or more flexible on paper. It's that a good partner shows up with production infrastructure and communication discipline already built — the stuff a stretched internal team doesn't have the bandwidth to invent for itself right now. Workflows that already exist instead of getting assembled under deadline pressure. Check-ins and documentation that hold a team together instead of quietly slipping when everyone left is already stretched thin. Pattern-recognition from problems somebody else already solved on a different project, in a different genre, six months ago.
That's the line between a vendor and a partner. A vendor takes the spec and hands back the deliverable. A partner understands why the work matters, catches the expensive problem before it's expensive, and is still around for the next milestone — not just this one.
Why this matters more now, not less.
When a team shrinks, institutional knowledge gets thin fast. The senior designer who used to mentor three juniors on UI patterns might not be there anymore. The person who owned the design system might be gone entirely. That's exactly the gap a real partnership is built to fill — not replacing the people who are left, but giving them the connective tissue to keep moving without reinventing every wheel under pressure.
The studios handling this well aren't the ones treating outside help as a stopgap. They're the ones building actual relationships with partners who can flex project to project, who already know how they work, and who don't need the pipeline re-explained every single time.
If you're evaluating a partner right now, a few things matter more than they used to.
Can they show up day one, in your tools and your standups, without a slow ramp — because nobody has slack for that anymore. Will they tell you when something isn't working, instead of just executing the brief as written. Can they scale down as cleanly as they scaled up, with no severance exposure and no awkward ending. And can they point to something they actually owned end to end, not just staffed.
For a long time, external development was something studios reached for after the important decisions had already been made. Increasingly, it's becoming part of how those decisions get made in the first place.
We think that's one of the more useful shifts our industry has made in a hard couple of years.
Not because it's easier for us.
Because it's one less thing a lean team has to carry alone.
