💡 Manager Market Health Analytics & Trend Insights

[github-actions[bot]]

Summary

A dedicated analytics view in the manager dashboard showing leading indicators: week-over-week vendor attendance rates, customer follow growth curves, busiest market hours, most/least-followed vendors, and vendor attendance reliability scores. Moves managers from reactive fire-fighting to data-driven market planning and vendor relationship management.

Market Signal

MarketWurks and FM Tracks offer backward-looking reporting (end-of-day sales, USDA compliance reports). VIBEPro charges $149–$595/month for analytics capabilities. No competitor provides forward-looking trend analytics tied to real-time coordination data (check-ins, follows, status updates). The PRD's Phase 2 roadmap includes "Manager reliability analytics and quality controls" — this proposal concretizes that vision with specific metrics and implementation direction.

User Signal

The PRD's Maria (manager persona) journey reveals the core problem: managers operate reactively. The existing Manager Dashboard (Epic 5) provides live market-day oversight, but after market day ends, managers have no trend visibility. Issues like declining vendor attendance, stagnating customer growth, or consistently late vendors are invisible until they become crises. All 10 open issues in the signals file are infrastructure/compliance — no product analytics exist yet.

Technical Opportunity

All required data already flows through the system: the check_ins table tracks attendance, the follows table tracks customer engagement, and the audit_log captures all actions with timestamps. Analytics queries are straightforward aggregations over existing Cloud SQL tables. The Go backend can expose GraphQL queries for analytics data; the frontend renders charts using a lightweight charting library (Victory Native or react-native-chart-kit). No new data collection infrastructure is needed — analytics simply queries what's already there.

Assessment

Dimension	Score	Rationale
Feasibility	high	All data already exists in check_ins, follows, and audit_log tables; analytics is aggregation queries + chart rendering
Impact	med	Gives managers trend visibility they currently lack; supports proactive market planning and vendor relationship management
Urgency	med	Most valuable at Growth scale (20 markets, 160 vendors); pilot markets benefit from basic counts immediately

Adversarial Review

Strongest objection: Small-market managers (10–15 vendors) may not need or use analytics, and building analytics is scope creep for an MVP that hasn't launched yet.

Rebuttal: This is explicitly a Phase 2 feature, timed for when the platform reaches 20 markets and 160 vendors (PRD 12-month target). At pilot scale, the analytics view can simply show basic counts and trends with minimal UI investment. The key insight is that the data is already being collected via audit logging and check-ins — analytics is just querying what's already there. Not building it would waste the rich operational data the architecture captures by design.

Suggested Next Step

Define the specific metrics for the analytics dashboard: vendor attendance rate trend (8-week rolling), follower growth per market, vendor reliability score formula, peak hour identification. Create wireframes for the manager analytics tab. Evaluate Victory Native vs react-native-chart-kit for mobile charting.