Use case · Revenue Operations
What was our churn last month?Same question. Same number. Every time.
Two people ask on different days and get the same 4.1%. The number comes from one declared definition, not from whichever table a query happened to find.
How it is answered
Same question.
One definition. One answer.
Aether links every measure it discovers to the term your business declared, and answers from that declaration.
What was our churn last month?
What was our churn last month?
Both answers come from one definition ↓
- Formula
- Paid subscriptions that ended in the month ÷ paid subscriptions active on the first day
- Filter
- Paid plans only · trials and internal accounts excluded
- Calendar
- Fiscal calendar, by month
- Declared by
- Finance · certified 2 Sep 2026
-- from: Churn (declared, certified) SELECT COUNT(*) FILTER (WHERE ended_at >= p.starts AND ended_at < p.ends)::numeric / COUNT(*) FILTER (WHERE started_at < p.starts AND (ended_at IS NULL OR ended_at >= p.starts)) AS churn FROM subscriptions CROSS JOIN fiscal_month('2026-09') p WHERE plan_type = 'paid' AND account_kind NOT IN ('trial', 'internal');
Fig. — Two people, one definition, one numberIllustrative data
- 01Finds the declared definition
Churn, certified by Finance: formula, filter and fiscal calendar in one place.
- 02Writes the query from it
The SQL follows the declaration and never steps outside it.
- 03Locks the query
Refreshes and automations run it again; they never rewrite it.
- 04Shows where the number came from
Lineage and certification are one tap away. With no definition yet, Aether says what it assumed and asks to define it.
- Knowledge Hub
Declared once, used everywhere.
- Cortex
Where meaning and memory meet.
- Trust
Every number shows its proof.