Project Status
Roadmap
What we're building next, in priority order. Subject to change after each weekly review.
Phase 1 — Foundation: shipped 2026-05-08
New brand (Montserrat / DM Sans / black + orange), two-hub navigation (Client Hub / Reporting / Client Info), dark sidebar with admin pencils, bento-grid Home with the program timeline, full-width layout, and the Client Info hub with bento grid + editor. CoreBoard renamed to FPM Client Hub project-wide. See Where We Are.
Now (this sprint)
- pending Apply
add-client-tier.sql+add-client-info.sqlto the production Supabase project. Backfill tier labels and primary contact names for every active client so the new HubNav and greeting render with real data. - pending Force re-authentication of every existing Google integration so the Google Ads scope works for every client. Affects ~60% of active clients.
- pending Wire Meta Ads to all paying clients (currently only Denver). Audit each Meta account's permission grant.
- pending Ship n8n workflow templates for Email / SMS counts. One template per GHL location, dispatched on weekly schedule.
Next
- planned Microsoft Clarity integration. Either via Clarity Data Export API or via a small n8n proxy. Adds 4 metrics (sessions, rage clicks, dead clicks, scroll depth).
- planned SE Ranking as a possible replacement or supplement to DataForSEO. They have an MCP server we could integrate with, plus richer agency-tier reporting. Decision still open — see DataForSEO.
- planned GHL Lead Type Breakdown: qualified calls (≥60s), unique first-time callers, walk-ins, outbound contact attempts. Pure GHL extension, no new integration.
- planned Local Dominator native integration — replace iframe embeds with API calls so the geo-grid data lives in our DB and can be reported on.
Later
- planned AI Insights panel — daily summary of what changed and why, generated by an LLM that has access to the metrics and a small business-context prompt.
- planned Per-stage cycle time in the GHL pipeline (how long a lead sits in each stage on average).
- planned Multi-location client support (one client row, multiple GBP locations, multiple GA4 properties — aggregated views).
- planned Submit Request inbox UI for admins (currently surfaces in Slack only).
- planned "View as client" toggle for admins so they can preview the read-only experience without logging out.
- planned Email-scheduled PDFs — auto-deliver the monthly report on the first of every month.
Explicitly not doing (for now)
- A native mobile app. The dashboard is responsive enough for tablet and good enough for phone in a pinch.
- White-labeling for client subdomains. Unnecessary complexity at our scale.
- A query builder / custom dashboard configurator. Adds support burden, dilutes the curated view we sell.
- Multi-currency. Every client we serve operates in USD. Add it the day a non-US client onboards.
Where to push back
If a request from leadership lands and it does not appear above, ask: does this serve more than one client and unlock more than 2 hours of recurring weekly work? If not, it goes to the backlog.