Data & Analytics
Your metrics, compiled before you ask.
ZeroTwo automates weekly KPI reporting by running SQL against your Postgres or MySQL database, computing week-over-week and month-over-month trends, and delivering a formatted Google Sheets spreadsheet every Monday morning.
What changes
Prep time
Monday morning spent fixing queries and pasting into sheets
Delivered before you wake up
Query maintenance
Breaks silently when schemas change, nobody notices for weeks
Validated before each run, failures flagged immediately
Auditability
Numbers in a spreadsheet with no way to trace how they were computed
Results include the source queries so any number can be verified
Ad-hoc follow-ups
"I'll follow up after the meeting" (takes all afternoon)
Segment breakdowns already included in the spreadsheet
The weekly metrics meeting starts in 30 minutes. The spreadsheet is stale.
All the data is technically in one place. Stripe syncs to Supabase via Fivetran, PostHog events land in the same Postgres cluster, product tables are native. But the queries were written by a data hire who left in August.
Monday morning becomes re-deriving everything by hand. The data exists. The queries should be simple. The gap between those two things is filled with broken views, stale CTEs, and tribal knowledge that left six months ago.
How ZeroTwo builds your KPI report
Pulls revenue and billing metrics from synced Stripe tables
SupabaseMRR, net new, expansion, and churn broken down by plan tier and customer segment, computed against your targets. SQL visible in the execution log.
Pulls product engagement and adoption data
SupabaseDAU, activation rate, and feature adoption computed from PostHog events and native product tables. WoW and MoM trends derived from timestamp data.
Computes derived metrics and flags outliers
GoogleZeroTwo calculates NRR and churn rate by segment from raw query results, then flags any metric with unusual week-over-week movement. Sandbox code is inspectable.
Writes the formatted spreadsheet with audit trail
Google SheetsZeroTwo delivers executive summary, detailed trends, and raw data in separate tabs. A metadata tab logs every query that ran and the row counts returned.
Get started in under 10 minutes
Connect your tools
One-click OAuth for each integration. No API keys, no engineering.
Describe what you need
“Every Monday, pull MRR, active users, churn rate, and NPS from our Supabase database. Compute WoW and MoM trends, then deliver the spreadsheet to #metrics in Slack.”
It runs on schedule
Every Monday morning, the updated spreadsheet lands in your team channel.
Frequently asked questions
Yes. Every query is visible before execution. You can edit the SQL, adjust joins, or add filters. Execution logs show what ran, how long each query took, and how many rows returned. Nothing runs as a black box.
ZeroTwo can connect to Stripe and PostHog via API alongside your database. But if you already sync via Fivetran or Airbyte, ZeroTwo queries the database directly. One connection, faster execution, your existing pipeline stays the source of truth.
ZeroTwo validates every query before each run. If a column was renamed or a view stopped refreshing, the report flags the specific metric that failed instead of delivering stale numbers silently.
Yes. Net revenue retention, churn rate by segment, custom ratios. ZeroTwo computes them in a code sandbox from the raw query results. You define the formula once. The sandbox code is inspectable so you can verify the math.
ZeroTwo runs read-only queries with configurable timeouts. Point it at a read replica for large datasets. Query performance is logged so you can monitor and optimize.
Related workflows
- Data & AnalyticsCohort Retention Analysis
- FinanceRevenue Variance Analysis
- Data & AnalyticsScenario Modeling
Stop doing the work your tools should do for you.
Set it up once. ZeroTwo runs it every time.