The most valuable thing a delivery partner does is tell you the brief is wrong. Everything else on the statement of work (the code, the tickets, the burndown) is the cheap half of the job now, and buying a partner as though execution were the scarce thing is how a company ends up with exactly the system it specified and none of the outcome it wanted.
Most lists of outsourcing partner red flags cover the familiar ones: a fixed quote before anyone asked about scope, a team nobody can name, vague IP terms, promises that sound too fast. Those are worth checking. The red flag those lists leave out is the one that feels best in the room: a supplier who agrees with everything you wrote.
Two shifts collided recently. Deloitte's 2024 Global Outsourcing Survey reports outcome-based relationships gaining ground, with talent and agility now sitting alongside cost reduction as reasons to outsource. At the same time, AI-assisted development pushed down the cost of building the specified thing. So the contracts moved to outcomes while the evaluation stayed where it was: buyers still shortlist on rate card, headcount and whether a supplier will follow instructions.
RxVantage hired us to move a pharmaceutical SaaS platform off its monolith and onto an event-driven architecture. We did that, and the published results were a "50% reduction in server costs", "30% faster deployment times" and "Zero downtime during migration". What was not in the brief was the org chart. Features were slow partly because the team structure created bottlenecks, with everyone waiting on everyone else, so we reorganized delivery into small autonomous pods that each owned a slice of the platform end to end.
A brief is a diagnosis, not a specification. It records what the buyer believed was wrong on the day they wrote it, usually under pressure, usually with the symptom mistaken for the cause. Scope discipline protects you from paying for work you never asked for. It does nothing at all to protect you from paying, precisely and on time, for the wrong work.
Telling a client the brief is wrong is harder than the migration was. Saying their team structure is the constraint lands on a person who is sitting in the room, it reads as blame, and it is the single most likely moment for a supplier to lose an account. We said it because the alternative was shipping a faster platform into the same gridlock and calling the engagement a success.
Outcome-based contracts make this sharper, not safer. If a buyer purchases a result but hands over a fixed method, they have transferred the risk of their own diagnosis to a supplier who was never allowed to question it. That arrangement does not fail loudly. It fails as a delivered scope sitting next to a flat metric, in much the same way that an AI agent nobody scoped to a number fails.
For anyone running an evaluation right now, the question that separates suppliers is not whether they can do the work. Assume they can. Ask what they would change about the brief before they quote, and then ask which piece of their portfolio started as a different brief than the one that shipped. Every firm has an answer to the first. Only a team that has actually held the line has a specific story for the second, with a named constraint and a decision that cost them something. That story is also the difference between a partner and a supplier, and it is worth more than any rate-card comparison.
A team that agrees with everything during the sales process will agree with everything during delivery. You will get what you asked for, on time, and it will not be the same as what you needed.
Agreement is the cheapest thing a supplier can produce. Be suspicious of how much of it you are getting.