TRASCRIZIONE 🔗
WEBVTT
00:00:00.080 --> 00:00:05.599
Welcome to Automation Ladies, the only podcast we know of where girls talk about industrial automation.
00:00:05.839 --> 00:00:08.400
This episode is brought to you by Inductive Automation.
00:00:08.480 --> 00:00:09.919
It's just Nicky again.
00:00:10.080 --> 00:00:19.440
I am actually recording today with Russell from Overview AI, a company that I met and and I met Russell briefly at Automate this year.
00:00:19.679 --> 00:00:24.000
As uh a thank you to, I will say to Jessica G at NVIDIA for introducing us.
00:00:24.160 --> 00:00:29.039
I got to go um and have do an interview and learn about uh a little bit about their product.
00:00:29.280 --> 00:00:41.520
And I was uh surpr I can't I shouldn't say this, but I was surprised that I was impressed because I've been um, you know, we've all been hearing about AI vision systems for a really long time now.
00:00:41.679 --> 00:00:45.119
Um, and they all seem really promising.
00:00:45.200 --> 00:00:51.359
Um, and I'm sure they all have their their great features and things, problems that they can solve that weren't solvable before.
00:00:51.600 --> 00:00:57.280
But it's just one of those things like I feel like there were over the last few years a dime a dozen of them.
00:00:57.600 --> 00:01:03.600
And I wasn't really seeing anything that that was particularly like jumping out at me as impressive.
00:01:03.920 --> 00:01:08.640
And I was I was really happy to see um overview and what they were doing.
00:01:08.719 --> 00:01:19.519
Um, and the focus of that particular interview was me looking at kind of their new uh generative AI feature of generating defects for training, which is powered by NVIDIA.
00:01:19.760 --> 00:01:30.159
So they were trying to kind of get, you know, everybody in their ecosystem to get a little bit more uh, I guess, people knowing about what they do and how it's powered by NVIDIA and stuff like that.
00:01:30.319 --> 00:01:36.640
And uh, as you may know, if you've been following me for a while, I've been kind of paying attention to the NVIDIA ecosystem for a couple years now.
00:01:36.719 --> 00:01:39.200
Um, they've taken a bigger role at Automate, which is kind of cool.
00:01:39.280 --> 00:01:42.400
Instead of just, I think last year they didn't have a booth at all.
00:01:42.480 --> 00:01:43.840
They just had a bunch of partners.
00:01:44.000 --> 00:01:50.480
This year they had their own booth and then also like a partner directory um and a tour of a bunch of their different partners.
00:01:50.879 --> 00:02:00.239
So, anyway, with that long introduction, I wanted to get Russell on the show and talk about overview and what he does.
00:02:00.480 --> 00:02:04.159
And so this is a typical episode we're gonna, you know, kind of hear about his journey and everything.
00:02:04.319 --> 00:02:10.719
But as an entrepreneur, we're probably gonna focus a little bit more on his company and what he does and why he's solving the problem that he's solving.
00:02:10.960 --> 00:02:21.919
Um, and then I'm um I just made this uh commitment um as we were preparing for the episode, but I genuinely would love to see a live demo um of the system.
00:02:22.319 --> 00:02:24.560
And I think that you guys would too, as the audience.
00:02:24.639 --> 00:02:25.599
So stay tuned.
00:02:25.759 --> 00:02:29.520
We're gonna start our live demos on LinkedIn again probably next year.
00:02:29.599 --> 00:02:31.599
Um, to be honest, we're already like in November.
00:02:31.680 --> 00:02:35.039
It's crazy how fast 2026 has gone by.
00:02:35.599 --> 00:02:38.639
So, with that, Russell, thank you so much for coming on the show.
00:02:38.800 --> 00:02:39.919
It's great to have you with us.
00:02:40.000 --> 00:02:40.639
How are you?
00:02:40.960 --> 00:02:41.439
I'm good.
00:02:41.520 --> 00:02:42.639
Thanks for having me, Nikki.
00:02:42.719 --> 00:02:44.560
I'm happy to be here, happy to chat.
00:02:44.719 --> 00:02:58.159
Um, and it was great to meet you at Automate and uh appreciate the kind words about some of the stuff that we're working on and and how we're able to um try to differentiate from, as you said, uh a lot of AI vision systems the last few years have been dime a dozen.
00:02:58.400 --> 00:03:10.000
But how how do you build a lasting business and you know, while maintaining, you know, a customer uh focus so that it's it's actually useful and you can get into production, get value out of it.
00:03:10.400 --> 00:03:10.879
Yeah, yeah.
00:03:10.960 --> 00:03:12.240
It's kind of, I feel like so.
00:03:12.319 --> 00:03:23.599
I actually um I may have told you this already, but I started out as a machine vision sales engineer for KeInts in um the beginning of my career, uh sometime between 15 and 20 years ago now.
00:03:23.840 --> 00:03:25.280
And it was new at the time.
00:03:25.360 --> 00:03:29.360
Like the technology was relatively new and it was all rules-based, of course.
00:03:29.599 --> 00:03:32.800
But and and I don't know that this has really changed that much.
00:03:32.960 --> 00:03:36.639
Of course, we've gotten like very much more mature about it since then.
00:03:36.960 --> 00:03:44.560
But vision is one of those things where like the the application, the success of the application always depends on the installation.
00:03:44.719 --> 00:03:46.719
Like there are so many factors that go into it.
00:03:46.800 --> 00:03:51.199
It's not a product that you can just sell and it's, you know, like a vacuum, it vacuumes dirt.
00:03:51.360 --> 00:03:55.599
Like no matter what home you're in, it's gonna vacuum the dirt.
00:03:55.680 --> 00:03:57.199
Um, vision systems are not the same.
00:03:57.280 --> 00:04:00.639
They're they're looking at like it's always kind of a customized problem set.
00:04:00.960 --> 00:04:07.199
And even back then, there were, you know, we would have a catalog that showed all these different applications that were easy to solve.
00:04:07.280 --> 00:04:09.919
Like, oh, check if there's a
Load full transcript
cap on the bottle or not.
00:04:10.159 --> 00:04:13.919
And at the time that I was selling vision systems, those were super easy to do.
00:04:14.080 --> 00:04:18.240
Like it was rare that we found a cap that wasn't detectable by a vision system.
00:04:18.480 --> 00:04:29.279
But I was in this in in the Bay Area, and so I was working with a lot of kind of cutting-edge technology companies that were not buying a system to see if a cap was on or not.
00:04:29.519 --> 00:04:35.360
They were trying to solve a problem that was very difficult to solve with vision or any other technology for that matter.
00:04:35.519 --> 00:04:43.519
And vision systems at the time were so freaking expensive that like you really wouldn't want to use one unless you had a problem that was otherwise difficult to solve.
00:04:44.000 --> 00:04:53.759
And I have a feeling that we're still in this phase where there are the like the frontier applications now are the ones that have been difficult to solve so far with existing vision technology.
00:04:54.000 --> 00:05:05.839
Um so, anyway, with all that being said, uh I yeah, let's just start with our first question because otherwise I'm gonna get into like all kinds of crazy stuff right off the bat without even without the audience even knowing who you are.
00:05:06.160 --> 00:05:13.279
So if you could start us off with giving an introduction of yourself and like how did you get into what you're doing now?
00:05:13.519 --> 00:05:22.800
Um and in particular, like for us and our audience, we like to know how the peck people got into industrial automation as a field, because most people don't even know about it.
00:05:22.959 --> 00:05:25.439
Um so I'll I'll let you take the floor, Russell.
00:05:26.240 --> 00:05:26.639
Thank you.
00:05:26.720 --> 00:05:28.160
Yeah, I'm I'm Russell.
00:05:28.240 --> 00:05:31.439
I'm I'm one of the co-founders um of Overview AI.
00:05:31.759 --> 00:05:55.040
Uh we've been around for almost eight years now, and really with the with the focus to um make uh machine vision uh as easy as possible for the end user to to ultimately get uh those cameras into production to reduce scrap, ultimately improve yield, and and produce better quality in the factories.
00:05:55.279 --> 00:05:59.519
And uh that that's really been the mission um from the early days.
00:05:59.759 --> 00:06:10.959
And the reason why we started it was kind of a very clear idea that AI was advancing, especially in 2018-2019.
00:06:11.120 --> 00:06:18.480
Everyone in Silicon Valley and in San Francisco, where where we're based, thought that self-driving cars were right around the corner.
00:06:20.399 --> 00:06:23.680
Two of my co-founders were at Tesla.
00:06:23.839 --> 00:06:32.800
And at Tesla, they were combining on one hand, ramping up manufacturing um extremely quickly as they were you know growing like crazy.
00:06:32.959 --> 00:06:39.199
And on the other hand, they had a big self-driving car team trying to put self-driving into the Teslas back then.
00:06:40.160 --> 00:06:45.439
Um, self-driving cars took a lot, were a lot harder and took a lot longer than we all thought.
00:06:46.079 --> 00:07:09.360
However, there was a lot of optimism back then, and so this jump from my co-founders at Tesla of like, can we just apply this self-driving car technology onto the factory floor uh to create value was was very um was not a very large leap to take when you were in the right place at the right time, especially around this era in Tesla.
00:07:09.519 --> 00:07:34.800
And so then they pulled me in, and I had been at a self-driving car research center at UC Berkeley, where I went to school, um, and it was immediately obvious that this was transferable and in fact uh significantly easier to do um than putting a soft driving car on the road would be to put AI into a camera that can do uh valuable things in a factory.
00:07:34.879 --> 00:07:36.959
And so we started with defect detection.
00:07:37.040 --> 00:07:41.759
So AI-based defect detection uh in the industrial automation space.
00:07:41.839 --> 00:07:43.120
So that's how we got into it.
00:07:43.360 --> 00:07:51.360
And so we we all all three of us, and then we met up with the fourth guy who was a camera hardware expert, and we we started over for you.
00:07:52.319 --> 00:07:55.519
And your background is in the software side of things as well, right?
00:07:55.680 --> 00:08:03.600
Or can you tell us like what kind of engineering um did you get into and what did you think you were gonna do in your career before you ended up here?
00:08:04.160 --> 00:08:07.360
Yeah, so I studied electrical engineering and computer science.
00:08:07.519 --> 00:08:13.120
Um, and I thought I was gonna be a software engineer or maybe even an AI researcher.
00:08:13.360 --> 00:08:13.600
Okay.
00:08:13.920 --> 00:08:46.960
And I ended up um after um leaving, after graduating and leaving the lab, we um I ended up working at Salesforce on AI essentially infrastructure for uh data center optimization, which is slightly tangential, but I think there was at the time in the research, there was a little bit of a disillusion in how long it would take to get these AI models um to work for self-driving cars because there was just you had to get 99.99999%, otherwise people die.
00:08:47.200 --> 00:08:55.919
And that challenge um wasn't as interesting as getting that, you know, these core kind of discoveries done, and now you're solving a tail problem.
00:08:56.639 --> 00:09:18.159
And um and then when I was um connected with Chris and Austin through Tesla, and they pitched me on this idea that you could, you know, apply this in a much more controlled environment, I was immediately not only it made sense, but I felt like I we had the technical ability to to build this company.
00:09:18.480 --> 00:09:20.480
Had you ever been inside of a factory before?
00:09:20.720 --> 00:09:23.759
Um, I had been do done like a jelly belly uh tour.
00:09:23.919 --> 00:09:24.080
Okay.
00:09:24.480 --> 00:09:28.960
So I'd seen, and that's a quite um automated facility in um in the Bay Area.
00:09:29.120 --> 00:09:29.279
Yeah.
00:09:29.519 --> 00:09:36.720
Um so I had seen some, but it was not um, I would not by any means say I had a lot of manufacturing experience.
00:09:37.039 --> 00:09:46.320
Yeah, it's definitely like a hidden world, I think, to most people, unless people have seen like how it's made, or if they've been lucky to be on a cool factory tour like that.
00:09:46.480 --> 00:09:50.559
I went on a factory tour of a of a coors brewery in Mexico when I was in college.
00:09:50.799 --> 00:09:57.519
Um, and so that was like my one and only glimpse into any kind of automated line um manufacturing.
00:09:58.240 --> 00:09:59.759
It completely caught my interest.
00:10:00.000 --> 00:10:05.360
When you went to Jelly Belly, did you ever think like was that before you joined um Overview or was that after?
00:10:05.919 --> 00:10:06.399
That was before.
00:10:06.559 --> 00:10:10.000
I actually went again after and I had a very different I had a very different feeling.
00:10:10.240 --> 00:10:10.879
I know, right?
00:10:12.240 --> 00:10:16.639
You started looking in all kinds of places after that, especially once you've done vision.
00:10:16.799 --> 00:10:31.919
Um, like I it's been I don't I'm I don't I'm not as obsessed about it now, but like I couldn't go to the grocery store without pointing out like inconsistent labels or like barcodes that weren't looking right or like laser marked things that were I was like who who sold this thing?
00:10:32.159 --> 00:10:43.440
Um I think the last thing I did, I I posted like sometime last year, maybe I bought uh a case of Stella and like a bunch of the labels were totally misaligned.
00:10:43.519 --> 00:10:44.480
And I was just like, how?
00:10:44.559 --> 00:10:46.000
I think it's 2026.
00:10:46.080 --> 00:10:48.240
Like, how have we how have they not fixed this by now?
00:10:48.399 --> 00:10:49.759
Early vision can fix that.
00:10:49.919 --> 00:10:51.679
Like rules-based vision can fix that.
00:10:51.759 --> 00:10:53.039
That's super easy.
00:10:53.200 --> 00:10:55.919
Um I mean, I I couldn't agree more.
00:10:56.080 --> 00:11:04.320
When I, for example, um recently I had a a wearable electronics that um where my battery died uh out of nowhere.
00:11:04.639 --> 00:11:09.200
And I immediately called the quality team and said, I can solve your problem.
00:11:09.279 --> 00:11:11.120
And now they're they're a major customer of ours.
00:11:11.360 --> 00:11:16.960
So so I kind of not only do I look and it annoys me, like labels, whatever.
00:11:17.039 --> 00:11:19.360
You go to a Home Depot, you go to a Costco.
00:11:19.600 --> 00:11:28.320
But if it's something I see and I use and I'm like, oh, that's a problem, then I'm immediately looking at that as a sales opportunity for for overview.
00:11:28.480 --> 00:11:32.960
And uh, you know, this sort of hit close to home with the battery dying.
00:11:33.039 --> 00:11:38.399
But then turns out, you know, if I if I'm experiencing that as a consumer, there's a good chance they're aware of it and trying to solve it.
00:11:38.480 --> 00:11:49.519
And we happen to have a solution today that's uh very mature and the right and really the right solution for a lot of um a lot of these sections, whether it's electronics or cosmetic or for consumer.
00:11:49.840 --> 00:11:50.000
Yeah.
00:11:50.080 --> 00:12:07.519
And one of the things that I so back when I used to do this, it was like big, you'd have to put together obviously you still have to do this, like lenses and lights, and and it's probably a little bit less now with the AI because you can compensate for for different types of images um and and probably more variability than the rules-based stuff in the past.
00:12:07.759 --> 00:12:12.159
But you'd have to really architect the whole system and then the the the price of those things was insane.
00:12:12.399 --> 00:12:27.600
Like if you needed a color camera and you needed like five megapixels or something, you'd you'd be looking at like tens of thousands of dollars, multiple tens of thousands of dollars for a system, um, not including the installation and and everything like that.
00:12:27.840 --> 00:12:30.159
And so sometimes it would be like, oh, I can fix this problem.
00:12:30.240 --> 00:12:34.080
And they'd be like, well, it's not, it's not a big enough problem for us to spend all this money on.
00:12:34.240 --> 00:12:40.559
And one of the things that did impress me in particular about aside from your technology, was your business model.
00:12:40.960 --> 00:12:51.440
Tell me a little bit about like why are you guys not doing a SaaS subscription and making it as difficult as possible for people to know what the price of the solution is gonna be up front?
00:12:51.600 --> 00:12:51.840
Like that.
00:12:51.919 --> 00:12:53.679
I feel like that's kind of the history of vision.
00:12:53.840 --> 00:13:01.360
It was like, oh, what's the one of my life models that I've literally applied to almost everything since then is the answer to everything is it depends.
00:13:01.519 --> 00:13:13.360
Because you could just never upfront tell anybody what a vision solution was gonna look like or how much it was gonna cost until you really like put piece together all those variables and then probably also tested it in the lab.
00:13:14.240 --> 00:13:17.759
Um and so like you couldn't even ballpark somebody really.
00:13:17.919 --> 00:13:22.720
But you guys have like a very transparent pricing structure and it's like a one-time thing.
00:13:22.879 --> 00:13:27.840
So I bet that call is pretty easy when you say, Hey, I saw this problem, I can fix it.
00:13:28.399 --> 00:13:44.720
And if they ask, like, it's like you actually know roughly what it's gonna cost or you know how it's gonna be implemented, and people only have to pay for it once they don't have to keep paying for it for the rest of their life, which
I feel like I just always associated with like, hey, if you're gonna put AI into this thing now, now you're probably gonna charge for software.
00:13:44.879 --> 00:13:47.200
I mean, you come from the Salesforce world, right?
00:13:47.360 --> 00:13:51.279
So SaaS is everything where it was for a long time.
00:13:51.519 --> 00:13:55.440
What made you take a contrarian approach to that from a go-to-market perspective?
00:13:56.159 --> 00:13:57.600
So it's a great question.
00:13:57.679 --> 00:14:04.320
We we initially started off charging uh our recurring revenue model, like a lot of people do.
00:14:04.559 --> 00:14:05.039
Yeah.
00:14:05.600 --> 00:14:09.200
A few years into it, we realized one that creates friction.
00:14:10.080 --> 00:14:21.279
Two in a factory, generally the budgets are designed to take uh CapEx expenditures and turn it into OpEx savings.
00:14:21.600 --> 00:14:27.919
So if you're doing anything that's outside of that model, you're gonna have resistance.
00:14:28.559 --> 00:14:38.240
However, our cameras are very, very, very, very good at turning CapEx into OpEx savings, reducing scrap, increasing yield, automation efficiency.
00:14:38.480 --> 00:14:46.960
And so if you instead of trying to fight for recurrent revenue, we really um dove into two things.
00:14:47.120 --> 00:14:52.879
One, making our products excellent so that we could win a land and expand motion.
00:14:52.960 --> 00:15:11.120
We we believe in our products so much that if we can sell you one, we think that there's enough problems in a factory that will continuously occur that you will can you will keep buying from us and we will make we will create long-term customers who don't just buy one product and we can get re-occurring revenue from them by solving more problems.
00:15:11.360 --> 00:15:11.519
Yeah.
00:15:12.000 --> 00:15:25.759
And that's been one of the best decisions we've ever made because it's allowed us to scale a lot faster with a lot less friction, and it forced us to make our products so good that people would keep buying them.
00:15:26.159 --> 00:15:35.360
And then we believed our products were so good, and we the value proposition was so clear that we felt comfortable to have our pricing be transparent.
00:15:35.519 --> 00:15:40.720
You can go onto our website and we have a shop and you can buy it with your credit card with a clear price tag.
00:15:41.440 --> 00:15:45.840
And so, but to be able to feel comfortable doing that, we needed the products to actually work.
00:15:46.320 --> 00:16:05.519
And then the second thing that happened was when we went into this land and expand motion, our business became predicated on how quickly you can get that first camera into production by proving value and working so that they then feel comfortable to buy more systems.
00:16:05.600 --> 00:16:13.200
And so it really made us focus on uh um uh speed of install and uh speed of deployment.
00:16:13.279 --> 00:16:22.240
Uh and our systems ultimately are self-service, so it means we try to make the quality of life of the users as easy as possible.
00:16:23.039 --> 00:16:27.840
And you made a good point of like there's a lot of th factors that go into a vision system.
00:16:28.799 --> 00:16:33.600
I I like to think of a vision system as a product.
00:16:33.840 --> 00:16:40.399
People try to sell it like a product, but it's really disguised because it's a project, right?
00:16:40.559 --> 00:16:44.799
So you're you're doing an engineering project and you're just disguised as a product.
00:16:45.200 --> 00:17:00.399
And we kind of understand that, but want that project to be as simple and quick in each step of it as possible, so that we can then, you know, get them into production happy and getting a return on investment as quick as possible.
00:17:00.720 --> 00:17:06.640
Uh so part of what I thought too when I saw this was like, okay, it's been a long time since Vision started getting installed and stuff.
00:17:06.720 --> 00:17:19.759
So I would imagine there's a good amount of opportunity to take your camera and pop it into an existing installation of an older vision system that may not be performing up to par, or because it's you know, older technology.
00:17:19.920 --> 00:17:32.799
Um and then you don't really have to solve for the entire project all at once, because hopefully the you know existing system may have some of the things right, like the lighting, the position of the camera, the presentation of the parts, things like that.
00:17:33.119 --> 00:17:42.960
Um and that's I I guess kind of different from solving an entirely new application that has never had a vision system doing that.
00:17:43.200 --> 00:17:51.200
Um do you see how much do you see uh uh kind of like replacing older technology versus completely green-field applications in in your business?
00:17:51.519 --> 00:17:52.000
Yeah.
00:17:52.319 --> 00:17:58.640
So there's there's a lot of value in upgrading existing systems because they're already installed.
00:17:58.880 --> 00:18:04.880
We we made a conscientious effort to not focus on that, even though it would seem very intuitive too.
00:18:05.200 --> 00:18:15.440
And I want to there's a there's a few reasons why, but I think that something that stuck with me a few years ago was I was interviewing someone from KeIns actually in in Mexico.
00:18:15.680 --> 00:18:27.359
And I don't, I can't verify this stat, but they said something like 97% of the sales volume from KeAnts in Mexico was coming from greenfield applications.
00:18:27.519 --> 00:18:30.240
And only 3% was from retrofits.
00:18:30.400 --> 00:18:30.559
Yeah.
00:18:30.799 --> 00:18:33.680
And so you know, it made us think long and hard.
00:18:33.759 --> 00:18:40.960
It's like if we they're very different products to retrofit a camera is a very different product than to have your own set of products, which we do have.
00:18:41.200 --> 00:18:46.799
And so it's like what were we, it's hard to do two things very well when
you're a startup and you're growing.
00:18:46.960 --> 00:19:07.759
And so we made the decision to focus on an ecosystem of our products so we could control the hardware and then highly optimize the AI to not only be the most accurate in its category, but also have a lot of tools to make it very easy to use because we we we control the whole life cycle of it.
00:19:08.000 --> 00:19:14.640
But when you're retrofitting a camera, you don't know in advance what that camera's gonna be, the resolution, the connection.
00:19:14.720 --> 00:19:16.960
And so there's a lot more customization.
00:19:17.119 --> 00:19:29.039
And with more customization comes less uh friendliness because we we can't be as opinionated and therefore uh make it as easy to use because we just don't have that information in advance.
00:19:29.680 --> 00:19:30.480
Interesting.
00:19:30.880 --> 00:19:32.160
Yeah, no, that's a good point.
00:19:32.240 --> 00:19:34.160
That's kind of the opposite of what I was thinking.
00:19:34.400 --> 00:19:43.119
Um so when do you guys work directly with the customer to do the installation when it's a greenfield project to like select the product and set it up and test it?
00:19:43.279 --> 00:19:46.079
Or do they is it a completely self-serve, like they do that themselves?
00:19:46.240 --> 00:19:47.039
How does that work?
00:19:47.680 --> 00:19:51.119
So customer success is is important in any business, right?
00:19:51.279 --> 00:19:54.720
You need to make sure and customer enablement, you need to make sure that they're happy.
00:19:54.880 --> 00:19:59.519
And especially vision is still has characteristics of being a project.
00:19:59.759 --> 00:20:05.519
And and we fundamentally are and our applications engineers and vision engineers are experts in that.
00:20:05.599 --> 00:20:09.359
And so we build self-service products, right?
00:20:09.519 --> 00:20:12.000
So everything can be done 100% by the customer.
00:20:12.240 --> 00:20:25.039
However, for a new customer, we're often gonna hold their hand through it, we're gonna help them with the lensing, the uh, the lighting, um, the setup, just to make it so that they have um the highest chance to be successful quickly.
00:20:25.279 --> 00:20:32.240
What tends to happen is that for two to three installs, they don't even want our help anymore because they know how to do it and the self-surpose aspect kicks in.
00:20:32.640 --> 00:20:36.480
But we prefer not to take it to chance that they could mess up the project.
00:20:36.559 --> 00:20:50.960
So we're there to advise, to consult, and to help from everything from the setup to the outputs of the camera because we have a very flexible um output so we can support all the PLCs, all the MES systems, custom dashboards, et cetera.
00:20:51.039 --> 00:20:55.440
And so we want to make sure that they they know the optionality they have, so it's as smooth as possible.
00:20:56.000 --> 00:21:01.359
Um, however, we don't do automation um because that uh is not you know our forte.
00:21:01.599 --> 00:21:04.400
Uh but we we do want them to be very as successful.
00:21:04.480 --> 00:21:16.000
So we're gonna, you know, especially with these green fields, we're gonna make sure that it's um has the highest chance of success so that and it's the fastest and optimize optimal way to do it so we can continue doing business with them.
00:21:16.480 --> 00:21:17.039
Yeah.
00:21:17.279 --> 00:21:20.319
If you had um, so you're eight years into this.
00:21:21.039 --> 00:21:30.559
Uh what do you feel like is kind of the next untapped, or not untapped, but like if you were to look at your plan to kind of grow as a company?
00:21:30.640 --> 00:21:38.640
Um, and I feel like a lot of success in the marketplace also kind of has to do with having an ecosystem, not gonna do the automation.
00:21:38.799 --> 00:21:47.279
What are you guys looking for in terms of if somebody's listening to this episode and they're in the industrial automation industry and they're not an end user customer, like they don't work in a factory.
00:21:47.359 --> 00:21:52.160
Um, are you looking for any kind of like partnerships or or starting to work with like OEM?
00:21:52.559 --> 00:21:55.279
Play in the sandbox with everybody else that's already in the industry.
00:21:55.599 --> 00:21:56.640
Yeah, it's a great question.
00:21:56.799 --> 00:21:58.880
Something I spend a lot of time thinking about.
00:22:00.240 --> 00:22:15.039
The the way that I recently see the world is that you have these tools like ChatGPT and Claude from Anthropic that are are making incredibly difficult and specialized work accessible to someone with no experience.
00:22:15.279 --> 00:22:18.880
I've never studied finance, I can make a financial document.
00:22:19.039 --> 00:22:28.000
I've never studied law, I can draft, you know, a legal agreement, I can um do CAD design now with the latest Chetch T model.
00:22:28.480 --> 00:22:33.200
Um and so it's really democratizing some of these engineering um tasks.
00:22:33.440 --> 00:22:36.559
And how does this translate to our industry?
00:22:37.359 --> 00:23:15.359
And I see it as a non-technical person can set up a machine vision system end-to-end if you use an AI agent, if you identify the core steps to being successful in the same way that ChatGPT does with a hardware in the loop system, you can democratize it to a very large distributor uh and value-added reseller and integrator network that already exists today, who a lot of them are very wary to touch machine vision because one, they get bogged down in it.
00:23:15.839 --> 00:23:41.440
And two, they don't have the expertise to qualify it, to say yes or no, because oftentimes saying no is very important, or you deliver something that doesn't actually work because it's too complicated, or there's some little thing there that they didn't account for, or there's scope creep, and you just you do have an unsuccessful project, and then you're wary for the next project.
00:23:41.759 -->
00:24:02.319
But we believe that uh, you know, and the first step towards that is our OV Spark, which is the first camera that has an onboard agent, will allow us to blow open the doors to get distributors and um integrators very successful at uh using our products, even if they're non-technical.
00:24:02.880 --> 00:24:12.880
And then as part of that, we have a companion product called the OV feasibility studio, which is gonna help non-technical people describe the application.
00:24:13.119 --> 00:24:18.640
And the job of that feasibility studio is to tell them when to say no.
00:24:19.200 --> 00:24:37.599
And if they say yes, it's it's a full simulated environment of this is the light you need, this is the lens you need, this is the camera model you need, and it creates a full project plan with the quote that they can send to give the customer confidence that the distributor knows what they're doing, and that's all automatic.
00:24:37.839 --> 00:24:46.960
And so, with those sort of principles, I think that there's gonna be a new paradigm for machine vision um with through these channels.
00:24:47.680 --> 00:24:48.799
That is really interesting.
00:24:48.880 --> 00:24:49.279
I love that.
00:24:49.440 --> 00:24:56.960
Um I've actually been in sort of the AI space also for like you you were mentioning back in like 2018 in the Bay Area.
00:24:57.119 --> 00:25:18.640
Um, that is I was working for an AI startup at the time that was doing um AI and supply chain, so for predicting demand for unreleased products, uh using big data and like Twitter sentiment and um weather data and all kinds of things like that to try to predict like how many people are gonna go to Target to buy this new movie when it gets released, when it's there's no historical data for how it sells.
00:25:18.960 --> 00:25:34.640
Um and we were doing a lot of uh data analytics, and at the time you had to be a data scientist or at least a sort of business um, you know, technical business user to be able to write SQL queries and things like that to do that type of work.
00:25:34.799 --> 00:25:44.160
Um so it was very siloed to, you know, there was usually a big bottleneck in these companies for who could get a dashboard made, for instance, right?
00:25:44.240 --> 00:25:47.759
I I need this dashboard to look at this data to be able to solve this problem.
00:25:47.920 --> 00:25:55.680
And I am now gonna go to my, you know, data person or my SQL person or whatever and see when they could get me this dashboard.
00:25:56.000 --> 00:25:58.640
And now, of course, it's very like self-serve.
00:25:59.039 --> 00:26:07.759
You can ask, you know, pretty much any application nowadays for uh well, I mean, we're looking at this in HMIs as well.
00:26:07.839 --> 00:26:21.759
Like we just did a demo at PacExpo for WinTech where you could just ask the HMI for a visualization of any given data for like let you know, let me see the OE for this machine for the last month, or you know, different things like that.
00:26:21.920 --> 00:26:28.240
So you don't have to have these hard-coded, I can only see the dashboards that somebody came up with when we installed the machine.
00:26:28.480 --> 00:26:34.400
Um so that's kind of been in the in the works for a long time in different areas.
00:26:34.720 --> 00:26:41.200
I've always been kind of skeptical of the you don't need to be an engineer to do engineering because now there's these tools that tell you what to do.
00:26:41.359 --> 00:26:56.079
Because if you don't know enough engineering to know if the tools are right or wrong, like, you know, kind of like not the same as with self-driving cars, but in the manufacturing industry, there can be some catastrophic results if you do some bad engineering on the on the plant floor.
00:26:56.240 --> 00:27:00.000
So I'm gonna give a little shout out um to our friends at Vincian here.
00:27:00.160 --> 00:27:09.039
I happen to be drinking uh tea from one of their wonderful cups that they gave me that says artificial intelligence, real manufacturing work.
00:27:09.200 --> 00:27:28.319
Um, and I'm a really big fan of a lot of what they do, including their there uh also have like an online store where you can put together a system and you can price it and you can buy it online, um, which price transparency and sort of the ability to buy things in our industry um has been a frustrating challenge uh for me.
00:27:28.480 --> 00:27:34.640
I actually worked at an early stage startup also last few years that was trying to solve one of those problems in the distribution space.
00:27:34.799 --> 00:27:38.240
Um, because it traditionally has been very difficult to buy things in our industry.
00:27:38.319 --> 00:27:44.880
Like you got to call a distributor and get somebody out to give you a quote, and you know, you got to wait for the PDF and you got to set up an account.
00:27:45.039 --> 00:27:49.039
And you typically have no idea what things are gonna cost until you talk to somebody.
00:27:49.279 --> 00:28:00.480
Um anyway, but I one of the first articles I read from Venction was like, you don't need to be an engineer to build machines because our website like walks you through it.
00:28:00.880 --> 00:28:18.720
And I I don't like big claims like big sweeping claims like that, like or things like, oh, uh we're in the post-plc era now because you know AI-enabled computers can now do they can like pan plan your emotion paths and logic and stuff like that.
00:28:18.960 --> 00:28:20.480
And I think there's nuance to these things.
00:28:20.640 --> 00:28:25.119
Yes, there's a lot of leaps that you can make with that, but is the PLC gonna go away?
00:28:25.359 --> 00:28:27.759
No, I I don't really think so, right?
00:28:27.920 --> 00:28:30.240
But we want to say these marketing terms.
00:28:30.319 --> 00:28:35.839
But I think one of the coolest things about AI right now in our industry is like at least lowering that barrier.
00:28:35.920 --> 00:28:45.200
Like you don't need to have as
many years of accumulated experience and expertise to be able to tackle a lot of these things now with the help of AI like guiding you.
00:28:45.359 --> 00:29:11.279
Um, and that is actually one of the things that I that I initially was pretty impressed with um, because I was shown uh the the sort of process of doing the generated feature or defect detection so that you can train your vision system without having a bunch of examples of the bad parts, which was a big part of what my job was qualifying these applications back in the day, was I needed to get examples of almost all the defects.
00:29:11.599 --> 00:29:16.480
And to make sure that, you know, we test them in the lab and make sure that we could actually catch all the defects.
00:29:16.559 --> 00:29:21.200
Um, and then we had to obviously manually train the model to catch all these defects.
00:29:21.440 --> 00:29:24.559
Here's a quick message from our sponsor, Inductive Automation.
00:29:24.880 --> 00:29:30.960
Every path, every project, every goal, every solution begins with an it.
00:29:31.759 --> 00:29:32.799
What is it?
00:29:33.440 --> 00:29:35.680
It is your breakthrough moment.
00:29:36.160 --> 00:29:39.440
It is when you build a foundation for innovation.
00:29:40.000 --> 00:29:46.319
It is your best idea that will solve unique challenges and revolutionize a process.
00:29:46.720 --> 00:29:51.839
It is when you integrate new technologies that will transform entire industries.
00:29:52.079 --> 00:29:57.759
If you have a vision for where it should end, then we know where it should begin.
00:30:02.319 --> 00:30:04.400
It starts with ignition.
00:30:04.640 --> 00:30:08.079
Thank you to Inductive Automation for sponsoring automation, ladies.
00:30:08.400 --> 00:30:10.240
Let's go back to the episode.
00:30:11.279 --> 00:30:18.079
Can you, I guess, walk us through all the different ways that you guys use uh generative AI or AI?
00:30:18.160 --> 00:30:31.200
Um, not in the in the actual inspection part itself, but you've mentioned like several use cases now, just in the rest of the business, setting it up and things like that.
00:30:31.920 --> 00:30:39.920
I don't know if that's the right question or or how you want to like talk about that, but yeah, I want to talk about that.
00:30:40.559 --> 00:30:55.519
How are we lowering the barrier and all this like time to market and time to value and all that kind of stuff, like using AI, um, aside from what you just mentioned, which is of course, now you don't necessarily have to have a vision specialist on staff or bring in a systems integrator every time you need to set up a new camera.
00:30:56.240 --> 00:31:03.839
Yeah, I think time to value is a great word for uh why generating defects is useful.
00:31:04.240 --> 00:31:43.839
We we've really crossed this barrier in the last year or so where you can generate such hyper realistic defects because you have these world foundation models that understand the material, the texture, how the physics
interacts with it and the light, that you can create a dent in metal or a bubble in glass or laminate that is so realistic that not only can you then send that to your various inspection tools, you know, your AI inspection tools or even your classical tools, uh, and that's big because you can get that data and train your model so much faster.
00:31:44.240 --> 00:31:51.519
But what's oftentimes the longest period of lag to get to that proof of value is you need to validate the system.
00:31:51.599 --> 00:31:54.559
You need to make sure that the system's working before you turn on the automation.
00:31:55.279 --> 00:32:17.279
And if you can if you can generate a bunch of scenarios of things that can go wrong and then back test those against your AI model to prove that it's catching something, uh you can feel not only you can have a data-driven approach to getting validated and qualified faster.
00:32:17.519 --> 00:32:20.400
So, for example, let's take an example like a scratch.
00:32:20.880 --> 00:32:46.640
If I can put a scratch on my part and then make the scratch small and big and move it around to every single spot on the part, and then run those 200 images through your inspection as a back test or as you know, a simulated environment, and it catches all of those, uh, you can then have the confidence that when you turn it on, it'll replicate that in the field.
00:32:46.720 --> 00:33:19.039
And so it really becomes a game changer in in you know, reducing the time to value on both the front end side of uh the AI, which is collecting the data, because you can generate it, or if you have rare defect modes, you can take one of them and expand upon that by generating similar things, smaller, bigger, uh, and then, or just you know, create scenarios that you haven't even seen before that you expect to be able to come because that person has that tribal knowledge from a previous generation of products that this could occur.
00:33:19.680 --> 00:33:22.319
Um and then of course, yeah, we talked about the validation part.
00:33:22.559 --> 00:33:27.599
So that's on the generative AI of the the image generation, right?
00:33:27.680 --> 00:33:30.400
The we call it synthetic data generation on the image side.
00:33:30.640 --> 00:33:32.960
For us, we call it our defect creator studio.
00:33:33.200 --> 00:33:59.039
However, there's the back half where you can generate uh using these like AI agents uh um useful uh visualizations, the business intelligence, the manufacturing intelligence, the HMIs, all for the operator, the quality manager, the plant manager to use that data as effectively as possible to not only reduce scrap, but ultimately to drive up yield.
00:33:59.119 --> 00:34:19.920
Uh for example, if I say I want a dashboard that is giving me a Pareto chart that's then split shift by shift to understand what's going wrong, where to focus my continuous improvement efforts, and then you find the number one failure mode and you want to know did I even fix it,
you can use that camera to see over time if you fixed it.
00:34:20.000 --> 00:34:23.440
And if you have, great, you go to the number two issue, the number three issue.
00:34:23.679 --> 00:34:35.840
And that is a much faster way and a more data-driven way to uh uh drive higher yield, which is good for uh not only for the margins, but also for the environment to waste less scrap is is is hugely important.
00:34:36.159 --> 00:34:43.199
Um and you it's very hard to improve what you can't measure, and this is just a way for you to measure now your improvements.
00:34:44.000 --> 00:34:44.559
Yeah.
00:34:44.800 --> 00:34:56.480
I remember I um I had to do a training on a vision system once, and I guess they had such a tight budget that they didn't even install a screen to see what was going on with the system.
00:34:56.800 --> 00:35:01.760
Like it was just it all it required was a monitor, like a basic computer monitor.
00:35:02.079 --> 00:35:09.519
Um and they had bought an old vision system from Keynes, so not the latest and greatest with a with a lot of the new features.
00:35:09.599 --> 00:35:16.000
They Keynes' like model, at least back then, was kind of like if you want you want a cheaper product, you can buy an older product.
00:35:16.079 --> 00:35:18.880
They don't really make like cheaper models, right?
00:35:18.960 --> 00:35:22.960
It's like we're gonna keep the existing generation around and that's gonna be the cheaper one.
00:35:23.119 --> 00:35:25.920
We may lower the price of it when we come out with a better product.
00:35:26.239 --> 00:35:41.840
But uh yeah, it was it was an injection molding facility, and they had A bought the wrong camera because it was just like they their budget was so tight, and I guess there was miscommunication in it, it was sold to a systems integrator by somebody like out of the territory, and they bought totally the wrong thing.
00:35:41.920 --> 00:35:48.079
But I just remember thinking, like, how why would you invest in this and you don't even want to see what is going on?
00:35:48.239 --> 00:35:54.639
Like, you're gonna not spend a couple hundred bucks or whatever it may cost to get a monitor.
00:35:54.960 --> 00:35:59.199
Um you just what want the product kicked out when it's bad?
00:35:59.760 --> 00:36:08.880
But I I was like, I was just kind of blown away that like not only did they not even want to see, they didn't care to see what was going on, they were definitely not collecting any data, doing any trending.
00:36:09.039 --> 00:36:13.199
Like it was just is this a good part or is this a bad part?
00:36:13.440 --> 00:36:20.000
Um and they ended up with a system that didn't let any defects through, but it definitely scrapped way too many good parts.
00:36:20.159 --> 00:36:30.960
Um, but again, they didn't really have any good way to use the information that they were getting from the vision system to improve anything, other than just not sending a bad part through.
00:36:31.039 --> 00:36:41.039
Um so it was really, I think the the thinking back then was can I replace a person that would otherwise have to look at this for quality inspection and just say, is this gonna pass or not?
00:36:41.119 --> 00:36:43.199
Like can we send this on to our customer?
00:36:43.360 --> 00:37:00.719
Um, so I'm hoping that more facilities out there are really thinking about it in the in that sense of looking at what data can we gather from this to improve our operations in the long run and the quality of this product and the yield and all of that, and not just, hey, let's make sure that we don't send a bad product out the door.
00:37:00.960 --> 00:37:09.119
Um Do you find that that that HMI I know that's something that you guys just recently uh improved or released, right?
00:37:09.360 --> 00:37:16.000
Is some additional um ability to look at the information that you need on the plant floor um from that perspective.
00:37:16.159 --> 00:37:24.719
Can you tell us a little bit more about that um in terms of the customer demand that drove that or any trends that you're seeing um aside from what you just mentioned?
00:37:25.039 --> 00:37:35.199
Yeah, I think that there's I think I mean I want to live in a world where we're using less energy to produce things, we're less wasteful, and we make better things.
00:37:35.360 --> 00:37:41.519
And so, you know, making better things, a vision system helps make better things because you you throw stuff away when it's bad.
00:37:41.760 --> 00:37:55.679
But it's much more exciting if you can actually make the same things for less energy by having a higher yield and you know, reducing scrap, because that's like a real, there's a real benefit to that for the planet and also for the factories on from a you know a return on investment perspective.
00:37:55.920 --> 00:38:09.519
But to access that, the only way is to use the data that you have to drive better factory processes, continuous improvement, and just make you know, to improve your automation or your processes.
00:38:10.079 --> 00:38:21.599
And so uh to me, it's always it's been like if you can make that data more accessible, more customizable to their scenario, and then more in their face, they're gonna use it and drive better decisions.
00:38:21.760 --> 00:38:43.920
And so as you you mentioned, right, with these tools, you with uh these agentic sort of dashboarding tools and HMIs, it's become so much easier that it's it's such it's a kind of a small leap to to push that front and center of the customer so they get the full value of you know this intelligence that's sitting on our factory floor.
00:38:44.239 --> 00:38:49.760
And you know, we we actually just display a web page with that through our camera, which is on the local web server.
00:38:49.920 --> 00:39:02.639
You can display it on an HMI, for example, that WineTech sells, or you can display it um on a laptop, or you can be in the office and go to the IP address of the camera, wherever, you know, if they're on the plant
network to see it there.
00:39:02.719 --> 00:39:04.400
And you can have different types of dashboards.
00:39:04.639 --> 00:39:12.559
But ultimately, I want to drive towards that future of higher yield and less scrap so you can make things more efficiently.
00:39:12.960 --> 00:39:29.760
Yeah, that's one of the things that we also kind of, you know, from an A, and we're considered kind of an old school HMI manufacturer because we've been making those screens, the touch screens, the traditional HMIs that just sit on the machine themselves for the operation of the machine, but then also, you know, trending and data and all that kind of stuff.
00:39:30.000 --> 00:39:32.480
Um but we have the same kind of philosophies.
00:39:32.719 --> 00:39:36.719
Like there, there are different users of the data that need it in different ways in different places.
00:39:36.960 --> 00:39:49.679
So you may have the screen for the operator, you may have a screen for maintenance person, um, and then you have an entirely different set of data that's being shown to you know the plant manager or uh somewhere else.
00:39:49.920 --> 00:40:00.320
And you need to have some flexibility in where you can see that and what you can do, and ideally not be nickel and dimed for every instance andor every screen that you need to either make or display or whatever.
00:40:00.480 --> 00:40:02.960
Um, so I love that flexibility because it is really important.
00:40:03.119 --> 00:40:11.039
If you're gonna really get value out of that data, it's not a it's not a one size fits all model as to what data is useful where.
00:40:11.360 --> 00:40:18.239
It's there's a number of different types of applications where that data should be served and available and useful.
00:40:18.800 --> 00:40:29.360
What would you say is, can you tell us like what are the coolest applications that you've seen or that you guys have been able to solve that you think would be fun for our audience to hear about, if any, that you're allowed to talk about.
00:40:29.440 --> 00:40:30.880
We know most things are under NDA.
00:40:31.119 --> 00:40:35.039
Yes, as yeah, factories are always tight-lipped about you know what they're doing.
00:40:35.119 --> 00:40:40.079
And it's always hard to do co-marketing because no factory wants to admit that they have quality issues, you know.
00:40:40.159 --> 00:40:40.239
Right.
00:40:40.480 --> 00:40:42.159
So it's always like, oh, you want to co work it?
00:40:44.000 --> 00:40:46.639
Yeah, we solved they don't want to admit that they had a problem in the first place.
00:40:46.719 --> 00:40:52.000
That's always a uh a funny um, you know, co-marketing challenge, I'll say.
00:40:52.239 --> 00:41:01.199
Um, in terms of applications, um, you know, I think I I'll speak less broadly, but you know, we we have a customer that was doing some parachute stuff.
00:41:01.440 --> 00:41:16.079
So it's always you know exciting when you know that your camera is making sure that that parachute is built correctly, because if that parachute is not built correctly and that ripcord is not, you know, made exactly to spec, you know, that that's some serious consequences.
00:41:16.639 --> 00:41:26.320
So so that's not you know, that's like a you know, a small, it was a small project for us, but it's always reminding me that you know this is this this this matters, right?
00:41:26.480 --> 00:41:31.440
Yeah, or for example, we do um inspections on the brake assemblies of cars on the welding.
00:41:31.760 --> 00:41:40.559
So if there's a weld on a brake assembly of a car, you know, you really want to make sure that that brake is not for the car, it's not gonna break on you.
00:41:40.719 --> 00:41:42.960
Um you you need to stop the car.
00:41:43.119 --> 00:41:52.239
Um or you know, so that's like the safety critical stuff always makes me proud because it's such it has just such a tangible impact on that.
00:41:52.400 --> 00:42:00.159
I mean, there's always some fun stuff when you're inspecting um, you know, things that I like, you know, things that I buy.
00:42:00.480 --> 00:42:18.000
So, you know, without getting into the things that I buy, and I'm like, oh, like I know that I'm buying this, I would buy it anyways, and now I know it's built slightly better uh because of overview is always um exciting, whether it's you know consumer electronics, e-readers, uh wearables, um, that kind of thing is like very, you know, it touches me personally.
00:42:18.159 --> 00:42:21.599
So that that I think I I enjoy that a lot.
00:42:22.159 --> 00:42:29.920
I um I wonder now if what what my NDA extends to, and it's been it's been some several years.
00:42:30.239 --> 00:42:35.599
But I remember I once bought a piece of technology that was very new and I wouldn't have otherwise probably bought it.
00:42:35.760 --> 00:42:40.239
Um because I like to wait a few generations, like when something new and hype comes out.
00:42:40.400 --> 00:42:44.320
Uh but I I just had to buy it because I was like, well, my product helped design it.
00:42:44.400 --> 00:42:50.400
And I'm like, I walk into this meeting with this, with these engineering group like all the time, and they're my I feel like they're my friends now.
00:42:50.559 --> 00:42:54.559
So I'm I've been like I I just wanted to go like wear the thing.
00:42:54.719 --> 00:42:59.760
Um, because you have this kind of personal connection and you kind of know, like, yeah, these people built something really, really super cool.
00:42:59.920 --> 00:43:00.800
Uh so that's cool.
00:43:00.880 --> 00:43:02.480
Have you ever been skydiving?
00:43:02.800 --> 00:43:05.360
I have been once, yeah, on a tandem jump.
00:43:05.599 --> 00:43:06.719
Would you go again?
00:43:06.960 --> 00:43:07.519
Oh, yeah.
00:43:07.679 --> 00:43:13.920
Now that I know some, at least maybe maybe that's if you're using the parachute brand that you guys work with.
00:43:14.719 --> 00:43:15.679
Exactly.
00:43:16.239 --> 00:43:21.920
Um, my CTO at one of my old
startups, he was a big parachute, uh, big um skydiving guy.
00:43:22.159 --> 00:43:38.960
And so I always wonder if there's like um the connection between people that are crazy enough to to build startups, um, if they need those constant like ups and downs and adrenaline rushes and your existential fear that you may your life may be over soon or your your business may be.
00:43:39.119 --> 00:43:55.119
Um, but you guys are doing, I I from what I've heard, and I I hope this isn't any kind of non public information, but um you guys are a profitable startup, which is a an oxymoron in some some ways um from the world that I come from, like VC funded startups usually takes a while to get to that point.
00:43:55.360 --> 00:44:15.360
Um I to me that was also like another big sign of just being impressed, um, that in The world that you guys operate in, um, in the space that you are being at that point at this point, like eight years in, um, without just having to rely on a bunch of strategic investors that are just willing to keep pumping money because they they really want to see the technology succeed.
00:44:15.440 --> 00:44:17.360
I feel like there's a lot of that in our space.
00:44:17.599 --> 00:44:22.000
Um they're not expecting profits for a very, very long time to come.
00:44:22.400 --> 00:44:25.840
And but they're, you know, they're kind of betting on these really big things.
00:44:25.920 --> 00:44:27.519
And that's kind of how I see humanoids.
00:44:27.599 --> 00:44:31.599
It's like they'll eventually be ubiquitous because people just will not stop putting money in them.
00:44:31.760 --> 00:44:41.519
They may or may not be the right solution for lots of things, but if you have enough people willing to lose enough money over a long enough period of time, it'll eventually happen.
00:44:41.679 --> 00:44:51.679
Um, but lots of other things are more dependent on you know investor sentiment and shifts in markets, and it's not this like big moonshot thing that everybody wants to pour their money into.
00:44:51.840 --> 00:44:56.480
Um, and industrial software and hardware tends to be one of those less sexy things.
00:44:56.639 --> 00:44:58.400
Um except humanoids now.
00:44:58.559 --> 00:45:00.239
So well, yeah, that's what I'm saying.
00:45:00.320 --> 00:45:02.400
I don't know that I would call them that exactly.
00:45:02.480 --> 00:45:06.320
Uh they're a little bit more flashy than than your industrial tech.
00:45:06.800 --> 00:45:11.679
Um how long did it take you guys to get profitable, if that's something that you can share, roughly.
00:45:12.480 --> 00:45:18.639
So, I mean, uh the history of our company is interesting because we really did a big pivot during the pandemic, right?
00:45:18.719 --> 00:45:22.400
In the pandemic in the US, a lot of factories shut their doors.
00:45:22.559 --> 00:45:25.280
Uh, no one was investing in in manufacturing.
00:45:25.360 --> 00:45:26.800
They were, everyone's hunkering down.
00:45:27.039 --> 00:45:31.599
A lot
of people couldn't come, the labor, you know, people couldn't come into the factory to work because of quarantines.
00:45:31.840 --> 00:45:36.559
And so it was sort of a time for us to do some rich um in um sort of introspection.
00:45:36.880 --> 00:45:44.639
And I I briefly touched on how we went from a um a recurring revenue business to to do a one-time fee.
00:45:44.719 --> 00:45:54.960
And that really happened during um uh the pandemic when we had this opportunity where we were able to reinvent ourselves um in a non-disruptive way because we had, you know, there was a shutdown.
00:45:55.440 --> 00:46:15.039
And so since then, you know, we've just we didn't set out to become profitable, but we wanted to find product market fit and build products that were genuinely useful, good value, and solve problems for customers that could also scale.
00:46:15.199 --> 00:46:17.840
And I think we did a pretty good job of that.
00:46:18.159 --> 00:46:26.159
And as we s invested in go to market and sales and marketing, we got more and more customers, we made them happy, they told their friends, they bought more.
00:46:26.320 --> 00:46:38.159
You know, at some point, relatively quickly, two and a half years after that, um, you know, we ended up just looking at the balance sheet one day and saying, wow, we're profitable.
00:46:38.400 --> 00:46:39.679
We should start hiring more.
00:46:40.000 --> 00:46:47.360
And so we were always hiring, but now we're not like, okay, well, we're we should, you know, the venture-backed company is like, if you're profitable, go hire more.
00:46:47.599 --> 00:46:50.639
So they're like, okay, let's turn on the jets, and we started hiring more.
00:46:50.800 --> 00:46:54.960
However, the growth sort of continued to grow even faster than that.
00:46:55.119 --> 00:47:04.639
And so we are really hiring aggressively, and we're trying to recruit um the best people we can around the world to help continue to grow overview.
00:47:04.800 --> 00:47:07.280
Um, but our growth is just staying ahead of that.
00:47:07.440 --> 00:47:11.440
And so um, you know, we've been able to remain profitable for the last few years.
00:47:11.519 --> 00:47:23.119
So it's been it's been a very exciting position, and we are trying to keep growing and keep releasing products that continue to make it easier for customers, more accurate, solve more problems um in this space.
00:47:23.519 --> 00:47:32.159
Yeah, and that is, I think, a real testament to the fact that you built a quality product that is easy to use because your own users will also be your best marketers, right?
00:47:32.239 --> 00:47:34.000
Because engineers do talk to each other.
00:47:34.239 --> 00:47:40.639
Um and there's plenty of there is plenty of stuff in our industry that people use they don't love.
00:47:40.880 --> 00:47:47.199
They use because they have to, they make it work, but they don't go evangelizing about it to their friends, right?
00:47:47.280 --> 00:47:58.800
And so I think it's a rare treat um when engineers get a chance to use something that really either works as well as advertised or actually exceeds their expectations, right?
00:47:58.880 --> 00:48:08.159
And it becomes easier to use over time, um, and not just because they went to like an expensive training and finally got the hang of something that has a large learning curve or whatever.
00:48:08.320 --> 00:48:21.599
Um and and that I think is a is an underlooked at, I think, aspect of go-to-market in our industry because we're so used to like this whole engineering, like you have to kind of go in and like prove the value.
00:48:21.840 --> 00:48:26.480
Um and you have to, there is there needs to be an expert that isn't the user.
00:48:26.639 --> 00:48:47.760
Um and so yeah, to me, I I was just like really happy to see that because there's not a lot of companies that take the uh what like you said, um, land and expand, you know, type of uh model with that in terms of making it really easy to get in the door um and just get started and and make that starting experience really good for everybody.
00:48:48.000 --> 00:48:51.119
Um that is one of the things that really drew me to the company.
00:48:51.199 --> 00:49:03.679
I can't I worked at an enterprise AI company back in 2018, and so it was not accessible at all to, you know, small companies or uh you couldn't set it up on your own.
00:49:03.840 --> 00:49:07.039
It was a whole, you know, we'd have to go in and do a multi-month engagement.
00:49:07.119 --> 00:49:09.840
But that's also the maturity of the AI tools and stuff at the time.
00:49:09.920 --> 00:49:16.960
It was just the only way to do it, and the only companies that could afford it were ones that were willing to pay a very high recurring cost to that.
00:49:17.280 --> 00:49:18.800
Um, because there was also a big cost.
00:49:18.880 --> 00:49:21.519
It was not a you know, set it and forget it on our side.
00:49:21.599 --> 00:49:31.280
There was a big like SLA delivery model with it, and it models have to continually be retrained, and there's a bunch of oversight and all kinds of stuff like that.
00:49:31.519 --> 00:49:39.039
Um and I love, and that's part of why we do the show, is like I want when there's a something really cool, like I want everybody to know about it.
00:49:39.280 --> 00:49:50.960
Um and I remember too when I was working for that company, and the, you know, there was kind of like the beginning of like, hey, there are AI models now that can solve a lot of problems.
00:49:51.199 --> 00:49:55.679
And I would meet with people that would come ask me if we could do this or do that with AI.
00:49:55.760 --> 00:49:57.199
And I was like, well, that's not our niche.
00:49:57.280 --> 00:50:04.400
So, like you know, said it's you have to be careful not to stretch yourself too thin and really focus on specific applications.
00:50:04.639 --> 00:50:11.199
So I think also at the time, too many people thought AI was something magical that could do many
different things.
00:50:11.519 --> 00:50:16.559
And it's I mean, the the foundation models today are kind of magical and they can do a lot of different things.
00:50:16.800 --> 00:50:22.159
But at least back then it was like everything has to be very specifically trained for a very specific application.
00:50:22.480 --> 00:50:27.360
Um and so I'd have to meet I'd have to meet with people and they'd be like, Can can your AI do this?
00:50:27.679 --> 00:50:28.639
I'm like, no.
00:50:28.880 --> 00:50:33.440
I mean, it could if we put enough effort and and money into it, but it but it doesn't.
00:50:33.840 --> 00:50:46.320
Um and I remember thinking, like, oh, there should be like a marketplace for AI models where people could discover what AI is out there that's capable of doing different things, like an angel list, but like an AI list.
00:50:46.719 --> 00:50:55.039
Um because it just seems such an inefficient market strategy to me to be like, hey, I have this crazy cool thing that does this.
00:50:55.199 --> 00:51:00.000
Um, but only people that will like let me knock on their door and take my meeting are gonna know about it.
00:51:00.320 --> 00:51:03.199
And you know, everybody else will have no clue.
00:51:03.679 --> 00:51:20.079
Um but I think now, like obviously, with the the internet was around at that time, but there's just I think a little bit more like parity in in finding information, especially too with the with the AI, if people are searching, you know, using Chat GPT or whatever.
00:51:20.320 --> 00:51:21.840
Um you guys focus on that?
00:51:21.920 --> 00:51:22.239
I'm curious.
00:51:22.320 --> 00:51:28.079
This is a whole nother conversation, but the marketing side of things, like if you ask Chat GPT, hey, what what kind of vision system do I need?
00:51:28.239 --> 00:51:30.400
Do does it recommend overview AI?
00:51:30.639 --> 00:51:32.719
And do you guys put a lot of thought into that?
00:51:33.280 --> 00:51:35.119
Yeah, we definitely put thought into that.
00:51:35.280 --> 00:51:37.360
Um it's it's newer.
00:51:37.760 --> 00:51:46.079
So we think that we have an outsize advantage in getting recommended because we're all the whole world is starting at the same place.
00:51:46.400 --> 00:51:53.519
And so for us, it's like um it's definitely something that we see we see that we can put an outsized effort to get outsized results into it.
00:51:53.599 --> 00:51:56.239
So for sure, uh a big focus for us.
00:51:56.559 --> 00:51:56.800
Cool.
00:51:56.960 --> 00:51:58.960
Well, I think we're coming up on on time here.
00:51:59.119 --> 00:52:05.920
Is there anything that we haven't talked about that you want to tell my audience about or make sure that we know about overview?
00:52:06.159 --> 00:52:12.480
Before ahead of us doing an actual demo where people can see, it's super frustrating to talk about like dashboards and not be able to see them.
00:52:12.559 --> 00:52:13.199
To me, anyway.
00:52:13.280 --> 00:52:15.280
I'm a visual learner in
a lot of ways.
00:52:15.519 --> 00:52:17.840
Yeah, no, I think that this is a great conversation.
00:52:18.000 --> 00:52:21.920
Um, yeah, we we uh it was a wide ranging and we we covered some good topics.
00:52:22.239 --> 00:52:27.280
I'm all over the place and I like to go on lots of tangents and I like to ask a lot of compound questions that don't always make sense.
00:52:27.360 --> 00:52:31.519
So I appreciate your uh your willingness to stick with me here.
00:52:31.920 --> 00:52:34.480
Thank you for leading leading the conversation to interesting places.
00:52:34.800 --> 00:52:35.920
Yeah, no, no worries.
00:52:36.079 --> 00:52:45.119
Um so yeah, my last question is typically like tell our audience if they what like who would you like to reach out to overview and and how?
00:52:45.280 --> 00:52:52.400
And then if there's anything cool from like if people just they're kind of you know tangentially interested in following you guys, where should they do that?
00:52:52.480 --> 00:53:00.639
And is there anything cool coming up that we should be aware of um in terms of events or releases or other other things?
00:53:01.599 --> 00:53:06.880
Yeah, I I would say that if people want to follow us, we're we're on LinkedIn at Overview AI.
00:53:06.960 --> 00:53:08.800
You can sign up for our newsletter on our website.
00:53:08.960 --> 00:53:22.880
We're also gonna be at Electronica um in Munich on November 10th to the 13th, where we're debuting uh a new unsupervised uh anomaly detection model that's incredibly easy to set up for PCBA.
00:53:23.039 --> 00:53:40.159
Um so for you know any sort of electronic server, we can look for uh defects, um, missing components with only five good examples and uh and a highly trained model that can uh detect very small things uh in in a very cheap um and fast to set up way within our ecosystem.
00:53:40.239 --> 00:53:45.119
So we're gonna be debuting that at Electronica Munich and um yeah on November 10th.
00:53:45.199 --> 00:53:46.159
So we're excited about that.
00:53:46.480 --> 00:53:47.039
Very cool.
00:53:47.199 --> 00:53:49.440
Um, what kind of roles are you hiring from?
00:53:49.599 --> 00:53:56.159
And are any of them, if they're like more so related to the industrial automation side than maybe like AI product development on your side?
00:53:56.320 --> 00:54:05.199
But tell us um if you're pulling anybody from our kind of side of the world, uh, what types of job opportunities do you have open that people should be looking out for?
00:54:05.599 --> 00:54:06.400
Yeah, absolutely.
00:54:06.480 --> 00:54:14.559
We're looking for automation engineers, we're looking for controls engineers, um, manufacturing um engineering people who want to be more customer-facing.
00:54:14.639 --> 00:54:25.599
So we're always looking for, you know, we call them forward-deployed engineers, we're looking for solutions engineers, and we usually pull from, you know, uh X usually extroverted manufacturing engineers or that.
00:54:25.760 --> 00:54:32.800
We're looking for vision engineers, um, marketing folks, uh, technical marketing folks who have manufacturing backgrounds um as well.
00:54:33.039 --> 00:54:38.480
We're also looking for pure sales folks, um, engineers on the software side, the hardware side, the embedded side.
00:54:38.639 --> 00:54:44.559
Um, and that applies not just to the US, but Mexico, Canada, uh, China, Taiwan, Japan, Korea.
00:54:44.639 --> 00:54:45.360
So you name it.
00:54:45.440 --> 00:54:46.000
We're we're hiring.
00:54:46.320 --> 00:54:46.719
Oh, wow.
00:54:46.800 --> 00:54:46.960
Okay.
00:54:47.280 --> 00:54:51.119
So I'm assuming that's overview.ai slash careers or something like that.
00:54:51.440 --> 00:54:52.239
Slash jobs, yeah.
00:54:52.480 --> 00:54:53.119
Slash jobs.
00:54:53.199 --> 00:54:53.599
Okay, cool.
00:54:53.760 --> 00:55:03.039
And um, yeah, we we pay above market rate and we try to uh give everyone um equity in the company so they can uh be a part of the growth um that we you know we all build it together.
00:55:03.360 --> 00:55:13.519
Yeah, and that is a really great opportunity right now um in terms of especially with your positioning, I think in the market, your uh profitability and stuff like that.
00:55:13.679 --> 00:55:17.760
Um I I've definitely worked for some equity that didn't turn into anything.
00:55:17.840 --> 00:55:20.480
So I know that's you know, some people have that startup bug.
00:55:20.559 --> 00:55:28.400
They want to try things that are a little bit riskier for a potentially outsized reward um or just for fixing a freaking problem that that's been bugging them for a really long time.
00:55:28.800 --> 00:55:41.360
Um but uh I, you know, I don't give any investment advice, but I would say it'd probably be a pretty good bet that you may get something from uh Overview AI equity if you decide to join this team, from what I can tell.
00:55:41.920 --> 00:55:43.920
And that's just my unsolicited opinion.
00:55:44.400 --> 00:55:45.599
That's the hope and the plan.
00:55:45.679 --> 00:55:46.480
So we'll see, we'll see.
00:55:46.639 --> 00:55:46.880
Yeah.
00:55:47.280 --> 00:55:47.679
Absolutely.
00:55:47.840 --> 00:55:50.320
So oh uh, I guess that's another question.
00:55:50.559 --> 00:55:57.199
Um do you have uh well, maybe, maybe not for this conversation, but I'll be like, what's your exit plan?
00:55:57.280 --> 00:56:04.079
Are you trying to IPO or um Yeah, I mean, right now we're we're we're growing so fast, we want to continue the growth.
00:56:04.239 --> 00:56:11.119
We want to release more and more products, um, not just um in the 2D vision, but eventually 3D vision.
00:56:11.280 --> 00:56:14.960
And then eventually um, how can you put that into different form factors?
00:56:15.199 --> 00:56:22.159
So mobile, uh, whether that combines with you know robots or drones, um, that kind of thing, you know, there's just so much.
00:56:22.400 --> 00:56:32.800
If you can see the world, understand the world, and then you know extract um value, there the roadmap is extremely exciting, especially with the advances in physical AI and these world foundation models.
00:56:32.880 --> 00:56:44.000
Um you can apply that to some incredible things in factories, and we have that bug to turn those uh incredible things and make it accessible, easy to use, and very deployable and scalable.
00:56:44.079 --> 00:56:45.599
So that's what we want to continue to do.
00:56:45.760 --> 00:56:47.840
Um, and we'll see where where that takes us.
00:56:48.159 --> 00:56:49.519
Very cool, very exciting.
00:56:49.679 --> 00:56:50.639
Thank you so much, Russell.
00:56:50.800 --> 00:56:51.360
I appreciate it.
00:56:51.440 --> 00:56:52.400
It was a great conversation.
00:56:52.480 --> 00:56:55.039
I'm very interested to see what you guys come out with next.
00:56:55.199 --> 00:57:08.000
Um, I'm not gonna be at Electronica, but I feel like that is an application I remember from back in the day um being very expensive to do due to the resolution and like the all the different ways that you have to present a board.
00:57:08.079 --> 00:57:10.400
I mean, the training is just ridiculous, like that the amount of time.
00:57:10.559 --> 00:57:16.079
I'm sure it's gotten better since I was doing it, but uh that is probably a very high value use case.
00:57:16.239 --> 00:57:18.400
I can see why you're excited about showing that off.
00:57:18.639 --> 00:57:20.239
So, with that, thank you so much.
00:57:20.400 --> 00:57:21.760
Thank you guys for listening.
00:57:22.000 --> 00:57:35.360
Reach out to me if you want an introduction to anybody at Overview, um, if the other bajillion ways to get a hold of them don't work for you, or if you want to just you know have a little chat about why I'm excited about this stuff and and these guys and their company.
00:57:35.440 --> 00:57:44.880
Um, and then Russell will have a uh guest profile like all of our guests on automationladies.io where there will be some links as well to their company and other things.
00:57:45.119 --> 00:57:52.400
And uh if you're interested in this, definitely keep an eye out for us doing a live demo on LinkedIn sometime in the near future.
00:57:52.639 --> 00:57:53.360
Thank you so much.
00:57:53.599 --> 00:57:53.840
Bye.
00:57:54.159 --> 00:57:54.960
Thank you, Nikki.
00:57:56.159 --> 00:57:58.239
Thank you for listening to AutomationLadies.
00:57:58.400 --> 00:58:10.079
If you like our content and you want to stay in touch, please connect with us on LinkedIn, follow the show page, subscribe to our YouTube channel, and you can send us a message or a copy on our website, automationladies.io.
00:58:10.639 --> 00:58:12.559
We look forward to getting to know you.