Is Your Software Vendor Delivering What You Pay For? 7 Signs to Check
Agencies and IT providers are hard to judge from the outside. Seven signs you can check yourself, without being a developer, that show whether you are getting real value.
Many companies rely on an outside agency, freelancer or managed service provider for a large part of their IT. That is often the right call. But it creates an awkward position: you pay for work you cannot fully judge, delivered by people whose incentives are not exactly the same as yours.
Most vendors are not dishonest. The problem is more ordinary. Over time, standards slip, priorities drift, and nobody on your side has the time or the background to notice. By the time it becomes visible, you have usually paid for months of it.
The good news is that you do not need to read code to get a reliable signal. Here are seven things you can check yourself.
1. You can see what you paid for
Ask for a list of what was delivered in the last month or quarter, and compare it with the invoices.
A healthy vendor can produce this easily, because they track it anyway: tickets closed, features shipped, hours spent per task. A vendor who struggles to connect invoices to concrete results is either badly organized or does not want you to look closely. Neither is good.
What to look for: a clear line from each invoice to specific, recognizable work. Vague items like "development", "maintenance" or "consulting" with large hour counts and no breakdown deserve a question.
2. Estimates and reality are in the same neighborhood
Pick a few recent tasks and compare the original estimate with what was actually billed and how long it actually took.
Software estimates are never perfect, and occasional overruns are normal. What matters is the pattern. If almost every task runs over, and the overrun is always explained after the fact rather than flagged early, the estimates are not really estimates.
What to look for: overruns that were announced before they happened, with a reason, and a rough balance between tasks that ran over and tasks that came in under.
3. The same problems do not keep coming back
Look at the last few months of bug reports or support tickets. Are the same issues reappearing?
Recurring problems are one of the clearest signs of low quality, because they mean the vendor is treating symptoms rather than causes. They are also expensive: you pay for the fix, then pay again when it breaks.
What to look for: fixes that stay fixed. If a problem returns, the vendor should explain what the underlying cause was and what changed to prevent it.
4. You own what you paid for
This one is less about quality and more about risk, but it matters just as much. Check that you have:
- access to the source code repository, under an account your company controls,
- admin access to hosting, domains, cloud accounts and key services,
- documentation good enough for another team to take over,
- a contract that says the code and data are yours.
If your vendor disappeared tomorrow, could someone else continue? If the honest answer is "not without a lot of pain", you are more dependent than you should be, regardless of how good the work is.
5. Changes are tested before they reach your customers
Ask how a change goes from "done" to "live". You are listening for a few things: a separate test or staging environment, some form of automated testing, and someone other than the author reviewing the change.
You do not have to judge the technical details. A vendor with a real process will describe it in a few clear sentences. A vendor without one will talk around the question, or tell you that their developers are "very careful".
What to look for: a process that exists independently of individual people, and production problems that are rare rather than routine.
6. Communication happens before problems, not after
Think about the last few times something went wrong. Did you hear about it from the vendor first, or from your own customers and staff?
Good vendors raise risks early, even when it is uncomfortable for them: "this will be late", "this approach will be expensive to maintain", "we need a decision from you by Friday". Vendors who only report good news are not protecting you, they are protecting the relationship.
7. Their recommendations sometimes cost them money
This is a subtle one, but telling. Has your vendor ever recommended something that reduced their own revenue? Simplifying a system, dropping a feature nobody uses, moving to a cheaper service, or telling you that a task is not worth doing?
A vendor who always recommends more work, bigger projects and more hours may be right every time. But it is worth noticing if they have never once suggested the cheaper option.
What to do with what you find
Score each of the seven signs honestly: clearly fine, unclear, or clearly a problem. Then:
- Mostly fine: keep the vendor, and repeat the check once or twice a year. It is cheap insurance.
- Several unclear: you lack visibility rather than having a proven problem. Ask the vendor for the information. How they respond is itself a signal.
- One or more clear problems: look at real deliverables before you decide anything. A focused spot check on a sample of recent work turns a suspicion into evidence you can bring to the table.
The aim is not to catch your vendor out. It is to replace "I have a feeling" with "here is what we found", which is a much better starting point for any conversation, including a good one.
If you are not sure whether you need a quick check or a broader review, read Spot Check vs. Full IT Audit first.