GASP
Core Customer Count Metrics Outcome

Total Customers

Total Customers: The number of active customers at the end of the period.

Formula

Total Customers = Count of customers with customer_status = active at period end

Computable definition

The canonical formula in the GASP formula grammar. The MCP server compiles it to SQL over the datasets listed below.

count_distinct(field.customer_id where field.customer_status = 'active') at period_end

Unit: count

Breakdowns

  • by_segment: one row per segment value

Notes: Active customers at period end, one per billing entity. ARPA divides by it and Logo Churn Rate reads it at period start. by_segment returns one row per customer segment.

Data requirements

Grain: End-of-month snapshot · Frequency: Daily sync · Aggregation: snapshot (month) · Staged: no · Main source: Billing.

Field Dataset Type
customer_id customer string
customer_status customer string
snapshot_date customer date
Example SQL (Postgres)
SELECT (SELECT COUNT(DISTINCT customer_id) FROM customer WHERE snapshot_date = :period_end AND customer_status = 'active') AS total_customers

Access: recommended sensitivity tier internal, access scope unscoped. Guidance your policy engine enforces.

From an agent: with the GASP MCP server, call lookup_metric({ "name": "Total Customers" }) or generate_query({ "metric": "Total Customers", "adapter": "<your adapter JSON>" }).

What It Tells You

The size of the base. Watch it beside MRR, since a base growing faster than MRR means ARPA is falling.

Connected in the GASP relationship graph.

Downstream: what this drives

  • Total Customers component of ARPA (Core)
  • Total Customers component of Logo Churn Rate (Core)
  • Total Customers measures Customer (Entity)

Try searching for:

↑↓navigate↵select