How to spot you need tech leadership — from a tech vendor

We're a tech vendor. We've watched great software die inside organizations that couldn't own it. Here's how to tell before you hire another one of us.

A confession.

We're a tech vendor.

We build Odoo ERPs. We ship POS systems and payment integrations. We write custom software, design IoT hardware, deploy AI assistants. We've delivered dozens of projects across Cambodia and the region.

And we've watched clients turn working software into failed projects.

Not because our code broke. Not because the vendor under-delivered. Because there was no one on their side of the table making the decisions that code can't make for them.

So here's a post we probably shouldn't be writing. From a tech vendor, about the limits of hiring a tech vendor.

The pattern nobody wants to name.

It goes like this:

A company outgrows its spreadsheets. Or its old ERP dies. Or a new regulation lands. Somebody says "we need a system." Quotes arrive. A vendor is chosen, usually the cheapest or the most aggressive. The project starts.

Six weeks in, decisions stall. A department head wants a custom report — does it fit scope? Nobody knows. The vendor says yes, adds hours. The CFO sees the overage and panics. The CEO, who greenlit the project on faith, can't evaluate the vendor's explanation because it's technical.

Nine months later, the ERP is live. Half of it. The other half is in a backlog nobody owns. Integrations that were supposed to save 20 hours a week save 8, because the workflows were designed around the old system's limitations and nobody had authority to re-question them.

The software works. The project didn't.

We've seen this play out enough times to know the culprit isn't the vendor, or the software, or even the scope. It's the missing role: somebody on the client side whose entire job is to translate the business's strategy into technical decisions, evaluate vendors as equals, and own the technology as a long-term asset instead of a purchase.

In most SMEs, that person doesn't exist. The CEO is too busy. The CFO doesn't speak the language. IT — if there is IT — is managing servers, not strategy. The vendor is happy to fill the vacuum, because the vacuum pays the vendor.

That's the pattern. And it's not a tech problem. It's a leadership problem wearing a tech problem's clothes.

Why a tech vendor can't save you from this.

We can't. Not really. And any vendor who tells you otherwise should be the first vendor you don't hire.

Here's why it's structural:

• Role conflict. We're hired to deliver the scope. We can't be the same people questioning whether the scope is right. If the client-side brief is flawed, a vendor who pushes back risks the contract. A vendor who doesn't push back burns the client's money.
• Incentive misalignment. Telling a prospect "you're not ready for this project" costs us the deal. Even when it's the right answer, it's the answer we're the worst-positioned to give.
• Scope limits. We're hired to build, not to do the strategy that should have preceded the build. The right strategic questions often happen before the vendor is even invited into the room.
• Power. We can't fire a bad partner for you. We can't reshuffle your team. We can't tell your CEO "no" when they ask for something that won't work. Even a vendor with a strong opinion is still an outsider with a financial conflict.

A great vendor is an asset. But assets don't run strategies. People do.

What changes with fractional tech leadership.

Fractional tech leadership is not a better version of a vendor. It's a different role entirely.

Where a vendor owns the how, a fractional tech leader owns the why. Where a vendor sells hours, a fractional leader is measured by business outcomes. Where a vendor is incentivized to say yes, a fractional leader is incentivized to say no — and is paid specifically to make the hard calls that an engaged CEO can't afford to make alone.

Practically, it looks like this:

• Someone at the strategy table who speaks both business and technical, and reports to the CEO
• A human who can evaluate vendor proposals as peers, not as clients taking what they're offered
• An accountable owner for technical debt, platform direction, and long-term stack coherence
• Authority to fire a vendor when needed — including us
• Part-time but steady: retainer-based, quarterly-reviewed, paid for what they decide, not for what they type

For most SMEs, this is not a full-time hire. A full-time CTO costs $200K+/year fully loaded, and the workload doesn't justify it. Fractional does. Usually somewhere between 10 and 40 hours a month, on retainer, with a clear remit.

The first thing a good fractional tech leader does isn't build anything. It's audit what you already have and ask: is any of this actually serving your strategy?

If the answer is mostly no — and it's mostly no, in our experience — the next tech project should not start until the leadership gap is filled.

That's why we wrote a cheat sheet.

The uncomfortable close.

We're a tech vendor. We sell Odoo, software, hardware, AI, the whole catalog. That's how we pay the bills.

But we also sell fractional tech leadership — and if our assessment says you need that before any tech, we'll tell you. Even when it costs us the vendor contract. Especially then.

Because the worst thing a tech vendor can do is deliver a perfectly-built project into an organization that wasn't ready to own it. We've been on the receiving end of that call enough times. It's not a call we want to take again.

Run the cheat sheet. Share it with your CEO. If the pattern lands, book a 30-minute assessment. We'll tell you straight what we see — vendor work, leadership work, or both.

— A tech vendor.

Book a 30-min assessment → Open the cheat sheet → Fractional Leadership →