Observed constraint
Fictional users reach a dense pricing comparison with weak hierarchy and no clear path for smaller teams.
FICTIONAL DEMONSTRATION · NOT A CLIENT CASE STUDY
This page demonstrates the structure and acceptance logic of a SaveX delivery. “Northstar Cloud” is fictional; no conversion, revenue or customer result is claimed.
01 · DECISION RECORD
Fictional users reach a dense pricing comparison with weak hierarchy and no clear path for smaller teams.
A task-first comparison with one recommended plan, visible limits and progressive disclosure for enterprise detail.
A minimal two-plan layout reduced visual load but concealed material limits and increased sales dependence.
Users can identify the relevant plan, limits and next action without relying on colour or hidden content.
FICTIONAL AUDIT EXAMPLE · NOT A CLIENT FINDING
The record below uses invented data to show how a real Audit separates a visible fact from a possible impact. No live product was reviewed for this example.
| Field | Fictional example |
|---|---|
| Finding and priority | F-01 · P2 · Pricing period may be hard to compare |
| Observed fact | At 320 CSS pixels in the simulated annual state, each plan card shows the monthly equivalent but not the annual total in the same visible group. |
| Evidence | DEMO-E-01 · /pricing · 320 CSS px · annual state · first load. Simulated capture record and reproduction steps only; no real screenshot is implied. |
| Interpretation | A buyer comparing plans could miss the billing period or total. This is a hypothesis, not observed user behavior. |
| Confidence | Medium · one bounded visual inspection; no participant testing or analytics data. |
| Recommendation | Keep the billing period and payable total together within each plan card. |
| Acceptance check | At each viewport agreed for the engagement, every plan shows its billing period, payable total, material limits and next action. A keyboard user can operate the billing control and identify the selected state. |
Priority boundary: P2 means meaningful friction is visible but the reviewed task remains possible. It is not a measured loss or revenue estimate.
02 · SPECIFICATION AND CODE
03 · QUALITY EVIDENCE
| Gate | Example evidence | Claim boundary |
|---|---|---|
| Visual QA | Viewport matrix and reviewed screenshots | No unexplained critical mismatch |
| Accessibility | Keyboard path, focus review and automated scan | No unsupported compliance claim |
| Performance | Named route, build and measured environment | No comparison without a baseline |
| GEO/SEO | Metadata, crawl and structured-content review where applicable | Marked not applicable for private surfaces |
Important: the entries above are demonstration criteria only. A real engagement receives results generated from its own repository and environment.