How to build Maxio revenue dashboards in Metabase

{
  "mcpServers": {
    "maxio": {
      "url": "https://<your-maxio-mcp-endpoint>",
      "headers": {
        "Authorization": "Bearer <MAXIO_SCOPED_TOKEN>"
      }
    }
  }
}

# Install the Metabase CLI
npm install -g @metabase/cli

# Log in (opens your browser; requires Metabase v62+)
mb auth login --url https://your-metabase.example.com

# Load a Maxio CSV export — creates a table AND a model
mb upload csv --file maxio-subscriptions.csv --collection root

# Refresh that same table later from a new export
mb upload replace <table-id> --file maxio-subscriptions.csv

Create a polished Metabase dashboard for Maxio subscription and SaaS-metric
analytics.
Work end to end: get the data into Metabase if it isn't there yet, then build.

Goal: Help finance and RevOps leaders understand recurring revenue (MRR/ARR),
churn, retention, billings, and usage/component revenue from Maxio (Chargify +
SaaSOptics) data.

Step 1 — Find or load the data:
- First, check what already exists in Metabase (search for Maxio tables and
  models). If durable Maxio data is already present — synced from a warehouse or
  uploaded earlier — use it and skip to Step 2.
- If nothing is there, pull it with the Maxio MCP server using scoped, read-only
  credentials: customers, subscriptions, products/price points, components,
  invoices, and transactions. Write each result to a CSV, then load it with the
  Metabase CLI — run "mb upload csv --file <export>.csv" so each upload creates a
  table and a ready-to-query model. Use "mb upload replace <table-id> --file
  <export>.csv" to refresh an existing table instead of creating duplicates.

Step 2 — Inspect before querying:
Do not assume exact table names. Map the available raw tables into these
analytical concepts where possible: Customers, Subscriptions, Products/Price
points, Components (metered / add-on), Invoices, Transactions, and (if present)
Revenue schedules. Inspect the actual tables and column names first.

Important:
- Build on whatever data is present; don't claim Metabase connects natively to
  Maxio — it reads a database or CLI-uploaded tables.
- Compute MRR from active recurring subscription revenue, normalizing to a
  monthly amount; keep metered/usage and one-time revenue separate.
- Separate voluntary churn from failed-payment (dunning) churn.
- For revenue recognition, use recognized/deferred schedules, not billings.
- Report in a single reporting currency.
- Only build a card if its underlying column/metric exists in the data.
- A single CSV is a point-in-time snapshot: MRR movement and cohorts need
  history, so build trend cards only if a warehouse sync or multiple uploads
  provide it.

Dashboard title: Maxio Revenue Overview

Sections:
1. Executive summary (KPI cards): MRR; ARR; Net new MRR; Gross revenue churn %;
   Net revenue retention; Accounts receivable.
2. MRR & ARR: MRR movement by month; ARR by product/price point; New vs. renewal.
3. Churn & retention: Logo vs. revenue churn; Gross vs. net retention; Renewal
   rate by cohort.
4. Billings, AR & dunning: Invoiced revenue; AR aging; Failed payments and
   recovery.
5. Usage & components: Metered usage; Component attach rate; Overage revenue.

Filters: Product, Price point, Component, Currency, Date range.

Reuse the models Metabase auto-created from uploaded CSVs, or (for a warehouse)
create reusable models: modeled_maxio_subscriptions, modeled_maxio_components,
modeled_maxio_invoices, and modeled_maxio_mrr (a monthly per-subscription MRR
model).

Output: Build the dashboard if you have permission; otherwise provide the exact
questions, SQL, model definitions, and layout. Include caveats for any metric
that cannot be calculated from the available data. Reconcile totals against
Maxio. Keep it practical, dense, and executive-readable. Avoid vanity metrics.

Sum a monthly MRR model built from active recurring subscriptions.

-- Requires a monthly MRR model built from active Maxio subscriptions
SELECT
  ROUND(SUM(mrr), 2)       AS mrr,
  ROUND(SUM(mrr) * 12, 2)  AS arr,
  COUNT(*)                 AS active_subscriptions
FROM modeled_maxio_mrr
WHERE month = date_trunc('month', CURRENT_DATE);

Cancellations and the recurring revenue lost with them.

SELECT
  date_trunc('month', canceled_at)                    AS month,
  COUNT(*)                                            AS churned_subscriptions,
  ROUND(SUM(mrr_at_cancel), 2)                        AS churned_mrr
FROM subscriptions
WHERE state = 'canceled'
  AND canceled_at >= CURRENT_DATE - INTERVAL '12 months'
GROUP BY 1
ORDER BY 1;

Metered and add-on revenue, kept separate from MRR.

-- Metered / add-on component revenue by month
SELECT
  date_trunc('month', period_ended_at) AS month,
  c.name                               AS component,
  ROUND(SUM(cu.amount) / 100.0, 2)     AS component_revenue
FROM component_usages cu
JOIN components c ON c.id = cu.component_id
GROUP BY 1, c.name
ORDER BY 1, component_revenue DESC;