Back to all case studies
Platform & Data Engineering
CloudDesk Technologies
Revenue, Churn, and Cohort on One Honest Surface
An executive analytics suite tracking $1.2M MRR, with tenant-safe cohorts and billing that ships beside the first login.
Next.jsClickHousePostgreSQLStripe Billing
Tenant isolation
Board-load time
The Challenge
What was already failing
Leadership had three dashboards and no shared definition of a customer. Cohorts leaked across tenants, and the Monday meeting started with an argument about the export.
The Solution
A query path that is fast, a tenant boundary that is boring, and a board view that matches the ledger.
01 // edge
Query at the edge
Cohort reads stay close to the reader. The board does not wait on a warehouse rebuild.
- Cohorts·Near
- Warehouse·Skip
- Board·Ready
02 // guard
Tenant boundary
Every series is scoped before it is drawn. One company’s churn cannot appear in another’s chart.
- Series·Scoped
- Churn·Private
- Filter·Safe
03 // checkout
The board view
MRR, retention, and billing sit on one surface, with the same number finance already closed.
- MRR·$1.2M
- Retention·One view
- Billing·Stripe = board
Edge
Query at the edge
CohortsNearReader-local
WarehouseSkipNo rebuild wait
BoardReadyMeeting-time
Guard
Tenant boundary
OKSealed
Series
Scoped
Before draw
Churn
Private
No leak
Filter
Safe
Tenant-bound
Checkout
The board view
MRR
$1.2M
Retention
One view
Billing: Stripe = board · No reconcile
The Solution
A query path that is fast, a tenant boundary that is boring, and a board view that matches the ledger.
01 // edge
Query at the edge
Cohort reads stay close to the reader. The board does not wait on a warehouse rebuild.
- Cohorts·Near
- Warehouse·Skip
- Board·Ready
Edge
Query at the edge
CohortsNearReader-local
WarehouseSkipNo rebuild wait
BoardReadyMeeting-time
02 // guard
Tenant boundary
Every series is scoped before it is drawn. One company’s churn cannot appear in another’s chart.
- Series·Scoped
- Churn·Private
- Filter·Safe
Guard
Tenant boundary
OKSealed
Series
Scoped
Before draw
Churn
Private
No leak
Filter
Safe
Tenant-bound
03 // checkout
The board view
MRR, retention, and billing sit on one surface, with the same number finance already closed.
- MRR·$1.2M
- Retention·One view
- Billing·Stripe = board
Checkout
The board view
MRR
$1.2M
Retention
One view
Billing: Stripe = board · No reconcile
Key Capabilities
What the system is trusted to do
01
Cohorts without a rebuild
Retention curves resolve for the meeting, not for the next morning’s export.
02
Tenant-safe series
Charts are scoped before they render. A filter cannot leak another customer.
03
Billing beside the login
Stripe state and the executive number are the same figure, not a reconciliation project.
Architecture
How the pieces connect
Engineered With
- Next.js
- ClickHouse
- PostgreSQL
- Stripe Billing
Results and Impact
The suite now carries $1.2M in tracked MRR. The Monday meeting starts from the screen, not from a spreadsheet argument.
- $1.2M tracked MRR on one board
- Tenant isolation held at 100%
- Monday meetings start from the screen, not an export
$1.2M
Tracked MRR
100%
Tenant isolation
<180ms
Board-load time
SaaS · CloudDesk Technologies
An executive analytics suite tracking $1.2M MRR, with tenant-safe cohorts and billing that ships beside the first login.
“We stopped reconciling the dashboard against the ledger.”
Start
A system with a number you can defend.
Tell us the constraint. We reply within one business day.