When You Can't Reach the Company That Built Your Site: Steps to Keep It Running

Years after commissioning a website or business system, some companies try to contact the development company again — only to find the phone number no longer works, emails go unanswered, or the company's own website no longer exists. This isn't a rare problem specific to any one vendor; it's a structural risk that can arise, with some probability, whenever a small or midsize business outsources a site or system to an external company. This article looks at why this situation can arise, what to check first when you encounter it, how the right response depends on where ownership of key assets actually sits, and how to hand things over to a new maintenance partner.

There are several patterns behind losing contact with a vendor. One is the development company going out of business — not uncommon for small studios or freelancers whose operations become unsustainable. Another is the departure or independence of the individual who handled the project; even if the company itself still exists, the person you actually worked with may have left without a proper handover, making them hard to reach. A third pattern is closer to a gradual fade-out: the company still exists, but with no formal support arrangement after the contract ends, responses to inquiries slow down over time. In all of these cases, the fault doesn't lie with the client — it's useful to understand this as a risk inherent to the structure of outsourcing itself.

- Business closure: the development company has ceased operations and its contact points no longer exist
- Staff departure or independence: the individual you worked with is gone, and there was no internal handover
- Gradual fade-out: the company still exists, but has no process for handling post-contract inquiries
- Acquisition or merger: the company was absorbed into another, and the contact point for former clients has changed

When you find yourself unable to reach the vendor, the first step is to identify which assets your business actually needs and who currently controls them. A site or system is made up of several components, and each one may be managed by a different party. Start by reviewing whatever contracts, quotes, invoices, and email exchanges you have on hand, and gather as much information as you can on the following.

- Domain name: who it is registered to — your company or the development company
- Server/hosting contract: who the contracting party is, and whether payments come directly from your company
- Source code: whether your company holds it as a deliverable, or only the development company has a copy
- CMS/admin login credentials: whether your company currently has working access
- Contracts and specifications: whether documents exist defining the scope of the work and deliverables
- DNS access: whether your company has the authority to change where the domain points

The options available to you differ significantly depending on where the assets you've identified actually sit. The table below outlines typical patterns and a general direction for each.

Once you've confirmed where your assets stand, the next step is to consult a new maintenance provider or development company and begin the handover. A typical process looks like this.

- 1. Inventory the current state: share whatever domain, server, source code, and login information you've confirmed with the new provider
- 2. Transfer ownership: process the changes needed to move the domain and server contracts to your company or the new provider
- 3. Assess the current site/system: have the new provider review the existing code and configuration to determine whether it can be maintained as-is
- 4. Address the most urgent items first: prioritize areas that went unattended during the gap, such as security updates and backup coverage
- 5. Agree on an ongoing maintenance arrangement: settle update frequency, cost, and communication with the new provider

Who holds the copyright or usage rights to a site's source code and design — your company or the development company — depends on the terms of the original contract. Ideally, a contract would clearly state who owns the copyright and the scope of any usage license, but in cases handled through verbal agreements or a simple purchase order, these rights can remain ambiguous. Questions like how far to respect the rights of a vendor you can no longer reach, or whether a new company may take over and modify the existing code, depend heavily on the specific contract and circumstances — when in doubt, it's advisable to consult a lawyer or other qualified professional. Rather than dealing with this only after the fact, preparing in advance can limit the impact considerably. In particular, keeping domain and server contracts registered in your company's name, and receiving and storing the source code as a formal deliverable, are basic but effective precautions. Systems and servers can also have an end-of-life (EOL) date, and reaching EOL while the maintenance situation is unclear only makes things harder to resolve — see A Guide to Preparing for System End-of-Life for more on that. For the general process of switching development vendors, see A Guide to Switching Development Vendors.

- Is the domain registered under your company's name?
- Do you know who the contracting party is for your server/hosting?
- Have you received and stored the full source code as a deliverable?
- Do you still have working login access to the CMS and server admin panels?
- Have you kept your contracts, specifications, and correspondence on file?
- Do you periodically check in, in case the development company's contact details have changed?

Losing contact with the company that built your site or system is less a problem with any particular vendor than a risk built into the nature of outsourcing itself, and it can happen to any business. When it does, the first step is to identify where key assets — the domain, server, source code, and login credentials — actually sit, and to shape your response around who holds that ownership. It's also worth reviewing The Complete Guide to System and Website Maintenance for a broader picture of how to prepare in advance.