Ideas worth
shipping.
Writing on AI enablement, software delivery, and the work that actually moves the needle. No fluff — just what we've learned building with teams.
What 'AI enablement' actually means for a business like yours
Everyone is talking about AI enablement as if the meaning were settled. For an owner running a real business with no data scientist, it mostly isn't. Here is what the term actually means, in plain language, minus the hype.
Your data moat is not your source of truth
'Data moat' is one of the most repeated phrases in AI strategy and one of the least examined. A moat is real and worth building — but it is not where your truth lives. The systems your data came from are. Here is what a data moat actually is, what it is not, and how to use one without quietly breaking your own architecture.
Start from the decision, not the data
Most AI projects start from the wrong end — 'we have data' or 'we should use AI' — and produce insight that nobody acts on. The teams that get returns start from a specific decision a human needs to make, and work backwards to the technology.
Your AI feature works. Nobody's using it.
Building an AI feature that works and getting people to use it are two different achievements, and the second is where most of the value quietly leaks away. The published gap between access and use is now 61 percentage points — and it is not a technology problem.
Most AI advice is written for companies that don't look like yours
The published AI playbook assumes a data team, a research function, and an eight-figure budget. Almost none of it survives contact with a company doing R15–50M that knows its trade cold and has no data scientist. Here is what actually changes at that scale.
Everyone in your company is looking at different numbers
Before AI can answer anything useful about your business, your systems have to agree on what a customer, an invoice, and 'revenue' actually are. In most mid-sized companies, they don't — and that disagreement is the real bottleneck, not the model.
Why your AI should never be the source of truth
Hallucination is not a bug you tune away. It is a structural property of how language models work. The teams who trust AI in production are the ones who decided, deliberately, which parts of the system the model is never allowed to decide.
What working AI teams actually look like in 2026
Most published AI team structures describe how it should be done. This post is about what it actually looks like in the teams that are shipping — the roles, the ratios, the rhythms, and the small operational habits that separate working from theatre.
Measuring AI ROI without lying to yourself
Ninety-five percent of enterprise AI investment produced no measurable return last year. Most of the failure is not in the technology. It is in measurement — what teams chose to count, what they chose to ignore, and what they hoped nobody would ask about.
Buy the boring, build the unique: an AI infrastructure framework
Most teams building AI features in 2026 are building too much of their own infrastructure. Here is a practical framework for what should live in-house and what should not — and what the total cost actually looks like when you count honestly.
Your data is your moat — and most companies' data isn't ready for AI
The model you choose is not your differentiator. Your data is. And the published numbers on how few companies have data that AI can actually use are bracing — between five and seven percent, depending on whose research you read.
The case for boring AI infrastructure
The teams shipping reliable AI are not winning on model choice. They are winning on evals, observability, cost control, and the fallback paths that fire when the interesting parts break.
POPIA, GDPR, and AI: what South African product teams need to know in 2026
South African teams shipping AI features cannot ignore either POPIA at home or the EU AI Act when serving European customers. Here is the practical compliance picture as of mid-2026.
Agents vs. workflows: choosing the right pattern in 2026
Most things sold as agents are workflows wearing a costume. Knowing the difference matters because the trade-offs — cost, latency, debuggability, reliability — go in opposite directions.
Why your RAG demo doesn't survive contact with real users
A working demo with five curated documents is not a working system. Here is what breaks when real users, real documents, and real load arrive — and how to build for it from the start.
Working through something similar? Let's talk.
Most of what we write here comes from real engagements. If it resonates, a conversation costs nothing.
- Format 60-min call
- Output Written summary
- Commitment None required