Arteris, Inc. (AIP) on Q3 2021 Results - Earnings Call Transcript
Operator: Good morning everyone and welcome to the Arteris IP Third Quarter 2021 Earnings Call. For opening remarks and introductions, I will now turn the call over to Erica Mannion at Sapphire Investor Relations. Please go ahead.
Erica Mannion: Thank you and good morning. With me today from Arteris IP are Charlie Janac, Chief Executive Officer; and Nick Hawkins, Chief Financial Officer. Charlie will begin with a brief review of the business results for the third quarter ended September 30, 2021. Nick will then review the financial results for the third quarter followed by the company's outlook for the fourth quarter and full year of 2021. We will then open the call for questions. Please note that this call will include forward-looking statements that involve risks and uncertainties that could cause actual results to differ materially from management's current expectations. We encourage you to review the Safe Harbor statements contained in our press release for a more complete description. All material contained in the webcast is the soul property and copyright of Arteris IP with all rights reserved. Please note this presentation describes certain non-GAAP measures, including non-GAAP net loss and non-GAAP net loss per share, which are not measures prepared in accordance with U.S. GAAP. The non-GAAP measures are presented in this presentation as we believe that they provide investors with a means of evaluating and understanding how the company's management evaluates the company's operating performance. These non-GAAP measures should not be considered in isolation from, as substitutes for or superior to financial measures prepared in accordance with U.S. GAAP. Listeners who do not have a copy of the quarter ended September 30, 2021 press release may obtain a copy by visiting the Investor Relations section of the company's website. Now I'd like to turn the call over to Charlie.
Charlie Janac: Thank you Erica and thanks everyone for joining us on the call this afternoon. We are excited to report our first quarter as a public company. I want to extend special thanks to the Arteris IP team for their hard work and support during the IPO process. We are excited about this next step in our company's journey notably since our Arteris IP is the first pure-play semiconductor IP company to go public on a major USA stock exchange in 19 years. I'll start this afternoon with a few highlights from the quarter, and then, because it is our first earnings call, I want to take some time to discuss our business and market opportunity as many of you may be new to the Arteris IP story. We reported a strong third quarter with GAAP revenue of $9 million, up 39% year-over-year. Demonstrating our continuing momentum through the end of third quarter 2021, we have added 28 new system IP customers marking the highest number of new customer additions in a nine month period in company history. In the third quarter alone, the total number of active customers increased from 166 to 179 with new customer applications ranging from automotive to machine learning to consumer, 5G wireless and data center SoCs with the highest number of customers creating new machine learning SoCs. This included two major automotive design wins for leading edge SoC projects, including one with BMW. We believe that our products are utilized in 70% to 80% of all automotive ADAS SoC projects. Geographically, the largest licensing regions for the quarter were EMEA followed by China and then closely followed by USA. There were 22 customer design starts in the third quarter, continuing the strong trend and taking a total of nine months ended September 30th to 65, our highest ever number in the nine month period. We saw strong performance in the third quarter across all of our system IP application market segments with notable new license contracts in machine learning and automotive. In addition, we were especially encouraged by the acceleration of automotive royalties as car electrification and automated driving deployment continues to expand. We have made good progress on the integration of Magillem following the acquisition November 2020 and are encouraged by the high renewal rates from our IP deployment software customers. Looking forward we believe our market opportunity remains very attractive on a sustained basis. For those of you who are new to the story, let me tell you a little bit more about Arteris IP. We are a leading provider of semiconductor system IP that enables our customers to deliver increasingly complex SoCs that not only process data, but also able to make decisions. The growth in a number of connected on-chip IP blocks and subsystems places an increasing premium on the interconnect IPs capability to move data inside complex SoCs, as well as our IP deployment technologies' ability to automate important aspects of the SoC creation design flow. We believe this increase in SoC complexity is creating significant opportunity for growth of our sophisticated system IP solutions. Founded in 2003, we have pioneered and emerged as a global leader in the development of interconnect IP technology for on-chip communication that address the complexity, performance and cost requirements of advanced SoC semiconductors. Traditional on-chip communication methods, such as hybrid buses are generally inadequate in handling communications within advanced semiconductors for sophisticated applications. We leveraged our extensive technological expertise to develop a new method for on-chip communications to address these critical semiconductor development challenges. This method is called network-on-chip, or NoC interconnect. By pioneering the use of proprietary networking techniques to remove the inherent architectural limitations of traditional on-chip communications to improve ease of integration, performance, silicon area, and power consumption, we help our customers to achieve their design goals faster, easier and at lower R&D and SoC unit costs. We're also a leading provider of IP deployment software, which enables our customers to more efficiently deploy the internally developed and commercially licensed semiconductor IP block libraries to accelerate creation of SoC type semiconductors. Our IP deployment solutions compliment our interconnect IP solutions by helping to automate not only the customer configuration of interconnect IPs, but also the process of integrating and assembling all of the customers' IP blocks into an SoC. Products incorporating our IP are used to carry critical data inside complex SoCs for sophisticated applications, including automated driving, artificial intelligence, machine learning, 5G and wireless communications, data centers and consumer electronics among other applications. IP deployment software together with our NoC interconnect IP and several NoC interface IPs that improve SoC data flow performance make up the system IP market segment. We work directly with our customers throughout the SoC development process and seek to develop long-term sustainable relationships with them as our technology becomes embedded in their products and processes. We also leverage our long history in interconnect IP design and are able to serve a broad range of applications and deliver customer specific features that are useful to other customers. For example, in the third quarter, we announced Aeva Technologies, an innovator in four dimensional LiDAR as our 200th customer in our Arteris IP history and via a leader in innovative automotive radar systems. The 200th customer milestone quickly follows the company's announcement of its 150th customer in November 2020 and is 100th customer in 2018, reflecting Arteris rapid growth as semiconductor design teams license the company's technologies to speed development and increase performance of SoCs. Specific to Aeva, they chose Arteris IP on-chip interconnect technology as part of their proprietary digital processing chip because our technology complements Aeva's high standards for functional safety. In addition, the Arteris IP interconnect technology increases digital processing chip performance by optimizing on-chip communications for high bandwidth and low latency data flows including state-of-the-art quality of service or QoS techniques. Within the artificial intelligence machine learning market in the third quarter, we also announced that the imaging of SoC leader, Eyenix license FlexNoC interconnect IP for its next generation image processing SoC. Eyenix chose Arteris IP on-chip interconnect technology as part of their proprietary image processing chip, because it enables them to design and integrate a complete and superior imaging solution without dependency on external IP blocks for the machine learning function. In addition, the Arteris IP interconnect increases image processing chip performance by optimizing on-chip communication for high bandwidth and low latency data flows using state-of-the-art quality of service techniques. Our technology also provides opportunities for our customers to reduce power consumption in battery operated applications. To ensure we stay at the forefront of technology innovation for these and other opportunities, we intend to continue ramping up our investments in the next generation product offering. As an example of this, we recently announced the launch of Arteris' Harmony Trace Design Data Intelligence Solution to ease compliance with semiconductor industry functional safety and quality standards. For design teams with functional safety requirements or creating complex SoCs or systems, Arteris Harmony Trace increase its system quality and the ability to achieve functional safety certification by creating and maintaining traceability between disparate systems for requirements, specification, hardware design, software code, test and documentation, so that engineers will know immediately when a change occurs and the effect of that change on other design artifacts and part of the system. The development of Harmony Trace was driven by our customers’ needs to establish an automated traceability flow and implement change management best practices between their existing requirements, specification, their electronic design automation tool suite, their code – software code repository and document tools. Harmony Trace allows our customers to use their existing tools and automatically link data between them due to Harmony Trace’s unique semiconductor industry specific semantic computing technology. As we look at the multitude of both captive and greenfield system IP opportunities in the market, we estimate that our TAM will expand to an estimated 3.2 billion in 2026 or 1.1 billion in 2020, driven by an increasing number of SoC design wins and growing complexity, increasing average selling prices of interconnect IP and IP deployment software, and are moved deeper into the knock interface IP market. More specifically, we believe our growth will be driven by technology trends requiring more sophisticated on chip processing in automotive machine learning, 5G and wireless communications data center and consumer electronic markets. Also the need for sophisticated system IP products is growing rapidly in order to address the requirements of smaller die size, lower power consumption and higher operation frequencies, as well as management of critical net latencies in a timely and cost effective manner. There are also structural growth factors such as regionalization of the semiconductor industry, more system houses building their own custom or partner customized silicon and lengthening of the semiconductor supply chain, which favors our IP deployment software. As a result, we believe these strengths have led to an increased economic benefit of in-licensing of system IP. And in fact, all commercial semiconductor IP. This is an exciting time to be at Arteris IP. Looking ahead, we recognize that our IPO is just one step on the journey of our company. While we are excited to have achieved this milestone, we have much more to do. We look forward to continuing our momentum in the years ahead and updating all of you in the quarters to come. With that, I'll turn it over to Nick to discuss our financial results in more detail.
Nick Hawkins: Thank you, Charlie, and good afternoon, everyone. As I review our third quarter results today, please note that I'll be referring to non-GAAP metrics. A reconciliation of GAAP to non-GAAP metrics is included in today's earnings release, which is available on our website. Given this is our first call as a public company, I want to start by sharing some perspectives about our business model and financial profile. Then I'll walk through financial highlights for the third quarter, and finally, I'll close with guidance for the fourth quarter and the full year before we open up the call for questions. Our revenues derived from licensing – intellectual property, licensing software, support and maintenance service, professional services, training services and loyalties. Our interconnect IP solutions include software licenses, services, software updates, and technical support. We enter into licensing agreements with customers that typically range from two to three years and generally consist of delivery of a design license that grants the customer, the right to use the IP license to design a contractually defined number of products and stand-ready support services that provides a customer with our application engineer support services. While revenue derived from our interconnect IP license agreements is typically recognized ratably over the duration of the license agreement. Customers typically pay fees either shortly after signing their agreements with us or at the start of each year following the design license term allowing our cash flow to run ahead of revenue recognition. In conjunction with our interconnect IP licensing agreements when products incorporating our IP are sold, we generate royalty revenue. Royalty revenues are recognized during the quarter, which customer shipments occur. And it calculated either as a percentage of customer chip RISC-V, or on a per unit basis as specified in a license agreement. Our deployment solutions include software licenses, software updates, and technical support. The software licenses are time-based licenses with terms generally ranging for one to three years. Revenue allocated the software licenses generally recognized at a point in time upon the later of the delivery date or the beginning of the license period or on a token basis. And revenue allocated to support services is recognized ratably over the support term. Given the variation in revenue recognition methodologies between our product offerings, as a management team, we focus on annual contract value or ACV as a leading indicator of financial performance. We define ACV for an individual customer agreement as the total fixed fees under the agreement also referred to as the total contract value or TCV divided by the number of years in the agreement term. As this calculation does not include the contributions from royalty payments, we also refer to ACV plus trailing 12-month royalties as a metric, which provides a more complete picture of our total revenue proxy. We monitor this metric to measure our success and believe that the historical increase shows our progress in expanding our customer's adoption of our platform. Moving on to our quarterly results, ACV plus trailing 12-month royalties and other revenue as of September 30 was $45.6 million, up 21% year-over-year on a pro forma basis including margin driven in particular by growth in automotive and machine learning applications and up 4% quarter-over-quarter. Total revenue for the third quarter was $9.0 million, up 39% year-over-year, while remaining performance obligations or RPO were at $50.6 million, up 48% year-over-year. Gross profit in the quarter was $8.1 million, representing a gross margin of 90% compared to $6.2 million in the year ago period. The high gross profit for the quarter was primarily attributed to the increase in licensing and support revenue partially offset by royalty revenues from the significant reduction of shipments from our customer HiSilicon. R&D expense for the third quarter was $7.6 million or 85% of revenue compared to 62% in the year ago period. The increase was driven by additional development costs and then additional head count and payroll expenses. We continue to invest in new and improved product offerings. Sales and marketing expense for the third quarter was $3.2 million or 36% of revenue roughly in line with the year ago period. We intend to continue to invest in sales and marketing as we continue to drive awareness in the market and expand our sales and application engineering forces and marketing efforts to capture the significant opportunity in front of us. G&A expense for the third quarter was $1.7 million or 19% of revenue compared to 40% in the year ago period. G&A reflects an increase in people and infrastructure related expenses associated with our public company ready efforts offset by a reduction in professional fees associated with our IPO. GAAP operating loss for the third quarter was $4.5 million or 50% of revenue increasing from a loss of $2.6 million or 41% of revenue in the year ago period. Non GAAP operating loss was $4.0 million or 44% of revenue increasing from a loss of $2.4 million or 37% of revenue in the year ago period. GAAP net loss in the quarter was $5.0 million or net loss per share of $0.24. Non-GAAP net loss for the quarter was $4.4 million or net loss per share of $0.21 based on approximately 20.6 million weighted average diluted shares outstanding. Turning to the balance sheet and the cash flow. We ended the quarter with $11.2 million in cash. Cash flow for operations was a usage of $2.5 million in the quarter, while free cash includes capital expenditure was a usage of $2.6 million. Subsequent to the quarter end, we closed our initial public offering resulting in net proceeds of $71.1 million. I would now like to turn to our outlook for the fourth quarter and the full year 2021. For the fourth quarter, we expect ACV plus trailing 12-month royalties of $48.5 million to $50.0 million and revenue of $10.0 million to $11.1 million with non GAAP operating gross margin of 32% to 54% and non GAAP free cash flow margin of negative 37% to negative 52%. For the full year, we expect revenue of $36.3 million to $37.5 million with non GAAP operating gross margin of 40% to 50%. And non-GAAP free cash flow margin of negative 20% to negative 35%. With that, I would like to open up the call to questions. Operator?
Operator: Our first question is from Mark Lipacis with Jefferies. Please proceed with your question.
Mark Lipacis: Hi. Thanks for taking my question and congrats on the first quarter out of the blocks here. I had a couple of questions. Charlie, maybe for you, could you talk about the process of you undergo for adding new customers? What do you have to do to convince them? How long does it take to convert somebody who's never used your IP before? And has – as becoming a public company, has it helped that process?
Charlie Janac: Yes, I think, it has definitely helped. One of the reasons for going public was to reassure the market that we are going to be a long-term sustainable company and then we were not interested in being bought, right. So the market was really afraid that we were going to go away the way some of the other competitors that we had due to acquisition. So that helped a lot. In terms of the process, it's actually shortening, I would say. So usually you go through the usual demonstration, evaluation and then basically a license negotiation and then closure. And that typically takes, I would say, there is a range on that, right. But I would say four to five months is a typical cycle with sort of the outliers being as short as a couple of weeks in one of the few cases we just laugh about it it's taken 10 years. So – but I would say four to five months is what that process takes and the IPO has definitely helped.
Mark Lipacis: Got you. That's helpful. And once you win a customer would you break in and you have a successful program there. Would you expect the customer to embrace your technology broadly for other projects? And I guess maybe another way to ask the question is, you've articulated the benefits of using your IP as time to market, lower cost, lower risk. Are there other benefits for the company to reuse your IP, to reuse it once, they've used it once for, I don't know, maybe continuity of their own product portfolio? Thank you.
Charlie Janac: Yes, I mean, Mark, this is a sticky technology, right. So once you break in and once you're successful, the customer has a track record of reusing the technology on subsequent projects. We have some restrictions about what we can disclose, but one of the customers that allow us to disclose this is essentially Mobileye where we've been essentially in five generations of projects of spanning 11 years, rights. So those are – we aim to foster those kinds of relationships. And for us the initial license deal is really presales for the next deals. What we typically see is that we get used on the complex projects where the customer has some – traditionally some difficulties with alternative technologies. And then as they realize how productive our products are and our methodology is, then they expand it to their less complex products in order to get the acceleration of essentially SoC generation across the entire portfolio. So, yes, we have to be very, very careful not just to have great high quality products, but also to have very strong customer support that makes it easy for the customer to use us on subsequent projects.
Mark Lipacis: Got you. Very helpful. I'll go back into the queue. Thank.
Operator: Our next question is from Matt Ramsay with Cowen. Please proceed with your question.
Matt Ramsay: Yes. Thank you very much. Good afternoon everybody. Guys congratulations on the first quarter out of the gate and congrats Charlie for getting through that script without fluffing your lines at all. That's quite an accomplishment. My first question is sort of a bigger picture one and the way that my team is sort of characterized the opportunity in front of our Arteris in the automotive market and in the AI machine learning market is a comparison back to 2009 through 2011, when a whole bunch of companies that were designing chips for mobile phones, we're faced with this smartphone inflection and needed to then design SoCs and needed on-chip interconnect to do that. And that was sort of the first phase of Arteris the company and the big inflection. And where we're at now is it seems like in the automotive industry a bunch of companies that are designing microcontrollers need to design SoCs and some of the auto companies themselves are designing chips for the first time. And in the AI market, you either have big cloud companies that are starting up chip design projects internally, or you have new start-ups in AI that all of those companies don't have been interconnect teams. And am I articulating the inflections that are driving opportunities for your company correctly? And maybe Charlie if you comment on that a little bit, I'd appreciate it. Thanks.
Charlie Janac: Yes. I mean, the smartphone SoC inflection was that you had architectures there are many to many communication, right, instead of the simpler ones where you had many initiators to a single target, which was the memory. The inflection point we're dealing with now is that these chips are allowed not to just process data, but they're actually allowed to make decisions. And that requires a much greater data traffic complexity. So those kinds of chips use much larger number of system IP products. They are more complex to design. So you essentially have to use productivity and automation to fight the growing complexity. So the current inflection is that these SoCs are making decisions and that's driving our business both today and in the future. And basically, the car is – one way to characterize the car of today and the near future is basically a power constrained server on wheels, right. And so the mechanics are becoming less important and the software and electronics are becoming more important. And that's essentially driving the industry to put more and more SoCs inside the car, including SoCs that are able to make some decisions.
Matt Ramsay: Got it. So that makes a lot of sense. As my follow up question, I'd be remiss if I didn't ask about BMW since you brought it up in the prepared script. If you could give us some sort of characterization of that customer now that you're talking about the design wins that you have is this for one chip or one program that they're doing? Was it – or is it broader than that? Is it something that was led by the NoC IP? Or maybe the design services parts of your business? If you could characterize the scope of that engagement, that would be helpful. Thank you.
Charlie Janac: Yes. So we actually – to follow up on sort of Mark's question, we typically do break in on one project, right, initially. So this definitely is one project. We're not allowed to say what it's for except to say that it's for a car. But the bigger picture here is that the car companies have lost control of their architectures, right. They were relying on tier ones to give them subsystems, which they assembled. And technologically, those subsystems really haven't changed a whole lot in decades, at least, they've been improved, but structurally they really haven't changed. Now the architecture of the entire car is being revolutionized partially forced by Tesla. And so the car companies are now in a fairly aggressive mode in getting back the control of the architecture of the car. So I don't think BMW is unique in that. Many of the ridesharing companies and many of the car companies are going to get involved either in building IPs, building at least defining the architectures together with semiconductor partners, so they can get customized chips for their software architectures, or in some cases they will build SoCs themselves. And so, this again is something new and something of an inflection point. And BMW is just one example that – that where BMW was kind enough to allow us to say who they are but they are others.
Matt Ramsay: Got it. Very clear. Thank you very much. Congrats on the early success. I'll jump back in the queue.
Operator: Our next question is from Hans Mosesmann with Rosenblatt Securities. Please proceed with your question.
Hans Mosesmann: Thanks and I also echo Matt's commentary about congratulations and a good job at the intro. Just to clarification Charlie, the BNW engagement. This is your first engagement with BMW.
Charlie Janac: Yes.
Hans Mosesmann: Okay. Congrats there. Just a high level question regarding renewals and – in terms of the outlook is that – still at a high level with part of the outlook for the quarter and years reengagement with your licensing customers?
Charlie Janac: So I think, it varies a bit by quarter by quarter, but generally I would say that about 70% of our business certainly of the licensing revenue is renewals and about 30% – maybe low 30% comes from new customers, so 70% is reorders.
Hans Mosesmann: Okay. And then lastly and about the opportunity here in terms of ASP expansion per license, what are the trends there all in? How much can you get from a customer if they license everything? Thanks.
Charlie Janac: Yes, so our ASP has been going up throughout the history of the company and it doesn't come from raising prices of each individual product. What it comes from is the fact that the SoCs need more system IP functionality, right. So you wind up the current SoCs needing cash coherency as well as a non-coherent interconnect. They have machine learning sections. So machine learning traffic is its own class. So it needs a machine learning interconnect. There is resilience. There is physical awareness because you want to take physical – I'm sorry resilience for functional safety for mission critical SoCs physical awareness, because now you need to take into account physical constrains upfront. You have to decide which data traffic stays on-chip and which goes off-chip. So you have a last level cash called quota cash. And you have all of the IPD software, which allows you to package all of your other IPs in the SoC. So, if you're going to buy all that from us today, it's going to be – per project it's going to be somewhere around $1 million where in the – on the average, we're probably somewhere around low 400,000s per SoC. And it will go up more in the future because you're going to have chiplets and other types of functionalities that will make the data traffic patterns even more complex.
Hans Mosesmann: Great. Great for the run rundown, Charlie. Again congratulations for the team.
Charlie Janac: Thanks, Hans.
Operator: Our next question is from Gus Richard with Northland. Please proceed with your question.
Gus Richard: Yes. Thanks for taking my questions and congratulations guys. Great job. Charlie, can you talk a little bit about where your incremental customers are coming from? Are they semiconductor companies? Or is it expanding into non-traditional system houses, cloud houses, et cetera?
Charlie Janac: Yes. So, obviously, there are a lot of system houses now starting to do SoCs and some of that is done with partners, so they're partnering with the traditional semiconductor companies to give them not custom chips, but customized chips based on existing platforms, but modified with a few additional IPs for their own particular requirements. And you also have a tremendous growth in start-ups in China. So, those are the two things. The system houses are starting to build chips and there is a lot of start-ups in – semiconductor start-ups in China. And also some of the major semiconductor companies are now starting to have issues with their own internally developed system IP. So we think that also provides an additional growth potential for our products. So those are the two things.
Gus Richard: All right. Yes, so that leads me to the second question. Basically, some companies have issues with the design for reuse and a shortage of integration, SoC integration engineers. Can you talk about sort of how you help alleviate those problems and incremental increases in productivity, and then how does that map into IP-XACT and how will that help accelerate designs to market?
Charlie Janac: Yes, so, there's two things here. One is the interconnect and one is the IP deployment software, even though ultimately they're extremely synergistic. So before Arteris, it took tens of days to build an interconnect. Maybe if you were particularly good at it, it could take even months, but it took tens of days even for the good guys. With Arteris, the really effective teams can build interconnect in days, right. And so that's a major productivity increase, which is one of the reasons why Arteris has grown so well. But as you say, there is a tremendous shortage of interconnect engineers and even semi – experienced semiconductor engineers. So what we need to do is we need to cut down the generation of interconnect to ours, right? And that’s something that we need to be working on. The other thing is what I call this intermediation of the supply – semiconductor supply chain. Some of these new entrants only do portions of the design cycle. They’re not IDMs, right? So they built couple IPs and they buy the rest. And so they have a fairly long, they may do use layout contractors, packaging houses, and so on and so forth. So they have a long chain of contractors or long supply chain. And the issue for them is how do you get it all to work when it comes back? All the stuff that you’ve bought in your license comes back and you need to turn into an SoC. And so you need a standard that is essentially allows you to package all of that stuff into a form that is easily integratable and IP-XACT is a very good way of doing that, right? It allows you to build an integration model around the IP without worrying necessarily about what’s inside the IP. It allows you to configure the registers, the exit boards. It allows you to manage high level connectivity. And so you have a much more, much better chance of taking all that stuff that’s coming back to you from all these suppliers and turning that into a working SoC quickly, efficiently, and at lower cost and lower risk. And so we’re involved in both those areas. And one of the things that we find is that the IP-XACT tools are actually making our interconnect IP subsystems easier to integrate in their SoCs. So we’re actually in some sense eating our own dog food. And it turns out that the two things are quite synergistic.
Gus Richard: Got it, very helpful. If I can speak in a third, I apologize. As we’re going to system and package, heterogeneous integration, as SoCs disintegrate a little bit into separate dye, how does that impact your business?
Charlie Janac: It makes it more valuable. It makes it more complex and we thrive on essentially allowing customers to manage the complexity. So think about it just, just as an example of the Ncore Cache Coherent Interconnect, right? The reason you need cash coherency is that you need to have smaller multiple cores that aren’t so quite so power hungry and generate so much heat and those kinds of things. But the software programmers are not trained in schools to worry about hardware. And I know this from my oldest son who’s a computer science guy and he was aghast at what it takes to manage hardware. So we need to handle that for the software teams. And so we came up with cash coherency, which essentially allows multiple processors to look like a single programming space. Now, what people want is to make multiple dyes look like a single programming space, and this is obviously a more complex and more expensive and more profitable problem. Right. And so the chiplets is a technology that is here to stay. It’s still not deployed by a huge numbers of people except on the leading edge, but it makes the interconnect much more complicated and much more sophisticated yet again.
Gus Richard: Got it. Thanks. Thanks so much. I’ll jump back in the queue.
Operator: Our next question is from Ambrish Srivastava from BMO. Please proceed with your question.
Ambrish Srivastava: Hi, thank you. I don’t want a Nick feel too left out, right out of the gate, Nick, pretty solid keeping the numbers tight, maybe as we learn the business model and the quarterly ebbs and flow. Can you just please frame for us visibility with respect to the KPIs? So if you look at ACV plus the LTM, RPO, deferred revenue that would be very helpful. And I did have a question for Charlie while you catch your breadth.
Nick Hawkins: Well, I’m delighted that you decided to give me a chance to shine Ambrish. So thank you for that. So yes, in terms of visibility, we have – I think from our previous conversations, we have a fairly strong and visible pipeline from whether you look at ACM and TTM royalties or you look at revenue. The one element of revenue that is not so 100% predictable is our IPD revenue because most of that is point in time upfront. So if you look at it from quarter-to-quarter it can fluctuate. But in long term, because we have a very high proportion of repeat customers. So the – what Charlie was talking about just to make it clear was that of our revenue, 70% of that rather booking 70% of that comes from previous customers, existing customers, and the other 30% from new roughly, the 70% that’s preexisting customers run on a 98% retention rate. So in other words, 98% of our customers come back. So even if there’s a point in time rev rec for an IPD customer, it might appear sort of in Q1, or it might appear in Q2 depending on when the customer decides to place that repeat order. The benefit of having ratable revenue recognition on pretty much all of our SIP, our interconnect revenue and or all contracts. And some of our IPD contract is that once that goes into the pipe into the waterfall essentially we can see for the next two, three, four years, how that’s going to play out into revenue and the same is true you mentioned ACV. The same is true seems true with ACV is again, waterfall of all current contracts. So if we have a contract, that’s a say a three -year contract, which is not unusual. Then that gets basically divided up into 36 months. And it goes on at 136 of that – sorry, one – which was annual 112 of that. So a year’s worth, so a three-year contract would 300,000 would be a 100,000 of ACV. And that would go on the day the contract signed and it would come off three years later. And so we can predict with a fair degree of clarity, which is why you don’t see a great deal of variation on these numbers from where we originally taught you, because we do have this incredibly visible pipeline. And we do also on operating expense of course because we can control that quite carefully. Does that kind of answer your question?
Ambrish Srivastava: Yes, yes. It does. It does. And it helps to certify what we’ve been talking about in the past. Thank you for that. And Charlie, on the – turning to you on the design chart, what are the areas that these are in, and then how would you characterize the and you gave us some good comparisons from a year ago for some other metrics, but how are the starts changing vis-à-vis end markets from a year ago, couple years ago. And then where do you see that going? I’m assuming it’s going to be more automotive SoC AI machine learning, but then it would be helpful to see what the comparisons were from a couple of years ago. Thank you.
Charlie Janac: Yes. So yes, I mean, the hot market I know a couple years ago, but a bunch of years ago was smartphone, right? So that was majority of the designs came there as that market consolidated the volume stayed the same, but the number of or they grew, but the number of designs and the number of companies have shrunk, right Now, it’s expanding a little bit with 5G, because 5G is going to be used for machine-to-machine communication. So, that part of it is expanding yet again, but the kind of the first, IoT market that actually works from a business point of view, and this is just my opinion is the automotive market. The car is really an IoT device. It’s – this whole huge multi-billion dollar investment is essentially turning the car from a mechanical device to a device that’s full time attached to the cloud. That’s attached to the electronic road infrastructure, which is going to emerge and the cars are also going to communicate to each other. Right? So, the car is really a very complex and actually the initial IoT device. It’s a very, very nice business and consequently everybody is piling into automotive, right? So the number of customers or that are potential automotive customers is just increasing because there’s such to growth in the number of chips that are going to be inside the car. But the biggest market is machine learning, right? And so some of the car chips are machine learning chips. The eight as chips are machine learning chips, but a machine learning is going to be everywhere and it’s going to be used for making this relatively complex system functionality to be more user friendly, right. That the machine is going to figure out how to operate itself in certain cases. So the largest number of designs in a future are going to be machine learning. However from our experience so far, I think we, Nick would say that we only probably have only ignoring the automotive guys, only one non automotive machine learning customer paying royalties, right? So the volumes of that market haven’t really restarted yet. And – but yet that is what is the future market? And then there’s a lot of other companies, there’s servers, there’s consumer devices. So we’ll take all of that. But the focus for us right now is really on automotive, machine learning and 5G from a product development point of view and feature development point of view.
Ambrish Srivastava: Got it. Got it. Thank you. And good luck.
Operator: Our next question is from Mark Lipacis with Jefferies. Please proceed with your question.
Mark Lipacis: Hi, thanks for working me back into the queue. Quick question here, one and it’s a follow up on the ASP question before. As you look at your projection for your own internal projections for ASP improvement over time, to what extent is that predicated that ASP expansion predicated on new IP that you haven’t develop at versus IP that you have already developed. And you’re just waiting for the customers to reach for it. Thank you. That’s all I had.
Charlie Janac: Well, that’s a good question and not completely easy to answer quantitatively. So clearly the products that we have the customer spend on those products is increasing, right? So there’s more cash coherent chips, there’s more machine learning chips, there’s more automotive chips. So those require more of the products that we already have. Right. But there’s also other things that need to be developed. And so, our strategy has been to not shortchange R&D spending. And so we are putting out a new product every year. That’s the goal is one new major product every year and as well three releases, two to three releases of every major product that we have that are sort of customer enhancement releases. And so we’re trying to keep pace with this market because we’re basically doing R&D for 10% of the chip, right? The interconnect is about 10% of the silicon area, roughly maybe a little bit more, depending on what functionality you put on. So we need to keep pace with this. And so we are going to be delivering new products continuously. And so I don’t know also was to take a guess maybe I would say half the growth would come from maybe 40% of the growth will come from the products that we have, and maybe 50% to 60% will come up from products that haven’t been developed yet. And one of the advantages Arteris has is because we see so many designs by so many customers. We have a fast rate of learning, there almost anyone, because we can synthesize the customer requirements of what they’re going to need from a much bigger sample base than for example, any internal group, right? So we are going to be continuously delivering at least one product a year for the foreseeable future, because that’s what the market can absorb and that’s what the market requires.
Mark Lipacis: Got it. Very helpful. Thank you, Charlie.
Operator: We have reached the end of the question-and-answer session. And I will now turn the call over to Charlie Janac for closing remarks.
Charlie Janac: Yes. So I would very much like to thank everyone on the call today. It’s been pleasure working with you and a pleasure for and also thank you for your interest in Arteris. And also before we close, I would like to acknowledge my thanks to our employees for their continued dedication and diligent work and to our shareholders for their support. And so we look forward to updating you in the future, and we like to have a pleasant afternoon and evening, depending where you are and thank you for your support of Arteris.
Operator: This concludes today’s conference, and you may disconnect your lines at this time. Thank you for your participation.
