Six docs, one product story.
Pick where you want to start.
Zunou's working notes — the Japan-led GTM strategy and the engineering reality it depends on, written for the team to react to. Each doc stands alone, but the through-line is one product: from market posture down to test runner. This page is the map.
- This is six interlinked docs, not a launch page. Working notes for the team to react to, shape, and act on.
- Five pillars in chronological order: GTM names what we're shipping · Dashboard measures whether it's working · Journeys shows where users drop · Foundation is the engineering work to ship · Quality is the verification contract that keeps it standing.
- Every page is the same skeleton: top banner, hero, executive summary, numbered sections, dark closing. Once you've read one, you know how to read the others.
- Three reading paths below — pick the one that fits your time. The 5-minute skim covers the exec summaries only.
- Every claim has evidence: file:line for code, citation URLs for industry numbers, GTM ref for strategy ties. No hand-wave; press into anything that doesn't add up.
Each pillar answers exactly one question.
Hover or tap any card to open. They link laterally too — most claims in one pillar reference at least one other.
GTM
The destination
What we're shipping into the market and why now.
Three beachhead waves: warm-circle pilots via VC + venture-studio partners — Kevin Brockland at Indelible Ventures (Malaysia) first, then Northface Media (or Headline). Then TAI Tokyo pilot late July / early August 2026 (Ilya-introduced). Then layered communities. Hybrid venue sponsorship + stage-gate Feb 2027 (≥4 of 6 PMF criteria → fuel · ≤2 → pivot · 3 → extend).
Dashboard
The measurement layer
How we'll know whether the GTM is working.
Five dashboards on PostHog Cloud US (no-PII event taxonomy) + Metabase + Grafana. The Monday-morning ritual that turns the magic number from a slogan into a contract.
Journeys
The user lens
Where users drop, why, and what each drop costs.
Six end-to-end customer journeys mapped against actual code. Specific bugs (incl. "sign in twice" + iOS keeping users out), where to fix them, and how each maps to the GTM magic number.
Foundation
The build plan
The engineering work that has to land before pilot #1.
Audit-driven Tier-1 pilot blockers (15 items, ROI-ranked, ~37 person-days, 3 weeks for 2 engineers). Mortality timeline ordering: UX/onboarding first, security second, reliability third.
Quality
The verification contract
How we keep what we ship from breaking.
Standardized test stack (Vitest · Playwright · Pest · Maestro · pytest · contract via GraphQL Codegen). Definition of Done. Why-100% thesis. The current scoreboard: D+, 21 services, 2 actually run tests in CI.
Three ways through. Pick the one that fits your time.
Each path is sequential — every link opens the next stop directly at the relevant anchor.
5-minute skim
Senior reviewer who needs the shape, not the detail. Five bullets per pillar, nothing else.
- 01 Overview ← you're here
- 02 GTM exec summary 5 bullets
- 03 Foundation exec summary 5 bullets
30-minute review
Recommended path for a first-pass team review. Skip the deep-dive sections marked § in each page; agenda navigation in the left rail.
- 01 Overview
- 02 GTM TL;DR long-form
- 03 Journeys all 6
- 04 Foundation Tier 1 the sprint
- 05 Quality scoreboard + DoD the contract
Deep dive
Engineering or strategy contributor preparing to act on this. Read in order; every claim has a source or a code citation.
- 01 GTM in full 25 sections
- 02 Dashboard metrics + setup
- 03 Journeys (every step) with file:line citations
- 04 Foundation (every recommendation) with where-to-fix paths
- 05 Quality (Why 100% + Beyond coverage) the philosophy
Five rules every page follows.
Once you internalize these you can navigate any page on the site at a glance.
Every page opens with an executive summary
Five numbered bullets. Same visual treatment across all six pages. If you only read one block per page, read this one.
Section anchors use § notation
References across docs (e.g. "GTM §05", "Foundation §03") are clickable in the agenda — left rail on desktop, top scroll on mobile/tablet.
Bug claims carry file:line evidence
Recommendations carry where-to-fix paths. Every actionable item maps back to a specific spot in the zunou-services repo.
Source citations on directional claims
Numbers like 'mobile users abandon pages >3s' link to the original source (Google study, AWS measurement, etc.) — short, clickable URLs.
Restraint, not decoration
Animations honor prefers-reduced-motion. No emoji, no AI splash. The site is a working document, not a launch page.
What's moved this week.
Where to go next
Open the doc that answers the question you have.
If you only have time for one thing today: read the GTM TL;DR. If you're here to act: go to Foundation Tier 1. If you want to understand what users see: walk the Journeys.
Six docs, one through-line: turn the magic number into a product reality.