Skip to content

Launch Plan

This document coordinates the AI Wallet launch across channels, assets, and partners. Objective: Sequence activities, define responsibilities, and set KPIs for a high-signal launch.

Key Insights

  • Timeline Pressure: YC deadline is Nov 10 @ 8pm PT (5 days away). The window of opportunity is narrow - AI landscape is evolving rapidly, and execution must be now. If doing YC, it has to be optimized for the next cohort that starts in two months.
  • Wedge: dev-first identity + consent + budgets layer that rides existing rails (OpenRouter PKCE, Vercel AI Gateway), not "another router." Cross-router end-user wallet + consent + discovery network for AI tools.
  • Positioning: "AI Wallet works with OpenRouter & Vercel" — neutral, complementary, distribution-first; publish small "Works with AI Wallet" directory and co-marketing. Think "Stripe + OAuth for AI" not "an app store."
  • 2–3 week solo build plan: Week 1 PKCE login + caps/kill-switch; Week 2 dashboard, consent receipts, Stripe top-ups; Week 3 Vercel Gateway compatibility + 3 starter integrations. Key is shipping v1 faster and getting 3–5 good design partners.
  • GTM motion: recruit 3 indie AI apps as design partners; offer rev-share; push "cross-app consent receipts & budgets" as the hook. Focus on indie tools + small SaaS. Lead with partner-friendly messaging.
  • Dual-track YC + Angels: Don't distort roadmap for arbitrary deadlines. Real usage + LOIs matter most. A BS vanity LOI doesn't move YC or good investors. Focus on shipping MVP fast → get 3–5 real design partners → use that to talk to both YC and angels/VCs.
  • Exposure Risk Management: The market already knows "AI wallet / billing / agents infra" is a thing. Your real edge will be how fast you ship, how well you design the dev experience, and how quickly you get real apps + users plugged in.
  • Risks to address: commoditization (routers/gateways), abuse/COGS spikes, provider terms, and stored-value rules; defensibility comes from end-user identity + UX + distribution.

Sources

  • archive/AI_Wallet_Topical_Threads/GTM-01Nov25-ChatGPTPlus.pdf
  • archive/AI_Wallet_Topical_Threads/YC-VCMarket-ExposureRisks-05Nov25-ChatGPTPlus.pdf

Decisions/Implications

  • Go US-first; keep scope tight (no model router). Ship login button + budgets + receipts that integrate OpenRouter/Vercel.
  • Use non-custodial, non-redeemable credits (Stripe; optional USDC) with strict per-user/app budgets and anomaly locks.
  • Lead with partner-friendly messaging: “Powered by OpenRouter,” Vercel template; emphasize complementary distribution, not infra replacement.

Next Actions

  • Implement OpenRouter OAuth PKCE; store app connections; enforce per-app caps and kill-switch.
  • Ship dashboard with usage, budgets, revocation, and downloadable JSON consent receipts.
  • Add Stripe prepaid credits (optional Coinbase Commerce); keep sessions short-lived; avoid long-lived keys.
  • Add Vercel AI Gateway compatibility and publish 3 starter integrations (Next.js, agents starter, CLI).
  • Run a design-partner sprint (3 indie apps), offer rev-share, request a doc link/listing from OpenRouter/Vercel.

Additional Evidence — Excerpts (YC-VCMarket-ExposureRisks-05Nov25-ChatGPTPlus.pdf)

  • Optimize for shipping + LOIs over artificial deadlines; dual‑track YC + angels to maximize credible traction during launch.
  • Track leading indicators tied to GTM: #integrations, budget enforcement events, receipt exports, partner pipeline velocity.

Suggested Sections

  • Launch objectives and scope
  • Timeline and phases
  • Assets and owners
  • PR, announcements, and partners
  • Community and developer programs
  • KPIs, monitoring, and fallback plans