// Generate LTX Studio product daily report with revenue, usage by segment (Enterprise, Pilot, Paying Non-Enterprise, Free), and DoD/DOW-avg comparisons. Use when: daily product standup, executive reporting, or when asked for 'yesterday's product numbers'.
| name | ltx-product-daily-report |
| description | Generate LTX Studio product daily report with revenue, usage by segment (Enterprise, Pilot, Paying Non-Enterprise, Free), and DoD/DOW-avg comparisons. Use when: daily product standup, executive reporting, or when asked for 'yesterday's product numbers'. |
| tags | ["reporting","daily-metrics","ltxstudio","product"] |
| compatibility | ["bq CLI installed and authenticated","GCP project access (ltx-dwh-explore for query execution)"] |
| metadata | {"author":"dbeer","version":"2.0","created":"2026-03-13"} |
Daily snapshot of LTX Studio product health: revenue by segment, usage metrics (active users, generations, tokens, downloads), with day-over-day and day-of-week average comparisons.
Slack channel: #ltx-product-auto-report
bq --project_id=ltx-dwh-explore query --use_legacy_sql=false --format=pretty "$(cat queries/product_segment_metrics.sql)"
The query returns two result sets:
Format per references/report-template.md. Key columns: segment, active_users, image_generations, video_generations, downloads, token_consumption, active_orgs, net_revenue, gross_revenue, plus *_dod_pct and *_dow_avg_pct comparison columns.
Flag any metric with >50% DoD or DOW-avg deviation.
shared/product-context.md — LTX Studio overview, user types, business modelqueries/product_segment_metrics.sql — Main product report queryreferences/report-template.md — Output formatting example--project_id=ltx-dwh-exploretime_granularity = 'day' filter on revenue tableaction_category = 'generations' filteris_enterprise_user flag — use org-based enterprise logicdate(action_ts) >= ...)date(action_ts) for partition pruning on usage tableSAFE_DIVIDE for all percentage calculationsUser: "Product daily report for yesterday"
User: "How did product metrics look yesterday?"
User: "Run the product report"
Adds the analyst layer (segmentation framing, filter/KPI surfacing, LTX-specific definitions, contextual follow-ups) on top of any Data MasterMind data interaction for LTX stakeholders (PMs, marketers, design, leadership). Wraps `get-data` / `validate-data` / `understand-data` / `visualize-data` — dialing intensity from a full guided session (for "look into X", "investigate Y", "do an analysis of …") down to a compressed wrap (for "what's MRR?", "is this number right?"). Output mode (chat-only or HTML artifact) is chosen up front for session-style asks. Always asks about Enterprise / paid non-Enterprise / Free segmentation and Studio-feature tier-gating when relevant. Do NOT use only when the user explicitly opts out ("just give me the number, no extras") or for templated feature dashboards (that's the Hex-based `dashboard-builder`).
Generate the LTX weekly leadership Slack post covering Open Source (HuggingFace LTX-2 family), API (revenue, endpoints, leads, industries), and Studio Enterprise (contracts, pilots, LTX-model consumption share). Runs every Monday via n8n: BigQuery → JSON parse → Slack render → LLM TL;DR → Slack webhook. Use when: weekly exec update, leadership Slack channel automation, or when asked for 'last week's LTX numbers'.
Build a structured data spec document for analytics topics by exploring the dbt codebase, identifying relevant events/models/columns, and producing a ready-to-use markdown reference. Use when: (1) starting a new data analysis, (2) documenting events for a feature or domain, (3) creating a reference for an agent or analyst.
Generate LTX Studio marketing & sales daily report with lead gen, spend, PELs/PQLs, sales metrics, and top org usage vs 7-day averages. Use when: daily marketing standup, GTM review, or when asked for 'marketing numbers' or 'lead performance'.
Generate LTX Studio sales opportunities report and credit limit alerts. Covers pipeline by rep/product (yesterday + QTD), new PELs/PQLs, future meetings, and enterprise orgs at 80%+ token usage. Use when: sales standup, pipeline review, account health check, or when asked for 'sales numbers' or 'credit alerts'.
Monitors key metrics and sends alerts for revenue, usage, enterprise accounts, backend costs, and API runtime. Routes requests to specialized monitoring sub-agents.