EGAIN Corp - Quarter Report: 2013 December (Form 10-Q)

UNITED STATES

SECURITIES AND EXCHANGE COMMISSION

Washington, D.C. 20549

Form 10-Q

(Mark One)

For the quarterly period ended December 31, 2013

OR

For the transition period from                  to                  

Commission File No. 001-35314

eGAIN CORPORATION

(Exact name of registrant as specified in its charter)

(408) 636-4500

(Registrant’s telephone number, including area code)

(Former name, former address and former fiscal year, if changed since last report)

Indicate by check mark whether the registrant: (1) has filed all reports required to be filed by Section 13 or 15(d) of the Securities Exchange Act of 1934 during the preceding 12 months (or for such shorter period that the registrant was required to file such reports), and (2) has been subject to such filing requirements for the past 90 days: Yes x No ¨

Indicate by check mark whether the registrant has submitted electronically and posted on its corporate Web site, if any, every Interactive Data File required to be submitted and posted pursuant to Rule 405 of Regulation S-T (§232.405 of this chapter) during the preceding 12 months (or for such shorter period that the registrant was required to submit and post such files). Yes x No ¨

Indicate by check mark whether the registrant is a large accelerated filer, an accelerated filer, or non-accelerated filer or a smaller reporting company. See the definitions of “large accelerated filer” “accelerated filer” and “smaller reporting company”, in Rule 12b-2 of the Exchange Act (check one):

Indicate by check mark whether the registrant is a shell company (as defined in Rule 12b-2 of the Exchange Act): Yes ¨ No x

Indicate the number of shares outstanding of each of the issuer’s classes of common stock, as of the latest practicable date.

eGAIN CORPORATION

Quarterly Report on Form 10-Q

For the Quarterly Period Ended December 31, 2013

TABLE OF CONTENTS

i

PART I.  FINANCIAL INFORMATION

Item 1. Financial Statements

eGAIN CORPORATION

CONDENSED CONSOLIDATED BALANCE SHEETS

(in thousands, except par value data)

See accompanying notes to condensed consolidated financial statements

1

eGAIN CORPORATION

CONDENSED CONSOLIDATED STATEMENTS OF OPERATIONS (Unaudited)

(in thousands, except per share data)

See accompanying notes to condensed consolidated financial statements

2

eGAIN CORPORATION

CONDENSED CONSOLIDATED STATEMENTS OF COMPREHENSIVE INCOME (LOSS) (Unaudited)

(in thousands)

See accompanying notes to condensed consolidated financial statements

3

eGAIN CORPORATION

CONDENSED CONSOLIDATED STATEMENTS OF CASH FLOWS (Unaudited)

(in thousands)

See accompanying notes to condensed consolidated financial statements

4

eGAIN CORPORATION

NOTES TO CONDENSED CONSOLIDATED FINANCIAL STATEMENTS (Unaudited)

Note 1. Summary of Business and Significant Accounting Policies

Organization and Nature of Business

eGain Corporation (“eGain”, the “Company”, “our”, “we”, or “us”) is a leading provider of cloud-based and on-site customer engagement software solutions. For over a decade, our solutions have helped improve customer experience, grow sales, and optimize service processes across the web, social, and phone channels. Hundreds of global enterprises rely on us to transform fragmented sales engagement and customer service operations into unified customer engagement hubs. We have operations in the United States, United Kingdom, Netherlands, Ireland, Italy, Germany, France, South Africa, and India.

Principles of Consolidation

We have prepared the condensed consolidated financial statements pursuant to the rules and regulations of the Securities and Exchange Commission and included the accounts of our wholly-owned subsidiaries. All significant intercompany balances and transactions have been eliminated. Certain information and footnote disclosures, normally included in financial statements prepared in accordance with generally accepted accounting principles, or GAAP, have been condensed or omitted pursuant to such rules and regulations although we believe that the disclosures made are adequate to make the information not misleading. In our opinion, the unaudited condensed consolidated financial statements reflect all adjustments (consisting only of normal recurring adjustments) necessary for a fair presentation of our financial position, results of operations and cash flows for the periods presented.

These financial statements and notes should be read in conjunction with our audited consolidated financial statements and notes thereto for the fiscal year ended June 30, 2013, included in our Annual Report on Form 10-K. The condensed consolidated balance sheet at June 30, 2013 has been derived from audited financial statements as of that date but does not include all the information and footnotes required by GAAP for complete financial statements. The results of our operations for the interim periods presented are not necessarily indicative of results that may be expected for any other interim period or for the full fiscal year ending June 30, 2014. We have evaluated whether there were material subsequent events requiring recognition or disclosure, and there were none.

Segment Information

We operate in one segment, the development, license, implementation and support of our customer interaction software solutions. Operating segments are identified as components of an enterprise for which discrete financial information is available and regularly reviewed by the Company’s chief operating decision-makers in order to make decisions about resources to be allocated to the segment and assess its performance. Our chief operating decision-makers, under Accounting Standards Codification, or ASC, 280, Segment Reporting, are our executive management team. Our chief operating decision-makers review financial information presented on a consolidated basis for purposes of making operating decisions and assessing financial performance.

Information relating to our geographic areas for the three and six months ended December 31, 2013 and 2012 is as follows (unaudited, in thousands):

5

In addition, identifiable tangible assets corresponding to our geographic areas are as follows (unaudited, in thousands):

The following table provides total revenue by category for the three and six months ended December 31, 2013 and 2012, respectively, (unaudited, in thousands):

For the three months ended December 31, 2013 and 2012, there was one customer that accounted for 16% and 19% of total revenue, respectively. For the six months ended December 31, 2013 and 2012, there was one customer that accounted for 18% and 17% of total revenue, respectively.  

Revenue Recognition

We enter into arrangements to deliver multiple products or services (multiple-elements). We apply software revenue recognition rules and multiple-elements arrangement revenue guidance. Significant management judgments and estimates are made and used to determine the revenue recognized in any accounting period. Material differences may result in changes to the amount and timing of our revenue for any period if different conditions were to prevail. We present revenue, net of taxes collected from customers and remitted to governmental authorities.

We derive revenue from three sources:

Revenue is recognized when all of the following criteria are met:

6

We apply the provisions of ASC 985-605, Software Revenue Recognition, to all transactions involving the licensing of software products. In the event of a multiple element arrangement for a license transaction, we evaluate the transaction as if each element represents a separate unit of accounting taking into account all factors following the accounting standards. We apply ASC 605, Revenue Recognition, for cloud transactions to determine the accounting treatment for multiple elements. We also apply ASC 605-35 for fixed fee arrangements in which we use the percentage of completion method to recognize revenue when reliable estimates are available for the costs and efforts necessary to complete the implementation services. When such estimates are not available, the completed contract method is utilized. Under the completed contract method, revenue is recognized only when a contract is completed or substantially complete.

When licenses are sold together with system implementation and consulting services, license fees are recognized upon shipment, provided that (i) payment of the license fees is not dependent upon the performance of the consulting and implementation services, (ii) the services are available from other vendors, (iii) the services qualify for separate accounting as we have sufficient experience in providing such services, have the ability to estimate cost of providing such services, and we have vendor-specific objective evidence, or VSOE, of fair value, and (iv) the services are not essential to the functionality of the software.

We evaluate whether each of the elements in these arrangements represents a separate unit of accounting, as defined by ASC 605, using all applicable facts and circumstances, including whether (i) we sell or could readily sell the element unaccompanied by the other elements, (ii) the element has stand-alone value to the customer, and (iii) there is a general right of return. We use VSOE, of fair value for each of those units, when available. For revenue recognition with multiple-deliverable elements, in certain limited circumstances when VSOE of fair value does not exist, we apply the selling price hierarchy, which includes VSOE, third-party evidence of selling price, or TPE, and best estimate of selling price, or BESP. We determine the relative selling price for a deliverable based on VSOE, if available, or BESP, if VSOE is not available. We have determined that TPE is not a practical alternative due to differences in our service offerings compared to other parties and the availability of relevant third-party pricing information.

We determine BESP by considering our overall pricing objectives and market conditions. Significant pricing practices taken into consideration include our discounting practices, the size and volume of our transactions, customer demographic, the geographic area where services are sold, price lists, its go-to-market strategy, historical standalone sales and contract prices. The determination of BESP is made through consultation with and approval by our management, taking into consideration the go-to-market strategy. As our go-to-market strategies evolve, we may modify our pricing practices in the future, which could result in changes in relative selling prices, including both VSOE and BESP.

Subscription and Support Revenue

Cloud Revenue

Cloud revenue consists of subscription fees from customers accessing our cloud-based service offerings. We recognize cloud services revenue ratably over the period of the applicable agreement as services are provided. Cloud agreements typically have an initial term of one or two years and automatically renew unless either party cancels the agreement. The majority of the cloud services customers purchase a combination of our cloud service and professional services. In some cases, the customer may also acquire a license for our software.

We consider the applicability of ASC 985-605, on a contract-by-contract basis. In cloud based agreements, where the customer does not have the contractual right to take possession of the software, the revenue is recognized on a monthly basis over the term of the contract. Invoiced amounts are recorded in accounts receivable and in deferred revenue or revenue, depending on whether the revenue recognition criteria have been met. We consider a software element to exist when we determine that the customer has the contractual right to take possession of our software at any time during the cloud period without significant penalty and can feasibly run the software on its own hardware or enter into another arrangement with a third party to host the software. Additionally, we have established VSOE for the cloud and maintenance and support elements of perpetual license sales, based on the prices charged when sold separately and substantive renewal terms. Accordingly, when a software element exists in a cloud services arrangement, license revenue for the perpetual software license element is determined using the residual method and is recognized upon delivery. Revenue for the cloud and maintenance and support elements is recognized ratably over the contractual time period. Professional services are recognized as described below under “Professional Services Revenue.” If VSOE of fair value cannot be established for the undelivered elements of an agreement, the entire amount of revenue from the arrangement is recognized ratably over the period that these elements are delivered.

7

Term License Revenue

Term license revenue includes arrangements where our customers receive license rights to use our software along with bundled maintenance and support services for the term of the contract. The majority of our contracts provide customers with the right to use one or more products up to a specific license capacity. Certain of our license agreements stipulate that customers can exceed pre-determined base capacity levels, in which case additional fees are specified in the license agreement. Term license revenue is recognized ratably over the term of the license contract.

Maintenance and Support Revenue

Maintenance and support revenue consists of customers purchasing maintenance and support for our on-premise software. We use VSOE of fair value for maintenance and support to account for the arrangement using the residual method, regardless of any separate prices stated within the contract for each element. Maintenance and support revenue is recognized ratably over the term of the maintenance contract, which is typically one year. Maintenance and support is renewable by the customer on an annual basis. Maintenance and support rates, including subsequent renewal rates, are typically established based upon a specified percentage of net license fees as set forth in the arrangement.

License Revenue

License revenue includes perpetual license rights sold to customers to use our software in conjunction with related maintenance and support services. If an acceptance period is required, revenue is recognized upon the earlier of customer acceptance or the expiration of the acceptance period. In software arrangements that include rights to multiple software products and/or services, we use the residual method under which revenue is allocated to the undelivered elements based on VSOE of the fair value of such undelivered elements. The residual amount of revenue is allocated to the delivered elements and recognized as revenue, assuming all other criteria for revenue recognition have been met. Such undelivered elements in these arrangements typically consist of software maintenance and support, implementation and consulting services and in some cases, cloud services.

We periodically sell to resellers. License sales to resellers as a percentage of total revenue were approximately 2% and 3% for the three months ended December 31, 2013 and 2012, respectively.  License sales to resellers as a percentage of total revenue were approximately 9% and 2% for the six months ended December 31, 2013 and 2012, respectively.  Revenue from sales to resellers is generally recognized upon delivery to the reseller but depends on the facts and circumstances of the transaction, such as our understanding of the reseller’s plans to sell the software, if there are any return provisions, price protection or other allowances, the reseller’s financial status and our experience with the particular reseller. Historically sales to resellers have not included any return provisions, price protections or other allowances.

Professional Services Revenue

Professional services revenue includes system implementation, consulting and training. For license transactions, the majority of our consulting and implementation services qualify for separate accounting. We use VSOE of fair value for the services to account for the arrangement using the residual method, regardless of any separate prices stated within the contract for each element. Our consulting and implementation service contracts are bid either on a fixed-fee basis or on a time-and-materials basis. Substantially all of our contracts are on a time-and-materials basis. For time-and-materials contracts, where the services are not essential to the functionality, we recognize revenue as services are performed. If the services are essential to functionality, then both the license revenue and the service revenue are recognized under the percentage of completion method. For a fixed-fee contract, we recognize revenue based upon the costs and efforts to complete the services in accordance with the percentage of completion method, provided we are able to estimate such cost and efforts.

Under ASC 605-25, in order to account for deliverables in a multiple-deliverable arrangement as separate units of accounting, the deliverables must have standalone value upon delivery. For cloud services, in determining whether professional services have standalone value, we consider the following factors for each professional services agreement: availability of the services from other vendors, the nature of the professional services, the timing of when the professional services contract was signed in comparison to the subscription service start date and the contractual dependence of the subscription service on the customer’s satisfaction with the professional services work.

8

As of June 30, 2013, we did not have standalone value for the professional services related to consulting and implementation of a majority of our core subscription services. This was due to the fact that we had historically performed the majority of these services to support our customers’ implementation of the subscription services. We determined at or around July 1, 2013 that we had established standalone value for these implementation services. This was primarily due to the change in our business focus, the growing number of partners we trained and certified to perform these deployment services and the consequential sale of subscription services without bundled implementation service. Revenues earned from professional services related to consulting and implementation of a majority of our core subscription services are being accounted for separately from revenues earned from subscription services beginning July 1, 2013 when the standalone value was established for those professional services.

For those contracts that have standalone value, we recognized the services revenue when rendered for time and material contracts, when the milestones are achieved and accepted by the customer for fixed price contracts or by percentage of completion basis if there is no acceptance criteria.

For cloud, consulting and implementation services that do not qualify for separate accounting, we recognize the services revenue ratably over the estimated life of the customer cloud relationship, once cloud has gone live or system ready. We currently estimate the life of the customer cloud relationship to be approximately 28 months, based on the average life of all cloud customer relationships.

Training revenue that meets the criteria to be accounted for separately is recognized when training is provided.

Deferred Revenue

Deferred revenue primarily consists of payments received in advance of revenue recognition from cloud, term license, and maintenance and support services and is recognized as the revenue recognition criteria are met. We generally invoice customers in annual or quarterly installments. The deferred revenue balance does not represent the total contract value of annual or multi-year, non-cancelable cloud or maintenance and support agreements. Deferred revenue is influenced by several factors, including seasonality, the compounding effects of renewals, invoice duration, invoice timing and new business linearity within the quarter.

Deferred revenue that will be recognized during the succeeding twelve month period is recorded as current deferred revenue and the remaining portion is recorded as noncurrent.

Deferred Commissions

Deferred commissions are the direct and incremental costs directly associated with cloud contracts with customers and consist of sales commissions to the Company’s direct sales force.

The commissions are deferred and amortized over the terms of the related customer contracts, which are typically one or two years. The commission payments are paid based on contract terms in the month following the quarter in which the commissions are earned. The deferred commission amounts are recognized under “Sales and marketing” expense in the condensed consolidated statements of operations over the terms of the related customer contracts, in proportion to the recognition of the associated revenue.

Accounts Receivable and Allowance for Doubtful Accounts

We extend unsecured credit to our customers on a regular basis. Our accounts receivable are derived from revenue earned from customers and are not interest bearing. We also maintain an allowance for doubtful accounts to reserve for potential uncollectible trade receivables. We review our trade receivables by aging category to identify specific customers with known disputes or collectibility issues. We exercise judgment when determining the adequacy of these reserves as we evaluate historical bad debt trends, general economic conditions in the U.S. and internationally, and changes in customer financial conditions. If we made different judgments or utilized different estimates, material differences may result in additional reserves for trade receivables, which would be reflected by charges in general and administrative expenses for any period presented. We write off a receivable after all collection efforts have been exhausted and the amount is deemed uncollectible.

Receivable from Insurance Recovery

In certain circumstances, we record insurance recoveries that will be recognized during the succeeding twelve month period in other current assets. Such amounts represent pending insurance claims and are recorded net of any insurance deductible in accordance with the guidance in ASC 410, Asset Retirement and Environmental Obligations, and other interpretations for recognition of an asset related to insurance recovery when probable.

9

Deferred Costs

Deferred costs are included in other assets. Such amounts include fees we pay to third party partners for technology and are deferred and amortized over the related customer contract term. Amortization of deferred third party partner fees is included in sales and marketing expense in the accompanying condensed consolidated statements of operations.

Leases

Lease agreements are evaluated to determine whether they are capital or operating leases in accordance with ASC 840, Leases. When any one of the four test criteria in ASC 840 is met, the lease then qualifies as a capital lease.

Capital leases are capitalized at the lower of the net present value of the total amount payable under the leasing agreement (excluding finance charges) or the fair market value of the leased asset. Capital lease assets are depreciated on a straight-line basis, over a period consistent with our normal depreciation policy for tangible fixed assets, but not exceeding the lease term. Interest charges are expensed over the period of the lease in relation to the carrying value of the capital lease obligation.

Rent expense for operating leases, which may include free rent or fixed escalation amounts in addition to minimum lease payments, is recognized on a straight-line basis over the duration of each lease term.

Stock-Based Compensation

We account for stock-based compensation in accordance with ASC 718, Compensation—Stock Compensation. Under the fair value recognition provisions of ASC 718, stock-based compensation cost is measured at the grant date based on the fair value of the award and is recognized as expense over the vesting period. Determining the fair value of the stock-based awards at the grant date requires significant judgment and the use of estimates, particularly surrounding Black-Scholes valuation assumptions such as stock price volatility and expected option term.

Below is a summary of stock-based compensation included in the costs and expenses (unaudited, in thousands):

We utilized the Black-Scholes valuation model for estimating the fair value of the stock-based compensation of options granted. All shares of our common stock issued pursuant to our stock option plans are only issued out of an authorized reserve of shares of common stock, which were previously registered with the Securities and Exchange Commission on a registration statement on Form S-8.

During the three months ended December 31, 2013 and 2012 there were 119,700 and 128,400 shares of common stock granted with a weighted-average fair value of $7.44 and $2.97, respectively.  During the six months ended December 31, 2013 and 2012 there were 261,850 and 157,250 shares of common stock granted, respectively, with a weighted-average fair value of $7.16 and $2.99, respectively, using the following assumptions:

10

The dividend yield of zero is based on the fact that we have never paid cash dividends and have no present intention to pay cash dividends. We determined the appropriate measure of expected volatility by reviewing historic volatility in the share price of our common stock, as adjusted for certain events that management deemed to be non-recurring and non-indicative of future events. The risk-free interest rate is derived from the average U.S. Treasury Strips rate with maturities approximating the expected lives of the awards during the period, which approximate the rate in effect at the time of the grant.

We base our estimate of expected life of a stock option on the historical exercise behavior, and cancellations of all past option grants made by the Company during the time period which its equity shares have been publicly traded, the contractual term of the option, the vesting period and the expected remaining term of the outstanding options.

Total compensation cost, net of forfeitures, of all options granted but not yet vested as of December 31, 2013 was $2,200,826, which is expected to be recognized over the weighted average period of 1.43 years. There were 77,929 and 288,482 options exercised for the three and six months ended December 31, 2013 and 191,952 and 284,069 options exercised for three and six months ended December 31, 2012.

New Accounting Pronouncements

In July 2013, the Financial Accounting Standards Board, or the FASB, issued ASU 2013-11, Income Taxes, which applies to all entities that have unrecognized tax benefits when a net operating loss, a similar tax loss, or a tax credit carryforward exists at the reporting date. The amendments in this update are effective for fiscal years, and interim periods within those years, beginning after December 15, 2013 (our fiscal 2015). We do not anticipate the adoption of this amendment to have a material impact on our consolidated financial statements.

In March 2013, the FASB issued ASU 2013-05, Foreign Currency Matters, which applies to the release of the cumulative translation adjustment into net income, when a parent either sells a part or all of its investment in a foreign entity or no longer holds a controlling financial interest in a subsidiary that is a nonprofit activity or business within a foreign entity. The amendments in this update are effective for public companies prospectively beginning after December 15, 2013 (our fiscal 2015), and interim and annual periods thereafter. We do not anticipate the adoption of this amendment to have a material impact on our consolidated financial statements.  

Note 2. Net Income (Loss) per Common Share

Basic net income (loss) per common share is computed using the weighted-average number of shares of common stock outstanding. In periods where net income is reported, the weighted–average number of shares outstanding is increased by warrants and options in the money to calculate diluted net income per common share.

The following table represents the calculation of basic and diluted net income (loss) per common share (unaudited, in thousands, except per share data):

Weighted average shares of stock options to purchase 2,136,411 and 2,210,706 shares of common stock for the three and six months ended December 31, 2013 and 726,836 and 2,650,351 shares of common stock for the three and six months ended December 31, 2012 were not included in the computation of diluted net income (loss) per common share due to their anti-dilutive effect. Such securities could have a dilutive effect in future periods.  

11

Note 3. Related Party Notes Payable

We had an interest-bearing subordinated loan, or the Note, from our Chief Executive Officer, Ashutosh Roy, which originated in 2002 and previously had a maturity date of March 31, 2012. On March 31, 2012, we entered into Amendment No.1 to the loan agreement with Mr. Roy. Pursuant to Amendment No.1 and subject to the terms and conditions contained therein, we agreed that (i) the maturity date of the Note would be extended 90 days to June 29, 2012; (ii) as of April 1, 2012 the “Face Amount” of the Note would be $5.6 million, which included $109,000 of interest for the 90 day extension. The Face Amount of $5.6 million reflects the reduced interest rate on the Note of 8% beginning April 1, 2012 prior to which the interest rate was 12%; and (iii) the Company may prepay the Note in full or in part at any time prior to the maturity date without interest penalty.

On June 29, 2012, we entered into Amendment No. 2 to the loan agreement with Mr. Roy. Pursuant to Amendment No. 2, and subject to the terms and conditions contained therein, we agreed to extend the maturity date of the Note to July 31, 2013. We could prepay the Note in full or in part at any time prior to the maturity date without interest penalty. On December 31, 2012, we made a $3.0 million partial repayment to Mr. Roy bringing the remaining indebtedness to Mr. Roy to $2.8 million.

On July 31, 2013, we repaid the outstanding amount of $2.9 million owed to Mr. Roy and terminated the loan agreement.  Interest expense on the related party notes was $0 and $111,000, respectively, for the three months ended December 31, 2013 and 2012.  Interest expense on the related party notes was $19,000 and $222,000, respectively, for the six months ended December 31, 2013 and 2012.

Note 4. Bank Borrowings

On June 27, 2011, we entered into a Loan and Security Agreement, or the Comerica Credit Facility, with Comerica Bank, or Comerica, as may be amended from time to time. Our obligations under the Comerica Credit Facility are collateralized by a lien on our assets. In addition, Mr. Roy has subordinated his security interests to those of Comerica pursuant to a Subordination Agreement dated as of June 27, 2011. The Comerica Credit Facility provides for the advance of up to the lesser of $1.5 million under a revolving line of credit, or the sum of (i) 80% of certain qualified receivables, less (ii) the aggregate face amounts of any letters of credit issued and any outstanding obligations to Comerica. The revolving line of credit matured on June 27, 2012 and bore interest at a rate of prime plus 0.75% per annum. As of December 31, 2013 there was no outstanding balance under the revolving credit line. The Comerica Credit Facility also provided $5.0 million to pay off obligations associated with our related parties, or the Comerica Term Loan, bears interest at a rate of prime plus 1.0% per annum, and is payable in 36 equal monthly payments of principal and interest with a maturity date of June 15, 2014. There are a number of affirmative and negative covenants under the Comerica Credit Facility, with the primary covenants being that we are required to maintain a minimum cash balance of $1.0 million and we must maintain a liquidity to debt ratio of at least 1.50 to 1.00. If we fail to comply with our covenants, Comerica can declare any outstanding amounts immediately due and payable and stop extending credit to us. As of December 31, 2013, we were in compliance with the covenants. Additionally, we account for the $1.0 million minimum cash balance as non-current restricted cash as the funds are not available for immediate withdraw or use and the term of the borrowing arrangement is more than 12 months. The Comerica Credit Facility also required Mr. Roy’s remaining related party debt to be repaid or converted to equity by the end of December 2011. Pursuant to an Amendment to the Loan and Security Agreement entered into on December 28, 2011, the time period in which Mr. Roy’s remaining related party debt to be repaid or converted to equity was extended to June 30, 2012. On June 28, 2012, we entered into another amendment that further extended the maturity date to July 31, 2013. In addition, Mr. Roy entered into an Affirmation of Subordination Agreement with Comerica, under which Mr. Roy acknowledges our execution of the Second Amendment and affirms his obligations under the Subordination Agreement with Comerica dated June 27, 2011.

On December 28, 2012, we entered into a Third Amendment to Loan and Security Agreement with Comerica, which amended the Second Loan and Security Agreement, entered into by the Company and the Bank on June 28, 2012. Subject to and upon the terms and conditions of the Loan Amendment, the Bank agreed to make a term loan to the Company in one disbursement in the amount of $3.0 million, which the Company was obligated to use to pay down indebtedness owed to Mr. Roy. As of December 31, 2013 and June 30, 2013, the amount outstanding under the Comerica Term Loans was $3.3 million and $4.7 million, respectively.

12

The Third Amendment to Loan and Security Agreement provides, in addition to other terms and conditions contained therein, that (i) the maturity date of the term loan will be June 28, 2016; (ii) the Company shall repay the term loan in thirty-six (36) equal monthly installments of principal in the amount of $83,333.33 each, plus all accrued interest, beginning on July 1, 2013, and continuing on the same day of each month thereafter through the maturity date, at which time remaining amounts due shall be immediately due and payable; (iii) the proceeds of the term loan must be used to pay-down the Note; (iv) the interest on the term loan is the prime interest rate plus one percent and (v) there are no prepayment penalties or warrants associated with the term loan.

On December 31, 2012, the Company used the proceeds of the term loan to pay $3.0 million of the indebtedness due to Mr. Roy.

Note 5. Income Taxes

Income taxes are accounted for using the asset and liability method in accordance with ASC 740, Income Tax. Under this method, deferred tax liabilities and assets are recognized for the estimated future tax consequences attributable to differences between the financial statement carrying amounts of existing assets and liabilities and their respective tax bases. Based upon the weight of available evidence, which includes our historical operating performance and the reported cumulative net losses in all prior years, we have provided a full valuation allowance against our net deferred tax assets except the deferred tax assets related to India as we believe it is more likely than not that those assets will be realized. Our provision consists of foreign and state income taxes. Our income tax rate differs from the statutory tax rates primarily due to the utilization of net operating loss carry-forwards which had previously been valued against.

The Company accounts for uncertain tax positions according to the provisions of ASC 740. ASC 740 contains a two-step approach for recognizing and measuring uncertain tax positions. Tax positions are evaluated for recognition by determining if the weight of available evidence indicates that it is probable that the position will be sustained on audit, including resolution of related appeals or litigation. Tax benefits are then measured as the largest amount which is more than 50% likely of being realized upon ultimate settlement. The Company considers many factors when evaluating and estimating tax positions and tax benefits, which may require periodic adjustments and which may not accurately anticipate actual outcomes. No material changes have occurred in the Company’s tax positions taken as of June 30, 2013 and in the three and six months ended December 31, 2013.

Note 6. Commitments and Contingencies

Warranty

We generally warrant that the program portion of our software will perform substantially in accordance with certain specifications for a period up to one year from the date of delivery. Our liability for a breach of this warranty is either a return of the license fee or providing a fix, patch, work-around or replacement of the software.

We also provide standard warranties against and indemnification for the potential infringement of third party intellectual property rights to our customers relating to the use of our products, as well as indemnification agreements with certain officers and employees under which we may be required to indemnify such persons for liabilities arising out of their duties to us. The terms of such obligations vary. Generally, the maximum obligation is the amount permitted by law.

Historically, costs related to these warranties have not been significant. Accordingly, we have no liabilities recorded for these costs as of December 31, 2013 and June 30, 2013. However, we cannot guarantee that a warranty reserve will not become necessary in the future.

Indemnification

We have also agreed to indemnify our directors and executive officers for costs associated with any fees, expenses, judgments, fines and settlement amounts incurred by any of these persons in any action or proceeding to which any of those persons is, or is threatened to be, made a party by reason of the person’s service as a director or officer, including any action by us, arising out of that person’s services as our director or officer or that person’s services provided to any other company or enterprise at our request.

Transfer pricing

We have received transfer pricing assessments from tax authorities with regard to transfer pricing issues for certain fiscal years, which we have appealed with the appropriate authority. We believe that such assessments are without merit and would not have a significant impact on our consolidated financial statements.

13

Litigation

On May 20, 2013, we filed suit against Pragmatus Telecom, LLC in the United States District of Delaware seeking a declaratory judgment that our products and services do not infringe directly or indirectly three patents purportedly owned by Pragmatus and that the claims of the Pragmatus patents are invalid. Pragmatus previously asserted these patents against certain of our customers. We have begun discovery and the matter is currently pending.

On May 17, 2013, we filed suit against Lodsys Group, LLC in the United States District Court for the Eastern District of Texas seeking a declaratory judgment that our products and services do not infringe directly or indirectly two patents purportedly owned by Lodsys and that the claims of the Lodsys patents are invalid. Lodsys previously asserted these patents against certain of our customers. The matter was settled on December 18, 2013.  We entered into a settlement agreement which among other items provides a license to the Lodsys patents. In the ordinary course of business, we are involved in various legal proceedings and claims related to alleged infringement of third-party patents and other intellectual property rights, commercial, corporate and securities, labor and employment, wage and hour, and other claims.

We make a provision for a liability relating to legal matters when it is both probable that a liability has been incurred and the amount of the loss can be reasonably estimated. These provisions are reviewed at least quarterly and adjusted to reflect the impact of negotiations, estimated settlements, legal rulings, advice of legal counsel and other information and events pertaining to a particular matter. In our opinion, resolution of all current matters is not expected to have a material adverse impact on our condensed consolidated results of operations, cash flows or financial position. However, depending on the nature and timing of any such dispute, an unfavorable resolution of a matter could materially affect our future results of operations or cash flows, or both, of a particular quarter.

Note 7. Fair Value Measurement

ASC 820, Fair Value Measurement and Disclosures, defines fair value, establishes a framework for measuring fair value of assets and liabilities, and expands disclosures about fair value measurements. Fair value is defined as the exchange price that would be received for an asset or paid to transfer a liability in the principal or most advantageous market for the assets or liabilities in an orderly transaction between market participants on the measurement date. Subsequent changes in fair value of these financial assets and liabilities are recognized in earnings or other comprehensive income when they occur. ASC 820 applies whenever other statements require or permit assets or liabilities to be measured at fair value.

ASC 820 includes a fair value hierarchy, of which the first two are considered observable and the last unobservable, that is intended to increase the consistency and comparability in fair value measurements and related disclosures. Valuation techniques used to measure fair value must maximize the use of observable inputs and minimize the use of unobservable inputs. Observable inputs reflect assumptions market participants would use in pricing an asset or liability based on market data obtained from independent sources while unobservable inputs reflect a reporting entity’s pricing based upon their own market assumptions. The fair value hierarchy consists of the following three levels:

Level 1 – instrument valuations are obtained from real-time quotes for transactions in active exchange markets involving identical assets.

Level 2 – instrument valuations are obtained from readily-available pricing sources for comparable instruments.

Level 3 – instrument valuations are obtained without observable market value and require a high level of judgment to determine the fair value.

The following table summarizes the fair value hierarchy of our financial assets and liabilities measured (unaudited, in thousands):

The Company uses quoted prices in active markets for identical assets or liabilities to determine fair value of Level 1 investments.

14

As of December 31, 2013 and June 30, 2013, we did not have any Level 2 or 3 assets or liabilities.

Our financial instruments consist of cash and cash equivalents, accounts receivable, accounts payable and debt. We do not have any derivative financial instruments. We believe the reported carrying amounts of these financial instruments approximate fair value, based upon their short-term nature and comparable market information available at the respective balance sheet dates.

Note 8. Share Repurchase Program

On September 14, 2009, we announced that our board of directors approved a repurchase program under which we may purchase up to 1,000,000 shares of our common stock. The duration of the repurchase program is open-ended. Under the program, we purchase shares of common stock from time to time through the open market and privately negotiated transactions at prices deemed appropriate by management. The repurchase is funded by cash on hand. For the three and six months ended December 31, 2013 and 2012 there were no shares repurchased.

15

Item 2. Management’s Discussion and Analysis of Financial Condition and Results of Operations

The following discussion in “Management’s Discussion and Analysis of Financial Condition and Results of Operations” (“MD&A”) contains forward-looking statements within the meaning of Section 27A of the Securities Act of 1933, as amended (the “Securities Act”), and Section 21E of the Securities Exchange Act of 1934, as amended (the “Exchange Act”).These statements may be identified by the use of the words such as “anticipates,” “believes,” “continue,” “could,” “would,” “estimates,” “expects,” “intends,” “may,” “might,” “plans,” “potential,” “should,” or “will” and similar expressions or the negative of those terms. The forward-looking statements include, but are not limited to, statements regarding: the effect of changes in macroeconomic factors beyond our control; our hybrid revenue model and its potential impact on our total revenue; our ability to predict subscription renewals or upgrade rates; our lengthy sales cycles and the difficulty in predicting timing of sales or delays; competition in the markets in which we do business and our failure to compete successfully therein; our expectations regarding the composition of our customers and the result of a loss of a significant customer; the adequacy of our capital resources and need for additional financing and the effect of failing to obtain adequate funding; the development and expansion of our strategic and third party distribution partnership and relationships with systems integrators; our ability to effectively implement and improve our current products; our ability to innovate and respond to rapid technological change and competitive challenges; legal liability or the effect of negative publicity for the services provided to consumers via our technology platforms; legal and regulatory uncertainties and other risks related to protection of our intellectual property assets; our ability to anticipate our competitors; the operational integrity and maintenance of our systems; the effect of unauthorized access to a customer’s data or our data or our IT systems; the uncertainty of demand for our products; the anticipated customer benefits from our products; the actual mix in new business between cloud and license transactions when compared with management’s projections; our ability to develop and expand strategic and third party distribution channels; the ability to increase revenue as a result of the increased investment in sales and marketing; our ability to hire additional personnel and retain key personnel; the effect of any future changes to our sales organization on our revenue growth rate; our ability to expand and improve our sales performance and marketing activities; our ability to manage our expenditures and estimate future expenses, revenue, and operational requirements; the expenses associated with new data centers, additional data center capacity, real estate and office facilities space; our ability to manage our business plans, strategies and outlooks and any business-related forecasts or projections; the effect of the voluntary change in our accounting policy on our ability to compare our financial results with our industry peers; the effect of changes to management judgments and estimates; risks associated with the uncertainty of pending litigation; the result of our failure to comply with the covenants under the Comerica Loan; the impact of any modification to our pricing practices in the future; risks from our substantial international operations; our inability to successfully detect weaknesses or errors in our internal controls; our ability to manage future growth; the trading price of our common stock; geographical and currency fluctuations; and our expectations in fiscal 2014 with respect to revenue, cost of revenue, expenses and other financial metrics. Forward looking statements are subject to risks and uncertainties that could cause actual results to differ materially from those expected.   These risks and uncertainties include, but are not limited to, those risks discussed in “Risk Factors” Item 1A in this report and in our Annual Report on Form 10-K for the fiscal year ended June 30, 2013 which is incorporated herein by reference. Our actual results could differ materially from those discussed in statements relating to our future plans, product releases, objectives, expectations and intentions, and other assumptions underlying or relating to any of these statements. These forward-looking statements represent our estimates and assumptions and speak only as of the date hereof. We expressly disclaim any obligation or understanding to release publicly any updates or revisions to any forward-looking statements contained herein to reflect any change in our expectations with regard thereto or any change in events, conditions or circumstances on which any such statement is based unless required by law.

All references to “eGain”, the “Company”, “our”, “we” or “us” mean eGain Corporation and its subsidiaries, except where it is clear from the context that such terms mean only this parent company and excludes subsidiaries.

Overview

eGain Corporation is one of the premier providers of cloud and on-premise customer interaction software for sales and service. For over a decade, our solutions have helped improve customer experience, grow sales, and optimize service processes across the web, social, and phone channels. Hundreds of global enterprises rely on eGain to transform fragmented sales engagement and customer service operations into unified Customer Interaction Hubs.  We have operations in the United States, United Kingdom, Netherlands, Ireland, Italy, Germany, South Africa and India.

Unbilled Deferred Revenue

Unbilled deferred revenue represents business that is contracted but not yet invoiced or collected and off–balance-sheet and, accordingly, is not recorded in deferred revenue. As such, the deferred revenue balance on our condensed consolidated balance sheets does not represent the total contract value of annual or multi-year, non-cancelable subscription agreements. As of December 31, 2013, unbilled deferred revenue decreased to $17.7 million, from approximately $24.8 million as of June 30, 2013.

16

Critical Accounting Policies and Estimates

Management’s Discussion and Analysis of Financial Condition and Results of Operations discuss our condensed consolidated financial statements, which have been prepared in accordance with accounting principles generally accepted in the United States of America. The preparation of these financial statements requires our 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 revenue and expense during the reporting period. On an on-going basis, our management evaluates its estimates and judgments, including those related to revenue recognition, allowance for doubtful accounts, deferred tax, valuation allowance and accrued liabilities, long-lived assets and stock-based compensation. Management bases its estimates and judgments on historical experience and on various other factors that are believed to be reasonable under the circumstances, the results of which form the basis for making judgments about the carrying values of assets and liabilities that are not readily apparent from other sources. Actual results may differ from these estimates under different assumptions or conditions.

There have been no material changes to these estimates for the periods presented in this Quarterly Report on Form 10-Q. For a detailed explanation of the judgments made in these areas, refer to “Management’s Discussion and Analysis of Financial Condition and Results of Operations” within our Annual Report on Form 10-K for the year ended June 30, 2013, which we filed with the Securities and Exchange Commission on September 23, 2013.

We have reassessed the critical accounting policies as disclosed in our Annual Report on Form 10-K filed with the SEC on September 23, 2013 and determined that there were no significant changes to our critical accounting policies in the six months ended December 31, 2013.

Revenue Recognition

We derive revenue from three sources:

We evaluate whether each of the elements in these arrangements represents a separate unit of accounting, as defined by ASC 605, using all applicable facts and circumstances, including whether (i) we sell or could readily sell the element unaccompanied by the other elements, (ii) the element has stand-alone value to the customer, and (iii) there is a general right of return. We use VSOE, of fair value for each of those units, when available. For revenue recognition with multiple-deliverable elements, in certain limited circumstances when VSOE of fair value does not exist, we apply the selling price hierarchy, which includes VSOE, third-party evidence of selling price, or TPE, and best estimate of selling price, or BESP. We determine the relative selling price for a deliverable based on VSOE, if available, or BESP, if VSOE is not available. We have determined that TPE is not a practical alternative due to differences in our service offerings compared to other parties and the availability of relevant third-party pricing information.

We determine BESP by considering our overall pricing objectives and market conditions. Significant pricing practices taken into consideration include our discounting practices, the size and volume of our transactions, customer demographic, the geographic area where services are sold, price lists, its go-to-market strategy, historical standalone sales and contract prices. The determination of BESP is made through consultation with and approval by our management, taking into consideration the go-to-market strategy. As our go-to-market strategies evolve, we may modify our pricing practices in the future, which could result in changes in relative selling prices, including both VSOE and BESP.

Subscription and Support Revenue

Cloud Revenue

Cloud revenue consists of subscription fees from customers accessing our cloud-based service offerings. We recognize cloud services revenue ratably over the period of the applicable agreement as services are provided. Cloud agreements typically have an initial term of one or two years and automatically renew unless either party cancels the agreement. The majority of the cloud services customers purchase a combination of our cloud service and professional services. In some cases, the customer may also acquire a license for our software.

17

We consider the applicability of ASC 985-605, on a contract-by-contract basis. In cloud based agreements, where the customer does not have the contractual right to take possession of the software, the revenue is recognized on a monthly basis over the term of the contract. Invoiced amounts are recorded in accounts receivable and in deferred revenue or revenue, depending on whether the revenue recognition criteria have been met. We consider a software element to exist when we determine that the customer has the contractual right to take possession of our software at any time during the cloud period without significant penalty and can feasibly run the software on its own hardware or enter into another arrangement with a third party to host the software. Additionally, we have established VSOE for the cloud and maintenance and support elements of perpetual license sales, based on the prices charged when sold separately and substantive renewal terms. Accordingly, when a software element exists in a cloud services arrangement, license revenue for the perpetual software license element is determined using the residual method and is recognized upon delivery. Revenue for the cloud and maintenance and support elements is recognized ratably over the contractual time period. Professional services are recognized as described below under “Professional Services Revenue.” If VSOE of fair value cannot be established for the undelivered elements of an agreement, the entire amount of revenue from the arrangement is recognized ratably over the period that these elements are delivered.

Term License Revenue

Term license revenue includes arrangements where our customers receive license rights to use our software along with bundled maintenance and support services for the term of the contract. The majority of our contracts provide customers with the right to use one or more products up to a specific license capacity. Certain of our license agreements stipulate that customers can exceed pre-determined base capacity levels, in which case additional fees are specified in the license agreement. Term license revenue is recognized ratably over the term of the license contract.

Maintenance and Support Revenue

Maintenance and support revenue consists of customers purchasing maintenance and support for our on-premise software. We use VSOE of fair value for maintenance and support to account for the arrangement using the residual method, regardless of any separate prices stated within the contract for each element. Maintenance and support revenue is recognized ratably over the term of the maintenance contract, which is typically one year. Maintenance and support is renewable by the customer on an annual basis. Maintenance and support rates, including subsequent renewal rates, are typically established based upon a specified percentage of net license fees as set forth in the arrangement.

License Revenue

License revenue includes perpetual license rights sold to customers to use our software in conjunction with related maintenance and support services. If an acceptance period is required, revenue is recognized upon the earlier of customer acceptance or the expiration of the acceptance period. In software arrangements that include rights to multiple software products and/or services, we use the residual method under which revenue is allocated to the undelivered elements based on VSOE of the fair value of such undelivered elements. The residual amount of revenue is allocated to the delivered elements and recognized as revenue, assuming all other criteria for revenue recognition have been met. Such undelivered elements in these arrangements typically consist of software maintenance and support, implementation and consulting services and in some cases, cloud services.

We periodically sell to resellers. License sales to resellers as a percentage of total revenue were approximately 2% and 3% for the three months ended December 31, 2013 and 2012, respectively. License sales to resellers as a percentage of total revenue were approximately 9% and 2% for the six months ended December 31, 2013 and 2012, respectively.  Revenue from sales to resellers is generally recognized upon delivery to the reseller but depends on the facts and circumstances of the transaction, such as our understanding of the reseller’s plans to sell the software, if there are any return provisions, price protection or other allowances, the reseller’s financial status and our experience with the particular reseller. Historically sales to resellers have not included any return provisions, price protections or other allowances.

18

Professional Services Revenue

Professional services revenue includes system implementation, consulting and training. For license transactions, the majority of our consulting and implementation services qualify for separate accounting. We use VSOE of fair value for the services to account for the arrangement using the residual method, regardless of any separate prices stated within the contract for each element. Our consulting and implementation service contracts are bid either on a fixed-fee basis or on a time-and-materials basis. Substantially all of our contracts are on a time-and-materials basis. For time-and-materials contracts, where the services are not essential to the functionality, we recognize revenue as services are performed. If the services are essential to functionality, then both the license revenue and the service revenue are recognized under the percentage of completion method. For a fixed-fee contract, we recognize revenue based upon the costs and efforts to complete the services in accordance with the percentage of completion method, provided we are able to estimate such cost and efforts.

Under ASC 605-25, in order to account for deliverables in a multiple-deliverable arrangement as separate units of accounting, the deliverables must have standalone value upon delivery. For cloud services, in determining whether professional services have standalone value, we consider the following factors for each professional services agreement: availability of the services from other vendors, the nature of the professional services, the timing of when the professional services contract was signed in comparison to the subscription service start date and the contractual dependence of the subscription service on the customer’s satisfaction with the professional services work.

As of June 30, 2013, we did not have standalone value for the professional services related to consulting and implementation of a majority of our core subscription services. This was due to the fact that we had historically performed the majority of these services to support our customers’ implementation of the subscription services. We determined at or around July 1, 2013 that we had established standalone value for these implementation services. This was primarily due to the change in our business focus, the growing number of partners we trained and certified to perform these deployment services and the consequential sale of subscription services without bundled implementation service. Revenues earned from professional services related to consulting and implementation of a majority of our core subscription services are being accounted for separately from revenues earned from subscription services beginning July 1, 2013 when the standalone value was established for those professional services.

For those contracts that have standalone value, we recognized the services revenue when rendered for time and material contracts, when the milestones are achieved and accepted by the customer for fixed price contracts or by percentage of completion basis if there is no acceptance criteria.

For cloud, consulting and implementation services that do not qualify for separate accounting, we recognize the services revenue ratably over the estimated life of the customer cloud relationship, once cloud has gone live or system ready. We currently estimate the life of the customer cloud relationship to be approximately 28 months, based on the average life of all cloud customer relationships.

Training revenue that meets the criteria to be accounted for separately is recognized when training is provided.

Deferred Revenue

Deferred revenue primarily consists of payments received in advance of revenue recognition from cloud, term license, and maintenance and support services and is recognized as the revenue recognition criteria are met. We generally invoice customers in annual or quarterly installments. The deferred revenue balance does not represent the total contract value of annual or multi-year, non-cancelable cloud or maintenance and support agreements. Deferred revenue is influenced by several factors, including seasonality, the compounding effects of renewals, invoice duration, invoice timing and new business linearity within the quarter.

Deferred revenue that will be recognized during the succeeding twelve month period is recorded as current deferred revenue and the remaining portion is recorded as noncurrent. At December 31, 2013, deferred revenue increased to $20.0 million, compared to $19.7 million at June 30, 2013.

Deferred Commissions

Deferred commissions are the direct and incremental costs directly associated with cloud contracts with customers and consist of sales commissions to the Company’s direct sales force.

The commissions are deferred and amortized over the terms of the related customer contracts, which are typically one or two years. The commission payments are paid based on contract terms in the month following the quarter in which the commissions are earned. The deferred commission amounts are recognized as selling expense in the condensed consolidated statements of operations over the terms of the related customer contracts, in proportion to the recognition of the associated revenue.

19

Results of Operations

The following table sets forth certain items reflected in our condensed consolidated statements of operations expressed as a percent of total revenue for the periods indicated:

Revenue

Total revenue increased 20% to $17.7 million in the quarter ended December 31, 2013 from $14.7 million in the comparable year-ago quarter. Subscription and support revenue, which is comprised of cloud, term license and software maintenance and support revenue increased 31% to $10.2 million in the quarter ended December 31, 2013 from $7.8 million in the comparable year-ago quarter. The increase in subscription and support revenue was primarily due to the expansion within our current customer base and new cloud contracts. License revenue decreased 11% to $3.1 million in the quarter ended December 31, 2013 from $3.4 million in the comparable year-ago quarter. Professional services revenue increased 24% to $4.4 million in the quarter ended December 31, 2013 from $3.5 million in the comparable year-ago quarter. The increase in professional services revenue was primarily due to the professional services for cloud arrangements which we have determined to have value to the customer on a standalone basis as of July 1, 2013 and therefore are accounted for separately. When accounted for separately, these professional services revenues would generally be recognized as the services are rendered.  Prior to this, professional services revenue for cloud arrangements were recognized ratably over the longer of the remaining contractual period or the average estimated life of the customer cloud relationship, once the cloud has gone live or system ready.

Revenue in Europe and Asia Pacific increased 36% to $8.6 million in the quarter ended December 31, 2013 from $6.3 million in the comparable year-ago quarter. The increase in revenue outside of the Americas demonstrates increased acceptance of our product world-wide. The impact of the foreign exchange fluctuation between the U.S. Dollar and the Euro and British Pound resulted in a net increase of $8,000 in total revenue for the six months ended December 31, 2013 as compared to the comparable year-ago period. To measure the impact of foreign exchange rate fluctuation, we recalculate current period results using the comparable prior period exchange rate.

20

Cost of Revenue

Total cost of revenue increased 37% to $5.8 million in the quarter ended December 31, 2013 from $4.3 million in the comparable year-ago quarter. Total cost of revenue represented 33% and 29% of total revenue in the quarters ended December 31, 2013 and 2012, respectively. The change was primarily due to increases of (i) $1.2 million in personnel and personnel-related expenses; (ii) $285,000 in cloud related expenses such as hosted network and lease costs paid to remote co-location centers; (iii) $173,000 in outside consulting partially offset by decreases of (i) $49,000 from the foreign exchange fluctuation between the U.S. Dollar, the Euro, British Pound and India Rupee and (ii) $21,000 in license related expenses. Gross margin for the quarter ended December 31, 2013 was 67% compared to 71% in the comparable year-ago quarter.

Total cost of revenue for the six months ended December 31, 2013 increased $2.8 million, or 32%, compared to the same period last year. The change was primarily due to increases of (i) $2.1 million in personnel and personnel-related expenses; (ii) $624,000 in cloud related expenses such as hosted network and lease costs paid to remote co-location centers; (iii) $184,000 in outside consulting partially offset by decreases of (i) $107,000 from the foreign exchange fluctuation between the U.S. Dollar, the Euro, British Pound and India Rupee and (ii) $39,000 in license related expenses. Gross margin for the six months ended December 31, 2013 and 2012 was 66%, respectively.

Operating Expenses

Research and Development