Getting started

Your Vendor Will Not Take Your Calls

By Zero Exposure | October 24, 2026

Illustration of a network of connected nodes beside a code window in brand blue

Many companies buy business software from a small vendor: a custom application, a niche industry product or something a local firm adapted for them years ago. For a long time the arrangement works. Then the calls go unreturned. The support line rings out. The vendor's email bounces, or it answers with a long delay and no solutions.

This post explains what a quiet vendor usually means, what you can reasonably ask for and how to keep the business running while you sort it out. It is general information, not legal advice.

Why vendors go quiet

There are a few common reasons, and most are mundane.

  • The vendor is a one-person company and that person has moved on, retired or is overwhelmed.
  • The product reached the end of its commercial life. The vendor has stopped selling it and has no interest in supporting it.
  • The company was acquired, and the new owner has no one assigned to your version.
  • The technology moved on. The vendor now works in newer tools and does not want to touch the old stack.
  • A dispute over invoices or a renewal made the relationship awkward.

None of these means the software is about to stop. It does mean that you cannot rely on them for the next problem.

What you may be entitled to ask for

Your contract matters. Many agreements include some rights that are worth knowing about. Check yours, or ask an attorney to, for the following:

  • Source code. Some contracts transfer it, some license only the running software, and some place it in escrow. If you own it, you can ask for it.
  • Documentation. Even without source code, a vendor may be able to give you deployment notes, a list of accounts or a database schema.
  • Data. Your data is yours. You can almost always ask for an export.
  • Hosting details. If the vendor hosts it, ask who holds the hosting account and what the notice period is for any change.

A short, written request is better than a phone call. It gives you a record and a date.

What to do while you wait

Do these in parallel with your request. They do not depend on the vendor.

  1. Take an export of your data now, if the software allows it, and keep it somewhere you control.
  2. Find out where the software runs and who pays for that. If a hosting or domain bill lapses, the software stops, regardless of the vendor's availability.
  3. Write down what the software does, who uses it and which processes depend on it.
  4. Avoid changes to the running system until someone has read the code.

When the source code is not available

Sometimes the answer is that there is no code to be had: the vendor holds it and will not release it, or it was lost. Your options narrow, but you still have some:

  • Maintain the running system as it is, looking after the hosting, the backups and the parts that can be touched without the source.
  • Capture what the software does, using its screens, its reports and its data, so that a replacement can be specified.
  • Plan a staged replacement on a timeline you choose, rather than one forced by a failure.

A Takeover Assessment establishes which of these situations you are in. We look at what is actually present, tell you what we found and describe your realistic options and what each costs.

Hosting and access come first

Often the most urgent item is rarely the software itself. It is the accounts around it. We move hosting, backups and access into accounts in your name as part of the assessment, because everything else becomes easier once those are in your hands. After that, an ongoing retainer can keep the software maintained, or you can handle fixes one at a time as projects.

What we avoid saying

We cannot tell you whether you have a legal claim against a vendor, and we will not guess. If the contract dispute is serious, involve an attorney early. What we can do is the technical side: read what exists, document it and keep it running.

A note on pace

A quiet vendor does not usually create a deadline on its own. Deadlines come from outside: a hosting provider retiring a runtime, a certificate expiring, a staff member leaving. That is why the early work is mostly about knowing what you have and where it lives. Once you know, you can choose when to act instead of reacting to the calendar.

Our approach

We work by email and scheduled calls. We tell you on the first call how AI is used in our work, we use it for first-pass reading and drafting and a person reviews everything. We do not change a live system without your written approval. If you need a security review, that is a different kind of firm and we will say so.

If your vendor has gone quiet, tell us about your software. Describe what it does and what has happened, and we will reply with what we would look at first and what it would cost. Prices for every entry point are on the pricing page.

Tell us what you have

In two weeks we know it, document it, and keep it running. Send a few lines about your software and we will reply by email.

Email us Tell us about your software