Basic and diluted loss per share

Basic earnings (loss) per share is computed by dividing net earnings (loss) available to common shareholders by the weighted average number of shares outstanding during the reporting periods. Diluted earnings (loss) per share is computed similar to basic earnings (loss) per share, except that the weighted average shares outstanding are increased to include additional shares for the assumed exercise of stock options and warrants, if dilutive. The number of additional shares is calculated by assuming that outstanding stock options and warrants were exercised and that the proceeds from such exercises were used to acquire common stock at the average market price during the reporting periods. Potentially dilutive options as of March 31, 2025 totaled 401,633 ( March 31, 2024 – 18,509) and warrants excluded from diluted loss per share as of March 31, 2025 totaled 1,733,741 (March 31, 2024 – 896,645).

Share-based compensation

The Company grants stock options to acquire common shares of the Company to directors, officers, employees and consultants. An individual is classified as an employee when the individual is an employee for legal or tax purposes, or provides services similar to those performed by an employee.

The fair value of stock options is measured on the date of grant, using the Black-Scholes option pricing model, and is recognized over the vesting period. Consideration paid for the shares on the exercise of stock options is credited to capital stock.

In situations where equity instruments are issued to non-employees and some or all of the goods or services received by the Company as consideration cannot be specifically identified, they are measured at fair value of the share-based payment. Otherwise, share-based payments are measured at the fair value of goods or services received.

Non-controlling interest

Non-controlling interest in the Company’s less than wholly owned subsidiaries are classified as a separate component of equity. On initial recognition, non-controlling interest is measured at the fair value of the non-controlling entity’s contribution into the related subsidiary. Subsequent to the original transaction date, adjustments are made to the carrying amount of non-controlling interest for the non-controlling interest’s share of changes to the subsidiary’s equity.

Changes in the Company’s ownership interest in a subsidiary that do not result in a loss of control are recorded as equity transactions. The carrying amount of non-controlling interest is adjusted to reflect the change in the non-controlling interest’s relative interest in the subsidiary, and the difference between the adjustment to the carrying amount of non-controlling interests and the Company’s share of proceeds received and/or consideration paid is recognized directly in equity and attributed to owners of the Company.

Revenue recognition

The Company recognizes revenue when its customer obtains control of promised goods or services, in an amount that reflects the consideration which the entity expects to receive in exchange for those goods or services. To determine revenue recognition for arrangements that an entity determines are within the scope of Accounting Standards Codification ASC 606, Revenue from Contracts with Customers (“ASC 606”), the entity performs the following five steps: (i) identify the contract(s) with a customer; (ii) identify the performance obligations in the contract; (iii) determine the transaction price; (iv) allocate the transaction price to the performance obligations in the contract; and (v) recognize revenue when (or as) the entity satisfies a performance obligation. The Company only recognizes revenue from contracts when it is probable that the entity will collect substantially all the consideration it is entitled to in exchange for the goods or services it transfers to the customer.

The Company earns revenue in two primary ways: 1) the sales of software-as-a-service (SAAS) from its interactive production software platform or 2) development and maintenance of custom-built software or other professional services.

The Company recognizes SAAS revenues from its interactive production sales over the life of the contract as its performance obligations are satisfied. Payment terms vary by contract and can be periodic or one-time payments. The Company determines that the customer receives and consumes the benefits of the service simultaneously as the service is provided. The transaction price is allocated to the contractual performance obligations and recognized ratably over the contract term.

The Company recognizes revenues received from the development and maintenance of custom-built software and other professional services provided upon the satisfaction of its performance obligation in an amount that reflects the consideration to which the Company expects to be entitled in exchange for those services. Performance obligations can be satisfied either at a single point in time or over time. For those performance obligations that are satisfied at a single point in time, the revenue is recognized at that time. For each performance obligation satisfied over time, the Company recognizes revenue by measuring the progress toward complete satisfaction of that performance obligation. The Company generally measures progress comparing hours incurred to total estimated hours.

For revenues received from the sales of advertising, the Company is deemed the agent in its revenue agreements. The Company does not own or obtain control of the digital advertising inventory. The Company recognizes revenues upon the achievement of agreed-upon performance criteria for the advertising inventory, such as a number of views, or clicks. As the Company is acting as an agent in the transaction, the Company recognizes revenue from sales of advertising on a net basis, which excludes amounts payable to partners under the Company’s revenue sharing agreements.

The Company’s contracts with customers may include promises to transfer multiple products and services. For these contracts, the Company accounts for individual performance obligations separately if they are capable of being distinct and distinct within the context of the contract. Determining whether products and services are considered distinct performance obligations may require significant judgment. Judgment is also required to determine the stand-alone selling price, for each distinct performance obligation.

During the three months ended March 31, 2025 the Company recognized $176,000 attributed to professional services.

License Revenue

The Company entered into a Technology License and Software Development Agreement (the “License Agreement”) in October 2024 which provides for the Company to license its gamification, engagement and QR code technology to ASPIS for use in ASPIS’s website business and for development of additional functionality for Versus’ technology.

Pursuant to the License Agreement, the Company granted ASPIS a license to use Versus’ technology in ASPIS’s website business that provides cybersecurity technology. ASPIS will pay for any required technology modifications, improvements and developments to Versus’ technology in addition to a license fee of $165,000 per month. The Company will retain ownership of Versus’ technology and ASPIS will hold an exclusive license to use Versus’ technology in the cybersecurity industry so long as ASPIS continues to pay the monthly license fee. The License Agreement has an initial term of one year with successive renewal terms of one year each upon ASPIS’s written approval, subject to earlier termination by the Company or ASPIS.

We recognize revenue when the performance obligations in the contract are satisfied. For performance obligations that are fulfilled at a point in time, revenue is recognized at the fulfillment of the performance obligation. Since the IP is determined to be a functional license, the value of the grant of use is recognized in the first period of the contract term in which the license agreement is in force. For the three months ended March 31, 2025 no revenue was recognized on our functional IP as the Technology Agreement with ASPIS as the license had not been delivered to ASPIS during the year.

As of March 31, 2025 the Company had not granted ASPIS access to its technology for use in ASPIS’s cybersecurity technology. The Company expects to begin the License Agreement in during the second quarter of 2025.

Recent accounting pronouncements not yet adopted

New accounting pronouncements 

In November 2024, the FASB issued ASU No. 2024-04, Debt-Debt with Conversion and Other Options (“Subtopic 470-20”) (“ASU No. 2024-04”), which intends to clarify the conditions in which induced conversion applies to convertible debt by outlining three criteria that must be met for an entity to apply the induced conversion model. The amendments in this ASU are effective for annual reporting periods beginning after December 15, 2025 (and interim reporting periods within those annual reporting periods). Early adoption is permitted as of the beginning of a reporting period if the entity has also adopted ASU 2020-06 for that period. The Company is currently evaluating how this ASU will impact its consolidated financial statements and disclosures.

In November 2024, the FASB issued ASU No. 2024-03, Income Statement-Reporting Comprehensive Income-Expense Disaggregation Disclosures (“Subtopic 220-40”). This ASU improves financial reporting by requiring that public business entities disclose additional information about specific expense categories in the notes to financial statements at interim and annual reporting periods. This ASU will be effective for annual periods beginning after December 15, 2026, for interim reporting periods beginning after December 15, 2027, with early adoption is permitted. We are evaluating the potential impact of this guidance on our consolidated financial statements and related disclosures.

Recent adopted accounting pronouncements

In December 2023, the FASB issued ASU 2023-09, Income Taxes (“Topic 740”): Improvements to Income Tax Disclosures. This ASU enhances the transparency and decision usefulness of income tax disclosures. It is designed to provide more detailed information about an entity’s income tax expenses, liabilities, and deferred tax items, potentially affecting how companies report and disclose their income tax-related information. The ASU is effective for public business entities for annual periods beginning after December 15, 2024, including interim periods within those fiscal years. The adoption of the guidance in the first quarter of 2025 did not have a material impact on our consolidated financial statements and related disclosures.

Management does not believe any other recently issued but not yet effective accounting pronouncement, if adopted, would have a material effect on the Company’s present or future consolidated financial statements.