Stadli Dashboard Structure (MVP v1.1)

Product Summary

Stadli is the all-in-one revenue + marketing OS for pro teams outside the big four. It launches with five integrated cores that work together from day one.

Flagship Features

Core capabilities that define Stadli’s MVP and roadmap-ready foundation.

Web App / Website

A unified digital front door for teams and fans. Built PWA-first for speed and reach, with shared data and schema across platforms.

  • Game Day Central with live content and offers
  • Integrated sponsor surfaces and push notifications
  • Built-in checkout for tickets, merch, and experiences
  • Seamless fan identity across web and app

CRM / 360° Fan Profile

A single source of truth for every fan’s engagement, purchase, and activity history.

  • Unified fan records from ticketing, merch, and web interactions
  • Live segmentation for targeting and personalization
  • Identity stitching and deduplication
  • Real-time revenue attribution per fan

Campaign Engine & Playbooks

Automate fan engagement and revenue growth through proven, data-driven plays and dynamic campaigns.

  • Prebuilt sports-specific campaigns and templates
  • Goal-driven automations (e.g., “3-game pack conversion”, “flash merch drop”)
  • Embedded checkout CTAs and personalized offers
  • Performance tracking and revenue impact dashboards

Stadli Narratives & Analytics

Insights and actions that surface daily to keep teams aligned on performance and opportunity.

  • Role-aware digest with contextual CTAs for GMs, Marketing, and Ops
  • Custom dashboards with fan and revenue insights
  • Stadli Web Tag for standardized, privacy-first event tracking
  • Closed-loop attribution across campaigns, sales, and fan actions

Commerce & Ticketing

A unified commerce core powering all transactions — from tickets to merch to bundles.

  • Native payment processing and secure checkout
  • Unified ticketing and ecommerce interface
  • Automated reconciliation via Tixr/Shopify webhooks
  • Fan wallet and order history with refund management

1. Main Summary (Dashboard Home)

The central hub for quick, daily clarity and action.

Top KPIs Strip

  • 7-day ticket revenue
  • 7-day merch revenue
  • DAU/WAU (web + app)
  • Total fan records

Narratives Feed

  • Short, human-readable stories (e.g. “Saturday ticket interest up 41% — launch a 3-pack”).
  • Each card with one-click CTA to launch campaign or view segment.
  • Role- & account-tailored CTAs and wording ensure relevance to GM/Marketing/Ops.

Next Best Actions Panel

  • 2–3 actionable prompts (“Re-engage lapsed buyers,” “Boost campaign performance”).
  • Actions are filtered by user role and team context.

Game Day Snapshot

  • Tickets sold vs. capacity
  • Quick weather glance
  • One-tap game-day push
  • Scope note (MVP): Sponsor activations and staff tasking are out-of-scope.

2. Team Content

Where staff manage the fan-facing experience (site + app).

Content Hub

  • Auto-ingested news, videos, galleries, rosters, bios

Game Day Pages

  • Schedules, standings, live feeds, ticket wallet links

Commerce Surfaces

  • Merch collections, offers, sponsor placements

Brand & Identity Settings

  • Logos, colors, layouts, and templates for site/app
  • Dashboard brand guardrails: enforce accent limits and neutral CTAs across internal UI.
  • Copy guardrails: Campaign Builder suggests on-brand text aligned to voice pillars.

3. Fans

The CRM / FRM core, unifying all fan data.

Fan Profiles

  • 360° view (ticketing + merch + engagement)

Smart Segmentation

  • Dynamic, rule-based filters (“STHs with dips in attendance”)

Segment Movers

  • Weekly trending segments (up/down)

Identity Resolution Panel

  • Review stitched profiles, audit matches

AI Transparency

  • Confidence indicators: Simple likelihood/quality badges on model-driven segments.
  • Explainability: “Why in this segment” rationale for quick audits and trust.

4. Campaigns

The action layer for fan engagement and revenue.

Campaign Builder

  • Push + email (drag-and-drop templates, sports-ready)

Prebuilt Plays

  • Quick recipes (“Renewal Nudge,” “3-Game Pack Upsell”)

Campaign Pulse

  • Live metrics on open rates, clicks, conversions, and revenue
  • Incremental lift: Shows uplift vs. baseline to reveal true added value.
  • Next actions: Inline suggestions (e.g., expand segment, clone to merch).

Boost/Pause Controls

  • One-click optimization for active campaigns

5. Analytics

Clear, attribution-first reporting.

Revenue Attribution

  • Tickets + merch, broken down by campaign and segment

Engagement Metrics

  • DAU/WAU, content interactions, app usage

Segment Insights

  • Contribution to revenue, churn/renewal rates

Exports & Logs

  • Audit-ready event data, CSV/SFTP options
  • Audience-aware exports: Formats tuned for ops staff and execs.
  • Executive snapshot: Each report includes a short “So what?” line.

6. Settings

Configuration and integrations.

Integrations

  • Day one: Tixr, WordPress, Stadli Analytics Snippets, Shopify, Facebook Ads, and other major tools.
  • GA (events) and Mailchimp imports supported via adapters; webhooks where available.

Permissions & Roles

  • GM, Marketing, Ops, staff access

Privacy & Compliance

  • Opt-ins, suppression lists, CASL/CAN-SPAM defaults
  • Compliance mode toggle: Regional presets (e.g., GDPR vs. North America).
  • Unified Consent Ledger: Channel-level consent across email, push, SMS.

System Settings

  • Time zone, branding, narrative delivery cadence

7. AI/ML Core Libraries & Strategy

The AI/ML capabilities will be built on a focused stack of open-source libraries and best-in-class APIs, selected for performance and suitability for core MVP features.

Core Data Science Libraries

1. Pandas

  • Function: Data ingestion, cleaning, transformation, and analysis foundation. Used across all data pipelines before modeling.
  • Powers: Prerequisite for all data-driven features.
  • GitHub: https://github.com/pandas-dev/pandas

2. Scikit-learn

  • Function: Core machine learning toolkit for foundational models. Powers clustering for segment discovery, baseline propensity models, and content-based recommendation algorithms.
  • Powers: Stadli Signals, Smart Segmentation, Fan Hub Personalization (v1).
  • GitHub: https://github.com/scikit-learn/scikit-learn

3. LightGBM

  • Function: High-performance gradient boosting framework for building accurate propensity models on tabular fan data. Selected for its speed and efficiency.
  • Powers: Stadli Signals (high-intent segments), Stadli Power Plays.
  • GitHub: https://github.com/microsoft/LightGBM

4. Dedupe

  • Function: Specialized library for probabilistic record linkage and entity resolution. Used to merge and unify disparate fan profiles into a single 360° view.
  • Powers: Unified Fan CRM, Identity Resolution Panel.
  • GitHub: https://github.com/dedupeio/dedupe

AI/ML Strategy & Approach

Generative AI & LLM Integration (API-First)

For features requiring advanced language understanding and generation, the platform will integrate with leading Large Language Model (LLM) providers via their APIs. This strategy ensures access to state-of-the-art capabilities while minimizing infrastructure overhead.

  • OpenAI (GPT Models): Industry-standard for high-quality, creative, and instruction-following text generation. Powers Stadli Narratives, generative campaign copy, and user assistance features.
  • Google (Gemini Models): Powerful multi-modal models with strong integration into the Google Cloud ecosystem. Used as a high-performance alternative for generative tasks and future multi-modal features.
  • Groq: Specialized inference engine for extremely high-speed, low-latency responses with open-source models. Powers real-time "AI helper" features, conversational interfaces, and other latency-sensitive applications.

Focus on Classical ML

The MVP will intentionally omit deep learning frameworks (PyTorch, TensorFlow) for internal model development. The core product challenges involve structured, tabular data, for which gradient boosting and classical ML models (LightGBM, Scikit-learn) are the superior and more efficient tools.

Transparency & Explainability (MVP)

  • Confidence indicators surfaced with model-driven segments and scores.
  • Simple rationale fields for segment membership and recommendations.

8. Tech Stack & Infrastructure (Cloudflare-First, Minimal)

9. Development Philosophy & Best Practices

Our approach to building Stadli is grounded in a set of core principles that ensure stability, scalability, and maintainability.

Safe Experimentation

  • Sandboxes & Playgrounds: Every new feature, integration, or significant change is first developed and tested in isolated sandbox environments. This allows for free experimentation without any risk to production data or services.

Production Integrity

  • Protecting Production: The production environment is sacred. Direct changes are strictly forbidden. All deployments follow a rigorous CI/CD pipeline with automated checks, and rollbacks are planned for.

Documentation as a Deliverable

  • Continuous Documentation: Documentation is not an afterthought; it's a critical part of the development process. Every API endpoint, data model change, and architectural decision is documented as it's made.

Visibility and Auditing

  • Comprehensive Logging: We log aggressively. Structured logs for application events, errors, and access patterns are maintained to ensure we can debug issues, monitor performance, and audit activity effectively.

Built for Change

  • Modular Architecture: The system is designed with modularity in mind. Components are loosely coupled and communicate through well-defined APIs. This makes it easier to update, replace, or scale individual parts of the platform without affecting the entire system.

LLM-Centric Architecture

  • Living Documentation for AI Collaboration: Every directory and module will contain a dedicated context file (e.g., _context.md). This file serves as a "living document," explaining the purpose, key functions, and relationships of the code within it. This practice ensures that any developer or Large Language Model (LLM) can instantly grasp the context of a given file, making AI-assisted development, refactoring, and debugging seamless and highly efficient.

Explicit Constraints

  • No vendor lock-in: Prefer open standards and reversible choices.
  • No dark patterns: Ethical UX by default for fans and staff.
  • Anti-fragility: Graceful degradation when integrations or models are unavailable.