Micro-Influencer Deliverable and Payment Tracker

AI Prompts to Build This

Copy these build prompts into Claude, Cursor, or your AI coding tool. Create a free account to unlock the full research behind them.

1. 1. Project Setup

   Create a Next.js 14 (App Router, TypeScript, Tailwind) app called "DeliverTrack" for brands running micro-influencer campaigns. Provision Supabase Postgres with these tables:
   
   - workspaces (id, name, owner_user_id, plan TEXT default 'free')
   - campaigns (id, workspace_id, name, start_date, end_date, status)
   - creators (id, campaign_id, name, email, phone, instagram_handle, tiktok_handle, stripe_connect_account_id)
   - contracts (id, creator_id, deliverables JSONB, rate_cents INT, usage_rights TEXT, due_date, signed_at, pandadoc_document_id)
   - deliverables (id, contract_id, description, status TEXT CHECK status IN ('not_started','submitted','needs_revision','approved','paid'), due_date)
   - submissions (id, deliverable_id, file_url, post_url, submitted_at, reviewer_note)
   - payments (id, deliverable_id, amount_cents, stripe_transfer_id, paid_at)
   
   Enable row-level security scoped by workspace_id via a workspace_members join table. Set up Stripe Connect (Express) onboarding for creators and Stripe Billing for the workspace subscription (Free/Growth $39/Agency $99).

2. 2. Deliverable Pipeline + No-Login Creator Upload

   Build the deliverable tracking pipeline and a public, token-based upload page that requires no creator login.
   
   Requirements:
   - Each deliverable gets a unique, unguessable upload token generated on contract creation.
   - The upload page shows the creator their deliverable list and due dates, with an upload widget (drag-and-drop file or paste a live post URL) per item.
   - On submit, update deliverable status to 'submitted', store the file/URL in a submissions row, and notify the brand via email.
   - Build a brand-side review queue listing all 'submitted' deliverables across creators, with Approve / Request Revision buttons.
   - Approve: set status to 'approved', create a payments row in 'pending' state, trigger the payment webhook.
   - Request Revision: set status back to 'needs_revision', require a reviewer note, and re-email the creator their upload link with the note attached.
   - Send an automated reminder (email + SMS via Twilio) 48 hours before any deliverable's due_date if it's still 'not_started'.

3. 3. AI Content Review Assistant

   Add an AI pre-check that runs when a creator submits a deliverable, before it reaches the human review queue.
   
   Given: the contract's deliverable description (e.g. "1 Instagram Reel, must tag @brand and use #BrandLaunch, minimum 15 seconds") and the submitted content (image/video file or a fetched post URL with caption text).
   
   Call a vision-capable model (Claude or GPT-4o-mini) with a strict JSON schema:
   { likely_compliant: boolean, missing_requirements: string[], confidence: number, notes: string }
   
   Check for required hashtags/mentions in the caption, approximate video length if inferable, and whether the content matches the described format. Never auto-approve or auto-reject — surface the result as a badge ("AI flagged: missing #BrandLaunch tag") in the review queue. Log every check to an ai_reviews table for auditing.

4. 4. Payment Batching and Stripe Connect Payout

   Implement the payment trigger and batch payout flow.
   
   When a deliverable's status flips to 'approved': create a payments row in 'pending' status linked to that deliverable and the creator's stripe_connect_account_id, then add it to the workspace's next scheduled payout batch (default weekly, configurable).
   
   Build a scheduled job (Vercel Cron, weekly) that:
   1. Groups all 'pending' payments by workspace.
   2. For each, calls stripe.transfers.create to the creator's Connect account for the deliverable's rate_cents, tagged with metadata for deliverable_id and campaign_id.
   3. On success, updates the payment row to 'paid' with the stripe_transfer_id and paid_at timestamp, and marks the deliverable 'paid'.
   4. On failure (e.g. creator hasn't finished Connect onboarding), leaves the payment 'pending' and notifies the workspace owner with the creator and reason.
   
   Expose a CSV export endpoint so a brand's finance team can reconcile every payment against the deliverable that earned it.