PATTERN NOTE
The brief that arrives is rarely the brief that delivers.
Most agency engagements start with a deliverable in the brief. Most successful engagements end somewhere bigger. The work between those two points is where the value gets made – and it's usually the part developers and builders don't budget for.
Vinay Raja
7 min
A developer comes to an agency with a brief. Rebuild our website. Brand our next community. Run a sales-incentive campaign. The deliverable is named in the first paragraph. The budget is anchored to it. The timeline is built around it. Everyone in the room agrees what is being bought.
Six months later – if the engagement actually worked – the brief that delivered is rarely the one that arrived.
The website rebuild turned out to be a platform-cost conversation that freed up the budget to keep improving the product. The community brand turned out to be a brand-architecture decision about how the masterbrand re-introduces a developer to a corridor it left fifteen years ago. The sales-incentive campaign turned out to be a category repositioning.
This isn't scope creep. The original problem was fully understood – by the developer, in the way the developer was framing it. The agency's job, when it's doing the strategic part of its work properly, is to keep asking what problem the deliverable is actually solving for, until the answer reframes the brief.
Why it matters
If a developer hires the agency that just delivers the brief that arrived, they get the artefact they specified. A new website. A new logo. A new campaign. Everyone hits the deadline. Everyone is happy. What they do not get is the larger problem solved.
A new website on top of a CMS that consumes the entire improvement budget is still a stagnant asset twelve months later. A new community brand that competes for attention with the parent brand is a sub-brand that drowns out the developer's own equity. A new campaign for a developer who is being categorised by the market as something they're not is just a more polished version of the wrong conversation.
The deliverable can be excellent and the engagement can still fail. The deliverable wasn't the problem.
For the developer or builder reading this: the question worth asking before you sign the brief isn't "will the deliverable be good?" It's "what problem will be in front of me twelve months after this ships?" If the answer is the same problem you were trying to solve when you wrote the brief, the brief was too small.
The deliverable can be excellent and the engagement can still fail.
How Tydal sees it
Every Tydal engagement starts with the brief that arrived. The Sense work is what makes it bigger.
Sense, in our practice, is not research-for-its-own-sake. It is the diagnostic work that pressure-tests the brief – what is this actually a brief for? What problem in the business does the deliverable need to solve, and is the named deliverable the right answer to that problem?
When the diagnostic surfaces a bigger problem, we name it and re-contract around the bigger problem rather than quietly delivering the smaller one. Tydal is a Consulting-led practice for this reason. The Studio capability is what ships the answer. The Consulting capability is what makes sure the answer is to the right question.
Where this shows up in our work
Somerford – the brief that arrived was brand a community. The brief that delivered was flip the brand architecture so the masterbrand can re-introduce a developer to a corridor it had left for fifteen years.
The AVJennings masterbrand website – the brief that arrived was replace the seven-year-old Sitecore site. The brief that delivered was free up the budget that the platform's running cost was consuming.
Harvest Square – the brief that arrived was brand a public-private mixed-tenure community. The brief that delivered started six months earlier – at the tender stage.
Waterline Place – the brief that arrived was deliver the next release stages. The brief that delivered was reset the precinct's brand architecture.
Pro9 – the brief that arrived was rebuild our website. The brief that delivered was reposition the brand from "construction supply" to "prop-tech."
What to do about it
If you are a developer or builder briefing an agency, three questions to put on the table before you sign:
What is the business problem this deliverable is buying down? Not the design problem. The business problem.
Twelve months after this ships, what would success look like? If the answer is "the new website is live" the brief is too small.
What's the agency allowed to push back on? The strategic agencies treat the problem statement as the fixed thing and the deliverable as the negotiable one.