ExDev Week said trust is everything. Agreed. Now look at where trust comes from.
GamesIndustry.biz just spent a week asking external development leaders about their industry. I'm glad to see the coverage: ExDev is probably the most underreported topic in games, considering it makes up a huge share of games production.
One topic kept coming up across a dozen studio interviews: trust. Joe Harford of Airship put it in seven words: "External development lives or dies on trust". He's right and I've watched partnerships with weak trust rot from the inside.
But look closely at how those same leaders describe trust. Harford’s own definition: “[a trusted] partner you can hand a messy, time sensitive brief to and know they’ll ask the right questions, protect your art direction and deliver on the date they promised.” Rav Tharanee of Third Kind Games is even more explicit: “Trust is earned through delivery, not promised upfront.” And Jean-Marc Morel explaining why Konami and Capcom trust NeoBards: “They know when they give us a project that it will be on time…and the quality will be there.”
Every one of those is a description of value, delivered repeatedly. Asked about trust, the industry's own leaders keep reaching for value language to explain where it comes from. So let me name the thing they're all pointing at.
Value sits underneath trust. Trust is what value produces, rep after rep.
Value, plainly
Value is what you receive for every dollar you spend. You can measure it objectively (did they do the thing?) or subjectively (do I like what they gave me?). It can also be measured personally (do I like working with them?).
Value is measured in many forms and differently by different organizations. But everyone measures it constantly.
Did the work arrive, to spec, on the expected date? Did it clear your quality bar and keep up as that bar moved? Does the team communicate? Are you regularly understood, does bad news travel, what does working together actually feel like? Do they ask good questions that improve your specs? Are problems caught while they’re still cheap, do they push back effectively when they should?
Organizations weigh these differently and they should. A porting engagement lives on certification passes and dates held. An art partnership lives on taste alignment. Co-development lives on integration and communication. Dollars are measured equally, but value is not.
There are many ways for a team to be worth the money: raw capability, reliability, quality of collaboration, judgment that compounds. Price tells you none of it.
Why value comes first
Trust and value differ in one structural way. Trust accumulates. It's a record, built interaction by interaction, and it can be grown, damaged and repaired. Value is present tense. It shows up in this milestone or it doesn't. You can fix an information flow, reset a relationship, earn back confidence. No conversation adds capability to a team that never had it.
I've sat inside a partnership where trust was missing. The client withheld information and the studio could feel it. Deprived of context, they stopped acting like creative collaborators and started acting like taskmasters. We brokered the hard conversation with the client about how the lack of transparency was creating the exact behavior they were frustrated by. The partnership recovered, because the work that followed it was worth trusting.
I've watched the opposite as well. A partnership born from a glowing referral, trust pre-installed, with teams moving fast from day one. Unfortunately the value never materialized and every early advantage evaporated within months. The trust was real. There was just nothing underneath it.
A low-trust, high-value partnership can be repaired. A high-trust, low-value partnership is already over.
The conversation everyone avoids
The ubiquitous talking points in exdev focus on trust because value sits next to a difficult subject: lower-cost labor regions competing directly with higher salaries. Games are purely digital and can be built from anywhere, so global talent and remote pipelines have turned rates into a worldwide market, putting pressure on incumbents in higher cost of living regions. That fight makes the whole topic understandably radioactive.
But the avoidance comes at a price. Inexperienced buyers overweight price in their decision making and when the industry talks about trust instead of value, it skips the education that would actually protect them. New buyers are left to learn through their own expensive mistakes, and studios doing excellent work at lower rates get lumped in with the ones that underdeliver, because nobody has drawn the line between price and value out loud.
But look at the topic objectively and the fight loses most of its toxicity. Cost is a number. Value is not.
A cheap bid that delivers below the quality bar destroys its own price advantage. The gaps surface as change orders, rework and blown delivery dates. That outcome is structural, never moral: a team priced below its capability was always going to close the gap somewhere.
At the same time, premium rates carry their own obligation. Charge more, deliver more. Deeper experience, fewer surprises and judgment that catches problems while they're still cheap to fix. A high rate that delivers all of that is worth it. But a high rate that delivers a logo collage and a process deck is the expensive version of the cheap bid.
None of that makes a rate right or wrong. It makes it a judgment call and the judgment is about capability, not price.
The policy that retires itself
More than once, a studio has opened a conversation with me on a version of the same policy: we exclusively work with people we know and trust, or who come recommended by people we trust. They mean it. In a market where you can't see who has actually done the work, that policy is sound risk management.
Then they meet a team that has shipped their exact problem many times over and the policy quietly retires. They get evidence and evidence instills trust that the team can do the work.
How to measure value
So how do you actually measure value?
You apply the same test you'd apply to any hire. Has this team done The Thing before? Not something adjacent, not something that suggests they could figure it out. The Thing.
Have they ported a game like yours to that platform, built that system, shipped a title at your quality bar and your commercial stakes? Proven and capable are two different claims. The team that has done it before arrives with everything worth paying for: judgment, pattern recognition, the shortcuts that only come from having been wrong once already. The team that hasn't will learn on your schedule and budget.
Trust follows
Trust is worth everything the industry says it is. It just isn't the starting point. It's what accumulates when a team is worth trusting keeps proving it, project after project, until the oversight relaxes and the relationship gets easier and cheaper to run.
So when you're choosing a partner, don't start by asking who you trust. Start by asking what you value and find who has actually delivered it. The trust builds itself from there.
We provide studio sourcing for game teams using world class market intelligence that surfaces who has actually done your Thing before. We'll be at Gamescom in August. If a partnership decision is on your horizon, let’s chat.
