Skip to content
This repository has been archived by the owner on Jul 2, 2024. It is now read-only.

Commit

Permalink
Update multi-sku-arr.md (#8788)
Browse files Browse the repository at this point in the history
Co-authored-by: kmorris50 <[email protected]>
Co-authored-by: sourcegraph-bot <[email protected]>
  • Loading branch information
3 people authored Mar 27, 2024
1 parent 7c0e919 commit 065c171
Showing 1 changed file with 46 additions and 1 deletion.
47 changes: 46 additions & 1 deletion content/departments/finance/multi-sku-arr.md
Original file line number Diff line number Diff line change
@@ -1 +1,46 @@
test markdown for Tommy and Kendrick hello!
### Multi-SKU ARR Recognition

In line with the Company's Cody + Search strategy, Finance believes it is important to introduce a multi-SKU ARR recognition guidance. Multi-SKU ARR recognition provides more granular insights into product performance, aids in customer segmentation, supports revenue optimization, and boosts investor confidence. By documenting and following this process, the company ensures accurate financial reporting, effective decision-making, and sustainable growth in the competitive market landscape.

Currently, we are categorizing enterprise ARR into four buckets:

-Professional Services ARR
-Platform or Recurring Fee ARR
-Software ARR
-Code Search ARR
-Cody ARR

Note: If we change methodologies, we will do so only in SFDC or a system of record. The ARR tracker does not scale for multi-product ARR recognition.

### Professional Services ARR Recognition

When calculating ARR recognition by SKU, we will apply discounting for software + services purchases according to the following rules:

-Discounts are first applied against all one-time/non-recurring revenue. E.g., implementation fees.
-Discounts are then applied proportionally against all included SKUs based on list prices.
-So if the customer was buying $100k (list price) of software and $50k (list price) of recurring services, but they were only paying $135k (i.e., they got a 10% discount), then we would record it and report it as $90k of software ARR and $45k of services ARR — 10% off of each product at list price.

Note that professional services must have their own line item(s) to get ARR recognition. If professional services are clearly outlined in terms of SKU name(s), quantity and price, the value should be excluded or carved from Search & Cody ARR.

### Platform Fee ARR Recognition

-Platform fees or any other ongoing fee charged to the customer will also impact the value of ARR, and will be applied directly to platform fee SKU. If for example the customer was buying $100K of Code Search Enterprise, but we also charged them a $10K Platform Fee, then we would record it and report it as $110K of total software ARR: $10k as Platform Fee ARR and $110k as Code Search Enterprise ARR.

### Software (Code Search & Cody) ARR Recognition

-Cody-only or Code Search-only deals are perhaps the most straightforward in which 100% of the seat quantity times price is attributable to Cody or Code Search, respectively.
-Code Intelligence platform deals are less straightforward in terms of product ARR allocation, given the standalone list prices for Search ($588) & Cody ($228) added together ($816) are greater than the Code AI list price ($708). Finance’s recommendation is to keep the same percent allocation of the standalone prices added together.

For Code Intelligence Platform:
-Cody ARR percent allocation for each unit at Code Intelligence Platform list price equals $288 / ($228 + $588) = 28%
-Search ARR percent allocation for each unit at Code Intelligence Platform list price equals $588 / ($228 + $588) = 72%

For Code Intelligence Platform (Cody BYOK):
-Cody ARR percent allocation for each unit at Code Intelligence Platform list price equals $180 / ($180 + $588) = 23%
-Search ARR percent allocation for each unit at Code Intelligence Platform list price equals $588 / ($228 + $588) = 77%

-If the Search & Cody seats differ, then, the Code Intelligence allocation does not apply. 100% of the seat quantity times price is attributable to Cody or Code Search, assuming we have factored in PS (including one-time fees) & platform fees..
-Cross-sells

- If the product is listed as beta,then we will not recognize product-level ARR even if there is a clearly defined seat quantity and price (annual)
- It is likely (especially in the context of repricing) that a deal will have an increase in Cody ARR that corresponds to a reduction in Search ARR. However, this may have a net zero effect in overall contract churn.

0 comments on commit 065c171

Please sign in to comment.