Roadmap
The schedule, in full, and what it actually means.
Hashmark is a 22-week build from the day the domain went live. The phases below are the published plan. We will update this page when reality diverges from it — including in the directions we wish it didn't.
Phase 0 — Foundation
Repo scaffolded, schema applied to production Postgres, domain acquired and serving. We are here.
Phase 1 — Ingestion
Cloudflare Worker accepts Companion App exports, normalizes the payload, writes to the hashmark schema. Playoff Vault never-delete trigger live and tested.
Phase 2 — Founder-playable
Single-user product runs end-to-end on the founder's own franchise data. Recap engine generates the first three-paragraph weekly story. Scout Archive timeline renders.
Founder-playable milestone
Internal milestone. The product is real enough to use daily on one franchise. Closed alpha begins.
Phase 3 — HashmarkIQ + College Years
HashmarkIQ methodology spec published. Rating column lives on the prospect surface. Generative college-career model trained and calibrated; outputs flagged as synthesized throughout.
Phase 4 — Multi-user leagues
Discord OAuth + app-managed sessions. League invites, role-aware permissions, commissioner tools. Discord bot ships with score posting and trade reports.
Public beta
Sideline tier opens to the public. Coach + Commissioner tiers enter live billing. Stripe wired. Status page goes live alongside.
Phase 5 — Editorial depth
Voice recaps via ElevenLabs Turbo v2. Year-end magazine generator. All-time team builder. Hall of Fame surface.
Phase 6 — Federation tooling
Studio tier features: multi-league management, API access, white-label theming. PC Companion (Electron) shell that automates the export upload from a Windows install.
Full launch
Marketing push, Hall of Fame tier opens, founder-pricing cohort closes. The product is in steady state and on its regular release cadence.
What is intentionally not on this roadmap
- An iOS app. The companion app already exists; Hashmark complements it on the web.
- Real NFL player data. Hashmark only handles what the user's own franchise generates.
- Save-file editing of any kind. We read exports, we never touch the game files.
- Gamification surfaces — streaks, leaderboards across franchises, social feeds.
When the plan slips
It will. Software schedules slip. When a milestone moves, we will move it on this page, dated, with the actual reason. The changelog will carry the same note. We will not quietly revise history.