Notion
2018–19
Simultaneously seeded YC + 500 Startups + Techstars portfolios + designer Twitter.
Over half of YC's recent batch became customers. 95% organic traffic.
First Round Review
Internal — for review
Marco Avila · 2026-05-11 · v1
Zunou works inside.
Now we make it work outside.
The product is alive because the density is there — every meeting on the same calendar, every chat in the same workspace, every decision routed back to the right person. The AI is useful because it has context. Take the context away and the AI is a chat box.
The 12-month question, then, is not "how do we sell an AI Chief of Staff" — it is "how do we manufacture that density inside small, defined groups in our home market, fast enough to matter, before the global incumbents close the window?"
¥30M ARR
Aspirational KGI
Within 12 mo of synchronized launch
4 + 4,000
Communities × TAI alone
Synchronized launch — sympathetic detonation
~6 months
To stop-or-go decision
Pre-committed PMF stage-gate
00 · Background
Zunou is a Japanese AI Chief of Staff company.
Anysigma is a partner working on its go-to-market.
The product: Zunou records executive-team meetings, extracts decisions and action items, surfaces commitments, and routes follow-ups via adaptive agents. Voice + chat assistant on the front end. Multi-team workspace on the back end. Currently waitlist-only with a PWA shipped end-April 2026.
Company nationality: Japanese. Founder Malek Nasser is based in Japan. The team is international. Japan isn't an "expansion target" — it's the home market. This proposal is about how a Japan-based company should launch in Japan, where the leverage is highest.
The opening: the "AI Chief of Staff" category has an empty seat in Japan. Xembly (the US category leader, $20M raised) shut down in June 2024. The remaining US entrants (alfred_, Klaio, Ashley AI) are consumer-priced individual tools with no Japanese localization. The category window in Japan is open for roughly 6–9 months before Notion AI / Slack AI / Microsoft Copilot ship comparable cross-app surfaces.
The proposal you're about to read answers one question: how do we manufacture density inside small Tokyo communities, fast enough to matter, before that window closes?
01 What this is
A proposal, not a verdict.
Every number here is a hypothesis. Every choice a defensible best-guess. If you finish reading and have no objections, we haven't written it well enough.
What this is
- ·A proposal grounded in evidence, with citations.
- ·A framework with a stop-or-go decision built in.
- ·A contract for what we instrument from week one.
What this isn't
- ·A final answer — strategy is a living document.
- ·A request for consensus — explicit objections preferred.
- ·A sales pitch — this is internal alignment.
02 Three things changed
The window is open right now. It won't be in 12 months.
A category leader exited. Japan's adoption tipped past 30%. Every productivity app is racing to embed agents.
Xembly
US category leader exited
June 2024 — $20M raised, customers Salesforce / Qualtrics / Twilio.
Source: GeekWire 34.6%
Japanese firms now use generative AI
March 2026 · Yomiuri Shimbun / Teikoku Databank · n = 23,349 firms · +14.2% considering.
Source: BigGo Finance summary 40%
Of enterprise apps will embed AI agents by EOY 2026
Up from < 5% in 2025.
Source: Gartner press release The counter-pressure: Gartner reports 88% of AI agent pilots fail to graduate to production — evaluation gaps (64%), governance (57%), reliability (51%). Most buyers have been burned. Our positioning is the response to that wound: not another agent pilot — the morning briefing your team will actually use tomorrow.
03 The architectural moat
MCP-native. The cross-app moat is in the protocol, not in marketing copy.
Notion AI sees Notion. Slack AI sees Slack. Microsoft Copilot sees M365. Zunou sees the entire Model Context Protocol ecosystem.
10,000+
Public MCP servers (Mar 2026)
Slack · Notion · Linear · Salesforce · GitHub · Google Workspace · M365 · Stripe · Sentry · Vercel · Supabase · Figma.
Source: DigitalApplied adoption stats 4,750%
MCP SDK download growth in 16 months
2M / month at launch (Nov 2024) → 97M / month (Mar 2026).
Source: Pento — Year of MCP 92%
Of new agent frameworks ship with MCP built-in
LangGraph · CrewAI · AutoGen + OpenAI / Microsoft / Google all on board.
Source: The New Stack — Why MCP won MCP went from "Anthropic-led standard" to industry-default standard between mid-2025 and early 2026. Anthropic donated the protocol to the Linux Foundation's Agentic AI Foundation in December 2025 — co-founded by Anthropic, Block, and OpenAI. Building bespoke OAuth clients per integration in 2026 is like building bespoke auth in 2018.
We adopt the protocol as a host and inherit the entire server ecosystem. Engineering effort to support our top 25 integrations collapses from ~25 OAuth implementations to 1 MCP host + 25 documentation pages.
Notion will not expose Slack via MCP. Slack will not expose Notion via MCP. We aggregate them.
04 The category right now
An empty seat in Japan. Six commoditising entrants globally. Three incumbents that will eventually compete.
The accurate answer to 'who else is doing this in Japan' is short. The answer to 'who could do this from a position of distribution' is longer.
| Competitor | Where | Status (May 2026) | Threat to Zunou |
|---|---|---|---|
| Xembly | US | Discontinued June 2024 | None — exited the market |
| alfred_ | US / global | $24.99/mo, individual | Low — wrong price point, no JP localization |
| Ashley AI · Klaio · Alyna | US / EU | Active, individual-tier | Low — no JP presence |
| Notion AI | Global · JP language ✓ | Notion-internal data only | High on commodity surfaces · low on cross-app agentic |
| Slack AI · MS Copilot | Global · APAC growing 19% YoY | Single-app surface; embedded distribution | Highest long-run threat — but neither will localize Keigo / Ringi |
| Otter · Fireflies | Global · partial JP | Meeting transcription | High on transcription · low on agentic CoS |
Japanese AI companies = partners, not competitors
Sakana AI ($135M Series B, Nov 2025), LayerX ($100M Series B, Sep 2025), ELYZA (KDDI-backed), Rakuten AI 3.0 — all sell foundation models or back-office automation. None compete with the exec CoS surface. The right move is co-marketing (joint PR Times release, joint AiSalon Tokyo demo) — not competing.
The 6–9 month window
Notion AI / Slack AI / Microsoft Copilot will ship cross-app agentic surfaces in the medium term. Zunou's defensibility is three things they will not build: cross-app context (architectural — see §03 MCP moat), JP-localized affordances (Keigo, Ringi), and the community-distributed habit loop.
05 The mechanic
Density manufactures product-market fit.
Not features. Not virality. Density — the threshold past which a small group's behavior changes.
Slack only becomes Slack at ~2,000 team messages — past that, retention jumps to 93%. Facebook only became Facebook when users hit 7 friends in 10 days. Below that threshold, users churn. Above it, they stay for life.
Zunou's working hypothesis — refit monthly against real cohort data:
5
Colleagues from the same community, active
1
Connected calendar
3
AI actions accepted within 14 days
The launch mechanic that produces this density is the part of the strategy that sounds unusual. Instead of launching one Tokyo community at a time (the Eventbrite playbook — city-by-city, the "campus model"), we light four overlapping communities in the same week, picked specifically because their members already see each other.
The physics term for this is sympathetic detonation — adjacent explosive charges igniting each other through shockwave coupling. The growth-theory term is percolation threshold — the moment a sparse graph flips from disconnected clusters into one giant connected component.
In plain terms: an attendee at AI Tinkerers Ginza on Tuesday sees three people at Venture Café Toranomon on Thursday. By the end of the launch week, "everyone I know is on Zunou" becomes literally true inside the Tokyo English-speaking founder graph.
One launch leaks. Four overlapping launches chain-react.
06 The four
Tokyo. Same week. Synchronized.
Not picked for prestige. Picked because their members already overlap — verified by roster sampling before launch.
TAI (Tokyo AI)
4,000+ members · Monthly meetup · Connpass · Slack
Largest technical AI community in Japan. Engineers, researchers, investors, PMs. Cross-cuts every other community in our launch graph.
AI Tinkerers Ginza
~200 selective · Monthly demo nights
Highest-signal builders — the people who write the tools other engineers adopt. If they pick up Zunou, it spreads from there.
Tokyo Founders Group
~150 operators · Private list
Operator-founders — exactly Beachhead A ICP. Bilingual, English-first leadership at Tokyo scale-ups.
Venture Café Toranomon
Weekly rotating · Thursday physical gathering
Highest-frequency repeated touchpoint in Tokyo. Same place every Thursday — compounding density through repetition.
07 How it actually unfolds
Five phases. Each gated on readiness, not on the calendar.
We don't promise dates we can't keep. We promise readiness gates the team agrees on in advance. Earliest plausible launch is summer 2026; later is fine if Phase 0 isn't clean.
- Phase 0 · Foundations
Ship the cost guardrails and platform readiness checks.
Token budget meter + Haiku/Sonnet routing tier (M5). JP landing page on
zunou.anysigma.com. Magic-number counters in the PWA. Events-feed v0 (Connpass + Doorkeeper public APIs). Validate 4 launch communities have ≥30% member overlap via roster sampling. Gate: all six items shipped, or no launch. - Phase 1 · The synchronized launch
Four Tokyo communities, same week.
Week 1: AI Tinkerers Ginza demo + Tokyo Founders private launch. Week 2: TAI presentation + Venture Café Thursday Gathering. Same-week PR Times release. Member-of-N badge live in product. Gate: 100 signups across the four, ≥30% calendar-connected.
- Phase 2 · IVS Kyoto + density push
Convert the conference into ARR-credible logos.
IVS LAUNCHPAD pitch (or side-event regardless). Booth with live "summarize this booth's pitches" demo. Pre-conference auto-prep emailed to RSVP'd attendees who connect calendar. Gate: NSM ≥ 60 WAU past magic number by end of phase.
- Phase 3 · Density compound + first paying logos
Prove paid conversion before the 6-month free runway expires.
First paid logo + PR Times release. Akai Wagon / Indelible portfolio rollouts. "This Week in Tokyo" digest hits 5,000 weekly uniques. Ringi automation alpha to 3 enterprise design partners. Apply for METI IT subsidy. Gate: ≥5 paid logos, MoM growth ≥ 20%.
- Phase 4 · Stage-gate review
The single yes/no/extend decision against six PMF criteria.
~6 months after Phase 1 launch. NSM ≥ 200 · One launch community at 25%+ density · 35%+ activation in 14 days · ≥3 paid logos · Inference ≤¥600/AU/mo · Member-of-N ≥ 15%. Hit ≥4 → fuel. ≤2 → pivot. 3 → extend 60 days.
- Phase 5a · If PMF — fuel
Raise sponsored-seat caps · open communities #5–10 · begin SI partner conversations.
NTT Data / Fujitsu / Itochu for the year-2 enterprise lane. Akai Wagon + Indelible portfolios fully active. Reach ¥30M ARR by month 12 of active rollout. Goal: KGI hit.
- Phase 5b · If pivot
Rotate the wedge — most likely Ringi-first vertical or events-only product.
Re-run validation (10 calls in 4 weeks) on the new wedge. Keep the four community partnerships warm; don't burn them. Aim to re-launch a focused product within 90 days.
08 Prior art
The pattern repeats. We're not improvising.
Four billion-dollar outcomes. Each manufactured density inside overlapping groups before going broad.
Discord
2015–16
Won gaming guild leaders ('supernodes') first; shipped Twitch integration as cross-community accelerant.
133% MoM growth at 3M users.
Growthcurve case study Figma Community
2019–20
Public gallery of design files / templates / plugins → SEO + activation + pull-mechanism.
300+ creators, 600+ public files. Became how non-users discovered Figma.
First Round on Figma's 5 phases Lenny's Newsletter
2020+
Free weekly newsletter for 9 months before charging anything; paid Slack as the dense layer.
1M subscribers by 2024.
Growth In Reverse 09 What we're committing
One number is a commitment. The rest are working hypotheses.
We're explicit about which is which. Pretending the budget envelope or per-user cost is locked-in would be dishonest at this stage.
¥30M ARR
Aspirational KGI
Within 12 months of synchronized launch · ≥20% MoM in second half
¥600 / user / mo
Working free-tier inference cap
Hypothesis to test against real consumption. Will refit at month 1.
¥18–24M
Working budget envelope (TBD)
Refine after Phase 0 produces real usage data.
Real envelope = (observed per-user inference × user count) + (community partnerships we choose to fund) + (line items we ratify). Don't make hasty assumptions.
10 What could break this
88% of AI agent pilots fail to graduate to production.
That's the Gartner finding for 2026. Most enterprise buyers have been burned, or seen peers burned. Our discipline is the response.
Source citations on every AI output. Addresses Gartner's #1 blocker — evaluation gaps (64% of failed pilots). Every action Zunou takes is anchored to the meeting / message / document it came from.
Human-in-the-loop on every external action. Addresses governance friction (57% of failed pilots). AI drafts; humans send. We never auto-act on someone's behalf.
Refuse to ship anything below 65% acceptance in beta. Addresses model reliability (51% of failed pilots). The metric is gated — if a feature can't beat the bar, it doesn't reach launch.
11 The moment we'll know
A pre-committed stop-or-go decision in ~6 months.
No 18-month death march. Six PMF criteria; three possible outcomes; one explicit rule we agree to in advance.
≥ 4 of 6
Fuel
Open communities #5–10. Raise sponsored-seat caps. Push toward the KGI.
3 of 6
Extend 60 days
Then re-decide. Don't force it; don't kill it prematurely either.
≤ 2 of 6
Pivot
Most likely candidates: Ringi-first vertical, or events-only product.
The six criteria: NSM ≥ 200 weekly active users past the magic number · One launch community at 25%+ density · 35%+ activation in 14 days · ≥ 3 paid logos · Inference cost ≤ ¥600 / AU / mo · Member-of-N ≥ 15%.
12 The ask
Seventeen decisions. Default = ship.
We don't need consensus — we need explicit objections so we can address them or proceed with the disagreement noted. React on each.
Strategy & launch · 1–13
01
Geographic focus — Japan-led for 12 months
Home market; second geography sequenced post-PMF, not preemptively.
default = ship
02
KGI — ¥30M ARR within 12 months of synchronized launch
≥20% MoM in the second half. Open: when the 12-month clock starts, given platform readiness gates Phase 1.
default = ship
03
NSM — WAU past magic number, in a partner community
Knowing it grows slowly at first.
default = ship
04
Magic number (v0) — 5 / 1 / 3 in 14 days
5 colleagues from same community + 1 calendar + 3 AI actions accepted, in 14 days. Refit monthly.
default = ship
05
Synchronized 4-community launch
Yes, or phase 2+2?
default = ship
06
Sponsored-seat cap — ¥720k worst case
50 members × ¥600 × 6 months × 4 communities. Bounded liability vs blanket 'free for a year'.
default = ship
07
Public events feed — before / with / after waitlist?
Connpass + Doorkeeper APIs + Lu.ma at launch.
default = ship
08
Calendar as gate
Accept that users without calendar see a deliberately broken-feeling product.
default = ship
09
Budget approach — methodology over total
Per-user inference math + sponsored-seat caps + line-item placeholders. Total ~¥18–24M is a working estimate, not a commitment.
default = ship
10
Stage-gate rule — ~6 months after Phase 1 launch
≥4 of 6 PMF criteria → fuel; ≤2 → pivot; 3 → extend 60 days.
default = ship
11
Adopt Masaru's positioning angle as the lead message
“Strategy in Notion. Tasks in Asana. Decisions in Slack. Good luck.”
default = ship
12
Retire HN / PH / IH and cold-LinkedIn
Replace with warm-intro + community + earned media.
default = ship
13
Community-discovery direction (A / B / C)
A = passive emergence (default); B = lightweight in-product recs (Phase 3+ test); C = community discovery as core surface.
default = ship
Operational gaps · 14–17
14
Pricing v0 — adopt tier shape + self-serve upgrade flow
From §16.5 gap audit (S1). Free + ≥¥3,500/mo paid. Refined via validation calls.
default = ship
15
Support model v0 — Marco + Malek covering JP/EN business hours
From §16.5 (S2). In-app widget + Slack channel. First CSM hire post-day-180 if Phase 5a fuel.
default = ship
16
Attribution v0 — last-touch for cohort analysis
From §16.5 (M2). Revisit at day 90 once data flows.
default = ship
17
Loop 6 commitment — invest product eng in meeting-prep viral loop
From §4.6 Loop 6. Loom rode this exact loop to 25M users — every shared video is an ad.
default = ship
13 Honest about what's missing
What we still need to build before launch.
A real plan names its gaps. Four operational gaps surfaced in the audit became Decisions 14–17 above. Here's the rest of the list.
Strategic · 5 gaps
- · Pricing v0 (tier shape + self-serve upgrade)
- · Customer support model (who answers in JP / EN, on what channel)
- · Crisis / outage playbook for launch week
- · Hiring plan tied to day-180 stage-gate
- · Advisor / investor update cadence
Product · 7 gaps
- · Mobile / PWA experience details
- · Account deletion + data export (APPI)
- · Team admin / permissions UX
- · Notification preferences
- · Performance budget + JP CDN
- · Accessibility (WCAG AA)
- · Error recovery during meetings
GTM artifacts · 8 gaps
- · Onboarding email copy (cadence ready)
- · Founder demo script for AI Tinkerers
- · Community-owner pitch deck (separate from this)
- · Investor pitch deck
- · Partnership MoU template
- · PR Times release calendar
- · JP press relationships
- · Customer reference library (Phase 2)
Measurement + risk · 8 gaps
- · Cohort analysis cadence (Mon / first Friday)
- · Attribution model (last-touch v0)
- · Qualitative feedback loop post-launch
- · Churn / exit interview process
- · Single-founder dependency contingency
- · Competitive-event response (Notion AI launch, etc.)
- · Launch-community-cancellation backup
- · Anthropic API outage graceful degradation
Tagged: MUST before Phase 1 · SHOULD before Phase 2 · DEFER to Phase 3+. The 17 decisions above resolve the highest-priority gaps. The remaining 24 need owners, dates, and tracking — Phase 0 work items.
14 How to engage
React on the 17. Push back specifically. Default = ship.
We don't need consensus — we need explicit objections so we can address them or proceed with the disagreement noted.
If you're on board
A single thumbs-up reply on the 17 is enough. We move forward and lock the Phase 0 owners + dates.
If you have a concern
Name the specific decision number + the alternative you'd ratify instead. We'll add it to the agenda for the live discussion.
Three ways to respond
Reply to Marco
Email or Slack DM. Decision number + ✅ / ⚠️ / ❌. One line each is fine.
Team thread
Slack thread on the launch channel. Everyone sees the reactions at once — fastest path to alignment.
Live review slot
30-min decision meeting once we have written reactions. Calendar invite from Marco when scheduled.
"If you finish reading this and have no objections, we haven't written it well enough."
15 The receipts
References.
Every numerical claim above traces back to a public source. Listed here for anyone who wants to verify or go deeper.
Market & competitive
- GeekWire — Xembly discontinued service June 2024
- BigGo Finance — Yomiuri/Teikoku JP gen-AI adoption 34.6%
- Gartner — 40% of enterprise apps will embed AI agents by EOY 2026
- Joget summary — 88% of AI agent pilots fail to graduate to production (Gartner)
- TechCrunch — Sakana AI Series B ($135M at $2.65B valuation)
- TechCrunch — LayerX Series B ($100M)
Model Context Protocol
- Anthropic — Introducing the Model Context Protocol (Nov 2024)
- Anthropic — Donating MCP to the Linux Foundation (Dec 2025)
- Pento — A Year of MCP: from internal experiment to industry standard
- The New Stack — Why the Model Context Protocol won
- DigitalApplied — MCP adoption statistics 2026 (10,000+ servers, 97M SDK downloads)
- Wikipedia — Model Context Protocol (neutral overview)
Growth & PLG benchmarks
- Mode — Facebook's "7 friends in 10 days" aha moment
- First Round Review — Notion marketing playbook (YC + designer Twitter seed)
- Growthcurve — How Discord grew (133% MoM at 3M users)
- First Round Review — Figma's 5 phases of community-led growth
- Growth In Reverse — Lenny Rachitsky's path to 1M subscribers
- Wikipedia — Sympathetic detonation (physics)
- Wikipedia — Percolation threshold (statistical physics)
Japan-specific context
- White & Case — Japan's first AI law (2025, promotion-focused)
- OECD.AI — METI subsidies for AI (50–66% of project cost reimbursed)
- IDC — Japan AI infrastructure 7× growth ($5.5B by 2026)
- SecurePrivacy — Japan APPI compliance (2025–26 enforcement)
- DemandSage — Slack statistics 2026 (APAC 19% YoY, Japan 24.46% of traffic)
- Tokyo AI (TAI) — community page (4,000+ members)
- AI Tinkerers Tokyo (Ginza chapter)
- Venture Café Tokyo (Toranomon Thursday Gathering)
AI cost & infrastructure
- Anthropic — Claude API pricing (Haiku / Sonnet / Opus)
- OpenAI — API pricing (GPT-5 family)
- Google — Gemini API pricing
- BenchLM — Claude API pricing 2026 reference
Behavioral design
Last verified: 2026-05-11. If a source url is broken or you want a section traced to a specific footnote, ask Marco. The detailed source-by-claim mapping lives in the internal strategy markdown.