Architecture
How RetentBase fits into your cancellation flow.
RetentBase sits between the moment a customer wants to cancel and the moment your team decides what to do with that reason.
It captures cancellation context and creates a review workflow. Your product, billing system, subscription changes, and customer communication stay under your control.
Data boundaries
The architecture follows the cancellation moment.
The important boundary is simple: RetentBase helps you capture and review why customers leave. It does not take over your billing system or the rest of your product.
Cancellation context
RetentBase receives the reason a customer selected and the context needed to review that reason later.
Billing boundary
RetentBase does not replace your billing system or make subscription changes automatically.
Review workspace
Your team uses RetentBase to review automatically detected churn issues and record what should happen next.
Clear responsibilities
What RetentBase handles, and what stays with you.
This is the practical architecture customers need to understand before integrating: RetentBase owns cancellation reason review, while product and billing control remain yours.
Responsibility
What RetentBase does
Captures cancellation reasons, automatically detects repeated reasons as reviewable issues, stores team decisions, and exposes docs and APIs for integration.
Responsibility
What stays with your product
Account access, product UX outside cancellation, billing authority, subscription changes, and customer communication remain under your control.
Responsibility
What your team decides
Act on an automatically detected issue, dismiss it, or resolve it after the pattern changes. RetentBase gives you the queue, not an automatic recovery promise.
Implementation paths
Move from architecture review to a clean launch path.
Start with the hosted flow when you want the smallest integration. Add public ingestion APIs when your product needs deeper control over the cancellation UX.
Related implementation pages
Continue from architecture into product decisions.
Use these pages to move from architecture review into the workflow, implementation, and product decisions that usually follow it.
Understand churn clearly
Start with the pages that define churn, interpret the signal, and give your team a reliable language for what is happening.
Guide
SaaS churn guide
A high-level operating guide for churn rate, churn analysis, and retention management in subscription SaaS.
Cluster
Churn reasons
Use structured churn reasons to understand what customers are actually saying when they leave.
Metric
Customer retention rate
Define customer retention rate clearly and connect it to the decisions your team needs to make next.
Benchmark
SaaS churn rate benchmark
Compare churn rate with the right context instead of relying on generic averages that flatten segment reality.
Run the retention workflow
These pages are for teams that already know churn matters and need a management cadence around review, ownership, and follow-through.
Problem
Churn review process
See why teams miss the signal when churn review is informal, fragmented, or too late to change outcomes.
Playbook
Run weekly churn review
A practical playbook for turning churn issues into one recurring review with owners and next actions.
Framework
Churn ownership framework
Define who owns churn decisions without isolating the work to one team that lacks the full picture.
Report
Weekly churn report
Build a weekly churn view that supports decisions instead of adding another passive reporting surface.
Evaluate implementation and stack fit
Move from strategy into product evaluation, implementation planning, and the systems that hold the evidence behind churn.
Comparison
RetentBase vs ChurnZero
Separate customer-success tooling from a churn decision workflow before the buying conversation collapses into features.
Integration
Stripe integration
Understand how billing data and cancellation events from Stripe fit into a retention review system.
Docs
API docs
Public integration docs for the hosted cancellation flow and the advanced RetentBase API surface.
Architecture
Architecture
Review the production architecture behind cancellation ingestion, issue detection, billing boundaries, and workers.