# TODO — investor-v1 deck

Open questions and pending tasks for the early-seed deck. Add, remove, and check-off as the deck iterates.

## Slide-specific open questions

### Slide 01 (cover + positioning)
- [ ] Reconcile **«builders» vs «creators»**. Slide 01 uses «builders» per Mark's voice-note 2026-05-09. The locked positioning in `raw/positioning.md` and `decisions/2026-05-08-positioning-growth-stack.md` uses «creators». Need to either (a) update raw/ + decision file to «builders» (recommend), or (b) revert slide to «creators». Decision needs Mark.
- [ ] Verify ecosystem user-base numbers: Telegram (~1B / ~300M super-active), World, Roblox, Line, Kakao, WeChat, LinkedIn — current numbers in slide are rough public estimates as of 2026; Mark to validate before pitch use.
- [ ] Choose multi-market visual treatment: (a) Telegram in branded blue + small «1 of N» tag, (b) Telegram in pill that swaps to other ecosystems, (c) ghost-row of other ecosystem logos under headline at low opacity. Currently leaning (c).
- [ ] Add ecosystem-by-ecosystem note: what stays similar / what changes when expanding (one paragraph per ecosystem — e.g. Roblox is UGC mini-experiences, WeChat is mini-program ecosystem, etc.). Useful for the «detailed» version of slide 01.

### Slide 02 (insight: perimeter)
- [ ] Decide which **example to lead with**: housewife (audience-expansion framing) or vibe-coder pain (tunnel-localhost). Different audiences land on different examples.
- [ ] Final list of **services replaced** (the «10 logos» wall): currently 11 items in the table. Trim or expand?
- [ ] Show **actual prices** on the «before» side or just service names? Compelling vs. verify-burden trade-off.
- [ ] Should **AI-native control surface** get its own micro-callout on slide 02, or stay folded inside the perimeter list?

### Slide 03 (what we built)
- [ ] **Crossed-out prices on each Apps Pro block** — show actual numbers (more punchy, more verify) or just competitor names (simpler).
- [ ] Whether the **App Store side** needs a sub-list of capabilities (discovery / earn / reviews / collections) or a single summary line + visual.
- [ ] Does **Apps Pro Academy** get a corner-callout here, or its own slot later in deck?
- [ ] Whether to expose the **AI-native connector** here vs. on slide 02 (currently mentioned in both).

### Slide 04 (flywheel)
- [ ] Show **two flywheel mechanics** (referral + community-vote) or **all three** (incl. data-network-effect). Currently leaning two for clarity.
- [ ] Tagline: **«We own the main traffic»** vs. **«We are the orchestration layer»** — different framings, different audience reactions.
- [ ] Surface specific mechanic icons (referral / vote / push / track) on diagram, or keep diagram pure?
- [ ] Weave in one founder quote? Would humanise; need a real Apps Pro user willing.

### Slide 18 (ask)
- [ ] **Round size** — Mark to fill
- [ ] **Valuation / structure** — Mark to fill
- [ ] **Lead investor targets** — Mark to surface from web3-VC database (3 000 contacts) + warm network
- [ ] **Specific hires** to enumerate in use of funds (1-2 senior roles?)
- [ ] **Closing target date / timeline**

### Trailing slides (09-18)
- [ ] **Renumber** to 05-14 (since old 05-08 moved to `_appendix/`). Housekeeping; not blocking.
- [ ] Add **dual-version (visual + detailed)** treatment to traction slides 11-13 — Mark wanted dual-version pattern; currently only 02-04 have it.

## Cross-deck open questions

- [ ] Lead Apps Pro traction with **«13» or «25» sales**? Loom call (Mark) said 13; Anton call (same day, later) said 25. Reconcile to one canonical number.
- [ ] Decide on **dual-version pattern scope** — apply to all main slides (1-4 plus 9-10 plus 18) or just 1-4?
- [ ] Audit **all slides** for the «builders» / «creators» wording once decided.

## Source-of-truth propagations pending

- [ ] Add **«perimeter»** framing to `raw/positioning.md` and `raw/business-model.md` — it's structurally bigger than just a deck slide.
- [ ] Update `raw/creator-tools/market-research-ai.md` to call out **«verified market data, not Perplexity-style scraping»** framing.
- [ ] Consider lifting **«perimeter»** to its own `raw/perimeter.md` as a top-level concept (alternative to embedding in positioning/business-model).
- [ ] Update `raw/positioning.md` to broaden positioning scope: «messenger / superapp ecosystems with native mini-apps» as the long-term frame.

## Visual / design tasks (handed off / external)

- [ ] Designer brief for **before/after visual on slide 02** (10 logos chaotic → one Apps Pro box clean)
- [ ] Designer brief for **split-view with crossed-out prices on slide 03**
- [ ] Designer brief for **flywheel diagram on slide 04**
- [ ] Logo file + brand colours finalised for cover slide
- [ ] Phone-frame mock of @appss Mini App for slide 03

## Appendix / Q&A backup

- [ ] **Competitive landscape** detail (Mixpanel / AppsFlyer / Mailchimp / Tagger / Modash / Figma / Cursor / etc.) — covered partially in `_insights-pool.md` and slide 03; needs a single Q&A-ready slide
- [ ] **Financial projections** sheet (post-funding plan, 12-18 month outlook)
- [ ] **Real case-studies** (1-2 Apps Pro customers willing to be referenced)
- [ ] **Team bios extended** (Mark, Anton, CTO with photos and links)
- [ ] **Designer Studio deep-dive** slide
- [ ] **Market Research AI demo flow** slide (or recorded GIF / video)

## Multi-version housekeeping

If we end up wanting multiple decks (investor-v2 with feedback iteration, partner-deck, etc.), the structure supports it:
- `deck/investor-v1/` is current
- `deck/investor-v2/` for next iteration after sample-investor feedback
- `deck/partner-v1/` for partner-specific version

## Related
- [`INDEX.md`](./INDEX.md) — running order
- [`_insights-pool.md`](./_insights-pool.md) — candidate insights for slot 02
- `../../voice-notes/2026-05-09-wip-deck-slides-1-4.md` — Mark's restructure brief
- `../../cuts/investors/narrative-arc.md` — spine