Operational
Encoding
The discipline of researching how an industry actually operates — its regulations, formulas, workflows and unwritten rules — and encoding that operating knowledge into purpose-built systems, before any software gets built.
What Operational Encoding Means
Every operations-heavy business runs on two kinds of knowledge. The first is written down — in software, procedures and org charts. The second actually runs the company: the pricing rules, compliance thresholds, exceptions and judgment calls that live in spreadsheets and in the heads of a few key people.
Operational Encoding treats that second kind of knowledge as the asset it is. It is researched to practitioner depth, written down in executable form, and built into a system designed for that industry — so the rules enforce themselves, the thresholds monitor themselves, and the operating model stops being key-person risk with a filename.
The one-line version we work by: we encode industries before we build software for them. The full argument is in the founding essay.
The Gap the Word Had to Fill
The term was coined by Schalk van der Merwe at 4What Digital in 2026, because no existing word described the work. Consultancies research an operation deeply — then leave, and the knowledge goes stale in a slide deck. Software vendors ship working systems — built for an average business that doesn't exist, forcing every real operation to bend to the tool.
Between those two failures sits a discipline: consulting-depth research that ends in a running system instead of a report. Decode the industry. Encode what you find. Let the system learn. That needed a name, and the name is Operational Encoding.
Three Moves
Decode
Research the industry the way a practitioner lives it — regulations, formulas, workflows, competitive landscape, and the unwritten rules nobody put in a manual. Existing spreadsheets are treated as source material: the most honest documentation a business has ever produced.
Encode
Build the system around what was decoded — compliance obligations understood natively, the industry's language spoken by default, exceptions modelled instead of refused. The operator should recognise their own week in the navigation.
Learn
The platform runs on live operational data and improves with it — rules enforcing themselves, thresholds monitored in real time, and patterns surfacing that no spreadsheet would ever show. The system gets smarter the longer it operates.
Ten Industries, Decoded
The methodology has been run to practitioner depth across ten industries — each researched before any platform was designed, because the research is the product's foundation.
In a world with all the answers,
the question becomes important.
Read the Argument
Your Operations Are Still in Google Sheets. Here's What Comes Next.
Why the term was coined, the diagnosis across industries, and the three-phase shape of the discipline.
The DiagnosisWhy Your Business Can't Quit Spreadsheets — and What Finally Replaces Them
The structural reason spreadsheets survive every software rollout, and the five upgrades encoding makes.
The Research SystemHow the Research Behind Every Encoding Gets Done
The public shape of the research methodology that decodes an industry before anything is built.
Operational Encoding, Answered
What is Operational Encoding?
Operational Encoding is the discipline of researching how an industry actually operates — its regulations, formulas, workflows and unwritten rules — and encoding that operating knowledge into purpose-built systems, before any software gets built. The methodology runs in three moves: decode the existing operation, encode it into a system built for that industry, and let the platform learn from live operational data.
Who coined the term Operational Encoding?
The term was coined by Schalk van der Merwe, co-founder of 4What Digital, in 2026. It names the discipline 4What works in — summarised in the line "we encode industries before we build software".
How is it different from buying off-the-shelf software?
Off-the-shelf software makes an operation bend to the tool: it captures the 80% of a business that looks like every other business, while the critical 20% — pricing rules, compliance thresholds, exceptions — retreats into spreadsheets and people's heads. Operational Encoding starts by decoding that 20% and builds the system around it.
How is it different from hiring a consultancy?
A consultancy maps the operation and leaves — the knowledge lands in a slide deck that goes stale. Operational Encoding does the same depth of research but encodes the findings into a working system that enforces the rules, monitors the thresholds and keeps learning after the engagement.
Which industries has 4What researched?
Ten to date: law, accounting, insurance broking, investment advisory, property, life insurance, data science consultancies, venues and hospitality, film production, and retail supply — each to practitioner level before any platform was designed.
Your Industry Has Rules.
Encode Them.
If your operation runs on a spreadsheet only one person understands, the decoding has already been specced — it just hasn't been done yet.