StreamVerse Connect — MVP Launch Center

PHASE 1 · P0

Foundation and product direction

Keep the business simple and make sure everything points toward the same campaign-first product.

Define the core StreamVerse product Completed: connect studios with creators, manage campaigns, distribute keys, communicate, and build creator relationships. Done Simplify the business model Creators stay free. Solo and small indie developers receive a useful free tier. Future revenue comes primarily from professional Studio, Pro / Publisher, and eventually Enterprise SaaS plans. Done Remove the old charity and donation model Remove donation systems, charity checkout, donation percentages, charity dashboards, and charity-specific business language from the current MVP. P0 Domain secured: streamverseconnect.com Keep the public product English-first and suitable for the global gaming market. Done Document the current operator StreamVerse Connect is currently operated by an individual in Finland. Forming an Oy can be reconsidered after real traction makes it worthwhile. Done Keep an MVP operating-cost budget Prefer free allowances and inexpensive infrastructure. Review hosting, database, storage, email, API, and other recurring costs before introducing new services. P0

PHASE 2 · P0

Build the complete campaign workflow

This is the core StreamVerse MVP. Everything else is secondary until this works with real users.

Authentication foundation Creator and developer authentication already exists. Continue testing account isolation, session handling, and creator/developer login flows. Existing Creator and studio profile foundations Profile, studio membership, and media-kit foundations already exist and should be preserved rather than rebuilt. Existing Persist real game listings Studios need to create and manage real games instead of relying on prototype or hardcoded game cards. P0 Persist real campaigns Create a simple campaign data model with game, studio, campaign status, requirements, deliverables, capacity, deadlines, and key availability. P0 Build creator applications Creators discover campaigns, apply with relevant information, and can see the status of their applications. P0 Add approval and rejection workflow Studios review applicants and approve or reject creators without needing a complicated workflow engine. P0 Add secure game-key management Studios add keys, assign them to approved creators, and track whether a key is available, assigned, or claimed. P0 Connect simple campaign communication Focus messaging on direct studio ↔ creator conversations and campaign-specific communication. Do not expand into a full Discord replacement. P0 Add essential notifications Start with application received, application approved or rejected, key assigned, and important campaign updates. P0 Add basic campaign and creator discovery Keep filters useful but simple. Advanced creator discovery belongs in later paid functionality. P0 Run the full two-account campaign test Test the complete workflow using separate developer and creator accounts: developer creates a game and campaign and adds keys → creator discovers the campaign and applies → developer reviews and approves → key is assigned → creator receives the key and submits content → developer reviews the submission and completes the campaign. Critical

PHASE 3 · P0 / P1

Trust, safety, and legal basics

Make the MVP safe enough for real creators and studios without building enterprise moderation infrastructure.

Terms, Privacy, and Community Guidelines Initial legal pages now exist. Keep them accurate as the actual product and third-party services change. Existing Account and data deletion information Users have a dedicated path for understanding how to request account or personal-data deletion. Existing Basic reports and owner moderation Support reporting for scams, stolen or invalid keys, impersonation, harassment, misleading campaigns, and other abuse. P0 Review permissions and sensitive data Verify Supabase RLS, public profile behavior, game-key access, studio membership permissions, Twitch data access, and account isolation before inviting larger groups. P0

PHASE 4 · VALIDATION

Run real campaigns with real users

Validate behavior before building more features.

Recruit the first creators and indie developers Start with a manageable group of creators and approximately 3–5 real developers or studios willing to give direct feedback. First users Complete the first real campaign Follow the full journey: game → campaign → application → approval → key → communication → creator content / result. Critical Interview creators and studios Ask what was confusing, what required work outside StreamVerse, what saved time, and what would make them return for another campaign. Learn Track useful MVP metrics Track registered and active creators, studios, active campaigns, applications, approvals, keys distributed, and campaign activity. P1

PHASE 5 · REVENUE VALIDATION

Find the first paying studio

Only build serious billing infrastructure after studios demonstrate that they want the product.

Get studios to run another campaign Repeat usage is stronger evidence than registrations or page views. Validate Find the first studio interested in paid tools Learn which higher limits, analytics, team tools, or workflow improvements are valuable enough to pay for. Validate Test Founding Studio if demand exists A simple early-access offer can validate willingness to pay before building a complicated subscription system. Later Introduce billing only after validation Keep the architecture subscription-ready, but do not spend weeks building billing before a studio is genuinely interested in paying. P1 Reach 1, then 5 paying studios Start tracking paying studios and monthly recurring revenue once subscriptions genuinely begin. Goal

Get StreamVerse to
real campaigns and real users.

Building the core product