Roadmap

1. 0
   Week 1In progress1 of 7 tasks

   Phase 0 · Kickoff and setup

   Agreed scope, final screen designs, accounts in place, and access to F.A.M.’s domain and email.

   Tasks

   • 0.1Settle ownership, running costs and v1 scopeNoah
   • 0.2Draft and sign the agreement with FAMNoah
   • 0.5Create service accounts and add keys to environment secretsNoah
   • 0.6Update build-plan.md and architecture.md to match the decisions
   • 0.7Scaffold the Next.js app and repo layout
   • 0.8CI (lint, typecheck, tests) and Dependabot
   • 0.9Send FAM the kickoff checklist and DNS instructionsNoah
2. 1
   Weeks 2–4Up next0 of 13 tasks

   Phase 1 · Foundation

   Secure staff sign-in, and the YETI proposal running from the database behind a private link.

   Tasks

   • 1.1Database schema with organization_id on every table
   • 1.2Access rules per organization and role
   • 1.3Staff sign-in with Google or Microsoft (Auth.js)
   • 1.4Import the YETI deck into the database
   • 1.5Serve the client proposal page from the database, pixel-identical
   • 1.6Share links: create, expire, revoke, passcode, noindex
   • 1.7Publish flow: frozen, versioned proposal snapshots on the CDN
   • 1.8Image uploads to R2 with on-the-fly resizing
   • 1.9Deploy staging and live on Cloudflare with preview links
   • 1.10Nightly database backup to R2, plus a restore test
   • 1.11Error alerts (Sentry) and uptime monitoring
   • 1.12Browser test: open the YETI proposal, pick, review
   • 1.13Custom domain for client links (Cloudflare for SaaS)
3. 2
   Weeks 5–7Up next0 of 11 tasks

   Phase 2 · Proposal builder

   The team builds and edits proposals in the admin, with a live phone and desktop preview.

   Tasks

   • 2.1Dashboard: proposal list, statuses, progress, headline numbers
   • 2.2Proposal builder shell: outline, editor, live preview
   • 2.3Edit cover, intro, contacts, instructions, About, FAQ and closing
   • 2.4Stops, days and groups with drag-to-reorder
   • 2.5Group settings: set time, category, required picks, "None of these"
   • 2.6Add options to groups with per-proposal fees and notes
   • 2.7Budget check per group and stop
   • 2.8Fee visibility switch per proposal
   • 2.9Draft autosave, versions, preview as client, publish
   • 2.10Duplicate a proposal and save as template
   • 2.11Brand kit screen
4. 3
   Weeks 8–9Up next0 of 12 tasks

   Phase 3 · Library and artist autofill

   A shared talent, vendor and venue library. Type an artist’s name and their photo, links, bio and stats fill in.

   Tasks

   • 3.1Talent & vendors library: search, tabs, filters
   • 3.2Artist lookup service with caching
   • 3.3Spotify lookup (photo, genres, link, player)
   • 3.4YouTube lookup (subscribers, views, top video)
   • 3.5Apple Music links via the iTunes Search API
   • 3.6Bio and hometown from MusicBrainz and Wikipedia
   • 3.7Autofill card: search, pick the match, edit, save
   • 3.8Manual stats fields with "as of" dates
   • 3.9Weekly stats refresh and trend sparklines
   • 3.10Venues library
   • 3.11Clients list
   • 3.12Import FAM's roster spreadsheet
5. 4
   Weeks 10–11Up next0 of 8 tasks

   Phase 4 · Client picks and alerts

   Picks save live, email alerts when a client opens or sends, a live responses view and PDF export.

   Tasks

   • 4.1Record client actions live, browser-first with retry
   • 4.2Picks follow the client across devices
   • 4.3Locked submissions replace the mailto send
   • 4.4Responses screen
   • 4.5Dashboard activity feed and views chart
   • 4.6Email setup with Resend and SPF/DKIM/DMARC
   • 4.7Emails: opened, picks sent, nudge, stall reminder
   • 4.8Export picks to PDF
6. 5
   Weeks 12–13Up next0 of 16 tasks

   Phase 5 · Launch extras, polish and launch

   Link previews, due dates, one link per decision-maker and a Monday digest, then phone testing, training and the first real proposal.

   Tasks

   • 5.1Rich link previews for each proposal
   • 5.2Picks-due date with countdown and add-to-calendar
   • 5.3Named decision-makers: one link per person, attributed votes
   • 5.4Picks receipt emailed to the client
   • 5.5QR code for the share link
   • 5.6Slack or text alert when a client opens or sends picks
   • 5.7Monday digest email
   • 5.8Won/lost tracking and export to spreadsheet
   • 5.9Test on iPhone, Android, Mac and Windows; accessibility pass
   • 5.10Speed pass for mobile data
   • 5.11Runbook and keys document
   • 5.12Go live on pitch.fieldathletic.comNoah
   • 5.13Import and verify FAM's data with themNoah
   • 5.14Launch checklist dry run
   • 5.15Team training and how-to videosNoah
   • 5.16Send the first real proposalNoah

About 13 weeks from kickoff to launch, with a working demo at the end of every phase.

Task status from the build’s task list, updated September 26, 2026.