What we're building and where it stands
Muses Live is a managed UGC platform. Apps and consumer brands launch creator programs; vetted creators film short videos from Muses scripts and post them on TikTok and Instagram; the Muses team runs everything in between. Brands pay a fixed fee per creator plus a weekly charge based on views.
Four kinds of user
Every conversation, file and approval belongs to a campaign, and each campaign has exactly one lead admin from the Muses team. Brands and creators never talk to each other directly.
Sets up and watches
Creates campaigns, sets budget and weekly cap, optionally approves creators, scripts and drafts, sees analytics, messages their admin.
Films and posts
Applies through lessons and a tryout, joins campaigns, gets a daily script, uploads drafts, posts, gets paid fixed monthly pay plus a views bonus.
Runs campaigns
Muses campaign manager. Publishes job posts, picks creators, releases scripts, reviews every draft first, runs chat. Only sees campaigns they lead.
Runs Muses
Approves creators, assigns a lead admin to each new campaign, manages people, demo requests and invite codes. Sees everything.
Stack and architecture
One Next.js app on Vercel talks to Supabase for data, sign-in and live updates. Videos and files go straight from the browser to Cloudflare R2 with short-lived upload links, so large files never pass through our server. Access is enforced in the database with row-level security, not only in the app.
Solid lines are live today. Dotted lines in "To add" are the integrations the engineer owns.
Campaign lifecycle
The core loop, from a brand creating a campaign to the weekly invoice.
Pricing rules: $500 per creator per month base fee (minimum 3 creators). Performance is billed weekly on views; the rate per 1,000 views drops as weekly views rise, and spend never goes over the brand's weekly cap. All of this lives in one pricing module used by the wizard, invoices and creator pay.
Creator journey
Creators don't see the job board until a Muses reviewer approves them. Known creators can skip onboarding with an invite code.
Brand journey
Campaign states
Only the lead admin moves a campaign through staffing, live, paused and ended. Brands edit only while it's a draft.
Data model
The main tables. Everything that happens on a campaign hangs off campaigns; the creator's link to a campaign is campaign_creators.
Also: pricing_tiers, training_modules, training_attempts, training_quiz_keys, invite_codes, leads. Schema and access rules are in supabase/migrations, one file per change.
Who can do what
Enforced in Postgres with row-level security plus guard triggers on sensitive columns, so a user can't, for example, approve themselves or read another brand's campaign even with a hand-made request.
| Area | Brand | Creator | Admin | Super admin |
|---|---|---|---|---|
| Campaigns | Own brand's; edit only as draft | Ones they're on | Ones they lead | All |
| Creator approval | Only if switched on | Can't change own status | Shortlists | Approves creators |
| Scripts and drafts | Review if switched on; notes go to admin | Only scripts released to them; own drafts | Write, release, review all | All |
| Analytics | If admin shares them | Own posts | Their campaigns | All |
| Chat | Their admin only | Their admin only | Creates threads, picks members | All |
| Files | Own campaign's | Own uploads only | Their campaigns | All |
Built, in progress, and what we need from you
The product screens and flows were built in-house and work end to end. The engineer's job is to make it safe, reliable and connected before real clients and creators arrive.
- Landing page, book-a-demo, sign-up and log-in for all roles
- Brand campaign wizard with pricing slider and weekly cap
- Creator onboarding: lessons, tasks, tryout videos, 24h review, invite codes
- Job board, applications, shortlists, creator selection
- Daily script inbox, drafts, review loop, posts
- Realtime chat: files, voice notes, reactions, replies, mentions, read receipts
- Admin and super admin dashboards, approvals, people, demo requests
- Mobile layout for the creator side
- Access rules with automated tests
- Changes from internal testing on real phones
- Lesson videos for onboarding
- Auto-approve drafts after 48 hours with no brand reply
- Stripe billing: $500 per creator monthly + weekly views invoice (first version)
- Turning email confirmation back on, removing demo data before launch
- Security review of access rules, uploads, secrets and server actions; fix what you find
- Stripe: review and test billing end to end, including failed payments and refunds
- Analytics: connect an aggregator for real views (daily refresh plus on-demand), replacing dummy numbers; later TikTok and Meta APIs
- Production setup: paid Vercel and Supabase plans, backups, a staging copy
- Email sender for password reset and confirmation
- Error tracking and uptime alerts
- Load and edge-case testing before launch, especially uploads from phones
Out of scope for v1: creator payouts happen outside the platform for now. Posts-gone-live tracking waits for API approval.