// 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'.
| name | ltx-marketing-daily-report |
| description | 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'. |
| tags | ["reporting","daily-metrics","ltxstudio","marketing","sales"] |
| 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 go-to-market performance: marketing spend and lead generation, sales activity (reach-outs, meetings), top enterprise org usage, new activations, and credit limit summary.
Slack channel: #ltx-marketing-auto-report
bq --project_id=ltx-dwh-explore query --use_legacy_sql=false --format=pretty "$(cat queries/marketing_sales_daily_report.sql)"
The query returns marketing & sales metrics including:
Key tables:
ltx-dwh-prod-processed.marketing.sf_perf_marketing_agg_w_spend (marketing spend & leads)ltx-dwh-prod-processed.marketing.final_sf_lead_opportunity (sales metrics)See shared/bq-schema.md for full table schemas.
Format per references/report-template.md.
Flag any metric deviating >50% from 7-day average.
shared/bq-schema.md — Table schemas, columns, joins, segmentation CTEsshared/metric-standards.md — Standardized metric definitions with SQLshared/product-context.md — LTX Studio overview, user types, business model--project_id=ltx-dwh-exploreis_enterprise_user flag — use org-based enterprise logicdate(action_ts) >= ...)ltx_studio = true on sales funnel tableis_lt_team = false on all user-level queriesSAFE_DIVIDE for all percentage calculationsshared/bq-schema.md)User: "Marketing daily report"
User: "How did leads perform yesterday?"
User: "Marketing performance vs last week"
User: "Run the GTM 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 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'.
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.