Commercial architecture · enterprise scope · governed rollout
All prices per month · Excl. VAT
Annual contracts · South Africa
01 / 04
1–2 stores requiring a controlled frontline operating layer.
R45,000 / month
monthly contract scope
1–2 stores
network scope
Single dealerships and lean groups requiring a controlled frontline operating layer. Whether you run one Toyota store or one Kia franchise, this tier enforces response discipline and booking accountability.
Governance depth
Store-level enforcement of response standards and workflow discipline.
02 / 04
3–8 stores that need one operating standard across locations.
R95,000 / month
monthly contract scope
3–8 stores
network scope
Growing dealership groups that need one operating standard across locations. Built for 2–5 store networks running any brand combination — Toyota and Isuzu, VW and Audi, or a pure Chinese OEM group.
Governance depth
Cross-store SLA enforcement with unified operational standards.
03 / 04
9–20 stores requiring live command visibility.
R195,000 / month
monthly contract scope
9–20 stores
network scope
Regional operators and dealer groups requiring live command visibility across 6–20 stores. Any brand mix. Cross-store SLA enforcement, heatmaps, and executive dashboards unified across the network.
Governance depth
Network-level policy enforcement with executive oversight architecture.
04 / 04
21–50+ stores needing institutional governance and board-grade oversight.
R395,000 / month
monthly contract scope
21–50+ stores
network scope
Large portfolios requiring institutional governance and board-grade oversight. Multi-brand groups, OEM programs, and PE-backed operators running 20+ stores across any combination of franchise agreements.
Governance depth
Portfolio-wide governance architecture with intelligence-led enforcement.
Beyond Network Intelligence
For national and multi-country portfolios, holding companies, OEM program operators, and PE-backed groups requiring custom governance architecture. Pricing is agreed individually based on network scope, reporting complexity, and implementation requirements.
Included at every tier
01
Every tier includes the frontline control layer: SLA Enforcement, AI Urgency Inbox, Revenue Recovery Workbench, Booking Execution, WhatsApp governance, and the immutable audit trail.
02
Append-only event log from day one. Every assignment, escalation, override, booking, and policy change is recorded permanently. Board-ready. OEM-compliant. POPIA-ready.
03
Each tier includes governed rollout, workflow calibration, and operator setup. What expands as pricing rises is network scope, policy depth, reporting complexity, and named support.
Feature comparison
| Capability | Operations | Governance | Command | Intelligence |
|---|---|---|---|---|
| Core modulesSLA enforcement engine | Included | Included | Included | Included |
| AI urgency inbox | Included | Included | Included | Included |
| Revenue recovery workbench | Included | Included | Included | Included |
| Booking execution and calendar | Included | Included | Included | Included |
| WhatsApp governance layer | Included | Included | Included | Included |
| Immutable audit trail | Included | Included | Included | Included |
| Visibility and reportingBoard-ready reporting | — | Included | Included | Included |
| Cross-store SLA benchmarking | — | Included | Included | Included |
| Multi-brand OEM reporting | — | — | Included | Included |
| Revenue command center | — | — | Included | Included |
| Executive and investor reporting | — | — | Included | Included |
| Multi-region network rollups | — | — | — | Included |
| Support and successPlatform onboarding | Included | Included | Included | Included |
| Dedicated implementation lead | — | Included | Included | Included |
| Named success manager | — | — | Included | Included |
| SLA-backed platform uptime | — | — | Included | Included |
Recovery potential
Pricing follows operating complexity, but the economic case is still revenue discipline. AUTORA is bought to stop response leakage, protect bookings, and give leadership a governed path from inbound demand to accountable execution.
Commercial clarity
No. AUTORA OS sits above your CRM, DMS, and channel stack. It governs response timing, booking execution, escalation, and accountability across the network.
Most deployments move from configuration to live governance within a few weeks. Larger multi-store and multi-brand programs take longer because reporting, escalation design, and integration scope are deeper.
AUTORA is designed to sit above existing systems. The platform can work with dealership CRM and DMS environments already in use while governing the operational behavior around them.
Neither. AUTORA is contracted as operating infrastructure. Commercial scope is set by network complexity, governance depth, and the executive visibility layer required.
Yes. AUTORA is deployed as infrastructure, not month-to-month utility software. Engagements are typically annual so governance standards, reporting baselines, and rollout discipline can settle properly.