Electronics Manufacturing Delays Start Before the Machines Do

James Sweetlove
|  Created: November 18, 2026
At a Glance

In the latest episode of the CTRL+Listen Podcast, James Sweetlove engages with Ralph Richart and Steve Rubinstein from MetisLogic to discuss the challenges of electronics manufacturing delays. The conversation highlights the critical "first mile" phase that occurs between design completion and production initiation, revealing common pitfalls in procurement, program management, and material tracking that can impede efficiency, especially in high-mix, low-volume production environments.

Go Deeper with AI:
Electronics Manufacturing Delays Start Before the Machines Do_Cover

Electronics manufacturing delays usually start long before a machine turns on, in what MetisLogic calls the first mile: the messy middle between design done and production start. On this episode of the CTRL+Listen Podcast, James Sweetlove talks with MetisLogic (formerly PartSnap) founder Ralph Richart and C.O.O. Steve Rubinstein about why procurement, program management, DFM/DFA, and material tracking break down on high-mix, low-volume and NPI builds, and why high-volume fixes like faster machines and automated storage don’t solve them.

They unpack how the material picture shifts from quote to order to production, why manufacturing is a binary outcome, and the three questions every supplier should be able to answer: what do we have, are we ready to build, and what did we build. Ralph also makes the case for engaging your contract manufacturer early, before a stackup decision costs you weeks of redesign, and explains where AI helps today and where a great manufacturing engineer still wins. If you run prototype, NPI, or pre-production builds, you’ll come away with a clearer picture of where your lead time actually goes.

Listen to the Episode

Watch the Episode

Resources from this Episode:

Transcript

Introduction:

When the supply chain got wonky in COVID, I think we all thought that was going to be a one-off and COVID was going to get solved. The supply chain was going to stabilize, and it’s anything but, James, as you well know.


James Sweetlove (JS): So, what exactly is the first mile of manufacturing, and why do you think it’s something that’s overlooked real?

Ralph Richart (RR): You know, James, that’s a great question. The way we define the first mile of manufacturing is this segment from design done to manufacturing start. And so, you know, as an OEM, you’ve invested all this time doing the design. You’ve likely gotten a quote from your contract manufacturer. Now you’re ready to go. And so that journey from “hey, I have this design, we’re ready to go” to actual manufacturing start, that’s what we call the first mile, or the messy middle. You know, it’s procurement, program management, DFM/DFA, and then ultimately production start. And so, Stevie, I think, do you want to talk a little bit about why we think it’s overlooked?

Steve Rubinstein (SR): Yeah. So, what’s been missing from all that is the connective tissue, what we refer to as the material workflow. You know, what’s tracking, what’s ordered, what’s actually arrived, what’s still missing, all of that. And that key piece in the first mile has been missing and overlooked for a couple of reasons. So, first, you know, if you think about the high-volume manufacturers, the few that do the most, if you will, or build the biggest, they don’t feel this pain as much. They’re working with stable BOMs. They’re doing bulk purchasing. Repeat orders mean that, you know, that first mile is a small fraction of their job. And so, as a result, the tooling world optimized for them. That left everybody else, the majority manufacturers, you know, who run lower volume with a higher mix perhaps. They get stuck with problems that are misdiagnosed with the view of a high-volume cure. So, for example, you know, oh well, late deliveries, well, the cure for that is just faster manufacturing, you know, bigger, more expensive machines. Like, we’ll just throw not bodies at it, we’ll throw robots at it or whatever, right? Issues in the warehouse. You know, we got some really fancy receiving stations and automated rack systems for you. That’ll clean that all up. But, you know, these misdiagnoses just end up costing these manufacturers a lot of money or wasting their time, or it just doesn’t solve their problem, and they know that at the outset. You know, late deliveries, we find, are often caused by first mile issues. Changing requirements that no one caught in time. Faster manufacturing isn’t going to fix that. Similarly, warehouse issues, they’re not going to be solved by fancy receiving stations or automated rack systems. That equipment can’t reliably interpret labels on bags of cut tape. They’re more geared towards big reels. Same with the automated rack system. So, you know, that’s one of the reasons why these things have been ignored and the current solutions haven’t worked for them.

RR: Yeah, I think, Stevie, just to build on what you say a little bit, you know, James, it’s probably important for us to differentiate between big sustaining production and NPI slash, you know, early production, pre-production levels, where I think what Steve points out is, hey, if I have an 8-week build and it takes me a week or two to get to the shop floor, or three, then it’s still a smaller element of the total production time than is the 10-piece build where I’m expecting, you know, something to be done in a week or two. If I’m spending four or five days in the first mile, that’s a problem. If we can compress that time, then everybody benefits because I can have everything faster. And so, like what Steve says is, first mile delays put pressure on the production floor, whereas in sustaining production, first mile delays can be more easily absorbed on the production floor simply because we have more time.

JS: Right. That makes sense. Do you think this is something that’s become more important in the past six years due to market instability? Do you think it’s something that people—it’s harder to overlook now without it causing issues?

RR: For sure. Yeah. I think, you know, when the supply chain got wonky in COVID, I think we all thought that was going to be a one-off and COVID was going to get solved, the supply chain was going to stabilize, and it’s anything but, James, as you well know. And so, you know, again, on the sustaining production side, well, I probably pre-bought components a year or two in advance. I’ve got just, you know, scheduled deliveries. On the NPI pre-production side, we are, you know, working hand-to-mouth. We’re, you know, going from “I had this yesterday, I don’t have it anymore. What do you want to do?” And, you know, all this work, really, unfortunately, lands on the back of the program manager for the most part. They’re trying to solve all this change management while also delivering the right thing to the production floor. And so, yeah, it hasn’t gotten better. In fact, it’s gotten worse.

JS: Yeah, that’s what we’re hearing, seeing as well on our side. So how does the material picture change between quote, order, and production? Because that obviously plays into this whole thing.

SR: For sure, yeah. So, you know, quotes, they’re a snapshot in time, right? You know, that’s what was happening that day. And, you know, to be honest, the supplier is probably not going to overinvest in that process unless they’re really sure that they’re going to get the job. But, you know, once the order is in, the conversation starts, and the supplier and the customer, you know, are obviously very invested in making sure this works. So, you know, they’re resolving what’s really expected, you know, the timing, the parts, which, you know, which ones are important, which ones are less important. And then they’re re-evaluating, as, you know, we just discussed, based on what the current availability is as well as pricing and backlogs, etc. Yeah, today’s supply chain is as dynamic, as much of a mess, as it’s ever been. I don’t know if we’re at peak or somewhere close to it, but that means that all, you know, parts that were assed in quoting, you know, a good percentage of them may or may not be remaining after that.

RR: Yeah. And I think, you know, just to build on what Stevie said, you know, production is where the rubber hits the road, right? Production is where we actually have to go from the virtual to the physical. And so, you know, that workflow from quote to order to produce, that continues to refine the level of certainty of which we’re going to build. And going back to these gaps in this workflow, you know, there, it’s a bunch of interrelated processes which also can run independently. And so, you know, for example, if the three of us are all working for a manufacturer, Steve’s in procurement, you’re in program management, I’m in production, well, if you, the program manager, forget to tell Steve that we have a part change, then we will likely build the wrong thing. And so, you know, not having these connections between the three of us in a really robust way causes gaps in the production floor, which may end up with a line stop, may end up, you know, even worse, shipping the bad product. And so, you know, something we talk about as software people a lot, and me from a manufacturing background, is, in manufacturing, it’s a binary outcome. It’s good or it’s bad. There’s no “we’ll fix it tomorrow.” And so, I think, you know, that path to resolution is really important, and how things change along the way is, you know, the difference between quote, order, and produce.

JS: Right. No, it’s a really good—I like the phrase about it being a binary outcome. I haven’t heard someone use that before, but it’s very accurate.

RR: Yeah. So, fighting with software engineers on the regular basis who say, “We’ll fix it tomorrow.” Right? I’m like, “No, we can’t fix it.”

JS: Yeah, definitely. It’s working in the meantime.

RR: Yeah, totally.

JS: Yeah. So, do you want to tell us a little bit about your background and PartSnap and sort of how you operate in this space?

SR: Sure, I’ll start with that. So, Steve Rubinstein. I’ve known Ralph for a number of years, and, you know, soon after he started thinking about this problem and working on trying to solve this problem of, you know, the first mile of manufacturing, we were talking, and he asked me for some advice on, you know, building software tools, working with engineers, because I used to be one. As I say, I’m a recovering engineer. And, you know, I spent my career in software engineering and operations at a number of software companies in the Valley and around the country. You know, Apple, Netscape, Electronic Arts, etc. That’s far away from the electronics manufacturing industry. And so the problems in this industry, you know, that they were facing, were new to me. But they were also very interesting, and, you know, there are some parallels to other industries as well as I’d been in. The big bonus for me, of course, is that it gave me an opportunity to finally justify why I got an electrical engineering degree in the first place, so I could finally make use of it. And then, you know, the opportunity to work with Ralph, of course, convinced me to, hey, why don’t I get involved in this full-time, and we’ve been together ever since.

RR: So inseparable, and we’re both from New Jersey, so that helps. Yeah, and, James, my background: I’m Ralph Richart. I’ve been a manufacturer for longer than I care to count. I just had a birthday. I’ve also stopped counting those years. So, you know, they’ve been a long time. I started as a circuit board fabricator, so building the bare boards, for a long time. Always in the quick-turn NPI space. Most recently, I joined a contract manufacturer, and that’s where, you know, when I joined that manufacturer, their idea was we can find a way to make machines go faster. And that was a neat premise. It just didn’t hold a lot of water in the NPI build because it isn’t about machine time at that point. And so, after that experience ended, I spent a lot of time thinking about what the first mile looks like. What are the barriers which prevent us from going faster? How can we meaningfully change lead times on NPI and pre-production builds? And so, yeah, to, you know, build on what Steve said, I am a manufacturer to my core. I like to build things. I like to hold things. I like to think about manufacturing. I didn’t have the software background, and so, yeah, it’s a really good partnership between us to now bring software to bear that’s rooted in manufacturing experience. I think that’s critical, is that I’ve been in the shoes of most of our customers fighting to get a delivery out. And so, you know, as we build this thing, it is really from the perspective of the manufacturer.

JS: That’s great. No, I think that helps. I feel like sometimes the software, you get people that are always on the software side, and maybe they understand the concept of it and they understand, like, how to operate the software itself, but they may not understand how everyday person uses that and how that applies to their job in a daily aspect. So, it’s good to have that insight, I think.

RR: Yeah. And I think, you know, it also helps when we’re on discovery calls to be able to, you know, really have an engagement with a customer to say, “Yeah, oh, I’ve seen this problem before. I’ve been in your shoes. Let’s talk about it from, you know, how I might have seen that.” And at least give you an input that is just one more, you know, view to the world. I think it’s super easy as manufacturers to get super siloed up and say, “We’re the only ones experiencing this. It’s chaos. It’s terrible.” And it really helps to be able to at least be empathetic to their problem and say, “Yeah, we’re seeing this everywhere. It’s not just you. Don’t stress so hard.”

JS: Sure.

RR: Yeah. We can all solve the problem together.

JS: That’s great. So I think it was on your website, I saw, and maybe it was when we were having the conversation when we first talked. There was a phrase that said, “Every supplier should ask, what do we have? Are you ready to build? And what did we build?” Do you want to elaborate on that a little bit? Because I think it’s a great way to look at it.

RR: Sure. Yeah, this goes back to my manufacturing experience, which is every day we had a morning meeting, had every stakeholder in the building there, had, you know, someone from sales, someone from customer service, someone from program management, someone from production planning, someone from—I don’t know if I already said program management, but program manager is a key. And we spent this time trying to understand, you know, clear to build. Are we ready to go? And when I started thinking about this problem and thinking about a solution to this problem, what is clear to build? Clear to build is trying to answer these questions. What do we have? Has it arrived? You know, is anything here? Again, a lot of the people that we talk to are super backlogged and receiving, and so it’s really hard to answer the what do we have?

JS: Right.

RR: Right. Next question. Can we build it? Great question. Who’s allocated it? Is it in a kit box where no one can find it? Has anyone done that inventory? And so, you know, again, really critical question. Can production start? Everybody wants to know, can production start? That’s the, are we ready? And then finally, you know, again, in the NPI pre-production space, the what did we build is a massively important question for our customer. You know, we all love our customers, but we also understand that they’re going to do a lot via email. They’re probably not going to run an ECO for the changes we’re making along the way. And so, being able to answer quickly, hey, you know, customer calls, the board is burning on my desk, what did we build? Being able to respond to that quickly, James, is a massive, you know, improvement that you can give back to your customer. And so, again, I think a lot of systems, we really care deeply about getting to the floor, but we don’t necessarily remember to record everything we did so that we can regurgitate that customer if they have a problem.

JS: Right. Makes sense.

RR: So, it just seems like a place where we can be super accretive to our customers.

JS: Sure. No, definitely. And it kind of ties back to, maybe I’m wrong here, but I think it ties back to something else that you said to me, which is why it’s crucial to engage the CM early before decisions are locked in. So I think that ties in right to asking the questions early on and doing that assessment. Can you elaborate why that’s so important and how it’s harder to come back from making those poor decisions early on?

RR: Sure. Yeah, I mean, on the one side there’s the logistics side, which is, you know, continue to engage them on parts availability. You know, there’s a ton of great tools for parts availability, but there, the resource of your subcontractor shouldn’t be overlooked either. They may have relationship that’s not available online. They may be able to, you know, a broker where something’s hiding. I think the other side of that, though, is also the manufacturability question, and, you know, we can talk about how AI is going to play a role here, but, you know, understanding the experiential learning that your subcontractor has had, and that they can give you some really good feedback about, you know, this is how you should lay yourself out, avoiding, you know, weeks of redesign. So, you know, a good example is just yesterday I was on a call with one of my customers that I consult for. They’re in the design phase. We’re having a conversation with our fabricator about some of the choices that we might make on the stackup. And really the core of it all was, hey, let’s have this conversation now because we’re on a time crunch. If this stackup doesn’t work, then I’m back in redesign for another four weeks, and that’ll be terrible to the timeline. And so I think, you know, that engagement, I’ve advocated for this for years. Like, you can’t not engage early enough. You’re going to get such good feedback from your subcontractor about what their experiences are building your product. And it will just, again, save you at least a revision, if not, you know, months or weeks. And so, yeah, I’m a huge advocate of early engagement.

JS: Makes total sense to me. And then you kind of touched on the last thing I want to ask you, which was AI. How do you think AI is going to affect this process, and where do you think it fits in with everything here?

RR: So, I’ll open with, I don’t have a crystal ball. You know, I’m reading with the rest of us. You know, it’s interesting when we started this company, I spent the first six months writing, and, you know, I wrote this 300-page manifesto, and, you know, took forever and had Figma help me and did all this work. AI just wasn’t a thing. And, you know, now AI is part of our everyday life. We’re running our, you know, our product definitions through it. We’re having conversations with it. At the same time, James, I think that it would be unfair to say that AI could do this on its own. We’re just not there yet. And I think that I can extend that to the manufacturing process in general, which is in the NPI pre-production world. Gosh, like, give me a million tokens on Anthropic or a great manufacturing engineer. I’m going to take a great manufacturing engineer all day every day. It’s just not there yet to be able to say, you know, this board doesn’t look like that board. What is the reflow profile going to look like? This has this component on it. I need a step-down stencil. Let’s redo this stencil. And so, you know, I think as of today, there’s still tremendous value in the people that help us run the business. And AI hasn’t gotten there yet. And so, you know, where I’m hopeful that AI can continue to leverage itself and be the complementary, you know, tool to our businesses is in things like that, is, you know, can I take these large bits of data that seem completely unrelated and find a way to make reflow profiles faster? You know, the art side of the business is, I wonder, you know, how it will evolve to be a, you know, supporting actor in the artistic side of what we do.

JS: Right.

RR: It certainly isn’t there today.

JS: Right. So that actually kind of brings us to time. I had one more question for you. If people want to get in touch with you or, like, you know, learn about your services, have a conversation, what are the best ways to do that?

RR: Sure. Email is fantastic. info at either metislogic.io, M-E-T-I-S-L-O-G-I-C, or partsnap.io. We’ve actually gone through a name change since we’ve first talked to each other. We were once PartSnap. We are now MetisLogic. We’re on the web. I’m on LinkedIn: Ralph Richart. Steve’s on LinkedIn. We’ll be at a trade show. I don’t know when this airs, but, you know, the 24th will be in Portland. We’re going to go on the trade show circuit. But certainly looking forward to talking to people about anything. First mile.

SR: Yeah. And metislogic.io is the website if they want to take a look at things first before they send us personal mail. But we love to talk to people, so why not?

JS: Great. And I will include those links in the description of the video. So if anyone wants to get in touch, you can find that in the video description. Steve and Ralph, thank you so much. It’s been really great talking with you. I had a lot more questions, just such a limited time. Maybe we’ll do another episode sometime when you’re more established. It’d be great to learn how things are going.

RR: 100%. Appreciate the time, James.

SR: Yeah, thanks James.

JS: Everyone tuning in, thank you so much for listening. We’ll have another guest next time.

About Author

About Author

James Sweetlove is the Social Media Manager for Altium where he manages all social accounts and paid social advertising for Altium, as well as the Octopart and Nexar brands, as well as hosting the CTRL+Listen Podcast series. James comes from a background in government having worked as a commercial and legislative analyst in Australia before moving to the US and shifting into the digital marketing sector in 2020. He holds a bachelor’s degree in Anthropology and History from USQ (Australia) and a post-graduate degree in political science from the University of Otago (New Zealand). Outside of Altium James manages a successful website, podcast and non-profit record label and lives in San Diego California.

Related Resources

Related Technical Documentation

Back to Home
Thank you, you are now subscribed to updates.