CASE STUDIES
A file goes up when the client says yes.
No invented logos. No borrowed metrics. This page is the format — Symptom, Finding, Fix, Result — waiting for work we can name.
A case study is a document you can check. It is not a mood board.
HOW A FILE IS WRITTEN
| BLOCK | WHAT IT HOLDS | WHAT IT NEVER HOLDS |
|---|---|---|
| Symptom | The state before we started, in their words | A problem we invented to look busy |
| Finding | What was actually wrong, after we looked | A vendor we “selected” for a brand we don’t run |
| Fix | What we built, on which surface | A Pulse dashboard or an ERP we never shipped |
| Result | What changed, only if we can show it | A percentage with no source |
OPEN SLOTS — ZX A³ INNOVATION™
FILES
No public files yet. The first one will use the template below. Until then this list stays empty on purpose.
FILE TEMPLATE
CASE FILE — unpublished pillar: Autonomous | Adaptive | Architected surface: web | mobile | agents | iot | vlsi client: named only with written permission SYMPTOM what was broken FINDING what we found FIX what we built RESULT what changed — sourced, or omitted
FAQ