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
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. The 12-month question: how do we manufacture that density inside small, defined groups in our home market — fast enough to matter?
¥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
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.
Three things changed
The window is open right now. It won't be in 12 months.
A category leader exited. Japan's adoption tipped. Every productivity app is racing to embed agents.
Xembly
US category leader exited
June 2024 — $20M raised, customers Salesforce / Twilio
34.6%
JP firms now use generative AI
Mar 2026, Yomiuri/Teikoku, n=23,349 + 14.2% considering
40%
Of enterprise apps will embed AI agents
By EOY 2026, up from <5% in 2025 (Gartner)
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 use tomorrow.
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…
4,750%
MCP SDK download growth in 16 months
2M/mo at launch (Nov 2024) → 97M/mo (Mar 2026)
92%
Of new agent frameworks ship with MCP built-in
LangGraph, CrewAI, AutoGen + OpenAI / Microsoft / Google all on board
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.
The mechanic
Density manufactures product-market fit.
Slack works at ~2,000 messages. Facebook at 7 friends in 10 days. Zunou's hypothesis: 5 colleagues + 1 calendar + 3 AI actions, in 14 days.
5
Colleagues from the same community active
1
Connected calendar
3
AI actions accepted in 14 days
Instead of launching one Tokyo community at a time, we light four overlapping communities the same week, picked specifically for member overlap. The physics term is sympathetic detonation — adjacent charges igniting each other through shockwave coupling.
The growth-theory term is percolation threshold — the moment a sparse graph flips into one giant connected component. Tokyo's English-speaking founder/AI graph is small and densely interconnected. One launch leaks. Four overlapping launches chain-react.
The four
Tokyo. Same week. Synchronized.
Not picked for prestige. Picked for member overlap — so a launch attendee at AI Tinkerers Ginza on Tuesday sees three people from the launch at Venture Café Toranomon on Thursday.
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.
Prior art
The pattern repeats. We're not improvising.
Four billion-dollar precedents. 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 What we're committing
One number is a commitment. The rest are working hypotheses.
¥30M ARR
Aspirational
Within 12 months of synchronized launch
¥600/user/mo
Working free-tier inference cap
Hypothesis to test against real consumption
¥18–24M
Working budget envelope (TBD)
Refine after Phase 0 produces real data
Real envelope = (observed per-user inference × user count) + (community partnerships we choose to fund) + (line items we ratify). Don't make hasty assumptions.
What could break this
88% of AI agent pilots fail to graduate to production.
That's the Gartner finding. 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%).
Human-in-the-loop on every external action. Addresses governance friction (57%).
Refuse to ship anything below 65% acceptance in beta. Addresses model reliability (51%).
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.
≥ 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.
≤ 2 of 6
Pivot
Most likely candidates: Ringi-first vertical, or events-only product.
The six criteria: NSM ≥ 200 · One launch community at 25%+ density · 35%+ activation in 14 days · ≥3 paid logos · Inference cost ≤¥600/AU/mo · Member-of-N ≥ 15%.
The ask
Seventeen decisions. Default = ship.
React on each: ✅ on board / ⚠️ on board with concern / ❌ object. We don't need consensus — we need explicit objections so we can address them or ship anyway with the disagreement noted.
Strategy & launch (1–13)
01
Geographic focus — Japan-led for 12 months
Home market; second geography sequenced post-PMF, not preemptively.
On board
Concern
Object
default = ship
02
KGI — ¥30M ARR within 12 months of synchronized launch
≥20% MoM in the second half. Open: when does the 12-month clock start, given platform-readiness gates Phase 1.
On board
Concern
Object
default = ship
03
NSM — WAU past magic number, in a partner community
Knowing it grows slowly at first.
On board
Concern
Object
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.
On board
Concern
Object
default = ship
05
Synchronized 4-community launch
Yes, or phase 2+2?
On board
Concern
Object
default = ship
06
Sponsored-seat cap — ¥720k worst case
50 members × ¥600 × 6 months × 4 communities. Bounded liability vs blanket 'free for a year'.
On board
Concern
Object
default = ship
07
Public events feed — before / with / after waitlist?
Connpass + Doorkeeper APIs + Lu.ma at launch.
On board
Concern
Object
default = ship
08
Calendar as gate
Accept that users without calendar see a deliberately broken-feeling product.
On board
Concern
Object
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.
On board
Concern
Object
default = ship
10
Stage-gate rule — ~6 months after Phase 1 launch
≥4 of 6 PMF criteria → fuel; ≤2 → pivot; 3 → extend 60 days.
On board
Concern
Object
default = ship
11
Adopt Masaru's positioning angle as the lead message
“Strategy in Notion. Tasks in Asana. Decisions in Slack. Good luck.”
On board
Concern
Object
default = ship
12
Retire HN/PH/IH and cold-LinkedIn
Replace with warm-intro + community + earned media.
On board
Concern
Object
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 (category expansion).
On board
Concern
Object
default = ship
Operational gaps from §16.5 (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.
On board
Concern
Object
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.
On board
Concern
Object
default = ship
16
Attribution v0 — last-touch for cohort analysis
From §16.5 (M2). Revisit at day 90 once data flows.
On board
Concern
Object
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. Fold into S-tier features.
On board
Concern
Object
default = ship
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 what stays open between now and Phase 1.
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 of these. The remaining 24 need owners, dates, and tracking — Phase 0 work items.
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.
Drop into the team thread
Slack thread on the launch channel. Everyone sees the reactions at once — fastest path to alignment.
Take a slot in the live review
30-min decision meeting once we have written reactions. Calendar link from Marco when scheduled.
"If you finish reading this and have no objections, we haven't written it well enough."