TRANSKRYPCJA 🔗
WEBVTT
00:00:05.280 --> 00:00:07.919
Hello everyone and welcome back to the SourceForge podcast.
00:00:08.000 --> 00:00:15.759
I'm your host, Bo Hamilton, and today we are getting into a problem that every retailer knows in their gut, having the wrong stuff in the wrong place at the wrong time.
00:00:15.919 --> 00:00:20.719
Empty shelves when customers are ready to buy and markdown racks full of things that nobody wanted.
00:00:20.879 --> 00:00:28.640
The industry calls it inventory distortion, and the analysts at IHL Group put the global price tag at$1.73 trillion a year.
00:00:28.719 --> 00:00:30.640
That's trillion with a T.
00:00:30.960 --> 00:00:36.560
And for decades, the answer has been forecasting tools and dashboards that tell you what happened and maybe what's coming.
00:00:36.719 --> 00:00:42.000
But uh the company we're talking to today thinks the next step is AI that doesn't just predict what's next.
00:00:42.240 --> 00:00:43.679
It actually helps you act on it.
00:00:43.920 --> 00:00:49.439
Uh Jesta has been building retail and supply chain technology out of Montreal for over 55 years.
00:00:49.600 --> 00:00:53.679
And back in December, they launched a whole new AI division called Farsight IQ.
00:00:54.079 --> 00:01:02.960
It's machine learning plus AI agents that can spot a coming stock out and help your team fix it before it happens, with of course a human still in the loop.
00:01:03.280 --> 00:01:06.879
My guest is Scott Pearson, VP of Sales and Marketing at Jesta.
00:01:07.359 --> 00:01:10.239
And what I like about Scott is he's he's not just a software guy.
00:01:10.319 --> 00:01:13.519
He spent years on the retail side before crossing over.
00:01:13.680 --> 00:01:19.200
And he's been a VP, a COO, and a CEO in retail tech over a 30-year career.
00:01:19.359 --> 00:01:22.400
So he's he's lived these problems from both sides of the counter.
00:01:22.640 --> 00:01:24.719
So, Scott, I'm really happy to have you here.
00:01:24.879 --> 00:01:27.200
Um, welcome to the Stories Forge podcast.
00:01:27.280 --> 00:01:28.480
I'm excited to chat with you.
00:01:28.879 --> 00:01:30.319
Thank you very much for having me.
00:01:30.560 --> 00:01:32.239
Looking forward to the conversation.
00:01:32.640 --> 00:01:36.719
Now, I want to start with the the basics here because this is a brand new division.
00:01:36.959 --> 00:01:40.239
Farsight IQ just launched back in December, I believe.
00:01:40.319 --> 00:01:44.879
Uh, for listeners hearing about it for the first time, can you give us the elevator pitch?
00:01:44.959 --> 00:01:47.280
What does Farsight IQ actually do?
00:01:47.680 --> 00:01:48.079
Absolutely.
00:01:48.239 --> 00:01:51.519
So Farsight IQ was spun off as a separate division.
00:01:51.680 --> 00:01:59.680
We'll get into kind of the why, I think, in a little bit, but it wasn't really it wasn't really started in the the core context of it.
00:01:59.920 --> 00:02:02.319
The challenge is that retailers are short on data.
00:02:02.480 --> 00:02:06.319
In fact, we recognize that retailers are often overwhelmed by data.
00:02:06.400 --> 00:02:13.520
Uh data fragmentation, to your earlier point, fragmentation, sorry, across channels is one of the most common uh issues that we have.
00:02:13.599 --> 00:02:17.039
And then teams have a tendency to kind of plan in silos.
00:02:17.199 --> 00:02:19.680
So there's different teams dedicated to different areas.
00:02:19.919 --> 00:02:25.520
There's no really kind of oversight and overview of the entire area across the entire organization.
00:02:25.840 --> 00:02:27.680
So the core premise really was simple.
00:02:27.840 --> 00:02:30.000
Retailers don't fail because they lack systems.
00:02:30.159 --> 00:02:33.840
They struggle because decisions tend to lag reality.
00:02:34.080 --> 00:02:37.840
So Farsight's really just an it's not a reporting layer.
00:02:38.080 --> 00:02:54.240
It's a decision intelligence layer that observes demand, uh, anticipates outcomes, um, recommends actions, and then allows your team to learn and to imply or apply their human judgment as well.
00:02:54.319 --> 00:02:57.520
To your earlier point about human in the loop, I think that's key.
00:02:57.759 --> 00:03:03.039
So people need to feel comfortable that the recommendations are going to make sense and drive their business appropriately.
00:03:03.280 --> 00:03:07.439
As we looked at the problem, we actually came up with six different modules.
00:03:07.520 --> 00:03:10.879
Uh, and I'll touch on them really quickly just to get into the high level.
00:03:11.120 --> 00:03:13.039
At the highest level is forecast IQ.
00:03:13.199 --> 00:03:26.080
Forecast IQ is a machine learning uh tool that is dedicated to just predicting the future, uh, demand forecasts specifically, across both short-term and long-term, preseason horizons.
00:03:26.240 --> 00:03:38.400
It's unique because it allows you to split it into seasonal goods and non-seasonal, more staple items, and it uses what we refer to as an ensemble machine learning model, which is, I guess you could think, mixture of experts.
00:03:38.479 --> 00:03:48.479
So the various algorithms come up with their own unique positioning and forecast, and then it's a blending of all of those together based on the specific seasons, products, and categories.
00:03:48.719 --> 00:03:58.080
Then we said, okay, there's other areas that I need to, in order to be effective in forecasting demand, what happens if I have a new item that I've never carried before?
00:03:58.319 --> 00:04:04.159
Well, the only way for me to really accurately forecast that demand might be to come up with similar items.
00:04:04.400 --> 00:04:06.159
So that was a challenge in and of itself.
00:04:06.240 --> 00:04:08.159
So we looked at building out style IQ.
00:04:08.240 --> 00:04:10.400
Style IQ is an AI version.
00:04:10.560 --> 00:04:16.560
You upload an image, you say, please attribute this product for me based on the attributes associated with this product
Load full transcript
category.
00:04:16.800 --> 00:04:29.519
Style IQ is very robust in that ability to extract all of this information so that I'm now looking at items that have been that are very similar to previous items, so I can start to be more accurate in my forecast demand.
00:04:29.759 --> 00:04:37.360
Replenish IQ, the third module, is around how do I determine when to best replenish an item once it's selling in the store.
00:04:37.439 --> 00:04:46.639
And rather than just looking at min-max and things like that, which are very effective, uh, when I sell out of a product in one store, I want to make sure I'm replenishing that same product.
00:04:46.800 --> 00:04:58.240
I want to start to really cater my replenishment strategy more around the likely demand so that I'm not overstocking or understocking based on the demand in that particular location.
00:04:58.480 --> 00:05:06.480
Which brings me then to optimize IQ, which is now that I have inventory in stores, I want to make sure that I'm balancing my inventory appropriately.
00:05:06.720 --> 00:05:17.360
Optimize IQ is designed to do just that, to identify are there items in the warehouse that can move to stores or items in one slow-moving store that I can move to other locations?
00:05:17.519 --> 00:05:19.120
What makes sense from a business?
00:05:19.279 --> 00:05:25.439
And we're going to recommend ways for you to balance your stock accordingly to really optimize based on, again, that forecast.
00:05:25.920 --> 00:05:29.439
Risk IQ is another kind of overlay on top of that.
00:05:29.519 --> 00:05:32.319
That's where AI and ML really come together.
00:05:32.480 --> 00:05:36.399
And AI in this context, I mean generative AI or LLMs.
00:05:36.639 --> 00:05:42.000
So, how do I take those demands and I start to really look for outliers or risks?
00:05:42.240 --> 00:05:47.439
So we have a number of dashboards and AI-built skill sets that will start to drive.
00:05:47.519 --> 00:05:48.480
Here's some recommendations.
00:05:48.639 --> 00:05:50.959
If these are overstocked, these are understocked.
00:05:51.120 --> 00:05:56.720
This is an interesting trend going on in these locations that you need to be aware of and keep your eye on.
00:05:56.879 --> 00:06:00.399
So it's really a recommendation tool around how do you avoid risk.
00:06:00.639 --> 00:06:06.720
And then ultimately, there's something else we call advisor IQ, which is more your more traditional, I guess, chat bot.
00:06:06.879 --> 00:06:10.800
If you want, you can ask it real language questions, natural language questions.
00:06:10.959 --> 00:06:13.920
It will come back with recommendations, reports, scenarios.
00:06:14.000 --> 00:06:20.079
You can explore what can I do to increase my margins in this category, or where is my highest risk and following.
00:06:20.319 --> 00:06:24.319
It's just an interpretive tool that allows you to really ask any question.
00:06:24.560 --> 00:06:30.160
And we have a couple other more operational tools, uh, match IQ being
one of them, which does three-way matching.
00:06:30.240 --> 00:06:43.120
So again, we pulled all of those tools together to say what is it that retailers are really looking to try to accomplish in order to make sure they are avoiding those understocks and overstocks that we discussed in the first step of this conversation.
00:06:43.759 --> 00:06:44.160
Gotcha.
00:06:44.319 --> 00:06:47.040
Yeah, there's a lot of exciting uh capabilities there.
00:06:47.120 --> 00:06:49.279
Um thanks for giving us that overview.
00:06:49.519 --> 00:06:56.480
Um uh it it what kind of stands out to me is just, you know, it's the the act portion of the um the feature set.
00:06:56.560 --> 00:07:01.759
It's like it's not uh just sort of another tool that's telling you you know what already happened.
00:07:01.839 --> 00:07:09.279
It's sort of looking ahead and actually helping you do something about it through all these different um uh features um that are built into the platform.
00:07:09.600 --> 00:07:16.079
Um what's interesting to me, you know, is that Jesta isn't just some some startup kind of chasing the AI wave.
00:07:16.160 --> 00:07:25.279
You've been you've been building retail technology for over 55 years, um, much longer than a lot of these uh AI companies we we um hear about and chat with.
00:07:25.360 --> 00:07:27.519
Um so walk me through the the decision.
00:07:27.600 --> 00:07:32.079
Why spin up a dedicated AI division like right here and now?
00:07:33.040 --> 00:07:34.240
I think that's a great question.
00:07:34.319 --> 00:07:35.439
I think there's a few reasons.
00:07:35.600 --> 00:07:37.680
I guess I'd start with timing.
00:07:38.000 --> 00:07:46.000
You know, retailers are facing a level of volatility and complexity that traditional planning methods just weren't really designed to handle.
00:07:46.240 --> 00:07:51.920
I think everybody realizes that they need to be looking at how do I incorporate AI into my business model.
00:07:52.079 --> 00:07:55.680
Everybody else is doing it, and I can't be a laggard in this context.
00:07:55.759 --> 00:07:57.279
I need to stay ahead of the game.
00:07:57.439 --> 00:07:59.120
But where do I actually apply it?
00:07:59.199 --> 00:08:01.040
Where is it most important for my business?
00:08:01.199 --> 00:08:04.560
You know, demand channels are changing quickly.
00:08:04.720 --> 00:08:12.800
Um, channels behave differently online, handles behaves differently than stores do, marketplaces, all of these other things are going on.
00:08:13.040 --> 00:08:15.199
And the reality of it is inventory is expensive.
00:08:15.279 --> 00:08:18.399
That is your most expensive cost, is what you're buying in your inventory.
00:08:18.480 --> 00:08:22.560
So I need to really make sure that I'm highly efficient in how I manage all of that.
00:08:22.720 --> 00:08:32.399
So, and again, to my earlier point, there's probably more data than ever right now, but people still kind of struggle to turn that data into timely action.
00:08:32.559 --> 00:08:41.200
So, what can we do to help retailers make more timely decisions to make sure they're proactive rather than reactive to what's going on in their business?
00:08:41.600 --> 00:08:46.879
Now, um, I know, I know retail analytics isn't um particularly new, right?
00:08:47.039 --> 00:08:48.240
Forecasting tools aren't new.
00:08:48.399 --> 00:08:54.639
Retailers have been have been using dashboards and like demand planning software for for decades now.
00:08:54.799 --> 00:09:00.799
Um, from what I've read, the pitch with Farsight IQ is that it doesn't just like predicts predict what's next.
00:09:00.879 --> 00:09:02.320
It helps you act on it, right?
00:09:02.480 --> 00:09:08.639
So what's actually different here compared to some of the more traditional tools that have been used in in years past?
00:09:09.519 --> 00:09:10.000
Good question.
00:09:10.159 --> 00:09:14.559
Yeah, I think traditional analytics usually tells you what happened.
00:09:14.720 --> 00:09:23.360
Uh, there are forecasting and demand tools that have been around for a long time, and they give you an idea of what's likely to happen, but then you're always still laggard.
00:09:23.519 --> 00:09:25.679
You're falling behind, you're looking at what happened.
00:09:25.840 --> 00:09:28.799
Traditional forecast ties to predict what might happen.
00:09:28.960 --> 00:09:36.320
Farsight IQ is different because it's designed really to move beyond both of those things and help retailers decide what to do next.
00:09:36.480 --> 00:09:41.759
So it's not about what's happening, what's likely to happen, and what did happen, but what do I do next?
00:09:41.840 --> 00:09:45.200
So it really is helping you to do that next decision.
00:09:45.360 --> 00:09:47.279
Retail is incredibly complex.
00:09:47.519 --> 00:09:53.600
You can't treat every product, every store, every channel, you know, every demand pattern the same way.
00:09:53.759 --> 00:09:58.559
Uh basic replenishment items behave differently than fashion items, as an example.
00:09:58.799 --> 00:10:04.159
A new product, as I mentioned earlier, behaves differently than an item that you've carried for years.
00:10:04.399 --> 00:10:10.399
And stores oftentimes change also, as does e-commerce, and regions can be changing all the time.
00:10:10.639 --> 00:10:24.080
Then you need to tie in the other levels of complexity, such as promotions, various inventory constraints that you may have in a location, weather events, local factors, all of these things can distort demand.
00:10:24.240 --> 00:10:31.360
So a lot of forecasting tools try to force all that complexity through one method, and that's where things start to break down.
00:10:31.519 --> 00:10:46.799
That's why I mentioned before we're using Farsight IQ and forecast IQ specifically to really look at an ensemble to say there's a number of considerations, and we need to balance what these experts are coming up with to find the right decision in the right location at
the right time.
00:10:47.360 --> 00:10:52.639
Yeah, I mean, there's so many, there's so many moving pieces and and um you know areas to to watch.
00:10:52.720 --> 00:11:06.320
And it's it's really uh the problem that you're uh working to address with retailers is is um you know, it's it's trillions of dollars worth of of inventory and and um the numbers are pretty staggering.
00:11:06.399 --> 00:11:21.840
I mean, uh as I alluded to and mentioned in the in the intro, IHL Group estimates that inventory distortion, that's like out of stock and overstocks um combined, costs global retail$1.73 trillion a year, um, which is pretty staggering.
00:11:22.000 --> 00:11:24.960
So that just kind of visualizes the scale for listeners.
00:11:25.200 --> 00:11:29.200
Um you have empty shelves on one side, markdown racks on the other.
00:11:29.360 --> 00:11:35.519
How does better forecasting help retailers stop sort of bleedy money in both directions at once?
00:11:36.320 --> 00:11:37.039
That's a great question.
00:11:37.120 --> 00:11:46.000
I do I think that overstocks and stockouts look like opposite problems, but they're usually come from the same root issue, the same root cause.
00:11:46.159 --> 00:11:50.240
The retailer doesn't have a clear enough view of the true demand.
00:11:50.399 --> 00:11:55.440
If you underforecast, you run out of inventory, you lose sales, you disappoint customers.
00:11:55.679 --> 00:11:59.200
You might also create operational pressure as teams scramble to react.
00:11:59.360 --> 00:12:09.360
If you overforecast, you create excess inventory, you tie up working capital, your increase markdown exposure, you reduce margin, all these things kind of come into play together.
00:12:09.440 --> 00:12:13.200
Better forecasting helps because it creates a stronger demand signal.
00:12:13.360 --> 00:12:16.159
And that demand signal drives almost everything downstream.
00:12:16.320 --> 00:12:22.240
All the downstream decisions, how much to buy, where to allocate, where to replenish, when to replenish.
00:12:22.399 --> 00:12:25.200
So it really helps you to do more of that just-in-time inventory.
00:12:25.360 --> 00:12:38.399
So you could be much more intelligent about don't push everything out to the stores immediately, hold some back so that you can be more responsive to the needs of the market and make sure that you're you also have that sort of feedback coming in on a regular basis.
00:12:38.559 --> 00:12:40.720
Demand is much higher than we anticipated.
00:12:40.879 --> 00:12:57.759
Make sure that you're also taking your buying cycles and the length of time it takes for you to purchase new inventory from from your vendors into account as well, and really try to strive for just in time, but but also recognize that there is volatility and you need to be on top of this on a you know daily, weekly basis.
00:12:58.159 --> 00:13:08.000
They they almost look like opposite problems, like uh too much stuff, not enough stuff, but they're they're sort
of the same problem if you think about like you guessed, you guessed wrong about what people would buy.
00:13:08.080 --> 00:13:12.879
And if you fix the guessing portion of the issue, then both sides sort of get better.
00:13:12.960 --> 00:13:16.720
And it sounds like that's kind of what you're you're working on with far site IQ, right?
00:13:17.200 --> 00:13:22.320
Yeah, and then I and I mentioned earlier the the context of uh you know the real demand.
00:13:22.399 --> 00:13:31.039
And I guess I'll draw one other distinction that most planning tools are generally triggered very much toward what is considered to be constrained demand.
00:13:31.200 --> 00:13:36.559
Constrained demand is demand based on the product inventory that you had available at the time.
00:13:36.799 --> 00:13:39.120
The question is, what about unconstrained demand?
00:13:39.279 --> 00:13:42.720
If you had more inventory, what would the sales have been in the past?
00:13:42.799 --> 00:13:57.039
And therefore, how do I incorporate the opportunity, the unconstrained demand, in my forecasting tool so that I can identify if everything was always available in the right channel at the right time, what might my demand actually be?
00:13:57.200 --> 00:14:02.879
And that's where fireside IQ comes in is we have the ability to look at the unconstrained demand and then constrain it as well.
00:14:02.960 --> 00:14:05.840
So you can take a picture of that, and this is where the human in the loop comes in.
00:14:05.919 --> 00:14:09.919
Now the human can say, do I believe this unconstrained demand is accurate?
00:14:10.000 --> 00:14:15.600
And if so, let me beef up my inventory a little bit or follow what the AI model is telling me.
00:14:15.759 --> 00:14:30.720
And if I want to, you know, ratchet it back a little bit, or maybe my open to buy doesn't quite meet those numbers, I'm gonna live within my OTB and I'm gonna actually maybe constrain that a little bit more, and we're able to really provide the insights into both of those concepts.
00:14:31.120 --> 00:14:41.840
Now, I want to see if you're be able to give us a um a concrete sort of example to illustrate what it is you guys are are solving for um customers and clients.
00:14:42.000 --> 00:14:52.159
Um, can you give us a real example of a retail decision, maybe something a buyer or a planner deals with every week that Farsight IQ could help improve or maybe even automate?
00:14:52.639 --> 00:14:53.919
I think a number of things.
00:14:54.000 --> 00:14:57.759
So I guess I'll focus first on the forecast.
00:14:57.919 --> 00:15:00.960
A lot of people say forecasting is the most important.
00:15:01.279 --> 00:15:07.279
And I would argue in some cases forecasting is the most important because everything else works downstream from that.
00:15:07.440 --> 00:15:10.639
So getting your demand forecast down first and foremost is key.
00:15:10.799 --> 00:15:15.360
So most retailers I'm speaking to today are saying, let's start with the forecast.
00:15:15.679 --> 00:15:35.519
Interestingly enough, I have a slightly different point of view that maybe the best place to focus on is what I called risk IQ earlier, which is let's analyze your existing data and your existing inventory, what's available in each of the locations today, and let's start to identify where there's likely to be risk.
00:15:35.759 --> 00:15:52.159
This product is selling particularly well in these eight locations, and therefore I need to move more inventory into those eight locations, or it's really moving very slowly in these others, and which products, categories, uh, types of products are not moving, let's be more responsive to that.
00:15:52.240 --> 00:16:07.600
So I think risk IQ provides you the real-time insight, and it's a daily AI model that's running against the likely demand for each location that's changing on a daily, weekly basis, but it's also looking at the actual inventory and stock.
00:16:07.759 --> 00:16:14.960
That's where I see that stock balancing and optimization might actually provide some retailers more benefit than the forecast itself.
00:16:15.120 --> 00:16:18.240
Not to say the forecast isn't important, it clearly is.
00:16:18.480 --> 00:16:20.639
Most people want to start with the forecast.
00:16:20.799 --> 00:16:25.440
Let's look for that demand, let's look for the areas that are hitting my business the most.
00:16:25.600 --> 00:16:34.720
In many cases, it's the fashion inventory because right now I'm basing my fashion inventory on past years, past three, four year sales.
00:16:34.960 --> 00:16:36.799
And I didn't carry this product before.
00:16:36.879 --> 00:16:43.679
So how do I link this product to fast uh past products to make sure that I'm accurately forecasting that demand?
00:16:43.840 --> 00:16:47.679
And they want to focus on a very targeted area of business, which is smart, by the way.
00:16:47.840 --> 00:16:53.200
I do uh suggest that people implement the products and AI just in general.
00:16:53.440 --> 00:16:55.919
Find what makes the most sense for your business.
00:16:56.080 --> 00:17:00.559
Is it the broader forecast because everything downstream is impacted by that?
00:17:00.639 --> 00:17:03.600
Or is it targeted risks that you want to focus on?
00:17:03.759 --> 00:17:09.279
And if it's those areas, in what part of your business do you want to focus those areas and risks on?
00:17:09.440 --> 00:17:11.039
And let's really tackle it that way.
00:17:11.200 --> 00:17:22.559
So that's really where our conversations usually go is let's figure out what makes the most sense for your specific business, identify those areas that you want to move the needle, and then start to implement.
00:17:22.640 --> 00:17:24.720
You have to you have to take that first step.
00:17:25.279 --> 00:17:26.559
Yeah, forecasting is tough.
00:17:26.720 --> 00:17:31.359
I mean, uh the world often doesn't like to cooperate with uh with one's forecast.
00:17:31.519 --> 00:17:36.480
Um uh and retail,
especially, I know, loves loves uh changing things up on you.
00:17:36.559 --> 00:17:40.799
Um like I I just think of like the TikTok trends that maybe blow up and change things.
00:17:40.960 --> 00:17:48.640
Uh yeah, there's so many shifting like pieces that in a market that can um suddenly just throw your your carefully planned forecast out of whack.
00:17:48.960 --> 00:17:54.720
Um now I know I know far side IQ pulls an outside signals like like weather and local events.
00:17:54.960 --> 00:18:03.279
So, how does AI help retailers actually respond to those curveballs instead of just sort of reading about them in the next quarter's report?
00:18:04.079 --> 00:18:04.480
Great question.
00:18:04.559 --> 00:18:13.759
So, in from the forecast IQ perspective, we can incorporate any third-party data that can be fed into the system, weather being a good example.
00:18:13.920 --> 00:18:23.519
Um, events, known events, are usually inside of the event calendar for each retailer, but also outside external events, let's use World Cup as an example.
00:18:23.680 --> 00:18:25.119
Clearly, that was a factor.
00:18:25.200 --> 00:18:30.079
You had a lot of people coming into various cities that maybe are tourists and don't usually come in.
00:18:30.160 --> 00:18:46.319
So you need to start to look at the population of likely demand that's coming from these external events, and feeding all that into the AI engine allows you to train against past purchases and really ascertain uh likely probabilities and then apply those into your forecast.
00:18:46.559 --> 00:18:48.240
So that in and of itself is very important.
00:18:48.400 --> 00:18:51.599
Obviously, we get into the repunishment and the forecasting.
00:18:51.759 --> 00:18:57.440
You need to be more responsive if there's a World Cup going on in your city for the following three weeks.
00:18:57.599 --> 00:18:59.680
You need to be more responsive to how you address that.
00:18:59.759 --> 00:19:04.880
So pulling all those external data sources in is I think a challenge that most people have.
00:19:04.960 --> 00:19:10.240
It's putting your finger in the air and saying, I think we just need to beep inventory up by 25%.
00:19:11.119 --> 00:19:18.640
You know, then you're gonna find yourself sitting on a lot of merchandise that maybe you know is now stale or becomes stale and has to be marked down at a later date.
00:19:18.720 --> 00:19:22.960
So you need to be more uh responsive to all of these various factors.
00:19:23.119 --> 00:19:32.720
Our tool allows you to train against those external factors and the implications of those factors uh in the past to identify what's likely to occur in the future.
00:19:32.799 --> 00:19:49.119
And that's I think a key element is really recognizing that there's many, many factors, some of which maybe default just in the training model, some of which your team recognizes needs to be incorporated in for some period of time, and that you can then trigger it into those events.
00:19:49.200 --> 00:20:01.839
So we could be doing different forecasting, for example, for the store locations in the city where the World Cup is taking place or the Olympics might be taking place, et cetera, and then trigger it back so that it's not taking that into account for the other locations.
00:20:01.920 --> 00:20:05.039
So it really is that level of flexibility that you need in the tool.
00:20:05.359 --> 00:20:24.400
I I want to circle back around to the the human in the loop um element here, uh, because I think that sort of maybe worries uh potential, you know, customers is is the agentic AI portion, is handing the keys over to a machine to to um act on uh a user's behalf and and start forecasting and whatnot.
00:20:24.559 --> 00:20:42.480
Um I know Farsight IQ has these these AI co-pilots that can recommend and and actually execute actions, um, of course, with a human in the loop still, but how do you help teams move faster without losing that human oversight and making sure that there's still a proper review process?
00:20:42.720 --> 00:20:49.279
Where's that like that line between the AI acting and uh a person approving the decisions?
00:20:49.920 --> 00:20:51.039
No, it's a great question.
00:20:51.200 --> 00:20:55.599
I think it's it's in fact was kind of a major design principle for us.
00:20:55.839 --> 00:21:00.640
You know, we don't believe that retail AI should remove people from the decision process.
00:21:00.799 --> 00:21:03.519
In fact, retail is really too nuanced for that.
00:21:03.680 --> 00:21:10.640
Merchants and planners know things that maybe the AI tool doesn't know or understand and they have an intuition around it.
00:21:10.799 --> 00:21:16.400
The local events, vendor issues, visual change going on in the store, whatever it may be.
00:21:16.640 --> 00:21:18.799
So we want to make sure that the human is always in the loop.
00:21:18.880 --> 00:21:21.279
So if I look at the forecast as an example, forecast.
00:21:24.960 --> 00:21:30.960
Each planner, buyer, whoever is looking at that tool can say, okay, I think that's pretty accurate.
00:21:31.119 --> 00:21:36.640
I'm looking at what happened last year, and I think this might be a little bit overestimated.
00:21:36.720 --> 00:21:37.920
So I want to tune that down.
00:21:38.000 --> 00:21:40.319
And they're able to go in and modify and tweak.
00:21:40.400 --> 00:21:47.599
Now we're going to track the original forecast plus the modified forecast, and we'll tell you, were you more correct or was the tool more correct?
00:21:47.680 --> 00:21:50.559
And in fact, the tool itself will then learn from those as well.
00:21:50.720 --> 00:21:53.839
So the humans always in the loop from the forecast perspective.
00:21:54.079 --> 00:21:59.759
The underlying risk IQ I mentioned and replenish IQ, optimize IQ, those are purely recommendations.
00:22:00.799 --> 00:22:05.839
Based on your current inventory positions in each location, here's what we recommend you do.
00:22:05.920 -->
00:22:09.359
And in all instances, AI isn't triggering anything.
00:22:09.599 --> 00:22:14.559
The user has to go in and say, okay, yes, I agree with what AI is doing, or I want to adjust it slightly.
00:22:14.720 --> 00:22:19.440
So in no case are we actually writing straight back to the database using AI.
00:22:19.839 --> 00:22:24.480
In all cases, we are writing back only when somebody is approving it and pushing it through.
00:22:24.640 --> 00:22:32.559
And even then, in many cases, depending on configuration, there might even be an approver above the buyer that's actually making that decision.
00:22:32.720 --> 00:22:36.880
The approver still needs to be done and approving, okay, we're going to generate new POs.
00:22:37.279 --> 00:22:40.160
That's just not going to be AI that's generating POs for you.
00:22:40.319 --> 00:22:44.000
There's going to be human in the loop, sometimes two humans in the loop in that context.
00:22:44.400 --> 00:22:44.880
Gotcha.
00:22:45.039 --> 00:22:45.200
Okay.
00:22:45.279 --> 00:22:48.240
So yeah, so humans, humans set sort of the the guardrails.
00:22:48.400 --> 00:22:54.400
The AI recommends and only uh automates within the the approved sort of boundaries and parameters.
00:22:54.559 --> 00:22:58.559
Um I think that's yeah, I think that's a good, you know, a good way to frame it, good approach.
00:22:58.720 --> 00:23:04.240
Um yeah, the AI isn't ultimately, it's not replacing uh the judgment call, right?
00:23:04.319 --> 00:23:08.319
It's just sort of clearing the the busywork off of one's plate.
00:23:09.039 --> 00:23:18.880
Yeah, I I think AI brings, I guess, I guess I'd say scale, pattern recognition, and speed, but people bring judgment, context, accountability, and experience.
00:23:19.039 --> 00:23:20.720
So it's really a combination of those.
00:23:20.799 --> 00:23:23.920
I think that is kind of key to how this becomes effective.
00:23:24.559 --> 00:23:26.240
Yeah, I think that's a good strategy.
00:23:26.319 --> 00:23:44.480
Um, and of course, you know, um perhaps in the future, you know, as these AI's uh models and agentic AI capabilities continue to evolve, maybe there'll be additional sort of um uh maybe like feature sets with the more judgment-based calls with some of the automations, but um until then, you know.
00:23:44.960 --> 00:23:54.640
Well, I think what we'll see to that, there's probably, well, not probably, what will occur and what is occurring now is building out more, I guess I'll call it skills within AI.
00:23:54.720 --> 00:24:01.359
So allowing AI to use a very finite number of skills to actually execute on your behalf.
00:24:01.519 --> 00:24:12.160
You still, as a human, need to say, I want to execute this skill, but that skill will maybe do a little more balancing or something that the buyer might not be quite as attuned to.
00:24:12.319 --> 00:24:15.440
So there are ways to leverage AI and that kind of capability as well.
00:24:15.519 --> 00:24:21.839
And you know, we're seeing
more and more of this in the AI world in general, people building out various skills that would allow things to execute.
00:24:22.000 --> 00:24:25.200
But right now, we're saying most retailers are a little nervous about that.
00:24:25.359 --> 00:24:27.200
I don't want anything touching my database.
00:24:27.359 --> 00:24:34.960
I don't want to generate purchase orders that you know have a commitment, obviously financial commitment, without somebody being involved and saying, yeah, this is the way to go.
00:24:35.119 --> 00:24:39.279
And even with the skills, we there would be a lot of constraints and security tied around that.
00:24:39.599 --> 00:24:49.359
Yeah, let's let's uh let's zoom out to the buyers who who are thinking, like, okay, but is this is is my company even ready for this this next leap, right?
00:24:49.440 --> 00:24:54.880
Um I know every sort of AI vendor says it just like depends on the data, depends on the company.
00:24:55.039 --> 00:25:04.000
Um, but I want to get real, like how should retailers think about data readiness before they even start you know adopting AI driven forecasting?
00:25:04.079 --> 00:25:12.079
Like how clean does the the the data and the business um you know, house, metaphorical house need to be before you you move in?
00:25:13.119 --> 00:25:15.039
That's a great call, because I think you're right.
00:25:15.119 --> 00:25:20.960
A lot of retailers are experimenting with AI today, but not all of those pilots turn into real business impact.
00:25:21.039 --> 00:25:30.400
Uh and typically it is, as you're saying, it's it's we need to change it a little bit more from you know a project to a little bit of a science experiment.
00:25:30.480 --> 00:25:32.079
And you have to look at your data.
00:25:32.319 --> 00:25:37.279
You have to make sure that your data is ready to work through that, but not across your entire organization.
00:25:37.440 --> 00:25:45.279
Some people are going, we can't move on AI until we do a one-year project that cleans up our data and gets rid of all duplicates and does the following.
00:25:45.519 --> 00:25:48.160
I would argue that that's probably not the right approach.
00:25:48.319 --> 00:25:53.440
The best approach is probably to say, what are the, as I mentioned before, what are the lowest hanging fruits?
00:25:53.599 --> 00:26:00.079
Uh, where can I really tackle that and where's my biggest risk and the biggest benefit for me implementing AI?
00:26:00.160 --> 00:26:07.200
And let's focus on that level of data and let's you know segment it out and let's really target in on the areas that make the most sense.
00:26:07.359 --> 00:26:13.839
So your data needs to be clean, and that's part of any project as we migrate data over to where we're going to do the training.
00:26:14.000 --> 00:26:15.839
You don't want to train against bad data.
00:26:16.000 --> 00:26:20.799
So you want to make sure that if I'm going to focus on this data, it's four years worth of history.
00:26:20.960 --> 00:26:22.880
I need to make sure that all that data is clean.
00:26:23.039 --> 00:26:23.839
Totally agree.
00:26:24.000 --> 00:26:28.079
You do need to go through that cleansing process, sometimes augmentation as well.
00:26:28.240 --> 00:26:32.319
It's not, it's maybe enrichment, not just your standard data today.
00:26:32.559 --> 00:26:34.960
And that is an exercise you need to go through.
00:26:35.039 --> 00:26:37.680
But I don't see, don't think you need to boil the ocean.
00:26:37.839 --> 00:26:42.400
I think you need to really focus on, you know, where is it that you need to focus your attention on today?
00:26:42.559 --> 00:26:47.279
Let's make sure that there's data readiness in that context, and then let's apply it there only.
00:26:47.359 --> 00:26:54.720
And then really let's look at these various quality and goals signals that you're looking for and make sure that all attributes of products are complete.
00:26:54.880 --> 00:27:02.000
That's an area I do focus on with people to say, I've got your past products, your past products you didn't attribute particularly well.
00:27:02.240 --> 00:27:09.839
So let's go back and attribute them now so that any future product that has similar attributes, I'm I'm much more targeted in.
00:27:10.000 --> 00:27:16.079
So there are strategies around that that we would work with our customers to say, here's where you need to focus your attention right now.
00:27:16.240 --> 00:27:19.200
And let's identify those areas that make the most sense.
00:27:19.599 --> 00:27:20.240
That makes sense.
00:27:20.319 --> 00:27:20.480
Yeah.
00:27:20.559 --> 00:27:37.119
I I the data, the data um aspect is um something that I feel like could use some more um, I don't know, representation in a lot of these AI discussions because I always think like so much discussion is around AI and and what um agentic capabilities there are based on top of the data.
00:27:37.279 --> 00:27:45.279
But like not very many people are talking about the actual data itself and how how like clean and like val um uh reliable it is, right?
00:27:45.440 --> 00:27:49.519
And uh you mentioned like you know, a lot of times companies are are drowning in data.
00:27:49.680 --> 00:27:55.440
So uh I I kind of make sense that you kind of maybe gloss over that and focus in on what to do with the data.
00:27:55.680 --> 00:28:03.680
But with with AI, like you gotta, you still have to focus in on making sure your your data, the the root, the source is is valuable.
00:28:04.160 --> 00:28:04.720
Absolutely.
00:28:04.880 --> 00:28:07.839
I think they're drowning in data, which I said before.
00:28:07.920 --> 00:28:12.559
And I also think that the data is often siloed, which is also the other challenge.
00:28:12.720 --> 00:28:24.160
So if I have siloed data and I have a lot of it, but I there's no way for me to easily join that data together so that I have a semantic layer where I can communicate with a single layer of data, that's kind of key.
00:28:24.319 -->
00:28:35.680
So the forecast IQ product, as we pull data from various sources, we do normalize it and we put it into a structured data format that we can easily train against so that it's always consistent in training.
00:28:35.920 --> 00:28:44.880
But again, there are times when, even though I might have a ton of data, a lot of our retail customers today, I keep using attributes as an example, but I think it's the perfect example.
00:28:45.039 --> 00:28:53.119
They're carrying a particular product type and they've never bothered to identify whether it's a high top or a low top sneaker as an example.
00:28:53.359 --> 00:28:56.160
Well, then clearly your forecasts are going to be off a little bit.
00:28:56.319 --> 00:29:00.720
You're gonna be focusing on things that are a little less important, the color, the brand, that sort of thing.
00:29:00.880 --> 00:29:08.799
Not less important, but uh perhaps in the context of the broader real forecasting, I need to be looking at other attributes associated with that.
00:29:09.119 --> 00:29:33.440
Men's clothing is a good example is a picola pal, natural pal, double-breasted, single-breasted, two button, three-button, what all those types of things are, all factors that if you haven't identified that those attributes in your past products, then you need to start going back and repurposing, augmenting, and enriching your past products so that when I'm now introducing a new product, I'm aligning more closely with the actual demand based on those attributes.
00:29:33.680 --> 00:29:36.400
That's kind of a key enrichment area for sure.
00:29:36.880 --> 00:29:44.720
In your experience, like what separates a really useful uh AI project from something that's um just kind of experimental?
00:29:45.279 --> 00:29:50.000
Well, I think useful is you need to know what metric you're trying to change.
00:29:50.240 --> 00:29:57.839
You need to understand what your end result and goal is, and then really figure out all the things that you need to do to accomplish that specific goal.
00:29:58.000 --> 00:30:00.799
It's not just let's try it and see what happens.
00:30:01.039 --> 00:30:08.000
You need to say, I'm trying it to see what happens, but here's my goal, and here's the KPIs or the set of initiatives that I'm trying to improve.
00:30:08.160 --> 00:30:14.799
I'm looking to reduce stockouts by X percent, and these are the store locations that I'm having the biggest challenges with.
00:30:14.960 --> 00:30:24.559
And then we can start to isolate the store locations, the types of products, the balance and mix between seasonal versus staple goods, et cetera, et cetera.
00:30:24.720 --> 00:30:26.640
It just sort of cascades beyond that.
00:30:26.799 --> 00:30:35.839
And then based on all of that target goals that we're trying to initiate, it allows us to really dig a lot deeper into how do we make sure that we accomplish your goals.
00:30:36.000 --> 00:30:37.920
And here's the numbers we're going to be looking at.
00:30:38.079
--> 00:30:43.920
This is what we're feeding into, train the model to make sure that it knows exactly what it the end goal is.
00:30:44.000 --> 00:30:50.799
It's just not going out and saying, oh, well, you know, here's what I think, you know, it's here's what I think in order to accomplish this specific goal.
00:30:50.960 --> 00:30:51.920
That's kind of key.
00:30:52.240 --> 00:30:52.640
Gotcha.
00:30:52.720 --> 00:30:53.119
That makes sense.
00:30:53.200 --> 00:31:05.839
Yeah, because I and a lot of retailers I know are they're running some kind of AI pilot themselves, but um the the those pilots, a lot of them just never actually turn into making uh they never have much of a business impact, right?
00:31:06.640 --> 00:31:07.039
Yeah.
00:31:07.200 --> 00:31:11.279
And I also think to that point, you know, this is a little bit of a challenge.
00:31:11.359 --> 00:31:15.839
You know, every company is dealing right now with there's a bunch of tools out there today.
00:31:15.920 --> 00:31:18.799
And there's Quad Code, there's Codecs, there's this, there's that.
00:31:18.880 --> 00:31:21.759
And can I apply these tools inside of my own business?
00:31:21.839 --> 00:31:24.960
And of course, we're applying a lot of those tools in our business as well.
00:31:25.279 --> 00:31:41.039
But the the big challenge that you often have is that you're going against data that is not necessarily standardized in a way, or there's an AI front end that standardizes it in a way to really get meaningful data back in the proper way.
00:31:41.200 --> 00:31:54.480
So that's where a lot of our tools, in fact, inside of our core platform, we're actually building out that new agentic layer so that you can access data in a more effective and efficient manner, just in our core operational database.
00:31:54.640 --> 00:32:05.680
You're looking at uh you know various um MCP servers, you're looking at uh GraphQL data so that you have a more standardized language, I guess, almost to communicate with the data.
00:32:05.839 --> 00:32:07.759
So all that stuff is kind of critical as well.
00:32:07.839 --> 00:32:13.440
And just implementing tools and saying, let me point it to this data and therefore I'm gonna do better, unlikely.
00:32:13.599 --> 00:32:17.200
Not to mention the fact that these tools are changing almost daily.
00:32:17.440 --> 00:32:24.000
Um each week there's a new release of one of these models out there, and there's various harnesses that will tie into your data better.
00:32:24.079 --> 00:32:25.759
And so there really needs to be a structure.
00:32:25.839 --> 00:32:28.640
So that's in fact the advisor IQ I mentioned earlier.
00:32:28.799 --> 00:32:37.680
We built that as a harness that's looking at your data that has very targeted skills that are already predefined against very targeted data that's also predefined.
00:32:37.759 --> 00:32:45.759
So I have that language that I'm communicating with and how and through, that's all bringing back some really highly effective data.
00:32:46.000 --> 00:32:51.759
If you're just experimenting on your own, I suspect you won't be particularly happy with the results.
00:32:51.920 --> 00:32:55.039
So you need tools that are really targeted for that purpose.
00:32:55.440 --> 00:33:05.279
Well, speaking of results, uh for a retailer that does go all in on Farsight IQ, what does the success metrics uh, what do they actually look like?
00:33:05.359 --> 00:33:06.559
Like let's say a year in?
00:33:06.640 --> 00:33:12.240
Is it is it like fewer stockouts, is it better margins, is it just faster overall planning?
00:33:12.480 --> 00:33:15.599
What's the what are those what's the kind of the scoreboard you're looking at?
00:33:16.000 --> 00:33:16.640
Good question.
00:33:16.799 --> 00:33:19.359
I think kind of tied back to what I said earlier.
00:33:19.519 --> 00:33:23.119
For some retailers, success starts with you forecast accuracy.
00:33:23.200 --> 00:33:31.839
If you reprove the demand signal, like I said, downstream, everything else improves, buying allocation, replenishment, pricing, marks downs, planning, everything else.
00:33:32.000 --> 00:33:46.960
Other retailers might be looking again at specifically fewer stockouts, those types of things, but reducing excess inventory, improving sell through, protecting margin, which a lot of people sort of ignore, um, or reducing markdown exposure.
00:33:47.039 --> 00:33:50.000
So I think there's that productivity story as well.
00:33:50.160 --> 00:33:55.119
Planning and merchandising teams, spend a lot of time gathering data, reconciling spreadsheets.
00:33:55.200 --> 00:34:10.079
A lot of people are still using spreadsheets today, debating about assumptions, and then we're trying to also bring everything together so that you're looking at one common set of data, and AI can kind of surface these exceptions more easily for you when you're looking at a common set of data.
00:34:10.159 --> 00:34:14.079
So I think there's even that operational productivity set of things.
00:34:14.239 --> 00:34:16.639
So you are we seeing risks earlier?
00:34:16.800 --> 00:34:18.400
Are we acting faster?
00:34:18.639 --> 00:34:26.079
Are we connecting merchandising supply chain finance, uh, store operations around that same demand signal?
00:34:26.320 --> 00:34:32.159
And then more importantly, I guess to the earlier point we were talking about with the human in the loop, are we learning from these outcomes?
00:34:32.320 --> 00:34:37.199
We being the team, but also we being the aggregate of the AI and the team.
00:34:37.360 --> 00:34:40.159
And are we making our business more responsive?
00:34:40.239 --> 00:34:41.920
So I think that's kind of our goal.
00:34:42.079 --> 00:34:49.199
Success looks like to me is measurable operational improvements, a smarter way to run your business over in general.
00:34:49.679 --> 00:34:52.719
It sounds like that they're all they're all very interconnected, right?
00:34:52.880 --> 00:34:56.960
Because I feel like
you know, better forecasts, you're gonna uh it's gonna lead to fewer markdowns.
00:34:57.280 --> 00:35:09.519
Fewer markdowns is gonna lead to to better margins, and then um, you know, your your planners, um, whoever's, you know, the humans in the loop, they get they get their time back on top of it, which is um always a plus.
00:35:09.920 --> 00:35:12.719
There's a chain reaction of positive outcomes, it sounds like.
00:35:12.800 --> 00:35:20.559
Um, but this is this has really been really insightful, and I appreciate your taking your time to to give us the rundown of of the Farsight IQ platform.
00:35:20.719 --> 00:35:34.320
Um, I want to circle, uh just like cap off this episode and focus the the last question on you um because you've had a long, you know, career working uh in retail, but both, like I said in in the intro, both sides of the counter.
00:35:34.480 --> 00:35:36.880
Um, you were uh COO, CEO.
00:35:37.039 --> 00:35:39.360
Um, you're on the SourceForge podcast.
00:35:39.440 --> 00:35:42.480
So, I mean, you obviously have uh been quite successful.
00:35:42.719 --> 00:35:48.159
Um, if you could go back to the start of your career, what's what's one piece of advice you'd give yourself?
00:35:48.559 --> 00:35:57.920
You know, sort of how my career has kind of gone anyway, that I would probably tell myself to pay as much attention to the decisions being made and not the systems.
00:35:58.079 --> 00:36:12.480
So as I transitioned from retail, the first half of my career, into technology, there's a tendency to jump into the systems and what the systems do and what they're accomplishing rather than what's the decision behind what that system is supposed to be doing.
00:36:12.719 --> 00:36:21.280
You know, so earlier in my career, especially in technology, you know, it was easier to focus on the features, modules, these screens, how it was implemented, all of those things.
00:36:21.440 --> 00:36:29.199
But over time you start to realize again, it really goes back to what we were trying to accomplish and how do we accomplish that more effectively.
00:36:29.280 --> 00:36:34.559
So I think that's probably the main thrust of what I would say if I really could go back in time.
00:36:34.719 --> 00:36:37.119
And it's kind of been my path, I suppose.
00:36:37.199 --> 00:36:46.559
But where I would really want to focus on, even when I get into technology, is are we actually delivering on the promise of what this is supposed to be doing?
00:36:47.360 --> 00:36:48.159
I love that answer.
00:36:48.239 --> 00:36:49.280
That's that's so true.
00:36:49.360 --> 00:37:06.079
And I feel like it's it's harder, becoming more and more difficult for uh individuals to make you know effective decisions um and improve their decision making when we when we kind of offload a lot of our our processing to these external um you know brains uh with AI and whatnot.
00:37:06.239 --> 00:37:11.840
And so it's it's um you gotta you gotta take everything to account, make the proper decision that'll set you up for success.
00:37:11.920 --> 00:37:15.679
I think that just runs into the in the DNA of um Jesta too, right?
00:37:15.920 --> 00:37:19.280
You guys have been in the business uh for 55 some years.
00:37:19.519 --> 00:37:32.079
You kind of obviously have been, I'm sure, have been watching this AI uh moment and like they're determining when to jump in and and and when to actually make uh a product and a platform that's gonna make a difference.
00:37:32.239 --> 00:37:36.559
And um, you know, you don't want to to rush it out prematurely.
00:37:36.639 --> 00:37:42.000
And so Yeah, I think Farsight was a a very major multi-year investment.
00:37:42.159 --> 00:37:45.519
We've been, you know, before we launched it, there was a lot of stuff going on.
00:37:45.599 --> 00:37:56.079
And of course, the market was changing very rapidly in that period of time that we were building this, and even as we were building it, we were making that iterative series of adjustments, but there's no question about it.
00:37:56.159 --> 00:38:00.960
And of course, we continue to add and build on top of it because things are still continuing to change.
00:38:01.199 --> 00:38:05.039
So we need to be uh receptive to that and and adapted to that.
00:38:05.280 --> 00:38:11.760
You know, it's it's really about helping, I think, retailers move from hindsight to foresight and then from foresight to action.
00:38:11.920 --> 00:38:17.679
So there's where I think we're layering those extra from foresight to action components as we speak today.
00:38:17.840 --> 00:38:26.960
Some of the other things I talked about skills and being able to allow the agents over time to do more work for you, but I don't think the market's quite there yet.
00:38:27.119 --> 00:38:29.119
So let's make sure your humans in a loop.
00:38:29.280 --> 00:38:34.639
They're very uh very involved in making the final decisions and using their judgment as well.
00:38:34.719 --> 00:38:42.960
So well, for those interested in learning more about the platform FarsightIQ as well as JESTA, where's the best place to go to learn more?
00:38:43.360 --> 00:38:47.920
I think the best place to go is I would suggest right now FarsightIQ.com.
00:38:48.239 --> 00:38:52.639
FarsightIQ.com also ties back into the jestis.com.
00:38:52.719 --> 00:39:02.320
Uh and they can certainly go to this contact page, and I would welcome people to schedule a meeting with us on really either of the two platforms uh or reach out to me directly.
00:39:02.400 --> 00:39:10.480
I'm happy to have people reach out to me directly as well, uh, which is just spierson at jestis.com and happy to further conversations.
00:39:10.639 --> 00:39:11.679
Looking forward to it.
00:39:12.000 --> 00:39:12.400
Perfect.
00:39:12.480 --> 00:39:16.800
Yeah, we'll include links to everything mentioned uh down below in the in the show notes.
00:39:16.960 --> 00:39:19.519
But Scott, thank you so much for everything you shared with us.
00:39:19.599 --> 00:39:27.119
I I really did uh I think I think this is a really valuable conversation, and I hope uh and I know listeners and viewers will get a lot out of it.
00:39:27.199 --> 00:39:29.519
So um I'm excited to hear the feedback on this episode.
00:39:29.599 --> 00:39:30.400
But excellent.
00:39:30.559 --> 00:39:31.679
Thank you very much for your time.
00:39:32.239 --> 00:39:34.559
Thank you for listening to the SourceForge podcast.
00:39:34.639 --> 00:39:36.239
I am your host, Bo Hamilton.
00:39:36.400 --> 00:39:40.960
Make sure to subscribe to stay up to date with all of our upcoming B2B software related podcasts.
00:39:41.119 --> 00:39:42.559
I will talk to you in the next one.