Your Last Agency Built You a Surface. We Build You a System.
April 16, 2026
You've Hired a Great Agency Before. Here's What Still Went Wrong.
·6 min read
Brand Meets Code — Point of View · Agency Selection · 7 min read
You knew what to look for. You asked the right questions. The portfolio was strong, the team seemed sharp, and the work came back solid. And yet something still didn't land the way you expected. This is about the gaps that survive even a careful selection process — and what to look for the next time.
The selection process that still fails
By now you know how this works. You shortlist three or four agencies. You review portfolios. You run discovery calls. You ask about process, timeline, and team structure. You check references. You make a considered decision.
And you still end up, six months after launch, patching things that should have been right from the start. Attribution that doesn't hold up. Infrastructure that wasn't built for the tools you need to add. A site that looks exactly like what you asked for and doesn't quite do what you needed.
This isn't a failure of diligence. It's a failure of what the standard selection process is actually designed to surface — which is execution quality, not strategic depth. You found an agency that could build. What you needed was one that could think.
"The standard selection process finds agencies that can execute. It rarely finds ones that know what to build before you tell them."
The gaps that survive a good vetting process
1 — The pitch team and the build team are not the same people
You already know this in theory. What's easy to miss in practice is how completely the dynamic shifts once the contract is signed. The senior strategist who earned your trust in the pitch hands the account to a team you've never met. Their judgment shaped the proposal. It rarely shapes the daily build decisions.
The tell isn't whether they acknowledge this — most will. It's whether the people doing the work can speak to your business with the same fluency as the people who sold it. If you haven't had a substantive conversation with the actual build team before signing, you don't yet know who you hired.
The signal to look for: Ask to meet the build team before the contract is signed. The way an agency responds to that request tells you everything about how they run their projects.
2 — They executed the brief. Nobody questioned it.
You wrote a clear brief. They delivered against it cleanly. And the result was technically correct and strategically incomplete — because the brief described what you could see from inside the business, and nobody pushed on what was underneath it.
An agency that challenges your brief in the first conversation isn't being difficult. They're doing the only thing that separates strategic partners from skilled vendors. The questions that make you pause — about your buyers, your positioning, your conversion logic — are the ones that protect you from building something that looks right but lands wrong.
The signal to look for: Did they ask about your buyers before they asked about your brand guidelines? The sequence of their questions tells you what they're actually optimizing for.
3 — The foundation was never part of the conversation
Security. Data layer. Privacy architecture. API integrations. These are the decisions that determine whether your site works as a business system — and they almost never come up in a standard agency pitch because most agencies don't have strong opinions about them.
You found out they didn't when you tried to add a tool six months later and realized the site wasn't built to support it. Or when your analytics lead flagged that the event tracking was inconsistent. Or when legal raised a question about consent enforcement that nobody had a clean answer to.
These aren't edge cases. They're predictable consequences of a build process that treats the foundation as someone else's problem.
The signal to look for: Bring up consent signal propagation or data layer architecture early in the conversation. An agency that leans in with specific opinions has been in the engine room. One that pivots to design has not.
4 — The portfolio showed craft. It didn't show accountability.
The case studies were well-produced. The design was strong. What they didn't tell you — because almost no agency leads with this — is what actually changed for the client after launch. Whether the pipeline moved. Whether the conversion rate shifted. Whether the enterprise sales cycle shortened.
Portfolios are curated to demonstrate taste. Results require accountability. The agencies that can speak fluently about outcomes — not just deliverables — are the ones who stayed close enough to their work to know what it did. That proximity is rare and worth looking for specifically.
The signal to look for: Ask them to pick one project and tell you what changed for that client in the six months after launch. Not what they built — what changed. The specificity of the answer is the answer.
5 — The relationship ended at launch
The handoff happened. The project closed. And three months later you had questions nobody could answer cleanly, decisions to make about a codebase you didn't fully understand, and the growing sense that you were on your own with something that wasn't quite finished.
A site is not done at launch. It is done when it is performing the way it was designed to perform — and the period between launch and that moment requires the same quality of judgment as the build itself. Agencies that disappear after delivery aren't hiding something. They just built their business around shipping, not around outcomes. The distinction matters when you're the one left holding the site.
The signal to look for: Ask what the relationship looks like ninety days after launch. A vague answer about "support packages" is not the same as a team that stays accountable to results.
The thing that doesn't make it into any vetting framework
How did they behave before you were a client? Did they show up to calls prepared or did they ask you to re-explain things you'd already sent? Did they remember what mattered to you from the last conversation? Did they push back on something or agree with everything? The pre-contract behavior of an agency is the most accurate preview of their mid-project behavior — and mid-project is when it actually counts.
What to look for this time
None of this requires a different selection process. It requires sharper attention to what the process is already revealing. The agency that asks harder questions before the brief is finalized. The build team that can speak to your business on day one. The team small enough that the people who pitch are the people who build. The foundation conversation that happens before the first wireframe.
You already know how to run this process. What changes is knowing which signals to weight — and which answers, however well-delivered, are telling you to keep looking.
"You're not looking for an agency that can execute your vision. You're looking for one that can see further into it than you can."
If you're in this process right now, we're happy to be one of the conversations. Bring your brief, bring your hard questions, and we'll give you a straight read on whether we're the right fit. If we're not, we'll tell you that too. Start the conversation.
All articles
Theme