“We’re in it for the long haul” shows up on nearly every agency’s homepage. It’s also one of the least trustworthy sentences in the industry, because it costs nothing to say and almost nothing to walk back once the invoice clears.
Buyers have caught on. The questions we hear often from organizations sizing us up aren’t about our portfolio. They’re about what happens after: do you feel locked in once an agency builds your platform? Does “governance” quietly become “slow”? Does the senior team that pitched you disappear once a junior team takes over the build? Those are the real questions behind “long-term partner,” and they deserve a real answer instead of another version of the same line.
The tension: partnership language is cheap, and buyers know it
Nobody sells you “we’ll build it and then ghost you.” Every agency’s pitch deck has a partnership slide. The problem isn’t the promise, it’s that the promise is nearly impossible to verify at the point you’re making the decision. You’re being asked to trust a relationship that hasn’t started yet, based on language that every competitor uses too.
So the skepticism is fair. If “long-term partner” is going to mean anything, it has to be demonstrated in how the engagement is actually built, not just how it’s described in a proposal.
Our answer: build for the day the client might leave
Here’s the position we actually hold, and it’s a little counterintuitive: a good long-term partnership is one where the client is never trapped in it.
That means a few things in practice. We don’t outsource, the senior people who scope your project are the ones who build it, so there’s no quiet handoff to a different, less experienced team once the contract is signed. We document systems as living assets instead of tribal knowledge: the Institute to End Mass Incarceration got a full brand guide built directly into WordPress, so their team can maintain and evolve it without calling us for routine updates. On projects like BCIT’s enterprise WordPress framework, the explicit goal wasn’t just to build the platform, it was to build the client’s internal capacity to run it, because they were selected specifically to help their own IT team operate independently long-term.
If a client could run the whole platform in-house the day after we leave, that’s not a failure of the partnership. That’s what a real one looks like.
The trade-off worth naming
This isn’t the fastest or cheapest way to work, and we’re not going to pretend otherwise. Discovery takes longer when part of the goal is figuring out who owns which decisions before the build starts. Documentation takes time that a scrappier build wouldn’t spend. Training an internal team to maintain something is slower than just maintaining it for them indefinitely.
The trade-off is real: more upfront investment, in exchange for a platform and a team that doesn’t quietly become dependent on us to function. For a marketing microsite, that trade-off probably isn’t worth it. For a platform that’s core infrastructure, multi-department, multi-year, high-stakes, it’s the whole point.
What long-term has actually looked like
We’d rather point to what’s already happened than ask anyone to take this on faith.
Steelcase is a 10+ year relationship, one that included us taking over a complex mid-project handoff and architecting a full systems stack collaboratively with their internal team. Harvard has worked with us hand-in-hand for a decade, functioning as an extension of their team rather than a vendor they re-hire project by project. Café Bon Appétit started as a website engagement and evolved into something closer to core infrastructure, a custom API now serving as the secure real-time bridge connecting their systems across web, mobile, email, and digital signage.
None of these started as a ten-year commitment. They started as one project that worked, followed by a second, because the same team was still there to build it.
That said, not every relationship plays out this way, and pretending otherwise would undercut the whole point of this piece. Sometimes the right ending is a handoff: to an in-house team we’ve trained, or to a smaller agency once a platform has matured and stabilized to the point where our cost isn’t justified by what the client actually needs week to week anymore. And “ongoing” isn’t one size: some clients are on a lightweight keep-the-lights-on agreement, security patches, uptime, small fixes, and others are running full sprints of new feature development every quarter. Long-term doesn’t mean every client stays with us forever. It means whichever one you are, the size of the relationship matches what you actually need, not what’s easiest for us to keep selling.
What this means if you’re evaluating any agency, including us
“Long-term partner” is the wrong thing to take at face value from anyone. The better question is a structural one: if this agency disappeared tomorrow, could you still run what they built? If the honest answer is no, that’s not necessarily disqualifying, but it’s worth knowing before you sign, not after.
We’d rather be evaluated on that question directly. If you’re trying to figure out whether that kind of partnership actually fits your project, we’ve also written about where Modern Tribe is the right fit, and where it isn’t.