Summary of Significant Accounting Policies (Policies) | 3 Months Ended |
Mar. 31, 2015 |
Accounting Policies [Abstract] | |
Basis of Presentation and Principles of Consolidation | Basis of Presentation and Principles of Consolidation |
We have prepared these unaudited condensed consolidated financial statements in accordance with accounting principles generally accepted in the United States of America (‘‘U.S. GAAP’’). In accordance with U.S. GAAP requirements for interim financial statements, these condensed consolidated financial statements do not include certain information and note disclosures that are normally included in annual financial statements prepared in conformity with U.S. GAAP. Accordingly, these condensed consolidated financial statements should be read in conjunction with the consolidated financial statements and the notes thereto as of December 31, 2014 and 2013 and for the fiscal year ended December 31, 2014, the three months ended December 31, 2013 and the fiscal years ended September 30, 2013 and 2012 included in our Annual Report on Form 10-K filed with the Securities and Exchange Commission on March 6, 2015. In our opinion, the condensed consolidated financial statements contain all adjustments (which are of a normal, recurring nature) necessary to state fairly, in all material respects, our consolidated financial position, results of operations and cash flows for the periods presented. Interim results may not be indicative of results that may be realized for the full year. |
Segment Reporting | Segment Reporting |
|
We have one operating segment, providing on-demand business collaboration software solutions to the commercial construction industry. Our chief operating decision maker, the Chief Executive Officer, manages our operations based on consolidated financial information for purposes of evaluating financial performance and allocating resources. |
Use of Estimates | Use of Estimates |
|
The preparation of condensed consolidated financial statements in conformity with U.S. GAAP requires management to make estimates and assumptions that affect the reported amounts of assets and liabilities and the disclosure of contingent assets and liabilities at the date of the financial statements and the reported amounts of revenues and expenses during the reporting period. The estimates and assumptions used in the accompanying financial statements are based upon management’s evaluation of the relevant facts and circumstances at the balance sheet date. Actual results could differ from those estimates. Significant estimates are involved in our revenue recognition, depreciation, amortization and assumptions for share‑based payments. |
Revenue Recognition | Revenue Recognition |
|
For our CPM, Submittal Exchange, Greengrade and Latista solutions, we earn revenue from owners/developers, general contractors and architects in the form of subscription fees and project fees; and from subcontractors in the form of usage fees. For our GradeBeam, PQM and BidOrganizer solutions, we earn revenue in the form of subscription fees. Our arrangements do not contain general rights of return and do not provide customers with the right to take possession of the software supporting the solutions and, as a result, are accounted for as service contracts. |
|
All of our on-demand solutions include training and support. We evaluate whether the individual deliverables in our revenue arrangements qualify as separate units of accounting. In order to treat deliverables in a multiple deliverable arrangement as separate units of accounting, the deliverables must have standalone value upon delivery. In determining whether deliverables have standalone value, we consider whether solutions are sold to new customers without training and support, the nature of the training and support provided and the availability of the training and support from other vendors. We concluded that training and support do not have standalone value because they are never sold separately, do not have value to the customer without the solution and are not available from other vendors. Accordingly, the training and support are combined with the solution and treated as a single unit of accounting. |
|
We recognize revenue when there is evidence that an agreement exists with the customer and the customer has begun deriving benefit from use of the solution, the fee is fixed and determinable, delivery of services has occurred, and collection of payment from the project participant is reasonably assured. We recognize project fees and usage fees ratably over the average estimated life of the project and contract, respectively, and recognize subscription fees over the subscription period. The average estimated life of the project and contract is estimated by management based on periodic review and analysis of historical data. The applicable estimated life is based on the project or contract value falling within certain predetermined ranges, as well as the solution on which the project is being managed. We perform periodic reviews of actual project and contract data and revise estimates as necessary. Estimated project life durations range from 6 to 32 months, and estimated contract life durations range from 4 to 20 months. Subscription periods typically range from 6 to 36 months. |
|
For our PlanSwift solution, we earn revenue from the sale of software licenses and related maintenance and training. License revenue is recognized upon delivery of the license, maintenance revenue is recognized ratably over the period of the maintenance contract, which is generally one year, and training revenue is recognized when the services are delivered to the client. For multiple-element arrangements that include a perpetual license for which we have not established vendor-specific objective evidence of fair value ("VSOE") and either maintenance or both maintenance and training, we use the residual method to determine the amount of license revenue to be recognized. Under the residual method, consideration is allocated to the undelivered elements based upon VSOE of those elements with the residual of the arrangement fee allocated to and recognized as license revenue. For multiple-element arrangements that include a perpetual license for which we have established VSOE and either maintenance or both maintenance and training, we allocate the revenue among the different elements of the arrangement based on each element's relative VSOE. For subscription-based licenses, which include maintenance, we recognize the subscription fees ratably over the subscription periods, which typically range from 1 to 6 months. |
|
We have established VSOE based on our historical pricing and discounting practices for maintenance, training and certain software licenses when sold separately. In establishing VSOE, we require that a substantial majority of the selling prices for these services fall within a reasonably narrow pricing range. The application of VSOE methodologies requires judgment, including the identification of individual elements in multiple element arrangements and whether there is VSOE of fair value for some or all elements. |
Goodwill and Intangible Assets, Goodwill, Policy [Policy Text Block] | |
Foreign Currency Transactions | Foreign Currency Transactions |
Our functional currency is the United States Dollar. Asset and liability balances denominated in a foreign currency are remeasured to U.S. dollars at end-of-period exchange rates. Foreign currency income and expenses are remeasured at average exchange rates in effect during the period. We record foreign currency translation differences in accumulated other comprehensive income (loss). |
Net Loss Per Share | Net Loss Per Share |
Basic net loss per share available to our common stockholders is calculated by dividing the net loss available to our common stockholders by the weighted-average number of common shares outstanding, less any treasury shares, during the period. |
Recently Issued Accounting Standards | Recently Issued Accounting Standards |
In April 2015, the Financial Accounting Standards Board (“FASB”) issued Accounting Standards Update 2015-05, Customer's Accounting for Fees Paid in a Cloud Computing Arrangement (“ASU 2015-05”). ASU 2015-05 clarifies the accounting for cloud computing arrangements, as no specific guidance existed prior to this newly issued standard. The provisions of ASU 2015-05 must be applied to annual periods beginning after December 15, 2015 as well as interim periods within those annual periods. We are currently in the process of evaluating the impact of the adoption of ASU 2015-05 on our consolidated financial statements. |
|
On May 28, 2014, the Financial Accounting Standards Board (“FASB”) issued Accounting Standards Update 2014-09, Revenue from Contracts with Customers (“ASU 2014-09”). ASU 2014-09 outlines a single comprehensive model to use in accounting for revenue arising from contracts with customers. This update has an effective date of January 1, 2017. However, on April 1, 2015, the FASB voted to propose a one-year deferral of the effective date of ASU 2014-09. If finalized, we could elect to adopt the provisions of ASU 2014-09 effective January 1, 2018. Under this proposal, early adoption as of January 1, 2017 would also be permissible. We are currently in the process of evaluating the impact of the adoption of ASU 2014-09 on our consolidated financial statements. |