Koino StudioStart a brand
Roadmap

What ships when.
Public, dated, auditable.

We name the gap between today and v1 in writing. Every module stamped stub in the OS maps to a phase on this page. Anti-hallucination is part of the brand.

  1. v0

    Today (this branch)shipped
    • ·Landing page (animated, real design taste, proof-by-page)
    • ·Pricing page (3 tiers, real numbers)
    • ·Inquiry/waitlist (Supabase-backed)
    • ·Login (email+password, Supabase auth)
    • ·Client dashboard shell (overview, work, brain — real layout)
    • ·Team suite shell (today, clients, pipeline, agents, connectors)
    • ·Honest stub labels on every non-functional module

  2. v0.1

    +2 weeksnext
    • ·Vercel deploy at os.koino.capital + DNS
    • ·Connector grid: Figma, Notion, Drive, Stripe, Vercel, Gmail, Calendar, Resend
    • ·Stripe checkout for Studio / Operator tiers
    • ·Live Stripe milestone billing on Delivery acceptance
    • ·Brand brain export → Notion + Drive
    • ·Substrate health panel (reads ~/koino-self/discipline.log)
    • ·Connector keeper agent (rotation watchdog)

  3. v0.2

    +6 weeksqueued
    • ·Agent console: spawn / observe / override Anthropic-SDK agents
    • ·Drop drafter agent (concept → draft, rubric-scored)
    • ·Unified messaging (Gmail + LinkedIn DM + Telegram + in-app, threaded by drop)
    • ·Engagement reader agent (comments/DMs across platforms)
    • ·Public preview links for in-flight drops
    • ·Postman MCP wiring for the delivery surface

  4. v0.3

    +12 weeksresearch
    • ·Self-serve OS tier (system without the studio engagement)
    • ·Multi-brand tenancy in client dash (Atelier)
    • ·Public method docs + open rubric
    • ·First case study published

  5. v1.0

    +6 monthsvision
    • ·Three concurrent paying engagements running end-to-end inside the OS
    • ·Self-serve revenue exceeds engagement revenue (the OS, not the studio, is the business)
    • ·Agent fleet observable in real time by clients
    • ·Brand brain export becomes a portable standard