v1.2 depth expansion

Problem

The v1.0 launch shipped breadth coverage (top 20 connectors × 5 dashboards), but many connectors have richer analytics potential that the initial 5 dashboards don't cover. Users of high-engagement connectors like Salesforce or Stripe want deeper drill-downs, additional KPIs (pipeline velocity, cohort retention, churn analysis), and more specialized dashboards. Without expanding depth based on observed usage data—which connectors users actually engage with, which dashboards have the highest retention—expansion efforts risk building dashboards nobody uses. Depth expansion must be data-driven, prioritized by real adoption signals rather than roadmap intuition.

Context

• This milestone should deepen connector-specific dashboard packs and KPI narratives for Fivetran sources based on what users actually needed after the initial launch, not just what sounded interesting during planning.
• Expansion work is most valuable when it builds on stable foundations and clearly improves real workflows instead of reopening unresolved launch-quality debt.
• Expected touchpoints include dashboard pack YAML, dbt/example assets, connector fixtures, and quickstart docs, usage feedback, and any launch metrics or review artifacts that indicate where extra depth would matter most.

Possible Solutions

• A - Add the next roadmap ideas opportunistically: keeps momentum, but it risks building depth in areas users do not care about.
• B - Recommended: expand the highest-value workflows using observed usage and retention signals: keep scope tied to concrete evidence and stable foundations.
• C - Avoid depth work until a larger redesign is planned: safer, but it leaves real user demand unanswered for too long.

Plan

1. Review post-launch usage, support, and feedback to identify where deeper investment in connector-specific dashboard packs and KPI narratives for Fivetran sources would most improve real workflows.
2. Define a focused expansion scope with explicit non-goals so new depth does not sprawl into adjacent or unproven ideas.
3. Implement or queue the selected enhancements along with the docs, QA, and migration notes needed to make them safe to adopt.
4. Measure whether the added depth changed user outcomes enough to justify further expansion in the same area.

Implementation Progress

Review Feedback

• [ ] Review cleared