If You Change Agencies Tomorrow, What Happens to Your Website?

It’s the question almost nobody asks before signing with an agency, and the one that can end up costing the most.

If this relationship ends tomorrow, what do you actually keep?

Hostile question? It’s the same one you’d ask a cloud provider, an accountant, or a bank. But when it comes to a website or a custom development project, almost nobody asks it. We’re usually too eager to get started.

Then, three years later, the answer shows up on its own: you’re left with a domain you don’t control, hosting under someone else’s name, a purchased theme nobody knows how to update, and a developer who no longer replies.

The problem has a name: vendor lock-in

In technology, this is known as vendor lock-in: when you become so dependent on one provider that making any change becomes difficult, expensive, or simply impossible.

Not because there’s a contract forcing you to stay, but because your domain, hosting, code, licenses, or technical knowledge ended up concentrated in the hands of one person or provider.

What a hostage situation looks like when it doesn’t look like one

It’s almost never malicious. Most of the time, it’s just neglect.

The domain was registered with the agency’s credit card because everyone was in a hurry. The hosting ended up in a shared account with eight other clients. Nobody documented anything because documentation wasn’t included in the quote. The payment plugin was purchased using the agency’s license. And the only person who understands how the billing integration works is the same developer who left the agency last year.

None of those decisions were made to trap you.

Together, they trap you anyway.

The day you want to leave, your option isn’t to move.

It’s to start over.

And that’s where the real cost is: you don’t pay to leave. You pay to rebuild.

What it really costs

Let’s do the math.

A redesign you didn’t need, because migration was impossible. Three to six months of project work. Your internal team back in discovery meetings again. The SEO authority you spent years building, reset. And the exact same risk still sitting there, because nobody asked different questions this time around.

That’s not a project.

That’s a subscription to starting from scratch.

5 Questions to Ask Your Web Agency

Ask these before signing, not after. And if the answers make the agency uncomfortable, you’ve already learned something.

• Whose name is the domain registered under?
  Yours. Registered using your corporate email address, not an employee’s and not the agency’s. If the agency manages it, they should have delegated access, not ownership.
• Where does the code live?
  In a repository your company can access, not on someone’s hard drive. If they tell you the code is “on the server,” there is no repository, and there is no history of anything.
• Who owns the licenses?
  Themes, plugins, third-party services. If they’re under the agency’s license, the day you leave, they stop receiving updates. An outdated plugin is a vulnerability with a date on it, not a cost saving.
• Is the architecture documented?
  How the website connects to your ERP, accounting system, payment gateway, and other services. Written down. A third party should be able to read it and understand it without having to call anyone.
• How long does it take to get a response when something goes down?
  Ask for a number, not an intention. In our maintenance plans, the average resolution time is 15 minutes. That number exists because we measure it, not because it sounds good. Ask your provider for theirs, and ask them how they calculate it.

Why We’re Writing This

Because this benefits us less than you might think.

A client who asks these five questions is harder to retain through inertia.

If they want to leave tomorrow, they leave, and they take everything with them: domain, code, licenses, documentation.

No negotiation. No awkward phone call.

That’s exactly what we want.

We’d rather you stay because the work is valuable, not because leaving is expensive.

There’s a simple test for whether a technical relationship is healthy:

The day the provider leaves, everything should keep working.

If that day can’t happen, you already know what kind of relationship you have.

We don’t build things to be thrown away.