00 · SUBFeature · Subscriptions

Subscription lifecycle
with adult supervision.

Mid-cycle changes, ramps, overrides, downgrades, pauses, renewals — all instrumented, all reversible, all with the audit trail Stripe never gave you on its own.

01 · WHATWhat it is

Subscriptions are workflows.
Not configuration.

Most billing tools treat a subscription as a static record. In reality it’s the longest-running workflow your business has — twelve months of overrides, renewals, mid-cycle changes, and edge cases. Merged treats subscriptions like the workflow they are: every motion is a tracked event, every change is reversible, and every commercial exception lives next to the contract that authorized it.

Active · cycle 14/24

Subscription · ACME

LIVE
PlanENT · ANNUAL
MRR$15,333
Next invoiceMar 14
Active overrides02
RenewalQ3 · 90d
SyncOK
02 · INSIDEWhat's inside

The primitives.
Each one defensible.

We don’t ship features as bullet points. Each capability earns its place by replacing a tool, a script, or a meeting that exists in your stack today.

01

Mid-cycle changes

Add seats, swap plans, change billing cadence — proration handled by Stripe, recorded by Merged, defended by audit log.

02

Overrides as first-class entities

Custom discount, special term, indemnity clause — each override is queryable, expirable, and tied to the operator who issued it.

03

Renewal automation

90, 60, 30, 7-day pings to BD with full account context. No more 'we missed a renewal' incidents.

04

Lifecycle states

Trialing, active, paused, downgraded, cancelled, churned — modeled explicitly. Reports built on these states tell the truth.

05

Failed payment recovery

Dunning that respects the customer relationship. Operators see at-risk subs surfaced before the relationship breaks.

06

Bulk operations

Migrate cohorts when pricing changes. Apply overrides to a segment. All with a preview, a confirm, and a rollback.

03 · FLOWThe subscription workflow

How it actually
moves through your team.

  1. 0101 · Provision

    Quote acceptance creates the sub.

    Custom terms from the quote flow into Stripe automatically. The dial shows the new sub, its terms, and its renewal date instantly.

  2. 0202 · Operate

    Day-to-day from one surface.

    Operators handle support requests, plan changes, and cadence swaps without opening Stripe admin.

  3. 0303 · Override

    Commercial exceptions, recorded.

    BD issued a partner discount? Finance authorized a credit? Both are first-class overrides, queryable and expirable.

  4. 0404 · Renew

    Pings before churn risk.

    BD gets context-rich pings months in advance. The renewal motion starts a quote that closes back into the same subscription.

  5. 0505 · Recover

    Failed payments handled with care.

    Dunning that preserves the relationship. At-risk subs surface for operator follow-up before the customer leaves.

  6. 0606 · Retire

    Cancellations with audit trail.

    Why did this customer leave? Who decided to let them? When did the last invoice ship? All in one record.

04 · DIFFSide-by-side

Before Merged.
After Merged.

We measure ourselves by the work we delete. Every row below is a tool, a script, or a meeting that no longer needs to exist.

Dimension
Stripe + tickets + Slack
Merged Subscriptions
Override authorization
Slack DM, manual Stripe edit, hope it sticks.
Operator action with diff, expiry, and audit trail.
Renewal calendar
A spreadsheet someone updates twice a quarter.
Live pings 90/60/30 days out with full account context.
Mid-cycle changes
Engineering ticket because Stripe admin is too risky for ops.
Operator self-service with finance review on consequential motions.
At-risk visibility
Found out at month-end during reconciliation.
Surfaced in the dial when the second payment fails.
05 · FAQCommon questions

What buyers ask before signing.

Short, honest answers. The full answer lives inside the product.

01Does this work with usage-based pricing?
+
Yes. Metered billing, hybrid plans, and committed-use discounts are first-class. We meter against your usage source and bill the difference correctly.
02Can we model multi-year ramps?
+
Yes. Ramps, mid-cycle adds, and step-up pricing all model in the quote and flow into the subscription automatically.
03What about dunning customization?
+
Dunning sequences are configurable per cohort. You decide when to escalate, when to involve BD, and when to write off.
04How do we handle multiple subscriptions per customer?
+
Customers are first-class. Subscriptions, quotes, invoices, and credit notes hang off the customer record cleanly. The dial reads as one timeline.
06 · OPENTry this surface

Move subscription ops
off the engineering backlog.

Wire your Stripe account, import your existing subs, and watch every commercial exception land on a surface designed for the people who actually authorize them.