infini-platform

byBernard Vyas

# TMOE C2C Platform — PRD Phase 1 MVP (v1.0) Confidential | 10-Week Delivery ## 1. Background TMOE is a content-to-commerce aggregator connecting digital publishers (audience + content inventory) with brands (product discovery via editorial content). This PRD defines Phase 1 MVP scope — the operating system for TMOE's business. ## 2. Product Objectives - Publisher/brand registration, profiles, onboarding - Admin team: verify users, manage campaigns, oversee platform - Structured campaign creation, listing, management - ROI estimates via manually configured benchmarks - Campaign status, performance, and settlement dashboards - Data foundation for Phase 2 AI/automation **Failsafe:** If distribution integration isn't ready at launch, ops team manages distribution manually. Platform tracks status regardless. ## 3. User Roles **Publisher:** Registers, sets up profile (categories, traffic, content slots), browses/accepts campaigns, views earnings/payouts. **Brand:** Registers, submits campaign briefs, specifies SKUs/budget/markets/commerce links, monitors ROI & GMV. **Admin (TMOE internal):** Verifies users, creates/manages campaigns, assigns publishers, configures ROI benchmarks, manages settlement ledger. Backbone of Phase 1. ## 4. Phase 1 vs Phase 2 Scope | Feature | Phase 1 (Build) | Phase 2 (Future) | |---|---|---| | Campaign Creation | Manual form by brand/admin | AI-generated suggestions | | Publisher Matching | Admin-assisted + directory | ML-powered matching engine | | ROI Estimation | Manual configurable benchmarks | Dynamic ML predictive model | | Distribution | External/ops-managed | In-platform partner integration | | Optimization | Manual by ops/admin | Real-time automated | | Reporting | API-connected dashboard (auto) | Full attribution + real-time | | Settlement | Manual admin ledger | Automated engine | *Any AI/ML/automated matching/real-time optimization = Phase 2 only.* ## 5. Core Modules ### 5.1 Registration & Onboarding - Landing page with role selection (Publisher / Brand / Admin invite-only) - Email verification (OTP or link) - Multi-step onboarding wizard per role - Pending Verification state → admin approval gate - RBAC: publishers cannot see brand screens and vice versa ### 5.2 Publisher Profile & Inventory - Profile: name, URL, categories, description, contact - Traffic data: manual monthly sessions/pageviews - Content inventory: slots with type, category, estimated traffic, monetisation model (CPS/CPC/CPM/fixed), Available/Engaged status - Dashboard: active campaigns, earnings, payout status ### 5.3 Brand Profile & Campaign Brief - Profile: company name, website, industry, contact - Brief form: target categories, markets, SKUs, budget range, GMV/ROI targets, commerce links (D2C/marketplace URLs) - Dashboard: active campaigns, estimated vs actual, spend summary - Multiple briefs supported ### 5.4 Campaign Creation & Management **Campaign object fields:** name, category, target markets, assigned publishers, assigned brand, content type (new/existing), budget (content + distribution), estimated outcomes (traffic/clicks/orders/GMV/ROI), commerce links, status (Draft/Active/Paused/Completed/Cancelled), start/end dates. **Build:** Campaign creation form (admin; brand initiates brief), campaign listing (table/card + filters), campaign detail page (full info + status tracker + action buttons), status management with notifications, campaign history/audit log. ### 5.5 ROI Estimation Module Admin configures per-category benchmarks: CVR, AOV, traffic multipliers, CTR. Estimator inputs: content budget, distribution budget, publisher traffic, benchmarks. Outputs: estimated traffic, clicks, orders, GMV, ROI — displayed to brand at review. Estimated vs actual comparison view on dashboard (actuals via distribution API). ### 5.6 Performance Dashboard & Reporting API-connected, auto-updated (not manual). Data pulled from distribution partner APIs. - **Publisher:** active campaigns, status, traffic/clicks/CTR/orders/CVR/revenue, earnings & payout status - **Brand:** all campaigns, estimated vs actual side-by-side, live GMV/traffic/clicks/CVR, spend breakdown (CPC, CPO) - **Admin:** platform overview (total campaigns, pending verifications, aggregate GMV), campaign hub, settlement queue, user management ### 5.7 Settlement & Payout Ledger - Settlement record per campaign: GMV, payout model, amounts owed (publisher + ops partner), platform fee - Status: Pending → Approved → Paid (admin marks; publisher sees update) - CSV export of settlement records - Publisher summary: total earned, paid, outstanding ## 6. User Flows (Summary) **Flow 1 – Publisher Onboarding:** Sign up → email verify → wizard (company, categories, traffic, inventory, bank details) → Pending → admin approves → dashboard. **Flow 2 – Brand Onboarding:** Sign up → email verify → wizard (company, categories, markets, commerce links) → Pending → admin approves → dashboard. **Flow 3 – Brand Brief:** New Brief → form (name, category, market, SKUs, budget, GMV target, links) → admin converts to campaign → brand notified (Draft). **Flow 4 – Admin Creates Campaign:** Receives brief → fills campaign form → runs ROI estimator → assigns publishers → Draft → brand reviews → admin activates → publishers notified → publisher accepts → Active. **Flow 5 – Execution:** Content created outside platform. Distribution by ops team. Admin updates status/notes. Performance data entered at checkpoints. Admin can Pause or Complete. **Flow 6 – Settlement:** Completed → admin enters GMV/payout details → Approved → publisher notified → admin marks Paid → CSV export. **Flow 7 – Verification:** Admin reviews queue → Approve / Reject (with note) / Request More Info → confirmation email sent. Admin can suspend/deactivate anytime. ## 7. Design Requirements All screens: wireframes + hi-fi mockups + component library. Desktop primary, mobile-responsive. **Screens:** Onboarding, Publisher Profile & Inventory, Brand Profile & Brief, Campaign Creation Form, Campaign Marketplace, ROI Estimator Widget, Campaign Detail Page, Performance Dashboard, Settlement Ledger, Admin Panel, Notification Centre, Empty States & Errors. **Principles:** Professional B2B SaaS; role-aware nav; colour-coded status badges; helpful empty states; data tables over cards for dense views. Design provided by TMOE team. ## 8. Technical Requirements ### Stack Constraints - Web app (Chrome/Firefox/Safari/Edge), no native mobile - Responsive (desktop primary) - Cloud-hosted (AWS/GCP/Azure) - Dev + staging + production environments from Week 2 - API-first architecture (for Phase 2 readiness) - PostgreSQL preferred ### Auth & Security - Email + password with email verification; OTP nice-to-have - RBAC: Publisher / Brand / Admin - HTTPS enforced; no payment card data stored ### Integrations (Phase 1 only) - ✅ Transactional email (SendGrid or equivalent) - ✅ CSV export - ❌ GA/Search Console API, payment gateway, distribution partner APIs (all Phase 2) ## 9. 10-Week Timeline | Week | Milestone | Owner | Deliverables | |---|---|---|---| | 1 | Vendor Finalisation | TMOE | SOW, contracts, comms setup | | 2 | Discovery & Architecture | Vendor + TMOE PM | Tech stack, DB schema, environments, repo | | 3 | UI/UX Design ✅ Sign-off | TMOE Design | Wireframes → hi-fi mockups | | 4 | Auth & Infrastructure | Vendor | Auth, RBAC, onboarding flows, CI/CD | | 5 | Publisher & Brand Modules | Vendor | Profiles, inventory, brief submission, admin verification | | 6 | Campaign Module ✅ Sign-off | Vendor | Campaign creation, listing, status management, detail view | | 7 | ROI & Dashboards | Vendor | ROI estimator, distribution API integration, all 3 dashboards | | 8 | Settlement & Notifications | Vendor | Settlement ledger, payout tracking, email notifications | | 9 | QA & UAT ✅ Sign-off | Vendor QA + TMOE | Integration testing, bug fixes, UAT, security review | | 10 | Deployment & Go-Live | Vendor + TMOE Ops | Production deploy, SSL, training, pilot launch | ## 10. Out of Scope (Phase 1) AI/ML features, automated matching, real-time budget optimization, automated settlement/payment gateway, native mobile app, distribution partner API integrations, GA/Search Console API, A/B testing, multi-language, white-label, public marketplace. ## 11. Acceptance Criteria - Publisher: full registration → onboarding → admin approval flow works end-to-end - Brand: registration → campaign brief → active campaign with ROI estimate visible - Admin: campaign creation, publisher assignment, benchmark config, performance update, settlement ledger all functional - All email notifications fire correctly (verification, approval, assignment, status change, settlement) - All 3 dashboards show correct, role-appropriate data - Security: no public access to protected routes, no cross-role data leakage - Live on production URL with SSL - ≥1 pilot publisher + 1 pilot brand + 1 active campaign at go-live ## 12. Phase 2 Preview (Out of Current Scope) AI campaign creation, intelligent publisher-brand matching (ML), dynamic ROI modelling, in-platform distribution integration, real-time performance tracking, automated settlement engine, self-learning benchmark feedback loop. *Vendor should architect Phase 1 codebase/DB schema to anticipate Phase 2 (campaign data models, user roles, API layer).* ## 13. Vendor Instructions - Proposal covers Phase 1 only - Document tech stack with justification - Sprint-based process, weekly check-ins with TMOE product lead - Source code handed to TMOE in TMOE-owned repo at end of engagement - Vendor maintains all 3 environments throughout engagement - Document all assumptions before contract signing - Scope questions within 48 hours of receiving PRD - 1 month post-completion maintenance support required All technical/product decisions go through the designated TMOE product lead.