Good day, welcome to Guidewire's third quarter fiscal 2018 financial results conference call. Today's conference is being recorded. At this time, I'd like to turn the conference over to Mr. Curtis Smith, CFO. Please go ahead.
Good afternoon, welcome to Guidewire Software's earnings conference call for the third quarter of fiscal year 2018, which ended on April 30, 2018. My name is Curtis Smith. I am the Chief Financial Officer of Guidewire, with me on the call is Marcus Ryu, Guidewire's Chief Executive Officer. A complete disclosure of our results can be found in our press release issued today, as well as in our related Form 8-K furnished to the SEC, both of which are available on the IR section of our website at ir.guidewire.com. As a reminder, today's call is being recorded, a replay will be available following the conclusion of the call.
During the call, we will make forward-looking statements pursuant to the safe harbor provisions of the Private Securities Litigation Reform Act of 1995 regarding trends, strategies, and anticipated performance of the business, including additional information related to our recent acquisition activity. These forward-looking statements are based on management's current views and expectations as of today and should not be relied upon as representing our views as of any subsequent date. We disclaim any obligation to update any forward-looking statements or outlook. Actual results may differ materially. Please refer to the risk factors in our most recent Form 10-K and 10-Qs filed with the SEC. We will also refer to certain non-GAAP financial measures to provide additional information to investors. A reconciliation of non-GAAP to GAAP measures is provided in our press release. Reconciliations and additional data are posted in a supplement on our IR website.
During the call, we may offer incremental metrics to provide greater insight into the dynamics of our business. These details may be one time in nature, we may or may not provide updates in the future. With that, let me turn the call over to Marcus for his prepared remarks, then I will provide details on our third quarter results before providing our outlook for Q4 and fiscal 2018. Marcus and I will then take your questions.
Thank you, Curtis. Our third quarter financial results exceeded our revenue and non-GAAP profitability guidance ranges, with total revenue of $140.5 million and non-GAAP earnings of $0.05 per share. Momentum with cloud-based solutions continued in the third quarter. Almost 50% of our year-to-date new sales are subscriptions, and we continue to be at the high end of our prior communicated range of 30%-40%, with nearly all of the remainder coming in the form of traditional recurring term licenses. The transition to cloud-based solutions continues for both the P&C industry and for Guidewire. Cloud-based core systems and a delivery model in which the solution is delivered by the vendor in production are still relatively new concepts for P&C insurers. We are seeing broad interest in all regions and from all segments of our markets.
Smaller insurers have been earlier adopters of cloud core systems. The benefits of simplification and risk transfer are just as compelling to large and mid-size insurers. Cloud implementations should enable us over time to reduce the total cost of ownership for our customers through more standard implementations and integrations and the leverage of cloud-native architectures. Our market experience strongly suggests that lowering TCO, combined with a transfer of risk and complexity away from our customers' operations to a trusted partner, will increase the rate of market adoption. Cloud adoption comes at a time when insurers and their CIOs are challenged with managing extremely ambitious technology project agendas with finite resources and management bandwidth. By transferring non-differentiating core operations to Guidewire, our clients can focus their resources on driving value for policyholders by delivering new products and Digital Engagement.
Cloud economics are also compelling for Guidewire because we are compensated for bearing that additional risk and complexity with annual subscription fees that are substantially greater than comparable annual term licenses. Although we're still in the early stages of price discovery, we expect cloud deployments to drive a material expansion of our TAM, as both existing and new customers are attracted to the convenience, efficiency, and value that cloud-based core systems offer. The shift to cloud deployments also enables us to ensure that customers are on the latest release of our software, which avails them of the full benefit of our R&D investments and reduces our maintenance burden. We're very excited about the opportunity, and customers are excited as well, as reflected by the adoption of InsuranceSuite Cloud in the third quarter by two existing customers.
One of these is a tier 1 insurer who will be using InsuranceSuite Cloud to drive premium growth in a new line of business. The other is Grinnell Mutual, a regional insurer based in the Midwest, which had already licensed InsuranceSuite and has now opted for Guidewire to implement and manage it as a cloud-delivered solution. Looking at sales activity beyond InsuranceSuite Cloud for the quarter, we again enjoyed a mix of activities from new and existing customers. In the quarter, we added five new insurers to our customer community, four of whom selected InsuranceSuite, including an international business unit of Travelers, the second-largest writer of U.S. commercial property and casualty insurance and also a leading provider of auto, home, and business insurance.
Ayr Farm Mutual, based in Ontario, Canada, a provider of auto, home, farm, and commercial insurance, selected a broad set of products, including InsuranceSuite, DataHub, InfoCenter, and our digital products. Argentina's La Segunda Co-op, a group of companies offering P&C, group life, and retirement, selected InsuranceSuite, Business Intelligence for InsuranceSuite, and Client Data, Rating, and reinsurance management products. Also in North America, IAT Insurance Group, a specialty insurance company based in Texas, licensed PolicyCenter and Rating Management. In addition to these four, we added an InsuranceNow customer, Farmers Union Insurance, a mutual insurance company serving farmers, ranchers, homeowners, and businesses across North Dakota, who selected our all-in-one cloud-based solution, InsuranceNow, to replace their current core solution. We also continue to gain traction with our digital and data products. 13 existing customers selected one or more of these in the quarter.
In addition to sales momentum, we had an active quarter for implementations, with nine customers going live with InsuranceSuite, InsuranceNow, data or digital products during the quarter, and four customers having major version core upgrades. Turning to products. Last month, we announced the latest release of Guidewire Insurance Platform. This release includes enhancements to our core data and digital and all-in-one product families, along with more than 80 Ready for Guidewire validated accelerators. Collectively, these product enhancements and third-party solution additions enable insurers to reinvent customer agent and employee experiences. We also announced availability of our first P&C Insurance CRM applications for Salesforce Financial Services Cloud. These applications will be natively integrated to FSC and enable P&C insurers to unify their core digital and CRM strategies with much less complexity.
Finally, our leadership continues to be recognized by the industry, as demonstrated by our winning two awards for policy administration by industry analyst Celent. In summary, our third quarter performance reflects continued momentum in the marketplace, including continued adoption of products across the Guidewire Insurance Platform, and notable successes with the selection and implementation of InsuranceSuite Cloud. Adoption of our cloud service, as well as the robust attach rates of our digital and data products, continue to validate our platform value proposition and contribute to our growth. We look forward to our customers' and prospects' reception of the many products we are releasing this year, as well as celebrating the great progress many of them are making in their transformation initiatives relying on Guidewire. With that, I'll turn it over to Curtis to detail the financial results of our third quarter.
Thank you, Marcus. We had an active Q3. We exceeded our guidance ranges on both the top and bottom line. We successfully completed a capital raise, and we closed two new InsuranceSuite Cloud customers. As a result of this cloud momentum, and as noted by Marcus, almost 50% of our new sales year to date were subscription, and we continue to expect to be at the high end of our prior communicated range of 30%-40% of this year's new sales as subscriptions. We note that seasonally high Q4 activity will have a large impact on the final percentage. We are also on track to add four to five InsuranceSuite Cloud deals this year, with three closed year to date. Total revenue for the quarter increased 14% from a year ago to $140.5 million.
Within revenue, license and other revenue of $50.4 million represented a decrease of 15% from a year ago. As a reminder, a very sizable recurring payment from one of our Tier 1 customers was recognized in Q3 last year, but will be invoiced for payment and therefore recognized in Q4 in this and subsequent years. In addition, approximately $4.6 million of revenue that was expected in Q3 was recognized in Q2 due to earlier payments last quarter. Perpetual revenue in the third quarter was $5.7 million. Maintenance revenue was $18.7 million, representing an 11% year-over-year increase and at the midpoint of our guidance range. As we shift toward cloud subscription services, we do expect maintenance growth rates to moderate, as ongoing maintenance activities are included in the subscription fees.
Our rolling four-quarter recurring revenue, consisting of term license, subscription, and maintenance revenue, totaled $334.4 million in the third quarter, up 10% from a year ago. In Q3, this metric was significantly impacted by the quarter shift in invoicing for the customer I just referenced. Additionally, as we have mentioned previously, our ongoing transition to subscription and the eventual adoption of ASC 606 in fiscal year 2019 make this metric less relevant to our business. After this fiscal year, we will no longer highlight rolling four-quarter recurring revenue as a key metric. Services revenue was $71.4 million, a 50% increase from a year ago and also above our guidance range.
Faster services growth in the quarter was driven by three primary factors: greater demand for Guidewire services personnel and in some of our initial InsuranceSuite Cloud implementations, inclusion of and growth in InsuranceNow implementation and hosting services following the acquisition of ISCS, which did not incur until partly through Q3 of last year, and recognition this year of previously deferred services revenue. Turning to profitability. We will discuss these metrics on a non-GAAP basis, and we have provided the comparable GAAP metrics and a reconciliation of GAAP to non-GAAP measures in our earnings press release issued today, with the primary difference being stock-based compensation expenses, amortization of intangibles, the amortization of debt discount, and issuance costs from our convertible note, and the related tax effects of these adjustments.
Non-GAAP gross profit of $77.5 million decreased 4% from a year ago and represented a non-GAAP gross margin of 55.2%, compared to 65.1% a year ago. The expected decrease in margin was due primarily to the previously mentioned payment shift of a Tier 1 term customer, as well as the increase in our services revenue and investments in our cloud operations. The non-GAAP operating expenses were $75.2 million in the third quarter, an increase of 19% compared to a year ago. This increase was primarily driven by continued investments in R&D and sales, the impact of our recent acquisition of Cyence, and to a lesser extent, the work associated with several large infrastructure projects, including new ERP and configure-price-quote systems and related implementation expenses.
This resulted in non-GAAP operating income of $2.3 million, which was above our guidance range, primarily due to higher-than-anticipated revenue and modestly lower than anticipated expenses in the current period. Non-GAAP net income was $3.9 million or $0.05 per diluted share, compared to non-GAAP net income of $12.3 million or $0.16 per diluted share a year ago. Turning to our balance sheet. We ended the quarter with $1.2 billion in cash equivalents, and investments, up from $569.5 million at the end of our second quarter, primarily due to $571 million in net proceeds, adjusted for the cost of the cap call from the financing we completed in the third quarter. In addition, operating cash flow in the third quarter was $20.2 million, and free cash flow was $19 million.
Total deferred revenue was $134.6 million at the end of the third quarter, an increase from $130.9 million at the end of the second quarter. As a reminder, our deferred revenue balance can vary widely from quarter to quarter and has not been a meaningful indicator of business activity since we typically bill term license contracts annually and recognize the full annual payment upon the due date. However, deferred revenues will likely sustain higher levels as we increase sales of subscriptions, though we expect deferred revenues to continue to be highly variable. The growth of deferred revenue in the quarter was in part attributed to higher license deferred revenues generated by subscription sales. Now turning to guidance. First, let me address our expectations for the full year. I will speak to Q4, and finally, I will make some high-level comments on fiscal year 2019.
For the full year, we now anticipate total revenue to be in the range of $647 million-$653 million, an increase of 26%-27% from fiscal 2017. We expect annual license and other revenue to be in the range of $306 million-$312 million, an increase of 13%-15% from fiscal 2017. Our license and other revenue is being impacted by our transition to cloud-based subscription sales, which as noted earlier, we expect to be at the high end of our previously communicated 30%-40% range. Compared to term and perpetual licenses, we can recognize only a portion of the annual subscription invoices in the initial year due to ratable revenue recognition. Additionally, we expect perpetual license revenue between $9 million-$10 million for the year, a decrease from $13 million last year. Our outlook for maintenance revenue is $76 million-$77 million.
Services revenue continues to be elevated in fiscal 2018. In particular, cloud implementations and our work for new European customers currently require greater Guidewire participation. Our outlook for services revenue is $262 million-$266 million. Required build-out of services, processes, and best practices to support the cloud will require increased services support that cannot all be passed on to the customer. As a result, we expect services margin to be between 18%-19% this fiscal year. Due to higher profitability in Q3 and our higher revenue outlook, we are raising our non-GAAP operating income guidance for fiscal 2018 to $104 million-$110 million. We're also increasing our free cash flow guidance for the year to $115 million-$125 million.
In addition, we are raising our outlook for non-GAAP net income to $83.3 million-$87.7 million, or $1.05-$1.11 per diluted share, based on approximately 79.3 million diluted shares. Turning to Q4. We anticipate total revenue to be in the range of $234 million-$240 million. Within revenue, we expect license and other revenue to be in the range of $141 million-$147 million, maintenance revenue of $19 million-$20 million, and services revenue of $71 million-$75 million. For the fourth quarter, we anticipate a non-GAAP operating income of between $78 million-$84 million and non-GAAP net income of between $58.8 million and $63.2 million, or $0.72 per share-$0.77 per share based on approximately 82 million diluted shares. Looking ahead now to fiscal 2019. We want to provide some preliminary qualitative commentary.
Unless otherwise stated, all of our commentary is based on our adoption of ASC 606 on August 1st, 2018. As we have discussed in the past, the transition to subscription contracts and the adoption of 606 have an impact on our outlook for 2019, and this outlook is very much evolving. We will spend more time discussing this on our Q4 call and during our Analyst Day in September. With respect to top line, fiscal 2019 will be impacted by a number of factors. Two primary factors positively impacting growth. Subscription revenue associated with contracts sold in fiscal 2018 will increase in fiscal 2019, since we will be able to capture the full annual value of these contracts when compared to a partial year amount in fiscal 2018.
New term license contracts will recognize 2 years of annual license amounts due to our standard contracts being 2 years of duration at signing, coupled with annual auto renewals. Under 606, we will typically recognize the full 2-year contract value upfront. These positive factors will be offset by growth in new subscription sales, which will result in lower revenue recognized in fiscal 2019 due to ratable revenue recognition, as well as 2 accounting effects associated with our adoption of 606. The first, amounts due in fiscal 2019 for 2-year licenses sold in fiscal 2018 will not be recognized as revenue and will be accounted for as retained earnings. And 2, revenue lost to retained earnings due to existing long-term customer contracts that we are not able to modify to annual auto renewals. Netting these factors, we expect license and other revenue to grow modestly faster than in fiscal 2018.
This assumes subscription contracts will be approximately 40%-60% of new sales. At this mix, and assuming the successful modification of remaining long-term contracts, we expect 606 will have a net neutral impact on license and other revenue. With respect to total revenue, we expect growth to taper slightly as services revenue growth begins to normalize in 2019. Turning to profitability, there are three primary factors putting pressure on operating income and operating margin in fiscal year 2019. First, gross margin will be lower due to transition to the cloud and continued elevated services revenue as a percent of the total mix. Second, we previously indicated that 2018 would be a year of investment as we migrate to the cloud and invest in R&D and cloud operations to support this transition.
We have spent less than initially anticipated year-to-date in 2018, largely due to headcount additions being slightly back-end weighted in 2018. In 2019, we expect to slow our hiring and digest the investments made. The full impact of the investments made this year will be reflected in operating expenses in 2019. Third, we continue to expect Cyence to be diluted to our operating income in fiscal 2019. As a result of these factors, we do not expect to see operating margin expansion in 2019. As we have mentioned in the past, cash flow and other metrics will be key indicators of progress moving forward and further discussed at our Analyst Day. In summary, we executed well in the third quarter to deliver revenue and profitability that exceeded our guidance levels.
We are optimistic that we will see a seasonally strong fourth quarter, and that we remain well-positioned to continue capturing a meaningful share of the multi-billion dollar opportunity ahead of us. Thank you. Operator, can you now open the call for questions?
Thank you. If you'd like to ask a question, please signal by pressing *1 on your telephone keypad. If you're using a speakerphone, please make sure your mute function is turned off to allow us to know to reach our equipment. Again, press *1 to ask a question, and we'll pause for just a moment to allow everyone an opportunity to signal for questions. We'll take our first question today from Monika Garg with KeyBanc.
Hi, thanks for taking my question. First is I just want to confirm, I remember last time you gave us a metric like each 10% higher mix of subscription is about $3 million-$4 million negative impact to license revenue. Given that that mix is almost 10% higher than your previous guidance, is that the right way to think about negative impact on the license?
I think that's one way of look at it. We have done some sensitivity around that, looking at different ranges, and we are currently expecting to be at the high end of the previously announced range of the 30%-40%. As we move to the higher end of that range and have more subscription, we do then see less revenue come in, given that it's ratably recognized.
Got it. Curtis, the ASC 606 impact for next year, what you talked about, could you share how much is the negative impact on the license because of ASC 606 change? Like a dollar amount, like $10, any metrics you can share quantitatively?
Yeah. We did do some preliminary analysis of that, We're not sharing those numbers here, but we'll spend some more time on that when we get to our Q4 earnings call and when we talk about metrics going forward and impact of 606 going forward in our Analyst Day. One thing we did note, though, when we provided the preliminary commentary on 2019, is when we take both the puts and the takes from 606, both the positive and the negative, along with the subscription as a percent of revenue range we're expecting in fiscal 2019, which is now the 40%-60%, we believe that taking that all into account, that there is a net neutral impact from 606 on license and other revenue.
Got it. Thank you so much. That's all for me.
Next we'll hear from Jesse Hulsing with Goldman Sachs.
Yeah, thank you. Marcus, it seems like you're seeing a pretty big step-up in interest from new customers and existing customers on expansions for your cloud product. I'm wondering if you've given much thought to extending cloud beyond just new business and migrating the base, and if that were to happen, what would the timing of that look like?
Absolutely. Migrating the base is an important expected portion of the demand that we have ahead of us. Some of the acceleration in demand has been stimulated by us because we actively have been initiating these conversations, not necessarily with the minds transacting on them in the near term, but so that our customers understand our strategic direction and can start thinking about their overall deployment strategy. As they roll out the current project they may be involved in or future products they may license from us. It's very early in the transition. We're at a low single-digit number of InsuranceSuite Cloud customers out of a customer base of hundreds of insurers.
Our expectation is that, over time, a very large portion, quite possibly a majority or even a significant majority of our customers want the kind of division of labor that's involved in our cloud deployments as preferable to them. I think we have quite a few degrees of freedom in modulating the speed at which that happens. Obviously, we would never make commitments that we could not follow through with confidence. I think if anything, we will be constrained by our own appetite to follow through on that well than it will be by customer demand.
Yep. Curtis, question for you. Given the multiple puts and takes next year on growth with the subscription transition and ASC 606, and just the lumpiness of your contracts already playing into that, have you given thought to any metrics beyond what's being provided? You mentioned retiring trailing 12 months recurring revenue. I'm wondering if you've given any thought to ARR or some sort of metric to replace that to give us a little bit more visibility into demand quarter-to-quarter.
Yes. Thanks for that question. We spent some time in the past quarter talking to investors and analysts about what metrics might be helpful from their standpoint to better understand the progress we're making as we transition to a cloud business. Some of the things we've provided already, just as a reminder, the number of InsuranceSuite Cloud deals. We confirmed that number this quarter, that we're expecting 4 to 5 InsuranceSuite Cloud deals this year, and added 2 in the quarter. Another metric that we've been sharing is subscription as a % of new sales. In the quarter, we confirmed that 30%-40% range with the expectation for us to land at the high end of that range this year. In the past, we've also talked about breaking out and talking to subscription as a % of license and other revenue.
We pointed to, at the end of the year, that getting pretty close to 10%. When that happens, that we intend to break that out in FY 2019. To your question on the other key metric, the ARR ACV, it's clearly one that is at the top of our list to be thinking about and to be potentially adding to the mix to give you a better idea of the progress we're making in the transition to cloud. Our expectation is to talk about that more during Analyst Day, and potentially on the Q4 call.
Fantastic. Thank you both.
Next, we'll hear from Sterling Auty with JPMorgan.
Yeah, thanks. Hi, guys. First one's for you, Marcus. For an InsuranceSuite Cloud customer, what do the implementation times that you expect to be like for a brand new customer? What is the implementation time for an existing customer shifting into the cloud?
I appreciate the question, Sterling, because it's a chance to remind those listening that at least at this stage, there is no meaningful acceleration in implementation time for a cloud-based project versus our traditional on-premise ones. That's because the main drivers of implementation effort are configuration and integration. Those are not meaningfully different in the cloud world. We do believe that we have a lot of levers to drive higher standardization. That's something that we've been working on earnestly for years now, we're doubling our effort every year to urge customers and to give them strong professional guidance about the importance of conforming to a more standard solution. Of course, we're evolving our platforms to be ever more complete.
In the cloud modality, we think that we'll be able to advance that further, as well as make certain architectural advances in the product that will really leverage cloud scalability and serverless architecture and so forth. Over time, it's not only our expectation, it's our mission to significantly reduce the cost of ownership and to simplify and standardize projects. That will take time to evolve. For the time being, the programs are really very comparable in duration to what they are now. We've talked about this many times in the past. There's a lot of variation between our customers, depending on what product they're implementing and with what scope and so forth. Typically, we want our significant core system transformation programs to go live something like 12 to 18 months from the start.
That's great. As we think about the significant increase in revenue that you would get from an existing customer moving into the cloud, how should we think about how that layers in? What I mean is, if you have an existing full InsuranceSuite customer, are they going to move claims and then once claims is in the cloud, move policy? Would they do the entire InsuranceSuite, insurance line by insurance line or geography by geography? Just so we can understand how we might see the increase in the revenue associated with a customer moving into the cloud.
Yeah, that's a thoughtful question. I think that the sort of minimum unit of transition will be one of the core applications, policy claims or billing. It really wouldn't make sense to migrate slices of a claims implementation over, or slices of a policy implementation. It's quite possible that a customer would opt to do one core application at a time versus the entirety, though there may be cases where they would try to shift multiple at the same time. Of course, we have large, complex customers that may have more than one instance of our core applications because their businesses are disparate and may even operate semi-independently of each other. It's very case by case, but I think, again, the minimum unit will be a transition of one of the core applications to the cloud.
As we've talked about in the past, somewhere between 2.5 to 3x kind of improvement or increase in the annual recurring revenue to Guidewire, but now coming in subscription form, would be our expectation from where we sit today.
Got it. Thank you.
Our next question comes from Alex Zukin with Piper Jaffray.
Hi, this is Taylor Reiners on for Alex. I had a question for Marcus. I wanted to dig in on the Salesforce announcement from a couple of weeks ago that you now have two applications for their Salesforce Financial Services Cloud. I was wondering if you could speak to any early indications or tractions that you've seen in that area, then maybe any updates that you have for us from a go-to-market standpoint and any potential joint early customer wins. Thanks.
Sure. The Salesforce partnership is a highly strategic one for Guidewire. We are not in the habit of announcing lots of partnerships with other technology companies. They tend to be very difficult to implement successfully at a product level, then, of course, there's go-to-market complexities. The Salesforce is a very notable exception to that because of their tremendous market traction and the awakening of interest over the last few years in the P&C industry to rethinking, sometimes dramatically, their whole approach to CRM. Quickly following that is a recognition that any kind of CRM initiative they undertake has to be deeply integrated with the transactional and operational core, which is, of course, what we do. There's a very natural complementarity between our businesses and our value propositions, though it did take us a few years to mutually persuade each other of that.
Now I think we're completely on the same page and are working together in stride. There has been a very encouraging level of interest across the industry, including internationally for this connection. I think the expectation of a lot of insurers is that we would productize this integration and solve that complexity for them rather than them doing it themselves. At a go-to-market level, they're a great organization to work with. They're enormously successful and professional sales teams that we can complement with our deeper industry understanding as well as now a very coherent complementarity of value propositions.
Got it. Thank you.
Next, we'll hear from Justin Furby with William Blair & Company.
Thanks, guys. Marcus, I thought the Travelers announcement, I think in international markets in Europe was interesting because I don't think you have a relationship with them, at least here in the U.S. I guess I'm just wondering more broadly speaking, what the cloud does for you in terms of just strengthening your tier 1 pipeline. Second to that, can you just give some sort of update on overall bookings versus kind of your expectations in the quarter? I guess with all the moving parts, it's sort of hard to get a sense here. I've got one quick follow-up for Curtis.
Sure. With respect to the relationship between cloud and the tier 1, I would say tier 1 insurers are just as interested as any other segment in the market in disburdening themselves of some of the complexities of their core environments. Some tier 1 insurers are really an aggregation of multiple smaller businesses that work under one corporate umbrella. We think it's extremely likely, in fact, we're already seeing this happening, that some of those individual divisions who kind of think of themselves actually as smaller insurers, will be motivated to transition more quickly to the cloud for the same reasons that a completely standalone smaller insurer would be. Namely, that they just don't have the bandwidth to undertake all the different transformation programs that they want to do in data and analytics and Digital Engagement, et cetera.
The cloud delivery model becomes increasingly appealing to them. I think as we mature this model and as we have references to show for it, especially as we reduce total cost of ownership, I think we're going to see acceleration across all segments motivated by the cloud, including the tier 1. There was another portion to your question I just forgot.
Yeah, just around overall bookings in the quarter-
All right
in terms of how they came in versus what you expect.
As you know, we think of bookings very much on an annual cycle, which is also, I think, explains some of our reticence around bookings metrics because it's challenging enough to corral that on an annual basis and it's kind of daunting to think about doing so and reporting on it on a quarterly basis. That's some of the hesitation you hear from Curtis and me on that score. Specifically with respect to this year, on an annual basis, I think we feel really good about how things have gone. Across the board, across InsuranceSuite, InsuranceNow, the data products, the digital products, and the active conversations around the newer things we're doing, like Cyence and the Salesforce partnership which is a licensable addition to our product portfolio. It's the breadth as well as the quantitative aggregate of the demand that's been really encouraging.
That said, we have a lot of work ahead of us still in the remaining two months of the year. Sales execution will be extremely important if we're going to fulfill our commitments.
Got it. Thanks for that. Then maybe just quickly for Curtis, really appreciate the initial read for next year. I guess, just wondering on the services line, though, if you could, because it's such a big number for you guys, just wondering if there's any high-level commentary. I think the Street's in sort of a 20% growth number. Is that sort of a reasonable way of thinking about next year for now, or any other framework would be helpful? Thanks.
Yeah. We commented that the subscription growth level this year was unusually high. We expect that to begin coming back down to normal levels next year and in the coming years. That's part of the guidance that we provided around the services line. We'll be able to talk in more detail about that, too, in the Q4 call and in the analyst call as well.
Okay, got it. Thanks very much, guys.
Next, we'll hear from Rishi Jaluria with D.A. Davidson.
Hey, guys. Thanks for taking my question. I guess, Marcus, let's starting with you. As you look at the potential M&A landscape here, be it larger acquisitions like Cyence or smaller tech and technological acquisitions, I mean, no secret that we've seen some very elevated multiples in software and technology in general. Just wanted to kind of get your viewpoint on what you're seeing out there, how that sort of M&A pipeline looks, and how you're thinking about maybe valuation and where there's opportunities. Then I'll have a follow-up for Curtis.
Sure. Yeah, as you know, if you've followed us all the Insurtech phenomena over the last few years, it's certainly a very target-rich environment. Far more opportunities in early-stage technology companies than I would personally have ever imagined serving and even explicitly focusing exclusively on the P&C industry. It's an utterly different landscape than when the company was started some decade and a half ago. It's a very interesting vector of exploration for us that we had not put a lot of mind share towards in previous years. But now, through the very natural partnerships that we have for lots of analytics and digital offerings that naturally complement our transactional and operational platform in InsuranceSuite, as well as just our location here in Silicon Valley where the preponderance of the Insurtech phenomenon is happening.
kind of the, if it's modest to put it this way, our stature in the industry and the fact that we have so many prominent names in our customer community. All of these things help us be I think in an advantaged position for these conversations and allow us to be very patient in making the right choices and not overpaying to the degree that's possible in this environment. One individual on my team that's well known to most of the community on this call, Richard Hart, leads that whole evaluation and management of the pipeline. He's very busy with a lot of conversations, but he's also extremely disciplined about valuations, and I think that's served us very well so far in the deals that we've consummated to date.
Okay, thanks. That's helpful. Curtis, appreciate the color on next year and kind of helping us break down all the moving parts with subscription ASC 606. In terms of 606, I mean, I understand revenue impact's basically a wash. From an OpEx standpoint, should we expect some benefit from 606 on the OpEx side, which is maybe offset from increased subscription deals and higher services mix shifting a drag on gross margins?
Yeah. With more subscription, right? We guided preliminarily to a 40%-60% of new sales is subscription. That will have an adverse impact on gross margin and then operating margin. That's part of what we were factoring in when we provided the guidance around our operating margin, that we did not expect to see operating margin expansion in 2019. We noted some other things. Obviously, we continue to invest in the cloud and the cloud transition. We noted that some of the investments we made this year were to some extent backend loaded. We'll see the full-year impact of that in 2019 that we didn't necessarily see in 2018.
Those are some of the things that we preliminarily took a look at when we gave some guidance that we don't expect to see operating margin expansion in 2019 from sort of the guidance we've provided today for the full year.
Okay, thanks. Sorry, just to clarify. From just 606 alone, is there any benefit on the OpEx side from the adoption of 606, or is there no change there?
Modest.
Okay.
Potentially modest. Yep.
Okay, perfect. Thanks, guys.
We'll move on to Thomas Roderick with Stifel.
Hey, gentlemen, thanks for taking my question. Marcus, I wanted to just build on the earlier question about salesforce.com. Given that in your prepared remarks you highlighted the transformation journeys that a lot of your customers are undertaking to the cloud and really updating their offerings. We heard very similar remarks from Salesforce, which highlighted some very big deals in insurance just recently. If we think about what's driving some of these transformation journeys, particularly for your bigger customers, and thinking about sort of two choices that drive this. One sort of being inside out, starting with policy and claims and billing, sort of inward-facing functions, as opposed to outside in, the digital functions that face the consumer. Which of those two options are driving that? With respect to that, can you talk a little bit more about the integration points with Salesforce's FSC?
I think the motivations for core system replacement and undertaking digital transformation they're many and varied. They're also kind of consistent across companies. What I mean by that is there are lots of frustrations that can vary from organization to organization with the specific deficiencies of their specific frustrations they may have with their current system environment, i.e., they can't instantiate the product that they want to sell, or there's a limitation in their system environment that prevents them from selling in a particular market or adjusting their pricing with the frequency that they think they need to be competitive. Their customer engagement value proposition is eroding because the bar has been rising so much faster than they're able to keep up with.
The specifics of which concern is the most urgent will definitely vary, but it's a menu of maybe five to eight themes that we hear over and over again across our entire customer and prospect base that are strikingly similar, and they are very positively for us. They continue to grow in urgency. Where CRM fits into that is, I think, a recognition by insurers that they need to think about their policyholders not just as units of risk, which insurers are actually excellent at doing, modeling what financial exposure each customer might represent in underwriting carefully. Also as customers, as consumers, and who want to be catered to, who have life events, who have different preferences about how they want to be sold to and serviced, et cetera.
That need to have a much more customer-friendlier, omni-channel-like experience that the customers now expect from a retail or other financial services world has really come with conviction to the industry. That requires marrying two quite disparate domains, the very horizontal CRM and SFA-like functionalities that you have in a Salesforce, and then the transactional and operational platform that we have in InsuranceSuite which really need to intersect at the moment that you don't just want to look for information, but actually want to transact on either an existing customer or potentially a new customer. That transactional intersection is where our customers want us to build productized integrations between us and Salesforce. What we're doing is natively embedding Guidewire data entities and transactional flows into Salesforce Financial Services Cloud, so that natively in Salesforce screens, you are seeing Guidewire data.
We think that that'll be compelling to a very large segment of the industry, I should say. It requires some fairly heavy lifting at the product level so that it's a true native integration and not just punching out into different screens.
Makes perfect sense. That's a really helpful detail. Thank you. Curtis, follow-up question just around the numbers. Targeting now on the subscription side, sort of high end of the 30%-40% range for new sales for the year. Can you break out, and apologies if you've done this before, I don't think you have, but if we think about sort of the InsuranceSuite Cloud versus InsuranceNow, so the four to five high-end customers you hope to win on ISC as opposed to the myriad of tier 3 and lower customers that you might see on InsuranceNow, how should we think about the rough split that drives that high end of the 30%-40%? Maybe a better way to look at it is what's a typical average deal size for InsuranceSuite Cloud as opposed to InsuranceNow?
Just any direction you can give us on the split there would be really helpful. Thank you.
Yeah, thanks for the question, Tom. We haven't broken that out or provided detail around sort of where the segmentation around that 40%-50% among tiers or tier 1 to tier 4 or InsuranceNow versus other. That's not something we've historically talked to. It's something that we consider going forward as we continue to evaluate some of the different metrics that might be helpful for the investor community to better understand our progress in the cloud. That's one that we can consider when we start to prepare for our Analyst Day in September on our Q4 call.
I'll ask again in September. Perfect. Thank you.
Next, we'll hear from Brad Sills with Bank of America.
Hey, guys. Thanks for taking my question. One please on digital and data. Just if you could illustrate for us maybe some scenarios or use cases where customers have gone really deep there. What does the deployment look like over time? What are some of the scenarios that they're using digital and data for? Would the move to the cloud represent a potential catalyst for adoption of those offerings? Thanks so much.
Thanks for the question, Brad. You can think of digital as externalizing all of the data, all of the products, the pricing, the underwriting business logic, the transactional flows, everything that happens at the heart of the core systems that we build. Externalizing all of that to participants outside of the four walls of an insurer. Of course, you can extend that also to your own employees. The primary use cases are to the distribution channel, namely brokers and agents, that are still a hugely important part of how insurance is distributed. Also directly to policyholders, either for point of sale or equally importantly, for customer service, which can mean policy maintenance or it can mean claims.
What you're trying to do is enable a much more contemporary, potentially human involved process, but one that is as self-service and intuitive as possible to actually transact much more efficiently. Insurers have a sense of being behind the curve in delivering the kind of contemporary consumer-grade experience that people have been trained to expect from the likes of Amazon, Uber, et cetera. We divide our digital products into three families. Ones that support the distribution channel, which we call ProducerEngage, one for direct to consumer, the Policyholder Engage, and then one for vendor partners, such as body shops and others involved in the claims supply chain who have a need to interact with the insurance transactional flow. These are very broad in appeal, and we're experiencing a very high attach rate with them pretty much in all geographies and market segments.
On the data side, data is a huge frontier with many different dimensions to it. A portion of it is just managing the operational data and transactional data that's generated by the system and putting it into an operational data store that can be accessed by other enterprise systems. We call that product DataHub. There is a somewhat conventional Business Intelligence that naturally our customers want using that data. That's a product called InfoCenter. There's been mining that data for statistical predictive insight with a different set of machine learning-based tools that Guidewire Predictive Analytics that increasingly we are embedding directly in the screen flows of the core systems themselves. It's a principle that we call smart insurance.
There are other data horizons beyond that, namely what we're doing with Cyence, which is to incorporate for the first time data from outside the enterprise, that's generally out on the internet, and using it to essentially build a profile of potential insureds in advance of actually having them as customers or as insurers are making underwriting decisions. There's much more beyond that that we still aspire to. We think of data and digital not so much as products, but as product frontiers, where we can do a lot more with the current products we have as well as build a lot of new ones. Your question then second was about cloud, I think. Everything that we're building today, every major unit of functionality that we will be building going forward is cloud-based or cloud native, cloud only.
Multiple of the data products are only available in cloud form. We're in the process of transitioning all of our digital products as well to be cloud delivered. I think just as with the core itself, that we expect that will accelerate adoption.
That's great. Thanks, Marcus.
We have a follow-up question from Sterling Auty with JPMorgan.
Yeah. Thanks, guys. I just want to clarify a couple items. As we're all going to modify our models and set estimates, including for fiscal 2019, you mentioned that in respect to total revenue, expect growth to taper slightly in 2019. Against taper off as compared to what growth rate in 2018? Because you do have some acquisition related revenue with Cyence. I want to make sure we're all level set in thinking about which growth rate do we start with and then taper to come to the 2019 expectation?
Yeah. Thanks for the follow-up question, Sterling. The guidance growth rate that we provided in the call for the full year, and that's the one we're basing our 2019 growth rate off of, is the total revenue range that we provided, $647 million-$653 million. That's a 26%-27% growth rate over 2017. Includes all revenue in that number. What we talked about in terms of that high level sort of preliminary commentary on our total revenue growth rate for 2019, is we expected it to taper slightly off of that 26%-27% growth rate that we saw in 2018 over 2017. That's partly due to us seeing, as noted earlier, that services revenue growth begins to normalize. It was a sort of an accelerated level in 2018, and we see that coming back down in 2019.
All right. Perfect. That really helps. I want to take a step back. When you guys began the work, I know Curtis, this predates you, but I'm sure Richard kind of gave you the full download. As you started to work on 606, the discussion was going back to the customers. Customers typically, I think, had around a 5-year average first contract length. With 606, because of the high renewal rates, you go back and rework those deals. I thought the idea was to get them onto 1-year deals so that with the upfront recognition, you didn't end up with kind of a dramatic impact. When you talk about the 2-year term, did customers want to not go to 1 year? They wanted 2 year for some reason?
For new customers, if they choose term, are they also going with 2 year, or is there an option to go longer or even shorter with 1 year?
Yeah. We've made a lot of progress on modifying the existing customers' contracts to address this potential 606 issue. In many cases, though, it ends up being a 2-year term, and that's part of, I think, what we were evaluating when we were trying to assess the impact of 606 on our 2019 numbers. When we looked at that together with some of these other puts and takes we talked about, along with now what we're projecting to be our subscription as a % of new sales mix bumping up to 40%- 60%, we think overall the impact on 606 will be net neutral to license and other revenue.
That being said, we know there's still some work to do between now and the end of the quarter, and we intend to fine-tune our thinking around that and provide updates in more detail when we get to our Q4 call.
Last question, subscription, because we have several terms being thrown around here. We have subscription, we have term, we have cloud. Does subscription include all of the cloud licensing? Or maybe flipping it around, is there subscription revenue that is not cloud? If so, why does that get ratable treatment versus term?
There's a simple answer to that, Sterling. All subscription and cloud revenue are synonyms for us. All cloud revenue comes in subscription form, and there is no subscription revenue that is not cloud-based.
Perfect. Thank you, guys. I appreciate it.
Thank you.
That will conclude the question and answer session. I will now turn the call over to Mr. Marcus Ryu for any additional closing comments.
No additional comments. Thank you for all participating on our call today. Goodbye.
That does conclude today's conference call. Thank you for your participation. You may now disconnect.