Backend + Frontend Execution Roadmap

This roadmap is derived from:

• Current backend/frontend status in generated docs (generated/backend-domain-guide, generated/frontend-main-sections, generated/frontend-api-usage-reference)
• Matteo feature priorities
• Competitor pressure from Peec + Profound corpus

Current implementation reality

Backend readiness snapshot

Frontend readiness snapshot

Workstream roadmap (backend x frontend)

Phase	Workstream	Backend focus	Frontend focus	Target outcome
P0	Measurement reliability	Harden citation mismatch, share-of-voice, prompt history APIs	Ship clear visibility/citation/history comparison views with exact period selectors	Trustworthy measurement baseline
P0	Prompt operations	Stabilize prompt template/suggest/upload-csv endpoints and validation	Guided prompt library UX + CSV mapping wizard	Agency-usable prompt workflow
P1	Bias and variability controls	Add device split + repetition/sampling model + geo controls	Persona/geo/device filters + stability score cards	Data credibility and robustness
P1	Competitive and perception intelligence	Improve competitor compare + sentiment/perception endpoints	Competitor battlecards + perception panels	Better strategic differentiation
P1	Reporting engine	Standardize export/report payloads + report generation pipeline	PDF/share link/report pack UI + notes timeline	Agency reporting engine
P2	Integrations	GSC + Bing connectors; strengthen GA/Looker connector contracts	Connector setup UX + sync health visibility	Enterprise/scaled agency adoption
P2	Audit and advisor	Add audit generation endpoint + recommendation attribution model	One-click audit module + recommendation-to-result tracker	Sales enablement + learning loop

Dependency map

8-week execution plan (practical)

Definition of done by phase

• P0 done when

  • Measurement UX answers: visibility, citations, links/mismatch, and history diffs in < 3 clicks.
  • Prompt library and CSV import are agency-usable without manual support.

• P1 done when

  • Users can segment by persona/geo/device and understand result stability/confidence.
  • Competitor/perception and reporting workflows are client-facing ready.

• P2 done when

  • GSC/Bing connectors operational with visible sync health.
  • Audit module generates proposal-ready output.
  • Recommendation-to-result attribution closes the advisor loop.

Linked reference pages

• competitive-intelligence/product-features-roadmap-status
• competitive-intelligence/complete-reference-and-feature-catalog
• competitive-intelligence/feature-gap-deep-dive
• competitive-intelligence/coverage-audit-and-traceability