Subscription revenue console

Overview

Once a SaaS product has paying customers, someone has to answer questions like: who is about to renew, whose card failed, which plan is growing? This concept gathers those answers in one console and keeps the numbers traceable back to individual accounts.

The problem it explores

Early SaaS teams track plans, renewals and failed payments across billing tools and spreadsheets, and learn about churn too late.

Design decisions

1. Every number drills down

   Recurring revenue, churn and failed payments each link to the accounts behind them, so a figure is never a dead end.

2. Attention-first layout

   Upcoming renewals and failed payments sit at the top, because those are the items that need action today.

3. Built to extend

   Plans, add-ons and customer attributes are modelled as data, so adding a new plan is configuration rather than a code change.

What the concept includes

• Recurring revenue overview with plan breakdown
• Upcoming renewals and at-risk accounts
• Failed payment tracking
• Customer list with plan, status and lifetime value
• Billing events history per account

Under the hood

A Next.js console with a Django API and PostgreSQL, with Stripe as the billing provider. Webhooks keep local subscription data in step with Stripe, and metrics are computed from stored events so figures can be audited.