Cloud Services CRM

In subscriptions revenue loss does not start on renewal day but weeks earlier, when usage drops; because that drop is not visible on the billing side, the cancellation is only noticed when the renewal is refused.

A subscription is a record with start, renewal date and monthly amount fields. In Rapitek CRM, MRR and ARR come out of those fields, and the health score out of the threshold you define.

Calculate MRR, ARR and churn metrics from the amount and date fields on the subscription records
Define the components of the health score and its threshold yourself, and move accounts that fall below the threshold to the top of the list
Send the task tied to the time left until the renewal date to the account owner, and produce the quote from the same record
Open an upgrade opportunity for accounts whose quota and module usage rates cross the threshold

Subscription Record	A subscription is a record with start, renewal date and monthly amount fields. MRR and ARR are calculated from the sum of those fields, and churn from the proportion of cancelled records.
Customer Health Score	You define the components of the score and its threshold; login frequency, the modules used and open support tickets are fields on the account record, and an account that falls below the threshold moves to the top of the list.
Renewal Task	The renewal date is a field on the subscription record; a task tied to the time left until that date goes to the account owner, and the quote is produced from the same record.
Expansion Opportunity	Quota and module usage rates are fields on the account record; an upgrade opportunity is opened for an account that crosses the threshold, and feeding those fields from your product is set up over the REST API or webhooks.

In cloud services a customer is not sold once and done with; they are won again every period. When the number of active users on an account falls, or a critical module stops being used, nothing changes on the revenue statement: the figure looks the same until the renewal month, while the problem has already started.

Rapitek CRM puts usage activity next to the subscription record; when the health score drops, the account surfaces in the list before the renewal date arrives. The same data works in the other direction too: an account pushing the limits of its plan is flagged as an expansion opportunity just as clearly as an at-risk account. We build the carrying of usage data from your own product into the CRM; there is no out-of-the-box module, and the connection is written for each project over the REST API and webhooks.

Frequently asked questions

Can MRR/ARR be tracked?

Yes. MRR, ARR and churn are calculated from the amount and date fields on the subscription records, and the period comparison comes out of the report on those records.

Does it integrate with billing systems?

We build the connection to Stripe, iyzico or your bank; there is no out-of-the-box module, and collections do not land in the CRM by themselves. The connection is built for each project by our professional services team over our REST API covering 183 business objects, OAuth2, webhooks and import/export; we share its scope and cost in writing in the discovery call. When this connection is not built, subscription, collection and usage information is entered into the CRM manually or by file import; MRR, ARR, the renewal date and the health score run on those records.

How do we see the accounts whose renewal date is approaching?

The renewal date is a field on the subscription record; a task tied to the time left until that date goes to the account owner, the renewal quote is produced from the same record, and accounts with a low health score stand out in that list.