Home / Transcripts / QuickLogic Corporation (QUIK) · August 11, 2026

QuickLogic Corporation (QUIK) Earnings Call Transcript

August 11, 2026

NASDAQ US Information Technology Semiconductors and Semiconductor Equipment earnings 46 min

Earnings Call Speaker Segments

Alison Ziegler executive
#1

Thanks, operator, and I appreciate everyone being here with us. Joining us on the call are Brian Faith, our President and Chief Executive Officer, along with Elias Nader, our Senior Vice President and Chief Financial Officer. Before we go further, I want to remind everyone that a number of the things QuickLogic says on this call constitute forward-looking statements, and those carry risks and uncertainties. This covers things like — but isn't restricted to — what we project for profits down the road, how much revenue will grow and what cash flows will look like, our expectations for how the business will perform ahead, plus remarks regarding schedules, milestones and payments connected to our government contracts. It also takes in statements about contracts we anticipate winning and the size we think those deals will reach, along with statements concerning expected adoption rates and/or orders coming from our customers. Several things might lead actual outcomes to differ, including lagging market uptake of the company's newly launched offerings, the capacity to turn design prospects into customer sales, our capability to offset revenue lost as products reach end of life, how much design work customers undertake and when, whether the market embraces our customers' goods, the chance that fresh orders won't translate into later sales, our capacity to launch and manufacture new items built on advanced wafer technology promptly, our capacity to properly promote the low power, competitive pricing, and fast time to market of our new offerings, and fierce rivalry from competitors. The following factors could affect us: our capacity to bring on board and keep skilled staff; shifts in what customers want or what suppliers can provide; the overall state of the economy; developments on the political front; disagreements over international trade; natural catastrophes and other disruptions to business operations that might interfere with getting the company's products to market, meeting demand for them, or both; plus adjustments to tax rates and the possibility of owing more in taxes. If you'd like a fuller picture of the risks, uncertainties, and assumptions behind these potential differences, please refer to the risk factors covered in the periodic reports QuickLogic has filed most recently with the SEC. QuickLogic assumes no duty to revise any forward-looking statements or information, each of which speaks only as of its respective date, whether because of new information or later events. During this call, we'll share figures that aren't based on GAAP. If you'd like a full reconciliation between our GAAP and non-GAAP numbers, along with the rest of our financial statements, that's available in the earnings release we put out today. We've also added a fresh financial table to our IR page online, which lays out both current and historical non-GAAP figures. One thing to keep in mind: QuickLogic treats its website, the company blog, corporate X account, Facebook page, and LinkedIn page as ways to get information out about its business. That information could count as material, and QuickLogic might rely on those channels to meet its disclosure duties under Regulation FD. The script we read from during this session will be uploaded to the investor relations section of QuickLogic's site soon after the earnings call wraps up today. At this point, I'll hand things over to Brian Faith. Please proceed.

Brian Faith executive
#2

Thanks, Alison Ziegler. Hello, everyone, and I appreciate all of you being here for our Q2 2026 earnings call. Since we last spoke on a call like this, we've moved considerably closer to the objectives we set for 2026, and we've tightened our outlook for growth across the full year to somewhere between 70% and 80%. Given that expected expansion, our modeling still points to non-GAAP profitability as well as cash flow positive operations during the back half of 2026. Beyond what Storefront and RadPro bring in, we expect second half growth to come partly from fresh customers and additional market sectors, such as automotive, robotics, and commercial satellite applications. On top of that, we see solid potential to secure an eFPGA IP architectural license toward the end of this year. To put it simply, QuickLogic is on track for a highly successful 2026, and what we've achieved is putting us in a strong position to keep up our momentum in growth and market penetration through 2027 and afterward. Before I explain what has boosted our confidence in revenue growth for the full year 2026, let's briefly discuss what held Q2 back and why our Q3 guidance is for revenue that's flat. We had expected to wrap up a seven-figure extension to a contract with an existing customer toward the end of Q2. That extension's revenue was projected to be recognized across Q2 and Q3. The customer is still deciding which capabilities should go into the embedded FPGA and which ones will be fixed within the hardwired section of its ASIC before it locks in the design, and that has pushed back this contract extension. Because of that postponement alone, our Q2 revenue landed at the bottom of the guidance range, and for Q3 we're projecting no growth. We still expect to lock in this contract extension, yet the slip means it no longer appears in our 2026 forecast. Beyond that postponed extension, we are also taking a commercial ASIC design aimed at Intel 18A out of our second-half 2026 forecast. A few unknowns about this design have come up lately, and if things go as well as possible, the eFPGA hard IP contract tied to this ASIC won't be an opportunity until 2027. Those two shifts mean we're projecting Q3 revenue to stay level, but the contracts and orders already booked, along with the strides we're making elsewhere, give us enough confidence to lift the bottom end of our guidance for the full year. Driving the Q4 growth we expect is the work we continue to do under our contract with the U.S. government, whose ceiling was raised last year to $89 million in total value. We expect that this contract's revenue recognition will make up a sizable portion of Q4's total revenue. On top of that, we have a solid foundation from mature product business, steady interest in RadPro Dev Kits, and existing IP contracts already booked for Q4. Since the last conference call, orders for our RadPro Dev Kit have kept coming in and kept being delivered. We think this trend will persist, and with several evaluations underway right now, we're quite optimistic that initial demand for Storefront devices will show up in 2027. Work is still ongoing on the contracts tied to GlobalFoundries' 12LP process, which we mentioned on the prior conference call. That covers getting discrete FPGA test chips that we taped out for the contract carrying a $2.7 million ceiling value, announced on May 13th. Under this contract's scope, QuickLogic will receive test chips that we will characterize and put into a new 12LP eval kit, with a planned release in Q4. The eval kit will work with common third-party development environments that DIB and commercial customers both use. This lets customers speed up evaluations of discrete and chiplet designs that we can offer as Storefront solutions. Past these scheduled contributions lies an expected extension of our one million LUT contract to target Intel 18A-P, plus pending contracts with new customers I mentioned earlier. The bulk of what we're doing on Intel 18A in terms of development and customer design work has now shifted to Intel 18A-P. With Intel 18A-P, you get either a performance boost above 9% when power is held constant, or a reduction in power beyond 18% when performance is held constant. Since we could build on the development effort already completed for Intel 18A, the expense and schedule needed to create eFPGA hard IP for Intel 18A-P will be negligible. In fact, we anticipate getting a follow-on contract from the customer who paid for our one million LUT developments in Intel 18A, this time for an Intel 18A-P implementation, with delivery targeted for Q4. We'll continue collaborating with certain clients on Intel 18A projects, though our expectation is that the majority will move over to Intel 18A-P, which will likewise serve as the primary target for fresh design work. Our belief is that once Intel 18A-P becomes available, it will probably speed up design efforts, and along with that, bring more chances for our eFPGA hard IP. Beyond the follow-on contract for one million LUTs, we're engaged in close cooperation with a number of new clients on ASIC designs aimed at integrating our eFPGA hard IP. Late-stage talks are underway for two of these prospective deals. One involves a design intended for automotive, industrial automation, and robotics use cases. The other is with an overseas customer building an ASIC for a LEO satellite purpose. Additionally, we're engaged in tight collaboration with a fresh client who wants an eFPGA architectural license. Back at the start of this year, we secured a feasibility study deal worth five figures, aimed at assessing our eFPGA IP for one specific application. That agreement has just wrapped up, and now the client is looking into whether a tailored build of our IP, aimed at their own proprietary process, can satisfy their PPA targets. Early findings appear encouraging, and should things go well, an architectural license for our eFPGA IP would follow toward the end of this year. Most of you probably know that QuickLogic's first FPGA products were built on one-time programmable anti-fuse technology, which is an extremely dependable approach found in the mature offerings we've provided to defense and aerospace contractors across many decades. In addition to continued interest in those mature offerings, which have lately been incorporated into new programs, some DIBs have expressed interest in our current devices offered in packages smaller than what we presently provide. One of them specifically has signed a contract with us to finance and qualify that smaller package for new designs. Looking at the way we size up this opportunity, it has the potential to become a brand-new market worth multiple millions of dollars for QuickLogic, and it would require only a limited amount of ongoing operational expense. We're working hand in hand with that DIB, and we're also in discussions with other DIBs and aerospace firms to capitalize on this opening. In 2025, we rolled out our digital proof of concept approach as an extremely cost-effective way for both QuickLogic and prospective chiplet buyers to conduct evaluations. That approach has yielded more than five active proposals involving chiplets, targeting the GlobalFoundries 12LP, Intel 18A, and Intel 18A-P manufacturing processes. The 12LP eval kit I referenced earlier will strengthen these efforts by letting customers quickly advance past software simulations into real hardware evaluations. I think these proposals, along with others coming soon, will generate meaningful chiplet revenue starting in 2027. Having said that, I'll now hand the call to Elias Nader so he can present the financial data.

Elias Nader executive
#3

Good afternoon, everyone. For the second quarter, total revenue came in at $5.5 million. That represents 48.7% from Q2 2025 and an 8.5% increase from Q1 2026. The only reason this fell short of the midpoint of our guidance was a delay in extending an existing contract, something Brian Faith talked about earlier. New product revenue in Q2 reached $4.7 million, while mature product revenue was $0.8 million. Compared with Q2 2025, new product revenue rose 59.7%, and it was up 8.6% versus Q1 2026. Mature product revenue increased 6.9% against Q2 2025 and 8.8% against Q1 2026. Our non-GAAP gross margin for Q2 stood at 46.8%. That exceeded the midpoint of the 42% outlook we gave and marks a substantial rise from the 31% we reported in Q2 2025 and the 39.6% in Q1 2026. Non-GAAP operating expenses for Q2 came to roughly $3.5 million. Because of how R&D costs were allocated between OpEx and COGS, along with new hires, this landed a bit above our $3.3 million outlook; for comparison, it was $2.5 million in Q2 2025 and $3.2 million in Q1 2026. Our Q2 2026 non-GAAP net loss was $1.1 million, which works out to a loss of $0.06 per share. That compares with a non-GAAP net loss of $1.5 million, or a loss of $0.09 per share, in Q2 2025, and a non-GAAP net loss of $1.3 million, or a loss of $0.08 per share, in the first quarter of fiscal 2026. What separates our GAAP results from non-GAAP results mostly comes down to non-cash stock-based compensation expenses, restructuring charges, and taking out a significant non-recurring gain. Stock-based compensation for Q2 was $753,000, against an outlook of $900,000. Stock-based compensation totaled $843,000 in Q2 2025 and $858,000 in Q1 2026. Impairment charges came to $0 in Q2 2026, versus $300,000 in Q2 2025 and $0 in Q1 2026. Restructuring costs were $16,000 in Q2 2026, versus $21,000 in Q2 2025 and $11,000 in Q1 2026. We also took out a non-recurring gain of $950,000 that had been included in our GAAP results for Q2 2026. No non-recurring gains occurred in Q2 2025 or Q1 2026; during the second quarter, two customers each represented 10% or more of total revenue. At the end of Q2, net cash was $13.5 million, excluding a $5 million drawdown from our line of credit. That stacks up well against a projection of slightly less than $12 million and against the $3.8 million in net cash we reported at the close of Q4 2025; the $9.7 million increase in net cash across the first half of fiscal 2026 includes $9.8 million raised through our ATM before our last conference call. Turning now to guidance and outlook for our third fiscal quarter, ending September 27th, 2026. Given backlog and customer forecast, our total revenue guidance for Q3 is $5.5 million ±10%; we expect total revenue to break down as $4.7 million in new product revenue and $0.8 million in mature product revenue. At the start of this year, we were expecting mature revenue to rise in the back half. But looking at our latest projections, we now think mature revenue for the whole of 2026 will come in level with 2025, at roughly $3.3 million. Given the revenue mix we foresee for Q3, non-GAAP gross margin in that quarter should land at about 47% ±5%. Across the entire year, we are modeling a non-GAAP gross profit margin of roughly 51%. Keep in mind that because of how our industry works, we sometimes have to put certain expenses into COGS rather than OpEx, or capitalize some costs; those classifications involve labor and tooling tied to our IP contracts. That can create swings in our quarterly gross margins and operating expenses, though these typically offset one another on the operating line. With that in mind, non-GAAP operating expense for Q3 should come in at around $3.6 million ±5%. Because of variability in how R&D costs get allocated between OpEx and COGS, plus new hires, we are lifting our full-year non-GAAP OpEx outlook to a range of $13.7 million-$13.9 million. The projected roughly 17% rise in non-GAAP OpEx over 2025, set against our 70%-80% revenue growth outlook for 2026, shows how strongly the inherent leverage of our business model works. Once interest and other income are factored in, we forecast a Q3 net loss of about $900,000, or a loss of roughly $0.05 per share. Under our present outlook, we still expect non-GAAP profitability in the second half of 2026. The largest gap between our GAAP and non-GAAP numbers comes from non-cash stock-based compensation expenses. For Q3, we expect that compensation to be around $900,000; that's versus $828,000 in Q3 2025 and $753,000 in Q2 2026. As a reminder, stock-based compensation will move around during the year, and it can shift quarter-to-quarter depending on when grants occur. We anticipate cash use of approximately $400,000 in Q3; as a result, we expect to end Q3 with a net cash balance just above $13 million. Bear in mind that our cash use could shift depending on when certain contract payments and receipts land during the quarter. Under our current outlook, we expect positive cash flow in the second half of 2026; with that, thank you for your time. I'll now hand the call to Brian Faith for his closing comments.

Brian Faith executive
#4

Thanks, Elias Nader. For QuickLogic, 2026 is looking like it will be a really strong year. Taking into account the contracts and orders already booked, along with where things stand in talks over a couple of fresh agreements, we've tightened our outlook for growth across the full year to a range of 70% to 80%. Given that, we're projecting non-GAAP profitability as well as operations that are cash flow positive during the back half of 2026. While that matters a great deal, I also want to stress that at the same time, we've set the stage for ongoing expansion and profits in 2027 and afterward. Back earlier in this year, we projected that 3 tape-outs would be finished during 2026. The initial one is done, and we're on track to get a batch of test chips that we'll put into a 12LP eval kit. That should let our customers speed up their evaluations, and we think it will generate new designs we can offer through our storefront, whether as discrete devices or as chiplets. Beyond that, we have several additional chiplet possibilities underway that we expect will produce new contracts and storefront orders starting in late 2027; we have 2 further tape-outs planned for late 2026; for one of them, we'll have enough devices available to back initial production orders that we can deliver via our storefront initiative starting in 2027; we keep supporting demand for our RadPro eval kit and expect fresh orders throughout the second half of 2026. We're hopeful this will bring about the first storefront orders starting in 2027. We're also hopeful that during 2026 we'll land a contract for our second-ever eFPGA IP architectural license, and we'll collaborate closely with that end customer as it builds a device aimed at its proprietary fabrication process in 2027; we've just secured 2 new designs for our current mature products and have been given a contract to qualify a new small package option. That, we think, will unlock a multimillion-dollar chance to move into new designs starting in 2027. With all these achievements, I hope you share the pride I feel in how extraordinarily the QuickLogic team has executed, along with my strong optimism about our future growth. Thank you. I'll now open the call for questions.

Neil Young analyst
#5

Hi, everybody. I appreciate the chance to pose a question. If I look at what's left in the year, it appears Q4 now accounts for a big chunk of the growth narrative for the whole year. Building on that point, how confident are you about the risk around timing? Does any portion of that revenue recognition depend on milestones or deliverables that might slide beyond Q4 and into 2027? I also have a second question. Thank you.

Brian Faith executive
#6

That's an excellent question. Our business and engineering teams get together on a regular basis to confirm the technical resources are in place and to give priority to the work tied to revenue recognition. We've reviewed those contracts I referenced earlier on the call, along with when we would need to deliver these items, and we're arranging the work right now so those rev rec milestones can be reached; at this point, it comes down to finalizing a couple of these contracts for that to occur; that falls more to the business side, finalizing the contract, rather than engineering and the deliverables. To be clear, the engineering team is lined up, and for some of these items, work has already begun, so we can deliver and satisfy the revenue recognition expectations for the figures we just discussed.

Neil Young analyst
#7

All right, thank you. On to my next item — if I understood correctly, you said the bulk of your client base intends to shift over from Intel 18A to 18A-P, and because of prior development efforts, the expense of porting will be minimal. So in real terms, might that cause income tied to ongoing Intel 18A projects to slip as those clients wait to rework their designs for 18A-P? Or does work already underway on 18A continue without interruption? Could you share whatever you can on that? Appreciate it.

Brian Faith executive
#8

Sure. Across these calls, we've mentioned a number of 18A possibilities. From a single customer, we do in fact have a revenue stream tied to that one million LUT IP deal; as I noted during the call, our expectation is that it moves over to A-P. We've also put out a few additional proposals that would let us keep drawing on what we've already built for our 18A-P core, though those too might switch across to 18A-P. After the initial port is complete, any later licenses or derivative licenses stemming from that very first port to additional clients become extremely efficient for us in terms of both cost and time — which means we could reach our revenue goals if we land fresh contracts on 18A-P, or with clients who are shifting everything onto 18A-P. My sense is our coverage is solid. It demonstrates, I believe, the operating leverage our model provides, plus the reality that we possess automation through Australis to serve these clients promptly. In my view, a great deal of investment has gone into the broader ecosystem surrounding Intel 18A — not P. I suspect certain clients will take advantage of that, maybe when they're already well along in a chip design prior to making the switch, since you can picture that across the ecosystem at large, everyone needs specific items completed on 18A-P before chip designs can head in that direction. I'm referring to all the various IP you'd potentially be integrating there. As I mentioned, for some it will be a step-by-step shift as the ecosystem develops. Where digital content is high, we're able in certain instances to go much quicker, exactly as we're doing with our porting.

Neil Young analyst
#9

Thank you.

Brian Faith executive
#10

You're welcome.

Tyler Burmeister analyst
#11

Hey, guys. Good quarter.

Brian Faith executive
#12

Hello

Tyler Burmeister analyst
#13

Nice work on tightening up that outlook for the entire year. So, maybe I'll start with the folks using dev kits. Can you put any kind of figure on how many of them, I think what you said was they shift into Storefront revenue in the coming year? Any way to size that or frame that number would be helpful.

Brian Faith executive
#14

Those tie back to programs I'm not really at liberty to discuss. What I can tell you is that the parties who'd require a strategic Rad-Hard FPGA are ones we're already working with. Sometimes they've got dev kits in hand already, and I genuinely expect we'll see Storefront revenue in the next year tied to evaluations happening on those dev kits. How many exactly or what share, I won't get into that; but I'm quite confident they'll produce Storefront sales in the coming year.

Tyler Burmeister analyst
#15

Got it. Fine. I apologize for continuing to bring up inquiries regarding initiatives of this kind.

Brian Faith executive
#16

No problem at all.

Tyler Burmeister analyst
#17

Perhaps put it another way. In the past, you framed the overall strategic Rad-Hard chance, I believe, as 10 to 20 sockets spanning several programs. With these dev kits now sitting with customers, I'm curious whether you've kept talking with those customers. Have you perhaps noticed any shift in that set of opportunities — has it grown, do these discussions possibly confirm that set? Any detail you could offer on that would be interesting, I suppose. Thanks.

Brian Faith executive
#18

Yeah, how I'd put it, I guess, is that more groups are working with us today than back when we last talked on our Q1 call. So that opportunity set has gotten bigger, which is positive, and I think that's expected — once you have actual silicon and actual dev kits, you begin to find new opportunities that might have come from folks who were waiting to see how things went. But as soon as they witness actual silicon, they begin moving more quickly. So it's encouraging that it has grown. That's the reason we put that remark into today's script — we anticipate additional dev kits shipping between now and year-end to back more evaluations. I'd like to share more detail about these matters, but I hope you grasp the delicate position I'm in regarding non-disclosure agreements, especially for programs of this kind.

Tyler Burmeister analyst
#19

No, that makes total sense. My apologies for catching you off guard there, but I do appreciate the insight. That's everything from my side, folks.

Brian Faith executive
#20

Thank you, Tyler Burmeister.

Gus Richard analyst
#21

Yes, I appreciate you fielding the questions. Regarding the Rad-Hard contract, can you bring us up to speed on the amount remaining? And what's your expectation for the timing of the following tranche?

Brian Faith executive
#22

On the amount remaining, we have not made those specifics public. That said, I'll walk everyone through it again; right now we are carrying out work and performing against the $13 million tranche; that was announced by us in mid-December of last year, and we've stated during the call that our projection is for it to be completely recognized across this fiscal year, 2026. We also mentioned during the call that Q4 should play a major role in driving revenue growth. And inside Q4, the government contract would be a significant part of that; therefore our forecast is that an additional tranche will be in place prior to the close of the year, and it would be backing that up.

Gus Richard analyst
#23

Understood, thanks. That's useful.

Brian Faith executive
#24

I suppose I'll go ahead. Hi Gus Richard, allow me to tack one additional point onto that. I believe it's common knowledge that QuickLogic counts the U.S. government among its major customers, so you can always check the queue to identify which 10% customers we have along with their percentages, and from that you could likely work it out.

Gus Richard analyst
#25

Got it.

Brian Faith executive
#26

To see how far.

Gus Richard analyst
#27

Regarding the eFPGA, it seems a contract got pushed back; the customer isn't certain about which functions should be hard logic versus gate array. Can you give any indication of the revenue you anticipate from eFPGA licenses across the coming two quarters?

Brian Faith executive
#28

Taking eFPGA licensing as a whole, our category covers eFPGA support work plus the NRE work coming from the U.S. government. We don't provide that breakdown at, I suppose, the granularity you're specifically requesting; however, for the year's second half, that entire category is likely near, let me check, roughly $8 million-$10 million, in that vicinity, estimating right here. Concerning the bigger IP contracts, several are currently being executed and are already signed. I noted during the script that we're working on ones already signed, and a handful more sit in late-stage negotiations. Incidentally, winning every single one of those late-stage negotiation deals isn't necessary for us to hit the revenue growth targets we've laid out for the year, which fall between 70% and 80%. That's the reason we feel positive regarding that figure and our position in those talks. Incidentally, if I may, Gus Richard, you raised the extension that moved out of 2026, and I'd like to take a moment to expand so that everyone is, I suppose, completely clear on it. That design was already on one process node, and we'd completed certain deliveries and booked IP collected on it. That customer subsequently considered, for their applications, possibly moving to a more advanced process node. Moving to a more advanced process node is precisely why it would count as an extension for an existing customer and why it would generate additional revenue for QuickLogic. To a degree, I can see why they wished to conduct a somewhat more detailed analysis of what belongs in the eFPGA and what belongs in the hard logic. Because shifting to any of these more advanced process nodes, particularly beyond what we were already at, will represent a very substantial mass cost for them. I believe they wanted to confirm they're performing their diligence from their end customer's standpoint prior to making that decision. Though it's disappointing from a 2026 revenue standpoint, we're confident it moves to 2027 for us. I, once more, to a degree, can see why they're exercising caution regarding the partitioning prior to signing a contract with us. Back to you, Gus Richard.

Gus Richard analyst
#29

Understood. So I want to make sure about the eFPGA top line — you mentioned a figure of $8 million. Does that cover only the back half, or does it apply to the entire year?

Brian Faith executive
#30

The back half — though it also takes in our government work, since for us that sits in a single revenue bucket. It handles the IP as one combined piece.

Gus Richard analyst
#31

Alright, understood. Sounds good. Thank you very much.

Brian Faith executive
#32

Sure thing.

Richard Shannon analyst
#33

Hello there. Brian Faith and Elias Nader here. We appreciate you giving us the chance to ask a few things too.

Brian Faith executive
#34

Of course. Richard Shannon.

Richard Shannon analyst
#35

Hi. How are you all doing? Let's talk about the sales guidance for the year. The midpoint is unchanged from what you previously provided, and a significant contractor has shifted out to 2027, so you must have secured additional business or at minimum gained more confidence in some other business. Could you help us grasp the dynamics behind the midpoint remaining the same?

Brian Faith executive
#36

Yes. The largest element in that, Richard Shannon, is that when we laid out our range previously, we were taking a cautious approach, or we weren't including every possible item in the figure we're sharing. Despite the fact that we saw some movement there, that's the reason the midpoint did not change.

Richard Shannon analyst
#37

Alright, that makes sense. I'd like to build on something asked earlier, I believe by Tyler Burmeister, regarding Storefront in the coming year. My sense is that his focus leaned toward the RadPro product line specifically, yet he was curious how much Storefront revenue you'll generate beyond that. Could you go deeper on the product customers, the applications, and share any perspective on how large Storefront revenues might be next year?

Brian Faith executive
#38

Yes, that's a solid question. On our previous call, I believe that marked the first occasion we began discussing the multiple tape outs we had slated for the year, the three. Naturally, with any Storefront revenue, it's something tangible. A chip must exist for us to sell before any Storefront revenue can come in. Setting the RadPro items aside briefly, there's another test chip we anticipate receiving back later this year that's already been taped out, we'll get it onto eval kits, and interest from companies already exists around it. They've reviewed the spec sheet. They're aware it's on the way. We're engaged in certain commercial discussions, in some instances, concerning how those could be accessed by them next year for stacking within multi-chip packages. I genuinely believe that when you pair that with our RadPro plans, we've referenced single-digit millions of dollars in revenue for next year across all these various test chips. We still have those remaining two mentioned during this call that we intend to tape out before the year ends, and we do believe that simply considering cycle times for silicon, that silicon too would be ready next year for some level of sale. Early volume for customers. Beyond that, we didn't devote much attention to it today, yet there's been a substantial rise in the count of RFIs and RFPs and RFSs, request for information, request for proposal, request for solution, originating from various government channels. A notable uptick, in fact, in these requests. We've been drafting proposals and sending them in, and I'm hopeful that eventually, given it's a numbers game here, we'll secure one or more of these, which would then add to service revenue initially, but perhaps even some early device test chip revenue for Storefront before next year ends, purely based on the timelines the U.S. government has requested on these and how quickly we can respond using either existing silicon or silicon we could design rather fast. Does that address your question, Richard Shannon?

Richard Shannon analyst
#39

Understood; that helps a lot. Perhaps only a few additional items from my side, then I'll step aside. Regarding the RadPro offerings, I'd like to hear whatever reactions you're receiving from clients that have already received Dev Kits, and concerning the schedule you anticipate for choices from a number of those early customers — I believe you mentioned something like the close of the year or the beginning of next year. Does that still seem accurate based on what you know?

Brian Faith executive
#40

Correct. Once more, I'm unable to discuss details about what buyers are telling us, yet there has been substantial engagement surrounding those Dev Kits. We've delivered considerable training, and there's been plenty of regular contact with those buyers on the assistance front. Yes, my hope is that we will receive certain signals before the year concludes, as I mentioned earlier. Beyond that, as I noted, we've actually been introduced to additional teams inside these buyers that we weren't engaging with 3 months ago. To me, that's an encouraging indicator that this is reaching past the original group of buyers; those parties might likewise adopt something that could lead to testing or orders in the coming year; that's positive; it's a promising indicator. It's broadening, which means that even if we learn before the year ends that a number are satisfied with the component and intend to proceed, I don't believe it ends there. I believe it keeps expanding inside these organizations as more engineers begin experimenting with the software, experimenting with the hardware, becoming at ease with it, and beginning to spot programs of record where we can be inserted.

Richard Shannon analyst
#41

Alright, that sounds excellent. For my final question, I'll step outside the queue here. Is there any possibility you'll share with us what portion of sales came from the 10% customers during the second quarter?

Brian Faith executive
#42

Kindly look at the quarter once we file it. I'm not attempting to be corny.

Richard Shannon analyst
#43

Okay.

Brian Faith executive
#44

That's going to be included in it. I can't recall right this moment.

Richard Shannon analyst
#45

All right. I'll hold off on that question. That's everything I have, everyone. Thanks.

Brian Faith executive
#46

Thank you, Richard Shannon.

Rick Nehan analyst
#47

Thanks. Hello, Brian Faith, and hello, Elias Nader. I won't press you further on how confident you feel regarding this year's guidance. What I have is a somewhat unusual query concerning post-quantum cryptography, and where eFPGAs come into play there, considering that small demo effort you've got going with the organization based in Florida Atlantic. Does that fall under defense? Or is it outside of defense? In what way does an eFPGA serve a preemptive role for quantum computing, and when might that happen?

Brian Faith executive
#48

Those are excellent questions. I enjoy them. What we've discussed openly regarding post-quantum isn't confined to defense alone, though obviously there's a clear wish for it to be used in defense. Basically, you could consider anything tied to critical infrastructure as a potential hacking target. That might be a defense system, it might be a satellite communication system, it might be water systems that we've seen reported online. Any of those, I'd say, are targets that are prime for attempted hacking. I believe a presidential order actually came out, definitely after the last call, that said people ought to begin examining how we safeguard these systems using more sophisticated cryptography. The motive behind that wish stems from worry that, once quantum computing gets deployed for real, standard cryptographic systems will be compromised almost instantly. So now they're asking, "Well, how do I incorporate the safety mechanisms into these systems?" Post-quantum, PQC, is one thing being examined, and sadly, those algorithms haven't fully stabilized. They're still in flux. When you hear about something involving a critical capability and these systems that are critical infrastructure while standards are in flux, that's the ideal situation for FPGA or eFPGA, since with eFPGA, as everyone on the call knows, you can build it into your silicon and program the functionality afterward. That's a strong wish among those people examining post-quantum cryptographic algorithms, because they can execute that within the reprogrammable eFPGA core in their ASIC, and they can deploy the chips forward, programming it afterward. That's a major piece of the value proposition. We're witnessing considerable interest in that space right now, from both defense and non-defense. Once more, I think it's bolstered by the fact that the U.S. government is quite attentive to this as well. That's why you began seeing some marketing-side collaborations involving us and other partners, and why I think we've published a blog on it too, since we're clearly seeing interest there.

Rick Nehan analyst
#49

Yes, it does. I appreciate you walking me through that. Let me ask one more thing about it: when it comes to PQSecure, is the way you work together comparable to what you had — or still have — with ETH Zurich, where the Arnold chip came about essentially as a demo effort? Or should we see this as the initial move toward an actual commercial offering?

Brian Faith executive
#50

This one is further along than what we did with ETH in Zurich. That ETH Zurich group was an academic institution focused on research, and a great deal of their work centered on eFPGA for low-power computing; in certain respects the two are alike, since this marks the early phase of a trend, correct? Low power was the theme there; here it's about putting post-quantum cryptographic algorithms into deployment. What stands out as the main distinction today is that we're dealing with real businesses. No university or research body is involved. I'd describe it as substantially nearer to genuine products, tackling genuine challenges, and bringing in genuine revenue for QuickLogic, unlike the ETH Zurich effort, which amounted to a low-power proof of concept. Interest did come out of that, yet my sense is that what we have now will draw stronger, more concrete interest capable of producing revenue for us in the near term. For eFPGA, it's an unmistakably strong and persuasive use case. Unmistakably.

Rick Nehan analyst
#51

Alright. I appreciate all those specifics, Brian Faith, and thanks for letting me join the call.

Brian Faith executive
#52

The pleasure's mine. Thank you, Rick Nehan.

Brian Faith executive
#53

Alright, thanks for joining us today. Tomorrow, you’ll have a chance to connect with us at the Canaccord Genuity Conference in Boston. Our presentation is scheduled for 2:30 P.M. Eastern, and for anyone who isn’t in Boston, a webcast will be available. In addition, we’ll be taking part in the Needham Virtual Semiconductor & SemiCap Conference next week, followed by the Lake Street conference in September, and the CEO summit at SEMICON West in October. Thanks once more, and enjoy the rest of your day.

Operator operator
#54

Thanks. That brings us to the end of today’s call. At this point, you’re welcome to hang up, and we appreciate your joining us.

Read the full transcript via the API

You're viewing the first half of this call. Get the complete QuickLogic Corporation transcript - plus 132,000+ transcripts from 7,000+ companies, speaker segments and full-text search - through the EarningsAPI REST API or hosted MCP server.

Get an API key View API docs →

For developers and AI pipelines

Programmatic access to QuickLogic Corporation earnings transcripts and 132,000+ others is available through the EarningsAPI REST API and the hosted MCP server. Quarterly plans from $162 - full transcripts, speaker segments, full-text search, and the /api/v1/transcripts/recent polling endpoint for ETL pipelines.