Use of Estimates

The preparation of these unaudited condensed consolidated financial statements in conformity with GAAP requires management to make estimates and judgments that affect the reported amounts of assets, liabilities, revenue and expenses, and disclosure of contingent assets and liabilities. Significant estimates and assumptions reflected in these unaudited condensed consolidated financial statements include, but are not limited to, those related to revenue recognition, allowance for doubtful accounts, goodwill and intangible assets, impairment of long-lived assets, management’s going concern assessment, accounting for income taxes, and the valuation of stock-based awards. The Company bases its estimates on historical experience, known trends and other market-specific or relevant factors that are believed to be reasonable under the circumstances. On an ongoing basis, management evaluates its estimates as there are changes in circumstances, facts and experience. Changes in estimates are recorded in the period in which they become known. Actual results may differ from those estimates or assumptions.

Fair Value Measurements

Certain assets and liabilities are carried at fair value under GAAP. Fair value is defined as the exchange price that would be received for an asset or paid to transfer a liability (an exit price) in the principal or most advantageous market for the asset or liability in an orderly transaction between market participants on the measurement date. Valuation techniques used to measure fair value must maximize the use of observable inputs and minimize the use of unobservable inputs. Financial assets and liabilities carried at fair value are to be classified and disclosed in one of the following three levels of the fair value hierarchy, of which the first two are considered observable and the last is considered unobservable:

The Company’s cash equivalents are carried at fair value determined according to the fair value hierarchy described above. The carrying values of accounts and other receivables, unbilled receivables, accounts payable, and accrued expenses approximate their fair values due to the short-term nature of these assets and liabilities.

Goodwill and Other Intangible Assets

The Company records goodwill when consideration paid in a business acquisition exceeds the value of the net assets acquired. The Company estimates of fair value are based upon assumptions believed to be reasonable at that time but such estimates are inherently uncertain and unpredictable. Assumptions may be incomplete or inaccurate and unanticipated events or circumstances may occur, which may affect the accuracy or validity of such assumptions, estimates or actual results.

Goodwill is tested for impairment annually and more frequently if events and circumstances indicate that the asset might be impaired. The Company has determined it is a single reporting unit for the purpose of conducting the goodwill impairment assessment. A goodwill impairment charge is recorded if the amount by which the Company’s carrying value exceeds its fair value, not to exceed the carrying amount of goodwill. Factors that could lead to a future impairment include material uncertainties such as a significant reduction in projected revenues, a deterioration of projected financial performance, future acquisitions and/or mergers, and a decline in the Company’s market value as a result of a significant decline in the Company’s stock price. There were no impairment charges recorded during the three months ended April 30, 2022 or 2021.

Revenue Recognition

Overview

The Company recognizes revenue following the guidance under Accounting Standards Codification (“ASC”) 606, Revenue from Contracts with Customers. The Company’s revenue is derived from sales of software licenses and associated third party hardware and support services, as well as professional services and support fees related to the Company’s software licenses.

The Company recognizes revenue from contracts with customers using a five-step model, which is described below:

Identify the customer contract

A customer contract is generally identified when there is approval and commitment from both the Company and its customer, the rights have been identified, payment terms are identified, the contract has commercial substance and collectability and consideration is probable.

Identify performance obligations that are distinct

A performance obligation is a promise to provide a distinct good or service or a series of distinct goods or services. A good or service that is promised to a customer is distinct if the customer can benefit from the good or service either on its own or together with other resources that are readily available to the customer, and a company’s promise to transfer the good or service to the customer is separately identifiable from other promises in the contract.

Determine the transaction price 

The transaction price is the amount of consideration to which the Company expects to be entitled in exchange for transferring goods or services to a customer, excluding sales and VAT taxes that are collected on behalf of government agencies.

 Allocate the transaction price to distinct performance obligations 

The transaction price is allocated to each performance obligation based on the relative standalone selling prices (“SSP”) of the goods or services being provided to the customer. The Company’s contracts typically contain multiple performance obligations, for which it accounts for individual performance obligations separately, if they are distinct.

Recognize revenue as the performance obligations are satisfied 

The Company enters into contracts that include combinations of license, support and professional services, and third-party products, which are accounted for as separate performance obligations with differing revenue recognition patterns. Revenue is recognized when or as control of the promised goods or services is transferred to customers. The Company’s software licenses are primarily delivered on a perpetual basis, whereby the customer receives rights to use the software for an indefinite time period or a specified term and delivery and revenue recognition occurs at the point in time when the customer has the ability to download or access the software. The Company’s customers may also contract with it for a Software as a Service (“SaaS”) type license whereby the customer only has a right to access the software for a defined term. SaaS licenses are recognized ratably over the subscription period beginning on the date the license is made available to customers.

The Company’s services revenue is comprised of support services and professional services. Support services consist of software upgrades on a when-and-if available basis, telephone support, bug fixes or patches and general hardware maintenance support. Revenue related to support services is recognized ratably over the term of the contract. Professional services are recognized as the services are performed.

Revenues attributable to third-party products typically consist of hardware and related support contracts. Hardware products are typically recognized when control is transferred to the customer, which is defined as the point in time when the client can use and benefit from the hardware. In situations where the hardware is distinct and it is delivered before services are provided and is functional without services, control is transferred upon delivery or acceptance by the customer. Revenue attributable to third-party support contracts is recognized ratably over the term of the contract.

Significant Judgments

The Company’s contracts with customers often include promises to transfer multiple products and services to a customer. Determining whether products and services are considered distinct performance obligations that should be accounted for separately versus together may require significant judgment. Once the Company determines the performance obligations, it determines the transaction price, which includes estimating the amount of variable consideration to be included in the transaction price, if any. The Company then allocates the transaction price to each performance obligation in the contract based on the SSP. The corresponding revenue is recognized as the related performance obligations are satisfied.

Judgment is required to determine the SSP for each distinct performance obligation. The Company determines SSP based on the price at which the performance obligation is sold separately and the methods of estimating SSP under the guidance of ASC 606-10-32-33. If the SSP is not observable through past transactions, the SSP is estimated, taking into account available information such as market conditions, expected margins, and internally approved pricing guidelines related to the performance obligations. The Company enters into contracts with its customers that may include promises to transfer multiple performance obligations in the arrangement, such as software licenses, support, and professional services. The total fee of the contract may consist of one fixed price for all of the performance obligations or each performance obligation may be separately stated in the contract. Regardless of how the performance obligations are priced in the contract, the Company must determine the transaction price for each identified performance obligation. The Company recognizes the portion of the transaction price allocated to the software

license on a residual basis. The residual basis is used when the contract arrangement has at least one performance obligation for which the SSP is observable (i.e. hardware and/or support services). The residual method is also utilized to estimate the transaction price for software licenses, as the selling price for software licenses is highly variable and the SSP is not discernable from past transactions or other observable evidence. The Company periodically re-evaluates its use of the residual approach estimate compared to all available observable data before concluding the estimate is representative of SSP.  In these contracts, the Company has observable SSP for the associated support services, and hardware, if applicable, that are sold with the software license based on historical observable data of selling support contracts on a standalone basis. The Company also provides SaaS offerings, combining access to hosted software with support services (inclusive of technical support and unspecified upgrades and bug fixes). The hosted software and support services are representative of stand ready obligations with the same pattern of transfer of control. SaaS offerings do not include the right for the customer to take possession of the software during the contract term, and therefore have one distinct performance obligation, which is satisfied over time with revenue recognized ratably over the contract term as the customer consumes the services.

Services revenue is comprised of software license implementation, engineering, training and reimbursable expenses. Services are sold on both a standalone basis and as part of our customer contracts. The Company has concluded these services are typically distinct performance obligations. For implementation, engineering and training services, revenue is recognized on an input method as hours are incurred and services are provided compared to total estimated hours. The Company estimates the SSP for fixed price services based on estimated hours adjusted for historical experience using the time and materials rates charged in standalone service arrangements. When sold on a time and materials basis, SSP for services is determined by observable prices in standalone service arrangements. Certain engineering services sold with support contracts are not distinct in the context of the contract and those services are bundled with other distinct services to form a single stand ready performance obligation which is recognized ratably over the relevant service period.

The Company has utilized the cost-plus margin method to determine the SSP for Framework software support services offerings and hardware sales. When support services are sold on an “a la carte” basis with the Company’s software offerings, the Company typically determines the SSP of these support services based on this pricing relationship and observable data from standalone sales of support contracts. The expected cost-plus margin for hardware is based on the cost of the hardware from third parties, plus a reasonable markup that the Company believes is reflective of a market-based reseller margin. When observable standalone pricing for support service offerings are not readily available, the Company then reverts to the cost-plus margin method to determine the SSP for the support services.

Some contracts have payment terms that differ from the timing of revenue recognition, which requires the Company to assess whether the transaction price for those contracts include a significant financing component. The Company has elected the practical expedient that permits an entity to not adjust for the effects of a significant financing component if the Company expects that at the contract inception, the period between when the entity transfers a promised good or service to a customer and when the customer pays for that good or service, will be one year or less. For those contracts in which the period exceeds the one-year threshold, this assessment, as well as the quantitative estimate of the financing component and its relative significance, requires judgment. The Company estimates the significant financing component provided to its customers with extended payment terms by determining the present value of the future payments by applying an average standard industry discount rate that reflects the customer’s creditworthiness.

Payment terms with customers typically require payment 30 days from invoice date. Agreements with customers do not provide for any refunds for services or products and therefore no specific reserve for such is maintained. In the infrequent instances where customers raise a concern over delivered products or services, the Company has endeavored to remedy the concern and all costs related to such matters have been insignificant in all periods presented.

The Company occasionally enters into amendments to previously executed contracts that may constitute contract modifications. The amendments are assessed to determine if (1) the additional products and services are distinct from the product and services in the original arrangement; and (2) the amount of consideration expected for the added products and services reflects the SSP of those products and services. An amendment or contract modification meeting both criteria is accounted for as a separate contract. A contract modification not meeting both criteria is considered a change to the original contract and is accounted for on either a prospective basis as a termination of the existing contract and the creation of a new contract or a cumulative catch-up basis.

Contract Balances

Contract assets consist of unbilled revenue, which is recognized as work progresses in accordance with agreed-upon contractual terms, either at periodic intervals or upon achievement of contractual milestones. Unbilled receivables expected to be billed and collected within one year are classified as current assets or long-term assets if expected to be billed and collected after one year (see Note 8).

Costs to Obtain and Fulfill a Contract

The Company recognizes an asset for the incremental costs of obtaining a contract with a customer if the Company expects the benefit of those costs to be longer than one year. The Company has determined that commissions and special incentive payments (“Spiffs”) for hardware and software maintenance and support and professional services paid under its sales incentive programs meet the requirements to be capitalized under ASC 340-40. Costs to obtain a contract are amortized as selling and marketing expense over the expected period of benefit in a manner that is consistent with the transfer of the related goods or services to which the asset relates. The judgments made in determining the amount of costs incurred include whether the commissions are in fact incremental and would not have occurred absent the customer contract and the estimate of the amortization period. The commissions and Spiffs related to professional services are amortized over time as work is completed. The commissions and Spiffs for hardware and software maintenance are amortized over the life of the contract. These costs are periodically reviewed for impairment. The Company determined that no impairment of these assets existed as of April 30, 2022 or January 31, 2022. The Company has elected to apply the practical expedient and recognize the incremental costs of obtaining contracts as an expense when incurred if the amortization period of the assets that the Company otherwise would have recognized is one year or less. Total deferred capitalized commission costs were $260 thousand as of April 30, 2022 and $297 thousand as of January 31, 2022. Current deferred capitalized commission costs are included in prepaid expense and other current assets in the condensed consolidated balance sheets and non-current deferred capitalized commission costs are included in other assets in the condensed consolidated balance sheets. Capitalized commissions expensed during the three months ended April 30, 2022 and 2021 were $37 thousand and $49 thousand, respectively, and are included in the condensed consolidated statement of operations and comprehensive loss.

Net Loss Per Share

Basic net loss per share is computed by dividing net loss by the weighted average number of unrestricted common shares outstanding during the period. Diluted net loss per share is computed by dividing net loss by the sum of the weighted average number of unrestricted common shares outstanding during the period and the weighted average number of potential common shares from the assumed exercise of stock options and the vesting of shares of restricted and deferred common stock units using the “treasury stock” method when the effect is not anti-dilutive. In periods in which the Company reports a net loss, diluted net loss per share is the same as basic net loss per share. 

The number of common shares used in the computation of diluted net loss per share for the periods presented does not include the effect of the following potentially outstanding common shares because the effect would have been anti-dilutive: