§1The pick: Transparency Reporting
One feature from a 34-minute demo covering twenty-one. The evidence stack that made it this one:
- It's a provable gap. Transparency reporting is named across kodexglobal.com, but has no dedicated page — the site answers it only as a section and scattered bullets — while narrower features (Cost Recovery, Sign in with Kodex) have full pages. FOUND
- Their own motion undersells it. By the demo's own framing, reporting is the third act of a three-act walkthrough — and live sales calls, even hour-long ones, rarely reach it. A product page is precisely the async channel for what sales calls structurally never reach. FOUND (paraphrased here; verbatim sourcing in the submitted working doc)
- The claim is page-ready. "Completely automated, no input required from your team — simply using the platform, these reports get generated." None of the four credible competitors (Safari SOP, Exterro Subpoena Manager, DISCO Request, GovTransfer) leads with automated transparency reporting in their public marketing — checked, though not exhaustively ASSUMED — and none publishes requester verification, which the reports inherit their trustworthiness from; they all start work after an unverified document arrives. FOUND
- External urgency exists now. EU DSA transparency obligations; the e-Evidence Regulation operational August 18, 2026 with 10-day / 8-hour SLAs and fines to 2% of global turnover; post-fake-EDR scrutiny of how companies handle government requests. FOUND
- It has a story. Everything Kodex does is invisible outside the legal team. The transparency report is the only artifact the outside world ever sees — it lands on the public trust page. The feature nobody demos is the only one your users ever see.
- Their homepage validates the pain in their own copy. The third problem card on kodexglobal.com reads: "You lack the data to generate transparency reports, respond to audits and regulators, provide strategic insights to leadership." They name the pain on the front door — then never give the answer a page. FOUND
The demo's reporting footage was its weakest: slow generation, synthetic data they apologized for. So the page sells the outcome — audit-ready numbers, zero marginal effort, public trust — never the pixels. Runner-up was the API/automation layer ("what makes Kodex so powerful," their words), which serves the developer audience the PMM job posting names. Rejected: an API page already exists, developer marketing is the heaviest lift on a four-hour clock, and the legal/compliance buyer is the one signing checks today.
§2The buyer
Daily user / champion: legal ops · trust & safety · compliance analysts. Reference case: Coinbase's 5–6 person Global Intelligence team handling 4,000–5,000 requests a year. FOUND
Economic buyer: CLO / CCO — the Coinbase champion reports to the CLO. FOUND Secondary: CISO gates security; finance touches cost recovery; comms/policy owns the public trust page. ASSUMED
The archetype: compliance professionals live an administrative nightmare — understaffed and underfunded because they're read as a cost center (they don't grow revenue or AUM), personally exposed in a highly regulated environment, and their work is invisible until the day a failure makes it very visible. This comes from years working with exactly these teams at Red Oak. LIVED
The buyer insight, in one move: the transparency report is the one moment compliance work becomes visible value — to the public, to regulators, and to leadership. We are not selling a reporting feature. We are selling the cost-center-to-trust-asset flip.
Pain, concretely (the status quo): request data scattered across inboxes, ticket queues, and spreadsheets → reporting season starts with reconstruction → numbers nobody fully trusts get published anyway → zero bandwidth left to analyze trends or defend resourcing. Manual-process baseline documented across the category. FOUND Specific workflow details. ASSUMED
§3Positioning
For legal and compliance teams at companies holding user data, who must account — publicly, internally, and to regulators — for how they handle government data requests, Kodex Transparency Reporting turns the requests you already process in Kodex into audit-ready transparency reports and live operational dashboards. No spreadsheets, no quarter-end reconstruction, no numbers you can't defend. Unlike hand-built trackers or BI queries over ticket exports, every figure traces to a verified, auditable request record.
Category posture: a feature page within Kodex's platform story — not a new category claim. It inherits the network moat (15,000 agencies · 140,000+ verified agents · 190 countries) and extends it to the numbers: you can only auto-generate a trustworthy report if every request came through one verified front door. The page quietly re-sells the whole platform.
Hero line (chosen from four candidates): "Your transparency report writes itself." Direct, benefit-first, and the word "itself" carries the entire zero-effort claim. Runners-up: "The proof is a byproduct" (conceptual, needed a subhead to land), "Every request counted. No one counting." (on-voice but narrower), "Compliance, visible." (boldest, most abstract). It also extends a line Kodex already runs — "The work reports itself," on their request-management page — from a passing tagline to a page thesis. Lineage, not collision.
§4Message house
Roof: Your transparency report writes itself.
Pillar 1 — Zero effort by design
Reports generate from platform activity itself; dashboards are live, not compiled. Breakdowns by legal process, country, case nature; response-time and production stats; white-label output. FOUND Counter-position: the quarter-end spreadsheet scramble.
Pillar 2 — Numbers you can defend
Every request entered through one verified front door; full per-case audit trail (timeline, actions, Bates-numbered productions). FOUND This is the moat compounding: competitors' reports would summarize unverified intake.
Pillar 3 — From cost center to trust asset
Public: the report on your trust page. Regulator: audit-ready accounting under DSA / e-Evidence-era scrutiny. FOUND Internal: dashboards that turn "trust us, we're drowning" into a resourced argument — the first feature that pays the compliance team back. LIVED framing, dashboard capability FOUND
§5Voice & page architecture
Voice: Kodex's current-generation product pages, not their older persona pages — short declarative fragments ("One button. Real time. Every request."), concrete over abstract, email/fax/spreadsheet as the villain, recurring lexicon: verified, network, one place, audit trail, the work. No "AI-powered" filler. No fear beyond what the evidence carries.
Structure mirrors their newest page template, extracted from their live pages: announcement bar → centered fragment hero → gradient illustration panel (stylized product concept, never raw screenshots) → network stat strip → logo wall → problem section with dark contrast card → three named stages → three pillars with recreated UI vignettes → their own quote elevated to a centerpiece → FAQ → navy closer. Design tokens (navy #000040, brand blue #2d62ff, the gradient language) pulled from their production CSS; typeface matched to their licensed font by specimen comparison, settling on Figtree. One addition of my own: a light/dark mode toggle their site doesn't have. The logo wall mirrors the customer wall on their live homepage (screenshotted 2026-08-02) — site-published names only.
Hard rule: zero demo-tenant data anywhere. Every depicted table, number, and org name is invented. The demo recording never left the machine.
§6Assumptions register
| Assumption | Basis |
|---|---|
| Buying-committee shape (champion → CLO/CCO sign-off) | Coinbase case-study reporting line + lived pattern ASSUMED |
| Reports cover only requests processed in Kodex (no import of historical/outside-channel requests) | Demo shows in-platform generation only; FAQ on the page answers it honestly ASSUMED |
| White-label output is generally available | Seen in one demo tenant ASSUMED |
| Reporting cadence framing ("quarter-end scramble") | Transparency reports typically publish semi-annually; scramble framing kept generic ASSUMED |
| Kodex would ship this page in their current new-generation voice | Two copy generations visible on their site; newest pages got the sharp rewrite ASSUMED |
Each of these is a day-one question with the real messaging doc and persona deck in hand.
§7How AI was used
Fully documented — pipeline, tools, and the human/AI split — on The Build page. The one-line version: Claude Code ran as a parallel research team, a local video-intelligence lab, and a build partner; every judgment call — the feature pick, the positioning angle, the hero line, the design vetoes — was mine, made on evidence the system assembled.