Skip to content

Who stays, skips or cancels after every box

Connect the warehouse or database your subscription billing and store data land in, then ask in plain English: active subscribers against the 1st, gifts that turned paid, failed payments by decline code, churn by box and skips before the next cut-off.

For subscription-box and replenishment businesses in beauty, food, pet, kids and books, and their retention and operations teams.

Free plan. No credit card required.

Try a question

All 10 questions

ChatSubscriber agent

Active subscribers today against the 1st: what drove the change?

AI Analyst

Active subscribers rose 1,640 to 49,850 this month. New and returning subscribers added 3,560; cancellations and failed payments took 1,920.

On the 1st48,210

New+3,140

Reactivated+420

Cancelled−1,248

Failed payment−672

Today49,850

Readsubscriptionssubscription_eventsSQL

Keep itPin to dashboardEmail it weeklyAlert me

Sample data

Ask this on your own data

Every question, by who asks it

Taken from what teams in this industry ask Supaboard. Each one opens a free account with the question waiting.

01 · Retention

02 · Payments

03 · Gifts and the next box

Keep it running

What teams keep on a schedule once they've asked the question once.

Report · Daily 08:00

Payments still unrecovered

Every failed renewal from the last 7 days that hasn't recovered, with its decline code, in the retention lead's inbox.

  1. Timed Start
  2. Query Your Data
  3. Summarize Insights
  4. Send Email

Alert · Every 5 minutes

Payment-failure spike

A SQL check compares the latest day's renewal failure rate with the 30-day average and calls your webhook when it jumps.

  1. Alerts
  2. Send Webhook

Datasite · Month end

The board datasite

Active subscribers, churn by box, failed payments and gifting, on a private datasite the founders and board sign in to with Google or Microsoft.

The numbers it keeps watch on

Standard definitions, and where each one lives in Supaboard once you've asked for it.

MeasureDefinitionSourceIn Supaboard
Active subscribersPaid subscriptions not paused or cancelled at the end of the dayCommon practiceDaily report
Net subscriber changeNew + reactivated − cancelled − ended by failed payment, from the 1st to todayCommon practiceBoard datasite
Churn by boxCancellations within 14 days of a box shipping ÷ subscribers sent that boxCommon practiceAsk it after every release
Involuntary churnSubscriptions ended by a failed payment ÷ all subscriptions endedCommon practiceDaily report
Payment recovery rateFailed renewals later paid ÷ failed renewals, by decline codeCommon practiceDaily report
Gift redemption rateGift cards activated ÷ gift cards soldCommon practiceSeasonal question
Gift-to-paid conversionGift recipients who pay for a renewal ÷ gifts activatedCommon practiceMonthly question
Skip rateSubscribers skipping the next box ÷ active subscribers at cut-offCommon practiceCut-off week report

Where your data lives

Or attach an export to a conversation, as CSV or Excel:

  • XLSSubscription-app exportsUpload

The tables these questions read:

  • Subscriptions and their status history: active, paused, skipped, cancelled
  • Box releases and editions, with cut-off and ship dates
  • Gift cards and redemptions
  • Invoices and charges, with decline codes
  • Shipments by subscriber, box and variant

Teach it your definitions once

Rules are read with every question, so a term means the same thing in Chat, in Slack and in the Monday report.

  • Rule“Active means a paid subscription that isn't paused or cancelled at the end of the day.”
  • Rule“A gift converts when its recipient pays for a renewal.”
  • Rule“A cancellation counts against the last box shipped to that subscriber.”
How rules work

Already running on it

A subscription-box business on BigQuery tracks gift-card activations, active subscribers, payment incidents and churn by release on Supaboard.

A Supaboard customer, described without its name

Security

Read-only by construction

Database and warehouse queries are read-only. We give you the SQL for a read-only user too.

Credentials stay in the workspace

Scoped to the one workspace that connected them, never logged and never sent back to a browser.

SOC 2 Type II

An organisation-wide audit of the platform, covering every plan.

Frequently asked questions

Does it work with Stripe, Chargebee and Shopify?

Yes, through the warehouse or database their data lands in. Connect BigQuery, Snowflake or Postgres and your subscriptions, charges and orders are queried in place, read-only. There's no direct app connector: for a one-off question, export from the app to CSV or Excel and attach it to a conversation.

How does it tie a cancellation to a box?

Write it once as a rule, such as "a cancellation counts against the last box shipped to that subscriber". The agent reads its rules with every question, so churn by box means the same thing in Chat, in Slack and on the board datasite.

Can we see failed payments every morning?

Yes. An automation runs the question at 08:00 in your timezone and emails the list, with decline codes.

Can the team ask from Slack?

Yes. Mention Supaboard in a channel or message it directly, and the answer comes back in Slack. Claude can connect over MCP as well. Your data stays read-only.

Can it change anything in our billing or store?

No. Database and warehouse queries are read-only. Changes to connected apps require your approval.

Ask your first question on your own data

Connect a source, ask in plain English, and keep what you find.

Start FreeBook a 30-minute demo

Free plan. No credit card required.