There is a sentence we hear, with small variations, in almost every first meeting with a new company:
“I feel like I pay a ton of money, and things still don’t work.”
Sometimes it is the website that never quite gets finished. Sometimes it is the ERP implemented two years ago that the team still operates “in parallel” with Excel. Sometimes it is three different vendors, each invoicing every month, and nobody able to explain why inventory still doesn’t reconcile.
The first thing we tell whoever brings us this sentence: it is almost never about how much you are paying. It is about how the relationship is set up.
Why this happens
After years working with companies of all sizes across LATAM and Europe, we see the same patterns again and again:
Hours get billed, but nobody owns the outcome. The vendor complies: hours were logged, tickets were delivered. But nobody signed up to be responsible for the whole process working. When something lands half-done, technically everyone did their part.
Every system has a different vendor, and nobody sees the whole. The website with one agency, invoicing with another, the CRM with a third. The integrations between them are no man’s land. That is exactly where the money leaks.
The legacy software nobody wants to touch. That system that “works, but let’s not touch it”. Every small change is expensive because nobody understands the code, and the original vendor is long gone.
Progress reports that never turn into usable things. Meeting minutes, timelines, completion percentages. And yet, nothing new your team can actually use this month.
What changed (and why it is good news)
Building and customizing software today costs a fraction of what it did just a few years ago. Modern tooling, and AI used well, dramatically shortened the time between “I asked for it” and “I am using it”.
That changes the conversation entirely. The bottleneck is no longer writing code: it is the judgment to decide what to build, in what order, and taking responsibility for making it work. What is scarce is not hands, it is senior ownership.
If you are paying previous-era prices for previous-era results, it is not that technology doesn’t deliver. It is that the relationship was set up for another era.
What to demand from your next vendor
You don’t need to be technical to demand well. Four concrete things:
- An owner of the outcome, not of the hours. Someone who signs “this process will work”, not “I will dedicate X hours to it”.
- Senior people writing the code. Ask who will actually work on your project. If the person selling is not the person building, ask to meet the person building.
- Iterations you can see. Every two weeks, something usable. Not a report: something you can open and try.
- Communication even when the news is bad. Real projects have bad weeks. What is unforgivable is finding out late.
We work this way not because it sounds good, but because it is the only thing we have seen work: trust is built by delivering and communicating, even when the status is not ideal.
Where a fractional CTO comes in
Many of the companies that bring us this sentence don’t need yet another vendor. They need someone on their side of the table: a senior profile who maps out the systems and vendors, prioritizes, and is accountable for turning the investment into things that work. Without the cost of a full-time CTO.
We cover that in detail in What is a fractional CTO, and when do you need one?, and it is part of our strategic consulting practice.
If this sounds familiar
Bring the problem, no deck and no commitment: thirty minutes of conversation. We don’t promise magic. We promise you will see progress, and you will always know where your project stands.
