# Dashlyra - Product Foundation

## Product
- Name: Dashlyra - Tailwind SaaS Admin Dashboard Template
- Target users: SaaS founders, developers
- Style: modern, clean, minimal, professional
- Theme: light + dark mode

## Current Template Coverage
- Dashboard overview with KPI cards, charts, activity, revenue, and account health sections.
- Analytics pages for revenue, cohorts, funnels, and account table workflows.
- User operations pages for member management and role/access review.
- Billing pages for subscriptions, invoices, failed-payment recovery, and coupons.
- Settings tabs for profile, security, notifications, and API keys.
- UI kit pages for form components, widgets, empty states, onboarding, auth, errors, maintenance, legal, and docs.

## SaaS Expansion Feature Map
1. Multi-tenant workspace management and organization switching.
2. Role-based access control (Owner, Admin, Billing, Support, Analyst, Developer).
3. SSO/SAML sign-in and SCIM provisioning settings.
4. KPI dashboard for MRR, ARR, NRR, churn, CAC payback, LTV.
5. Revenue analytics by plan, expansion, contraction, refunds, failed payments.
6. Product usage analytics: DAU, WAU, MAU, stickiness, and adoption.
7. Funnel and conversion analytics for signup, activation, and paid conversion.
8. Cohort retention and churn trend analysis.
9. Customer 360 view with health score and lifecycle stage.
10. Subscription lifecycle management for trials, upgrades, downgrades, and cancellation.
11. Billing center for invoices, payments, taxes, and coupons.
12. Dunning and failed payment retry workflows.
13. Usage-based billing and metered quota tracking.
14. Feature flags and staged rollouts.
15. A/B experiment tracking with conversion outcomes.
16. Support center with ticket SLA, queue, and ownership.
17. Incident and status pages with uptime and scheduled maintenance.
18. Integration marketplace and sync health.
19. API key and webhook management with logs and retry history.
20. Audit logs, security controls, and session management.
21. Data governance (export, retention, deletion workflows).

## Suggested Expansion Page Structure
1. `landing`, `pricing`, `features`, `changelog`, `contact`
2. `auth/*` (sign in, sign up, reset, verify, 2FA, SSO, invite accept)
3. `onboarding/*` (workspace setup, import, billing, invite)
4. `dashboard` (executive + operations views)
5. `analytics/*` (revenue, retention, funnels, cohorts, adoption)
6. `customers/*` (list, segments, health, profile detail tabs)
7. `billing/*` (plans, add-ons, subscriptions, invoices, payments, dunning)
8. `product/*` (features, flags, experiments, releases, roadmap)
9. `support/*` (ticket list/detail, SLA, knowledge base)
10. `status/*` (incidents, uptime, maintenance)
11. `integrations/*` (marketplace, details, logs)
12. `developer/*` (api keys, webhooks, oauth apps, rate limits, events)
13. `settings/*` (workspace, members, roles, security, notifications, appearance)
14. Shared pages: `notifications`, `activity`, `search`, `help`, errors, maintenance

## UX Principles
1. KPI-first information hierarchy.
2. Consistent components and interaction patterns.
3. WCAG 2.2 AA accessibility target.
4. Complete UI states: loading, empty, success, and error.
5. Progressive disclosure for advanced controls.
6. Safe actions with confirmation and undo where possible.
7. Scalable tokenized design system.
8. Performance-conscious experience for dense data interfaces.
