SADC · Southern African Development Community · Evidence-Based Performance

Sixteen states. Countless independent businesses. Each one able to prove itself.

SADC coordinates trade and integration across Southern Africa. None of it helps a single independent business prove — to a bank, a buyer, a border — that it exists and performs consistently. MetriqOne does exactly that: field-level evidence each business owns, captures, and prints as its own proof. No head office. No aggregate. No permission required.

AngolaBotswanaComorosDRCEswatiniLesothoMadagascarMalawiMauritiusMozambiqueNamibiaSeychellesSouth AfricaTanzaniaZambiaZimbabwe

Regional Scale

16
Member States
370M+
Combined Population
$700B+
Combined GDP
1992
Founded — Windhoek Treaty

MetriqOne's Framework — Not a SADC Standard

FC4
The gap all BSC/OKR frameworks fail
CPL+XmR
The two-layer system that closes it
An independent business needs its own evidence. Not a programme's report. SADC runs trade protocols and development programmes across 16 member states, each generating reporting from the top down. None of it lets a single micro-business demonstrate, on its own terms, that it has been trading consistently and within limits. MetriqOne closes that gap where it actually matters — the individual business — and never asks it to belong to anything to do so.

Active Strategic Context

Simplified at the border. Still unprovable over time.

In 2026, SADC, COMESA and the East African Community began piloting a Tripartite Simplified Trade Regime for small-scale cross-border traders — simpler documents, a US$2,000 consignment threshold, faster crossings. It reduces paperwork at the point of crossing. It does nothing to help a trader show a bank or a bulk buyer that they have traded consistently, and within limits, month after month.

That evidence has to belong to the trader — captured in the field, printed on demand, owned outright. That is a Member Operator on their own Field account, not a line in someone else's programme report. Every framework that only reports downward from a head office misses it. MetriqOne starts at the business and works outward — which is why the proof holds where a programme summary cannot.

Proof that belongs to the business — even without a smartphone.

A Node-Business — an existing local print shop or service point — registers a micro-business as a Field account and handles the paperwork for anyone without a smartphone. To submit a completed form, it opens metriq.one/collect/ and scans the QR printed on that form. To hand over proof, it scans its own Node-Business QR, and the report requested prints from the list that appears.

The Node-Business never sees the signal — it is print-and-scan infrastructure only. The signal, and the proof, belong to the business. No one between the operator and their own evidence can read it, gate it, or claim it.

What an Independent Business Gets

Credit at a bank
A printed proof report shows a lender consistent, in-limit trading over time — evidence a self-declared income statement can never provide.
A contract with a buyer
A bulk supplier or formal-sector partner sees verified performance, not a promise. The business owns the report and chooses who to show it to.
No smartphone, no barrier
Paper form plus QR. A Node-Business prints the form, submits it by scanning the QR, and prints the proof. Offline-first by design.
Proof of existence
For a micro-business formal systems do not recognise, a field-generated record is the first document that says: this business is real, and here is how it performs.
Its own history, kept
An append-only, immutable record. Every reading preserved. Deactivation never deletes — a business that pauses keeps its full evidence history.
Early warning it controls
CPL fires weeks before an XmR breach — a threshold the operator sets. The business sees drift on its own data before anyone else could.

One Business Reading Its Own Signal

Revenue stability — own readingWithin limits
Trading consistency — own readingCPL threshold
Stock turnover — own readingWithin limits
Margin on a core line — own readingXmR signal
This is one independent business reading its own signal — not a head office reading across many. There is nothing to aggregate: the business owns the account, the signal, and the proof. It sees the CPL line move before an XmR breach, on its own data, and prints the proof exactly when it needs it.

CPL = Counter Productive Level — manually set threshold, active from day one. XmR = statistically derived Natural Process Limit, calculated once field readings accumulate. Two distinct early warning layers. Both active simultaneously, on the business's own data.
Overseeing many businesses you actually hold under one account — not running one of your own? That is a Federation or Enterprise deployment that reads across the nodes on your account. Different question, different page: AfCFTA Trade Monitoring →

Presentations & Resources

■
Southern Africa Corridor Deployment — Independent Traders
Independent cross-border traders as Member Operators — each on its own Field account, each printing its own proof. A Node-Business handles print, scan and submit. No aggregate.
Live ■
SADC Trade Protocol — Signal Architecture Brief
How MetriqOne maps to SADC accession and trade-corridor implementation monitoring — the standing tool an institution would otherwise build from scratch.
Live ↩
AU · Regional Intelligence
Continental deployment context. All 16 SADC member states are AU members. Agenda 2063 and AfCFTA apply across the region.
Live

MetriqOne's Framework

Falsifiability Condition 4 — The gap BSC, OKRs and LogFrame cannot close

Balanced scorecards, OKR frameworks, PuMP, and LogFrame all share the same structural failure: they operate without any formalised limits. A target is not a limit. A moving average is not a signal. Without limits — whether manually declared at deployment or statistically derived from the field data itself — there is no way to determine whether performance is within natural variation or whether something has genuinely changed.

MetriqOne names this precisely as FC4: absence of any formalised limits. MetriqOne closes FC4 with two distinct layers: the CPL — a manually declared threshold set by the operator before enough field data exists for statistical derivation — and XmR Natural Process Limits, calculated from field data using Wheeler's method once readings accumulate. This is MetriqOne's own framework definition, not an external or SADC-endorsed standard.

Ready to prove it?

The trilogy sets the academic and philosophical foundation. The platform delivers it in the field — starting with a single independent business proving, on its own, that it exists and performs.

View Deployment Tiers