The Visio Auto Suite: A six-product operating system for the SA automotive market.

1. The six asymmetries

These six asymmetries are not independent. They are facets of one underlying problem: information does not flow correctly between buyers, dealers, banks, and data brokers in the South African automotive market. Each product fixes one facet. Together they fix the system.

2. The architectural unity

The suite is held together by three structural decisions:

1. Doctor OS UI pattern. Every product uses the same Next.js 16.2.1, Tailwind 4, Geist, dark-mode-by-default, gap-px-card-grid visual language. A buyer who has used one product immediately knows how to use the next.
2. Shared Honesty Protocol. Every product enforces the same rules: no fabricated data, source-cited inputs, demo flags clearly visible until live data is wired, low-confidence outputs surfaced as warnings rather than masked. A single dishonest product would taint all six.
3. Unified vt_transactions ledger. Visio Trust owns the master transaction table. Every other product writes its primary key into this table when a transaction passes through it.

These three decisions are deliberate. They are also the same three decisions that Carvana made differently — Carvana built one product, one experience, one ledger from day one, and paid for it with $20 billion in capital and a near-bankruptcy. The Visio Auto Suite achieves the same coherence through software architecture instead of capital investment.

3. The three user journeys

Consumer journey.Buyer lands on a dealer page → uses Visio Approve to check eligibility (free) → optionally upgrades via Visio Open Finance for verified affordability → sees the Visio Inspect condition badge on their chosen vehicle → clicks “Buy with Visio Trust” → pays into escrow → vehicle is delivered → 7-day return window opens → after 7 days the escrow auto-releases. The buyer has experienced Carvana on a vehicle owned by an SA dealer, verified by AI, financed by a SA bank, and delivered by a SA logistics partner.

Dealer journey. Dealer subscribes to Visio Trust Velocity (R8K/mo) → onboards their inventory feed → connects WhatsApp Business → embeds the Visio Trust widget on their listings → gets a stock velocity dashboard → starts turning stock 1.6× faster within 60 days → converts saved floorplan interest into pure margin.

Data subscriber journey. OEM marketing team or bank credit ops sees the free public Visio Intent Index referenced in BusinessTech or Daily Maverick → subscribes to Growth tier (R15K/mo) → reallocates marketing budget toward higher-intent regions → measures ROI in next quarter → upgrades to Enterprise (R50K/mo).

These three journeys are not three separate products. They are the same underlying dataset accessed through three lenses, monetised three ways, with one shared vt_transactions ledger underneath.

4. The economic stack (year-2 steady-state)

The revenue is not concentrated in any single product. The diversification is structural, not designed-in. If Visio Trust takes longer to land Stitch EscrowPay, the other five keep generating revenue. If Visio Intent takes longer to land its first OEM, dealer subscriptions keep growing.

5. The legal posture (clean across all six)

• Not a credit provider. NCA Section 40 inapplicable.
• Not a credit bureau. NCA Section 70 inapplicable.
• Not financial advice. FAIS Section 1 explicitly excludes credit.
• Not a vehicle owner. Visio Trust is coordination only.
• Not a transport operator. Visio Trust integrates with licensed third-party carriers.
• POPIA-compliant. Explicit consent gates, encrypted storage, 90-day retention max, audit trails, k-anonymity in published aggregates.

The result is a six-product suite operating inside the SA automotive economy with zero financial-services regulatory burden. Compare this to the regulatory load on a SA bank trying to enter this market (full NCR registration, FAIS licensing, PA approval, basel-style capital requirements), or on a SA dealer chain trying to build their own version (NCA registration as credit provider for the captive finance arm, FICA compliance, dealer licensing in every province), and the structural advantage becomes obvious.

6. The competitive landscape

• Visio Approve vs ClearScore SA, JustMoney, RateCompare — generic, not vehicle-specific, do not handle Reg 23A formula
• Visio Inspect vs UVeye, Ravin AI, ProovStation — hardware-based, $250K capex per location, impossible economics for SA long tail
• Visio BDC vs Conversica, Impel, Fullpath, CarNow, Gubagoo — SMS/email-centric, English-only, $1.5K-$5K/mo USD, does not run on WhatsApp
• Visio Intent vs Lightstone, TransUnion AIS, NAAMSA — sell-out historical record providers, do not produce forward-looking intent data
• Visio Open Finance vs truID — B2B infrastructure, no consumer experience, no vehicle vertical
• Visio Trust vs Carvana, Cazoo, Vroom, Kavak, WeBuyCars — capital-intensive vertical retail, killed everyone except Carvana and WeBuyCars

In every case, the existing competition either does not address the SA-specific shape of the problem (US-built tools), does not address the long-tail economics (UVeye, hardware), or addresses the wrong layer (vertical retail instead of coordination). The Visio Auto Suite is the first product line built specifically for the South African market shape, at South African pricing, on South African channels (WhatsApp), in South African languages (English + Afrikaans + Zulu), against South African regulation.

7. The flywheel

Dealers subscribe to Visio BDC + Visio Trust
        ↓
Buyers use Visio Approve + Visio Open Finance + Visio Inspect on dealer pages
        ↓
Every interaction fires a signal into the Visio Auto signal engine
        ↓
Signals are k-anonymity-aggregated into Visio Intent
        ↓
OEMs and banks subscribe to Visio Intent for the aggregated view
        ↓
OEMs reallocate dealer marketing toward higher-intent regions
        ↓
Banks reduce cost-per-qualified-lead via better intent targeting
        ↓
The improved economics fund more dealer subscriptions to Visio BDC + Visio Trust
        ↓
[loop]

This flywheel is the structural moat. A competitor would have to build all six products simultaneously to get on it — and the cost of bootstrapping the dealer side without the data side, or vice versa, is prohibitive. The only way in is the way we built it: in one sprint, in one team, with one shared ledger.

8. What is left to do

1. ✅ Apply Supabase migrations. Combined SQL covering all 25+ tables across the six products. Done.
2. ✅ Vercel deployment. All 6 repos live at *.vercel.app. Done.
3. Wire the live signal feed. The visio-workspace signals table needs to flow into Visio BDC's routing engine and Visio Intent's aggregator.
4. Stitch EscrowPay partnership. Visio Trust ships with a stub; the partnership is the path to live escrow.
5. First 50 dealers. Outreach to the existing 329 dealerships in the visio-auto database, pilot at half price, document the case study.
6. First OEM and first bank. Toyota SA or VW SA for Intent; WesBank or Standard Bank for Approve lead-fees.

Year-1 realistic target: 50 paying dealers, R10M ARR. Year 2: 500 dealers, ~R237M ARR. Year 3: scale across SADC + secondary markets.

9. Why this is the right business

1. Compounds across all six products. A dealer using one becomes a candidate for all five others. A buyer using one becomes a candidate for the next two. A data subscriber funds the dealer acquisition.
2. Operates inside a clear legal gap. Zero financial-services regulatory burden, zero credit risk, zero inventory risk.
3. Targets the largest information asymmetry in the largest unserved market in SA automotive. R160B annual used-car market, 55.71% unorganised, 25% rejection rate, no Carvana equivalent.
4. Built end-to-end in a single sprint. All six repos exist, all six are pushed to GitHub, all six are live in production. There is no technology risk left to retire.
5. Defensible moat that requires building all six products at once. The data flywheel cannot be entered by a competitor incrementally.

10. Conclusion

This is not a product. It is a category. The category is asset-light coordination of a regulated, capital-intensive, fragmented physical market, applied first to South African cars, and applicable next to property, insurance, and any other high-value transaction where the existing market is bottlenecked by trust, finance and information friction.

We start with cars because that is where the data is, the regulation gap is wide, and the 6 products have already been built. Then we apply the playbook to the next vertical.

Companion papers in this series:
VRL-AUTO-004 — Visio Approve
VRL-AUTO-005 — Visio Inspect
VRL-AUTO-006 — Visio BDC
VRL-AUTO-007 — Visio Intent
VRL-AUTO-008 — Visio Open Finance
VRL-AUTO-009 — Visio Trust
VRL-AUTO-010 — Suite Overview (this paper)

References: All companion papers above. Six repositories at github.com/Iamhamptom/visio-{approve,inspect,bdc,intent,open-finance,trust}. Six live deploys at visio-{approve,inspect,bdc,intent,open-finance,trust}.vercel.app.

Cite as: Hampton, D. (2026). “The Visio Auto Suite: A Six-Product Operating System for the South African Automotive Market”. Visio Research Labs, VRL-AUTO-010.