The objection, in the words we actually hear
“We'd do it if we had someone technical.”
“Our IT guy is stretched. There's no way we can support another system.”
“Send us a proposal and we'll look at it when we find someone who can implement it.”
That last one is the dangerous version, because it never gets followed up. It's the polite form of “no”.
It's also, according to a study published in August, the wrong reason to stop.
What the research actually found
Morema, Adeyelure and Seaba surveyed 123 logistics SMEs in Ekurhuleni, Gauteng — IT staff, decision-makers and logistics managers — about what drives cloud ERP adoption. They published in the South African Journal of Information Management in August 2026.
They tested eleven predictors. Ten were significant. One wasn't.
The one that failed was skills availability.
Not “skills were a weak factor.” Not “skills mattered less.” Availability of technical skills inside the business showed no significant relationship at all with whether the firm intended to adopt better systems.
β = −0.113 · p = 0.799
The authors drew the obvious conclusion: “vendor-managed, SaaS-delivered cloud ERP architectures have materially reduced the in-house technical expertise threshold that historically constrained enterprise software adoption among resource-limited SMEs.”
In other words: the door opened, and nobody walked through it because they thought they needed to bring their own key.
But here's the part that's more useful than a sales line
Read that finding again carefully. Skills weren't the barrier — so what was?
Top management support. Organisational culture. Security perceptions. Competitive edge. Financial capability.
Every one of those is human.
That's a genuinely awkward result for a business thinking it's a technology problem. The constraint isn't hiring a technical person. It's that nobody inside the business owns this, the culture treats it as IT's problem rather than operations', nobody has convinced the team it's safe, and there's no line item for it.
You cannot buy your way out of that with a subscription.
Why this happens in logistics specifically
Ask an operator where a shipment is right now and the honest answer is usually a phone call.
Somewhere in every operation there's a person who knows which loads are running, which invoices are waiting on a POD, and which customer is chasing. That knowledge is usually undocumented, sits with one individual, and leaves when they take leave.
No amount of in-house technical skill fixes that. It needs someone to map the process, write it down, and build the thing that holds it.
What it costs to keep going as you are
We built quote-to-cash, dispatch and driver coordination automation for a Durban logistics client. The result was 40% fewer admin hours per week, 25% revenue growth, and 3x faster quote response.
Notice what wasn't in that sentence. Nothing about hiring. Nothing about licensing a platform and hoping.
What it took was an engineer on site, two days mapping how the work actually flowed, and three weeks building it.
The three options, honestly
The most common, and the most expensive way to solve this. Six months, twelve months. Possibly never, because the role doesn't exist and its budget is competed away every cycle.
The option the research says to be careful about. The same study found a negative trialability result: in SMEs with limited governance capacity, unstructured trial phases erode adoption confidence rather than build it. We wrote about that separately.
Someone maps your process, builds the specific automations, documents them, and trains your team. You end up with working systems and staff who can run them. Ownership stays with you; the dependency doesn't.
What to do this week
Not a technology procurement. Walk your own process.
Take one shipment — one, end to end, from the enquiry to the invoice. Write down every step, every system it touches, every person involved, and every place the same information gets typed twice.
Most operations finish that exercise having found three or four handoffs nobody owns. That map is worth more than any vendor deck, and it costs an afternoon.
If you want a second pair of eyes on it, we map it on site, free for two operators a month and tell you the one or two things worth automating first. You keep the map either way.
Sources
Morema, T.P., Adeyelure, T.S. & Seaba, T.R. (2026). Cloud ERP adoption in Ekurhuleni's logistics SMEs: A conceptual model. South African Journal of Information Management, 28(1), a2179. doi.org/10.4102/sajim.v28i1.2179 — CC BY 4.0.
Case study figures are Agentcy's own, published with client permission.