Creator Sponsorship Tracker

A lightweight single-user web app for solo creators to manage sponsorship deals, deliverables, payment tracking, notes, reminders, and reference attachments from one dashboard-oriented workspace.

MVP Purpose

This product replaces scattered spreadsheets, notes, and inbox memory with a focused sponsorship tracker optimized for fast manual entry and simple review. The first release is intentionally narrow: one authenticated user, one workspace, no collaboration, no realtime infrastructure, and no external deal automation.

Core MVP Capabilities

• Dashboard
  • Active deals
  • Deliverables due in the next 14 days
  • Unpaid deals
  • Overdue follow-ups
• Sponsorship deal management
  • Create, edit, view, and archive-style manage deal records
  • Track brand, campaign, dates, contact info, value, and summary notes
• Deliverable tracking
  • Checklist-style deliverables per deal
  • Due dates, completion state, and ordering
• Payment tracking
  • Expected payment date
  • Paid date
  • Payment status
• Follow-up management
  • Reminders tied to a deal
  • In-app reminder surfacing in MVP
  • Optional email reminders only if low effort
• Notes and attachments
  • Contact notes with note dates
  • Lightweight file attachments or stored links per deal

Scope Boundaries

Included

• Single-user authenticated web application
• CRUD flows for deals, deliverables, reminders, notes, and attachments
• Dashboard summary views
• Manual data entry for all dates, currency values, statuses, and notes

Excluded

• Team collaboration or shared workspaces
• Multi-role permissions
• Payment processing or collection
• Automated invoicing
• Contract generation or contract lifecycle management
• CRM automation
• Email/document parsing automation
• Complex analytics beyond summary counts
• Browser extension or mobile app

Product Model

The top-level record is a Sponsorship Deal. Each deal can own:

• Deliverables
• Reminders
• Contact notes
• Attachments

All records belong to the authenticated user and must be isolated by user_id in application behavior and persistence queries.

Experience Principles

• Low-friction entry: standard CRUD forms with responsive interactions
• Local-first feel: optimistic checklist updates, immediate dashboard refresh after mutations, and autosave where practical
• Simple navigation: dashboard first, then deal detail as the operational workspace
• No realtime dependency: request/response interactions only

Architecture Summary

• Monolithic full-stack web application
• Server-rendered or hybrid-rendered UI
• Internal HTTP endpoints or server actions behind the UI
• Service-layer writes for validation and business rules
• Relational database for structured data
• Managed authentication provider

Primary Data Areas

• users
• sponsorship_deals
• deliverables
• reminders
• contact_notes
• attachments

All tables use UUID primary keys and timestamps. Detailed field definitions belong in the technical specification and data model source documents.

Security Expectations

• Authentication required for all app routes except sign-in/sign-up
• Per-user data scoping on every query
• Validation and sanitization of user text and file metadata
• HTTPS in transit and managed encryption at rest
• Secrets stored only in environment configuration
• CSRF protection if cookie sessions are used

API and Interaction Constraints

• Stable JSON envelopes with data and error
• Soft validation errors for user-correctable input
• Fixed-window rate limits:
  • 120 req/min read endpoints per authenticated user
  • 60 req/min write endpoints per authenticated user
• Attachment uploads must enforce file type and size restrictions

Success Criteria for MVP

The app is successful if a solo creator can quickly answer:

• What sponsorships are active?
• What deliverables are due soon?
• Which deals are still unpaid?
• Which brands need follow-up next?
• What notes or files are attached to each deal?