WATCH · Choosing a Tech Partner_
What Leaves With the Agency When the Project Ends
Saleem Beg · Founder, Teque
● 1:42 · Posted 3 months ago
KEY TAKEAWAYS_
- Agencies are paid for delivery, not continuity — their model ends at launch
- Institutional knowledge walks out with the team unless you explicitly extract it
- Hold a knowledge transfer conversation before closing — covering decisions made, known risks, and the next three likely decisions
TRANSCRIPT_
There is a specific moment that happens in almost every technology project I've seen. The work finishes, everyone leaves, and you standing there with something you own but don't fully understand. It doesn't feel dramatic.
The handover document gets sent, the final invoice gets paid, and the people who understood the decisions, why it was built this way, what tradeoffs were made, what needs to happen next, they all gone, moved on to the next client.
So, you are now left with a system, a login, and maybe a manual if you're lucky, but the institutional knowledge that should have been transferred, it left with them. Why does this happen? Well, because agencies and consultancies are paid for delivery, not for continuity. The commercial model ends at launch. There is no incentive and indeed no budget line for the kind of ongoing
strategic oversight that actually protects what was just built. So, here's what you can do about that. Before the project closes, hold a formal knowledge transfer session. Not a handover document, but an actual conversation covering why decisions were made, what the known risks are, and what the next three decisions will probably be, and get it recorded because the knowledge
that leaves when people leave is institutional capital. So, treat it like one.
“The people who understood the decisions, why it was built this way, what tradeoffs were made, they're all gone, moved on to the next client.”
Prefer to read? This take is also a written article.
Read the article →
