Revenue Recognition |
3 Months Ended | ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
Mar. 31, 2026 | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| Revenue from Contract with Customer [Abstract] | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| Revenue Recognition | Revenue Recognition Revenue is recognized, in an amount that reflects the consideration the Company expects to be entitled to over the term of the agreement, when control of the Company’s product offerings are transferred to customers. The Company recognizes revenue through the following five-step framework in accordance with ASC 606, Revenue from Contracts with Customers: (1) Identification of the contract, or contracts, with the customer; (2) Identification of performance obligations in the contract; (3) Determination of the transaction price; (4) Allocation of the transaction price to the performance obligations in the contract; (5) Recognition of revenue when, or as, the Company satisfies a performance obligation. A performance obligation is a promise in a contract to transfer a distinct solution to the customer. The Company identifies performance obligations in its contracts with customers, which primarily include usage-based and subscription contracts. Usage-based contracts include fees based on usage of the Company’s platform or professional services, incurred on a time and materials basis, while subscription contracts represent the purchase of a committed data volume on the Company’s platform over a period of time. The transaction price is determined based on the amount which the Company expects to be entitled to in exchange for providing the promised services to the customer. For contracts that include multiple performance obligations, the transaction price in the contract is allocated to each distinct performance obligation on a relative standalone selling price basis. Revenue is recognized over time as performance obligations are satisfied. Variable consideration is evaluated on a contract-by-contract basis, and a constraint is applied using the facts and circumstances of the contract when applicable. On a limited basis, the Company enters into contracts whereby the consideration payable is contingent upon the conclusion of the legal matter. The Company does not recognize the revenue related to these contracts until the legal matter is resolved. Such amounts recognized have been immaterial to date. The Company’s software contracts do not allow the customer to take possession of the software supporting the cloud-based platform. Customers are not entitled to any refunds. The Company’s arrangements do not contain general rights of return. However, credits may be issued on a case-by-case basis. Amounts that have been invoiced are recorded in accounts receivable and in revenue or deferred revenue depending on whether the revenue recognition criteria have been met. Nature of Contractual Arrangements The Company’s revenue-generating activities directly relate to the sale and support of its legal product offerings within a single operating segment. The Company disaggregates revenue from contracts with customers based on how the nature, amount, timing and uncertainty of revenue and cash flows are affected by economic factors. The Company has two primary types of contractual arrangements: usage-based and subscription. Usage-based revenue is generated from contracts that are typically billed on a monthly basis and can be canceled with one month’s notice or are incurred on a time and materials basis. Subscription revenue is derived from contracts where customers are contractually committed to a fixed data volume over a period of time. Usage amounts above the fixed data volume are considered usage-based revenue. Subscription arrangements are billed in advance, typically on a monthly, quarterly or annual basis. Subscription revenue is recognized ratably over the life of the contract. In the three months ended March 31, 2026 and 2025, usage-based revenue represented 91% and 90% of total revenue, respectively, and subscription revenue fees represented 9% and 10% of total revenue, respectively. No significant judgments are required in determining whether services are considered distinct performance obligations and should be accounted for separately versus together, or to determine the stand-alone selling price. Deferred Revenue Deferred revenue primarily consists of amounts that have been billed to or received from customers in advance of performing the associated services. Of the $5.4 million and $4.3 million of deferred revenue as of December 31, 2025 and 2024, the Company recognized $2.6 million and $2.0 million as revenue during the three months March 31, 2026 and 2025, respectively. As of March 31, 2026 and December 31, 2025, the Company recorded $4.3 million and $5.4 million of current deferred revenue, respectively. The Company has no non-current deferred revenue as of March 31, 2026 and December 31, 2025. Remaining Performance Obligations Remaining performance obligations (“RPO”) represent the amount of contracted future revenue that has not yet been recognized, including both deferred revenue and non-cancelable contracted amounts that will be invoiced and recognized as revenue in future periods. RPO exclude performance obligations from certain time and materials contracts that are billed in arrears. RPO are not necessarily indicative of future revenue growth because they do not account for consumption in excess of contracted capacity. As of March 31, 2026, the Company expects to recognize approximately $20.2 million of revenue from RPO. The Company expects to recognize revenue of approximately $13.3 million as of March 31, 2026 from RPO over the next 12 months, with the remaining balance recognized thereafter. Incremental Contract Costs Incremental costs to obtain or fulfill a contract are recognized as an asset if the expected benefit is determined to be longer than one year. These assets are amortized over the expected period of benefit. As of March 31, 2026 and December 31, 2025, there were no material incremental costs to obtain or fulfill a contract, primarily based on the nature and terms of the Company’s contracts. Revenue by Groups of Similar Offerings and Geographic Area The following table sets forth revenue by groups of similar offerings (in thousands):
Software is comprised of revenues related to the Company’s DISCO Hold, DISCO Request, DISCO Ediscovery, and DISCO Case Builder products, as well as revenue related to Cecilia AI platform and the use of software within Auto Review. Services is comprised of revenues related to the Company’s DISCO Review offering and professional services, including services support for Auto Review. The Company determines the location of revenue using the billing address of each customer. The following table sets forth revenue by geographic area (in thousands):
|
||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||