The Client Dashboard, Worked: Self-Service Portal as Revenue Engine
The customer dashboard (S6.7) was designed as a portal; the SECTOR07a futures round showed it as a revenue engine (SECTOR07a-40). This is the worked example that connects the two: the dashboard is not a support amenity — it is the product surface where customers see value, self-serve their account, and renew their subscription. The dashboard is the storefront of the sovereign stack.
What the dashboard shows
The client dashboard shows the customer four things: their services (what agents are running, what deliverables exist, what the pipeline is producing), their meters (usage, spend, remaining budget — the same meters as OP-4 and S6.12), their evidence (the audit records, the post-mortems, the simulation receipts that prove the work — S7.15), and their account (tier, invoices, the ownership track of EX-1). The dashboard is the customer’s window into the fleet — and the fleet’s window into the customer.
The self-service loop
The dashboard turns support requests into self-service actions: the customer upgrades a tier, adds a skill product (EX-2), pauses a service, or exports their data — without a ticket. Each self-service action is a metered event, so the dashboard both reduces support cost (S6.10) and produces revenue (the upgrade, the add-on, the renewal). The self-service loop is the operational engine of the subscription model: the customer manages the account, the meter records the value, and the renewal is a decision the dashboard makes easy.
The dashboard as the proof surface
The dashboard is where the sovereign-stack promise becomes visible: the customer can see the evidence (audit records, simulation receipts, post-mortems) that the work was done and tested. That evidence is what justifies the price (EX-1, EX-2) and what makes the dashboard a revenue engine rather than a cost center. A customer who can see their value is a customer who renews; a customer who can verify their value is a customer who refers (EX-13).
Grounded in the EX worked-example series, the S6.7 dashboard article, the SECTOR07a-40 revenue-engine article, the S6.10 support article, and the S7.15 audit article. Third article in the Round D examples track.
