The spreadsheet is not a strategy

Let me describe your Monday morning.

You open your laptop. There are 6 tabs already waiting — a Google Sheet tracking client status, another for compliance deadlines, a third for team capacity. Somewhere in your inbox is an email from last Thursday about a regulatory update you haven't processed yet. Your CRM has a different version of the truth than your accounting software. Your project management tool has been "in implementation" for eight months.

You're not behind because you're bad at your job. You're behind because the tools weren't built for your job.

This is the reality for almost every professional services firm in South Africa — insurance brokerages, law firms, accounting practices, investment advisors, property managers. The operations run on disconnected tools glued together by key-person knowledge and manual processes.

It works. Until it doesn't.

The numbers nobody talks about

We spent the last six months researching operational workflows across seven industries. Not surface-level market reports — deep, practitioner-level research. What we found was consistent enough to be a pattern:

Insurance brokers spend 40% of their working day on non-revenue administrative tasks. 81% of clients who leave their broker cite the same reason: lack of regular, meaningful communication. Not price. Communication.

Law firms — 1,100 of them in South Africa — are currently under curatorship for trust accounting failures. 20-40% of billable attorney time goes unrecorded because the tracking systems are inadequate.

Accounting practices require their staff to log into 6-8 separate systems daily across clients. A third of each working day is consumed by SARS administration that could be automated.

Investment advisors spend 65% of their time on operational overhead instead of client-facing work. The FSCA imposed R119.8 million in penalties in the 2024/25 period alone.

These aren't edge cases. These are industry-wide patterns. The same fundamental problem wearing different industry costumes: operations built on disconnected tools, held together by people instead of systems.

Why generic software doesn't fix this

The typical response is: "Just get a better CRM." Or: "We'll implement an ERP." Or the classic: "We need a dashboard."

Here's the problem. A CRM doesn't understand FAIS compliance. An ERP doesn't know how to calculate trust account interest accruals for a law firm. A dashboard doesn't know that when a living annuity client's drawdown rate exceeds a threshold, it triggers a regulatory obligation.

Generic software is horizontal — it works the same way whether you're a bakery or a brokerage. Your industry has specific rules, specific formulas, specific compliance obligations, and specific workflows that no horizontal tool will ever encode.

Consultants understand this, which is why firms spend R500,000+ on McKinsey or Accenture to map their processes. But the consultant leaves. The PowerPoint deck gathers dust. The spreadsheet returns.

What an Operational Learning Model actually is

We coined the term because nothing else described what we were building.

An Operational Learning Model is a system that enters your business through its front door — your website, your marketing, your analytics — and progressively learns how to run your operations.

It works in three phases:

Phase 1: Learn. We research your industry with the depth of a consulting engagement but the speed of a technology team. Regulations. Workflows. Competitive landscape. The formulas your industry actually uses. The compliance requirements that keep your team up at night. We produce this in 4-6 weeks — not the 3-6 months a consulting firm would take.

Phase 2: Build. Using what we learned, we build a platform that was designed for your industry from the ground up. Not a modified CRM. Not a "customised" project management tool. A system that understands your specific compliance requirements, speaks your industry's language, and automates the workflows your team currently does by hand.

Phase 3: Run. The platform learns from your operational data. Compliance checks run automatically. Client health scores update in real time. Patterns emerge that no spreadsheet would ever surface. The system gets smarter every day it operates.

The architecture reuses 65-80% across industries. The domain intelligence is unique to each one. That's the point — you get the efficiency of a platform with the specificity of a custom build.

Why we're publishing this

Transparency is a strategic decision.

We could keep this methodology private, sell it behind closed doors, and hope clients trust us based on credentials. But we've seen too many agencies and consultancies hide behind vagueness. "We have a proprietary process." Great — what is it?

So here it is. We research industries. We encode operations. We build platforms that learn. We call it an Operational Learning Model.

What we don't publish is the how — the specific formulas, the data models, the 9-phase research methodology, the cross-vertical intelligence patterns. That's our IP, and it stays behind the gate until we're working together.

But the concept? The diagnosis? The evidence that your industry's operations are broken in predictable, fixable ways? That's public knowledge now. Because the first step to fixing something is admitting it needs fixing.

Seven industries. Ready to build.

We've completed deep research across:

  • Insurance brokerages — FAIS compliance, client lifecycle, claims tracking
  • Law firms — trust accounting, time tracking, matter management, LPC requirements
  • Accounting practices — SARS automation, FICA compliance, multi-entity management
  • Investment advisors — portfolio analytics, FICA/KYC, drawdown monitoring
  • Property practitioners — listing syndication, mandate tracking, PPRA compliance
  • Data science consultancies — project lifecycle, model deployment, delivery operations
  • Venues & hospitality — multi-stream revenue, event operations, guest experience

Each vertical has between 12 and 22 research documents, 100+ sourced statistics, regulatory deep dives, and wireframed platform concepts. Five have rendered explainer videos.

This isn't a pitch deck. It's proof of methodology.

The spreadsheet question

Ask yourself this: if your operations manager left tomorrow, how long would it take to rebuild what they know?

If the answer involves the phrase "it's all in their head" or "we'd need to check the spreadsheet" — that's the gap an Operational Learning Model fills.

Your industry has specific rules. Your compliance has specific requirements. Your workflows have specific patterns. And right now, all of that lives in disconnected tools, email threads, and the institutional memory of people who might not be there next year.

Google Sheets got you here. It won't get you where you're going.

Schalk van der Merwe is co-founder of 4What Digital, where he leads the development of Operational Learning Models for professional services firms across South Africa. Reach him at schalk@4whatmarketing.com or visit 4whatdigital.com/operations.