Stratify
Internal ops

Project Kickoff 2026 05 08

docs/internal/project-kickoff-2026-05-08.md

Source updated 03. Aug. 2026

Stratify v2 — project kickoff note

Date: 2026-05-08 Status at kickoff: Starting

Historical note: This file records the original kickoff context. Implementation details have evolved (auth is now Supabase EU — Clerk and Auth.js are both dead). Treat PRD §8 (v2.1 hybrid amendment) and the project CLAUDE.md as the current source of truth.

Problem

Stratify v1.0 underestimated two bottlenecks: (1) pilot onboarding is the real critical path—not retail user onboarding—and (2) partners and co-founders already asked for a B2B API layer in v1 conversations. Deferring that layer to phase 2 wastes the validation window for the core exit thesis (API licensing to neobrokers).

What we set out to build

v2 is a real iteration on v1.0: suitability, trade propagation, Stripe Connect, single-pilot constraint, and the design system stay in scope. Pilot discovery and pilot onboarding are tightened (four-eyes approval, track-record verification, JSON-schema strategy definition). New in the MVP scope is the B2B API layer (REST + webhooks, OAuth2-style M2M keys, sandbox environment, audit log). Web-first on Next.js + Vercel; native iOS/Android only in a later phase. Execution counterparty: Interactive Brokers.

Decisions recorded at kickoff

  • Trigger: Genuine iteration; v1.0 scope largely preserved.
  • Changed / new modules: Pilot discovery & onboarding; B2B API layer (new in MVP).
  • Stack (intent): Next.js + TypeScript on Vercel; Postgres in an EU region; Stripe Connect.
  • Counterparty: Interactive Brokers (IBKR API).
  • Platform strategy: Web-first; no native apps in v2.
  • Non-goals: Native iOS/Android, crypto, derivatives/margin, proprietary custody, multi-pilot configuration, robo-advisory, social feed, US market in v2.
  • Definition of done for v2.0 (intent): B2C closed beta (one live pilot, ten test users, one end-to-end trade in IBKR sandbox under 60s) plus in parallel a B2B sandbox pilot where one neobroker completes the integration test unaided.

Open questions (at kickoff)

  • Multi-region database strategy (EU-only initially—when is multi-region required?)
  • B2B partner commercial model (flat fee vs revenue share vs hybrid)—TBD until partner 1
  • Identity provider choices for B2B API—Sprint 1
  • IBKR onboarding lead time remains on the critical path (6–12 weeks)

Next steps (at kickoff)

Start Sprint 1: repository setup (Next.js + Postgres + auth), apply for IBKR sandbox (parallelisable, long lead time), ship pilot onboarding as the first route (/pilot/onboard—identity and track-record capture).

Originally drafted via internal kickoff workflow.