From nothing to first invoice.
Three phases, walked in order. Tap any step to open its concept page. Checkmarks save locally — pick it up where you left off.
Phase 1
Set up your catalog
Build your product once. You rarely touch this again.
- Open ›Configure your TenantName, reporting currency, invoice prefix, tax setup.
- Open ›Create RegionsOne per market you sell in. Each has a default currency.
- Open ›Create Feature FlagsThe smallest switches — one per capability you want to toggle.
- Open ›Define MetersAnything you meter: seats, storage, calls, GMV. Optional up front — components can provision one for you.
- Open ›Author Variable ComponentsName the component and choose a pricing model: flat, tiered, overage, commission, … No need to create a Meter first.
- Open ›Set Variable Component PricesPublish the numbers per currency, optionally overridden at module/bundle scope.
- Open ›Compose ModulesPin Variable Component versions and Feature Flags into capability groups with tiers.
- Open ›Compose BundlesPin Module versions into the plans customers buy: Starter, Pro, Enterprise.
Phase 2
Sell to a customer
Now your catalog is purchasable.
- Open ›Create a ClientYour customer. Assign them to a Region.
- Open ›Create a SubscriptionPin a Bundle version (or Module version) plus any extra Variable Components.
- Open ›Optionally negotiate a private dealA Custom Pricing Agreement overrides one component for one customer at next renewal.
- Open ›Revvly emits a CREATED eventMRR goes up. Analytics update.
Phase 3
Run the subscription
Things happen. Revvly records them.
- Open ›Stream usage eventsCounters update on each Subscription Variable Usage row in real time.
- Open ›Invoices are issuedEach renewal cycle, plus variable-usage true-ups and expansion charges.
- Open ›Mid-cycle changes become ExpansionsNew modules, version upgrades, commitment raises — prorated automatically.
- Open ›Adjust price with Discounts and overridesBounded, reversible reductions via Discounts; outright rate replacements via subscription-scoped overrides.
- Open ›Renewals and churn happenLifecycle events are written for every moment that moves the needle.
- Open ›Analytics rebuild from the event logMRR, ARR, NRR, churn — always derived, never manually edited.