WEBVTT
00:00:04.959 --> 00:00:08.720
Welcome everyone to another episode of Dynamics Corner.
00:00:09.279 --> 00:00:13.439
There's so many abbreviations in the world, and I'm excited about this one.
00:00:13.519 --> 00:00:14.880
I'm your co-host, Chris.
00:00:15.119 --> 00:00:16.239
And this is Brad.
00:00:16.320 --> 00:00:19.679
This episode was recorded on February 9th, 2026.
00:00:19.839 --> 00:00:21.440
Chris, Chris, Chris.
00:00:22.160 --> 00:00:24.000
We had a fun discussion today.
00:00:24.480 --> 00:00:36.960
We were able to start off talking about three-letter acronym trivia, and then we're able to talk about a great suite of applications and offering for customers within Business Central.
00:00:37.280 --> 00:00:41.119
And we were able to have a few additional tangents and talk about AI.
00:00:41.200 --> 00:00:45.840
With us, we had the opportunity to speak with Natalie and Ben from Ruck Software.
00:01:12.000 --> 00:01:12.640
That was pretty cool.
00:01:12.959 --> 00:01:13.920
Sounds much better.
00:01:14.480 --> 00:01:23.280
So you know, I I know it's early in the morning, and before we get started, I came up with a few questions for you.
00:01:24.000 --> 00:01:35.519
And what these questions are is um I I had a long conversation with Natalie recently, and we came up with this topic of three-letter acronyms.
00:01:35.920 --> 00:01:42.319
So I have a list of three-letter acronyms related to software development and ERP software.
00:01:42.480 --> 00:01:46.239
And I want to see if you guys know the answer.
00:01:46.560 --> 00:01:47.200
Alright.
00:01:47.519 --> 00:01:48.159
You ready?
00:01:48.400 --> 00:01:48.799
Yeah.
00:01:49.120 --> 00:01:50.079
We're super ready.
00:01:50.799 --> 00:01:54.719
I know it's early, but I'll give you guys the softballs first.
00:01:55.120 --> 00:01:55.920
API.
00:01:56.079 --> 00:01:57.439
What is API?
00:01:58.560 --> 00:01:59.920
Don't everybody answer at once.
00:02:00.079 --> 00:02:01.280
You should be like jumping off this.
00:02:01.359 --> 00:02:03.599
You know we're doing the business central trivia again soon.
00:02:03.760 --> 00:02:06.079
So do you want it, Natalie?
00:02:06.400 --> 00:02:10.800
No application programming interface?
00:02:11.120 --> 00:02:11.840
Correct.
00:02:12.159 --> 00:02:13.039
Oh, Ben.
00:02:13.520 --> 00:02:14.560
Ben and Natalie.
00:02:14.960 --> 00:02:15.439
I was sweating.
00:02:15.520 --> 00:02:16.800
I was sweating for a second.
00:02:17.039 --> 00:02:19.360
If you need to tap in Chris, you can tap in Chris too.
00:02:20.800 --> 00:02:21.599
SDK.
00:02:25.199 --> 00:02:26.879
This is another technical one.
00:02:28.879 --> 00:02:30.719
Really, really testing us this morning.
00:02:31.039 --> 00:02:34.719
If I have to jump from the technical ones to I'm blanking for now.
00:02:37.120 --> 00:02:42.400
Software development.
00:02:45.280 --> 00:02:46.159
So close.
00:02:46.479 --> 00:02:46.879
Kit.
00:02:46.960 --> 00:02:47.199
That's right.
00:02:47.360 --> 00:02:48.400
Software development kit.
00:02:49.199 --> 00:02:52.159
I may jump over some of these and we'll get into the ERP ones.
00:02:54.159 --> 00:02:54.800
IDE.
00:02:57.759 --> 00:02:59.439
Brad, what's going on right now?
00:02:59.759 --> 00:03:01.439
He's just trying to stump us, Natalie.
00:03:01.680 --> 00:03:04.400
I feel like he knows he's got two non-developers on the line.
00:03:06.319 --> 00:03:08.080
We got the wrong people on the phone.
00:03:08.719 --> 00:03:10.000
Okay, okay, okay.
00:03:10.159 --> 00:03:11.120
We'll jump to that.
00:03:11.280 --> 00:03:13.599
IDE's integrated development environment.
00:03:13.759 --> 00:03:15.520
Well, I mean, some of these we could do.
00:03:15.680 --> 00:03:16.000
Okay.
00:03:16.240 --> 00:03:17.360
We'll jump now.
00:03:17.680 --> 00:03:19.520
What is what is ERP?
00:03:19.840 --> 00:03:22.560
I'll give that one to Natalie so she can get a softball.
00:03:23.439 --> 00:03:25.120
Enterprise resource planning.
00:03:25.919 --> 00:03:27.919
Enterprise resource planning.
00:03:28.240 --> 00:03:29.120
CRM.
00:03:30.319 --> 00:03:32.639
Customer released management management.
00:03:32.879 --> 00:03:33.199
Okay.
00:03:33.520 --> 00:03:34.240
S CM.
00:03:36.560 --> 00:03:38.000
Supply chain management.
00:03:39.120 --> 00:03:40.159
WMS.
00:03:41.199 --> 00:03:42.319
Warehouse management system.
00:03:42.639 --> 00:03:43.759
Are these easier for you guys?
00:03:44.479 --> 00:03:45.280
I had some software on this.
00:03:47.280 --> 00:03:47.759
MRP?
00:03:48.479 --> 00:03:48.960
MRP.
00:03:49.759 --> 00:03:51.280
Material resource planning.
00:03:53.120 --> 00:03:54.879
Do we get to go in the other way later?
00:03:55.120 --> 00:03:56.639
Like later, do we get to ask you?
00:03:56.800 --> 00:03:58.159
Do we get to quiz you at the end?
00:03:58.400 --> 00:03:59.120
Absolutely.
00:03:59.360 --> 00:04:00.479
Absolutely.
00:04:01.759 --> 00:04:04.800
There have to be something that is valid and within our space.
00:04:04.879 --> 00:04:06.319
All of these are within our space.
00:04:06.400 --> 00:04:12.240
I I sat up late last night and I uh working long and hard to come up with these.
00:04:12.479 --> 00:04:13.840
So yes, yes.
00:04:14.240 --> 00:04:16.639
During that we did we do BOM during the game.
00:04:18.639 --> 00:04:19.040
He did.
00:04:19.120 --> 00:04:20.240
He did do BOM.
00:04:20.319 --> 00:04:21.360
He Ben got it.
00:04:24.079 --> 00:04:24.800
You guys threw me off.
00:04:24.879 --> 00:04:29.680
I have uh A D H Remember you can't you can't say that when you're when you're flying.
00:04:29.759 --> 00:04:30.959
You can't say B O's.
00:04:31.600 --> 00:04:32.240
Yeah.
00:04:34.560 --> 00:04:38.720
You know, that would be an interesting conversation to have.
00:04:39.839 --> 00:04:40.639
KPI.
00:04:40.800 --> 00:04:41.600
Ben, you know that one.
00:04:41.680 --> 00:04:44.160
I know you know key performance indicators.
00:04:44.560 --> 00:04:45.120
Yes, sorry.
00:04:45.360 --> 00:04:46.000
EDI.
00:04:46.879 --> 00:04:48.480
Electronic data interchange.
00:04:49.839 --> 00:04:50.480
S K U.
00:04:51.279 --> 00:04:52.399
Stock keeping unit.
00:04:53.120 --> 00:04:54.079
RFQ.
00:04:55.759 --> 00:04:56.480
Request for quote.
00:04:56.720 --> 00:04:57.279
Request for quote.
00:04:57.839 --> 00:04:58.000
Yes.
00:04:58.959 --> 00:05:01.439
POS, and we're not talking the profanity.
00:05:02.079 --> 00:05:02.879
That's where I was talking about.
00:05:03.040 --> 00:05:03.439
Point of sale.
00:05:03.680 --> 00:05:04.079
Point of sale.
00:05:04.319 --> 00:05:05.040
I know that's where you're going.
00:05:05.199 --> 00:05:06.399
That's why I had to cut this off.
00:05:06.560 --> 00:05:09.439
We're keeping this rated G today, hopefully.
00:05:09.600 --> 00:05:09.839
We'll see.
00:05:10.240 --> 00:05:10.959
That's good to know.
00:05:11.279 --> 00:05:12.079
MPS?
00:05:13.600 --> 00:05:13.920
N?
00:05:15.199 --> 00:05:15.279
M.
00:05:15.439 --> 00:05:15.759
I'm sorry.
00:05:15.839 --> 00:05:16.879
That's my northeast accent.
00:05:17.120 --> 00:05:18.079
Oh, you're gonna M.
00:05:18.959 --> 00:05:19.680
MPS.
00:05:20.319 --> 00:05:20.800
Yes.
00:05:21.279 --> 00:05:23.199
Material planning system.
00:05:29.040 --> 00:05:33.600
I should have just said, I should have just ran with NPS and gone net for motor score and just said next question.
00:05:34.240 --> 00:05:34.480
That's it.
00:05:34.560 --> 00:05:34.959
That's it.
00:05:35.040 --> 00:05:37.519
You should have master production schedule.
00:05:37.680 --> 00:05:40.079
I'm going to do another one.
00:05:41.839 --> 00:05:42.800
R UX.
00:05:44.560 --> 00:05:44.879
Oh.
00:05:46.639 --> 00:05:48.399
What does it stand for, Ben?
00:05:49.519 --> 00:05:51.680
Uh it doesn't stand for anything.
00:05:53.040 --> 00:05:56.879
I like the I like the crowdsourced multiple people.
00:05:57.040 --> 00:05:59.920
Is it rental UX?
00:06:00.240 --> 00:06:04.319
And I was like, sure, user interface or sure.
00:06:04.959 --> 00:06:06.720
It can mean whatever you want it to mean.
00:06:09.439 --> 00:06:11.120
It can mean many different things.
00:06:11.279 --> 00:06:14.959
And with that, would you mind taking a moment to introduce yourselves?
00:06:15.120 --> 00:06:16.319
We'll start with Ben.
00:06:17.040 --> 00:06:17.600
Sounds good.
00:06:17.839 --> 00:06:18.879
My name's Ben Cole.
00:06:19.040 --> 00:06:22.560
I'm currently a uh strategic sales executive at Rux.
00:06:22.879 --> 00:06:29.040
Uh in July of last year, I had my business, ERP Connect, um, that merged with uh Rux.
00:06:29.439 --> 00:06:30.800
So join the family.
00:06:31.120 --> 00:06:42.879
And uh as many people probably know, had the business central toolbox, which was more the horizontal tools, and then I'll let Natalie introduce herself and talk about some of the industry verticals that we focus on as well.
00:06:43.199 --> 00:06:43.360
Thanks.
00:06:43.920 --> 00:06:44.399
Natalie.
00:06:44.879 --> 00:06:46.160
I'm Natalie Lemke.
00:06:46.240 --> 00:06:48.240
I'm the CEO of Rux Software.
00:06:48.560 --> 00:06:57.360
We provide uh business central integrated solutions for organization organizations in the industrial asset management space.
00:06:57.600 --> 00:07:09.439
So think about businesses that have uh big commercial assets like cranes, trenching equipment, uh oil field equipment, and the related labor that services that equipment.
00:07:09.519 --> 00:07:13.680
Uh, and we deliver those solutions inside of Business Central.
00:07:13.839 --> 00:07:18.879
Uh the business was relaunched August of last year under the new brand name Rux.
00:07:20.079 --> 00:07:25.839
And now we know Rux means whatever you want it to mean.
00:07:26.879 --> 00:07:27.680
It does, right?
00:07:28.160 --> 00:07:29.759
We do with the rental equipment.
00:07:32.399 --> 00:07:36.959
I like I like there's all sorts of fun alliterations you can do, like Rux Rux.
00:07:37.839 --> 00:07:39.279
Uh Rux Rucks.
00:07:39.439 --> 00:07:39.600
Rux.
00:07:40.160 --> 00:07:41.519
Rucks runs rentals.
00:07:42.399 --> 00:07:43.759
Rux runs rentals.
00:07:43.839 --> 00:07:44.160
I like that.
00:07:44.240 --> 00:07:45.199
I like that R UI.
00:07:45.439 --> 00:07:50.800
See, it is interesting because it it does spark the question.
00:07:50.879 --> 00:08:00.560
And it also gives you the idea to have a three-letter acronym trivia game first thing in the morning without telling anyone to be prepared for it.
00:08:00.959 --> 00:08:06.000
So we do appreciate you uh being you know passing the exam that you had to take this morning.
00:08:06.079 --> 00:08:11.759
Your week can be uh set off right, but uh uh there's a lot of things I want to talk about.
00:08:11.839 --> 00:08:13.680
Ben, you had the the BC toolbox.
00:08:13.759 --> 00:08:26.240
Uh, you'd like to see a lot of your videos, and now I see you switched over to Rux with your your wonderful videos on tips and tricks and uh Freaky Friday uh uh extravagance that you do.
00:08:26.399 --> 00:08:27.600
Uh Natalie.
00:08:27.839 --> 00:08:34.399
Um would you mind telling us a little bit more about the rental portion of the Rux offering?
00:08:34.720 --> 00:08:36.480
I do have several questions on that.
00:08:36.559 --> 00:08:46.159
I know we spoke about it briefly when we had the opportunity to uh enjoy the cold weather at the Tampa event, not to talk about that again, but the rain that never came.
00:08:46.480 --> 00:08:52.240
Yeah, the rain that never came and the cold weather that Florida has been experiencing.
00:08:52.399 --> 00:08:53.679
None of us know what to do.
00:08:53.759 --> 00:08:59.360
It's been below 50 degrees most days, and there was frost on the grass last week.
00:08:59.600 --> 00:09:01.919
Oh god, whoa, 50.
00:09:02.159 --> 00:09:03.600
We're above 50 where I'm at.
00:09:03.840 --> 00:09:04.320
That's crazy.
00:09:04.720 --> 00:09:07.120
So you you're going to trigger me for this, though.
00:09:07.279 --> 00:09:12.559
I came back and this is the coldest it's been since 1900, I believe.
00:09:12.879 --> 00:09:17.039
And all of my stuff is dead, was burned.
00:09:17.200 --> 00:09:19.919
Like my entire backyard is brown.
00:09:20.159 --> 00:09:27.440
Like my plants, trees, bushes, just brown, and the leaves are falling off from the cold that we had.
00:09:27.679 --> 00:09:32.639
Uh, hopefully they all grow back because you know we're not supposed to have frost down here, like this far south.
00:09:32.720 --> 00:09:35.039
You're further north than I am, but this far south.
00:09:37.279 --> 00:09:39.039
I'm not made for this.
00:09:40.720 --> 00:09:41.039
Okay.
00:09:41.200 --> 00:09:47.039
Sorry for the the brief tangent, but to jump into the Rux rental rocking offering.
00:09:47.440 --> 00:09:48.399
Yeah, absolutely.
00:09:48.639 --> 00:09:58.159
So the easiest way to think about the rentals product that we provide is that it connects the fixed asset in Business Central with the revenue production process.
00:09:58.399 --> 00:10:03.919
So uh you use the three-letter acronym during the game show portion, RFQ.
00:10:04.159 --> 00:10:19.200
So we connect with quoting, we have a module that delivers features like rental contracts, the association of that contract to assignment of assets, pricing of those assets through nonlinear pricing.
00:10:19.279 --> 00:10:28.000
So if you think about hourly rate, day rate, week rate, month rate for renting that asset, different types of uh monetization.
00:10:28.159 --> 00:10:34.720
So usage-based monetization through time, um hours.
00:10:34.960 --> 00:10:44.399
Uh, it could be connected to labor usage with that industrial asset, and then through the closing of that contract, the invoicing of that rental periodic.
00:10:44.639 --> 00:10:48.720
I wrote a couple down for I was gonna say, what do we think MVP stands for?
00:10:48.879 --> 00:10:51.039
Oh minimum viable product?
00:10:51.279 --> 00:10:53.440
Yes, minimum viable product.
00:10:53.519 --> 00:10:54.960
Oh, so you have some you want to ask.
00:10:55.200 --> 00:11:02.080
We can go back, we'll go back to the rental, but if we want to rewind it, we want to, yes, uh, we want to do a quick rewind and you can ask us some.
00:11:02.159 --> 00:11:02.960
Go ahead.
00:11:03.679 --> 00:11:05.679
I wrote I wrote down a whole page.
00:11:05.840 --> 00:11:07.840
I was thinking about it after our conversation.
00:11:08.000 --> 00:11:08.720
I was like, I wonder.
00:11:09.600 --> 00:11:12.799
The conversation this morning, or if we have a whole page already?
00:11:13.840 --> 00:11:14.320
Whoa.
00:11:15.440 --> 00:11:16.159
Natalie can't.
00:11:16.399 --> 00:11:18.960
You can't have you prepared.
00:11:19.279 --> 00:11:20.720
Uh I've got one.
00:11:21.120 --> 00:11:28.000
Uh well, Ben, Ben maybe voted off the island because Ben is not wearing his hat.
00:11:28.639 --> 00:11:30.000
Uh it has not arrived.
00:11:31.360 --> 00:11:35.679
So when you get that check for tracking information, it has not arrived.
00:11:36.080 --> 00:11:37.600
Listen, that's the USPS.
00:11:37.840 --> 00:11:39.200
What's that acronym?
00:11:39.519 --> 00:11:40.320
Oh, trust me.
00:11:40.480 --> 00:11:41.840
It means it's not going to be delivered on time.
00:11:41.919 --> 00:11:43.200
That's what I know the acronym means.
00:11:43.519 --> 00:11:57.679
The USPS that that that tracking system for the USPS is probably the worst thing invented since the invention of what's the another bad invention.
00:12:00.080 --> 00:12:08.399
We need we need the Domino's pizza tracker software developers to just take a weekend and fix the USPS tracking system.
00:12:08.799 --> 00:12:11.200
I'm sure they could vibe hackathon for those people.
00:12:11.600 --> 00:12:13.759
I'm sure they could barco it because that's awful.
00:12:13.919 --> 00:12:17.120
All right, Ben, well, when that happens uh to arrive, we'll get it.
00:12:17.279 --> 00:12:27.679
Um, we'll have to you know see it everywhere going forward, you know, uh at the trade shows, at the Ben's Tips on Friday, and all those other things.
00:12:28.240 --> 00:12:37.039
You can you can be a guest star on like uh we could do we could it's a feature Friday, but we could do a freaky Friday where we like switch bodies and your meeting.
00:12:37.840 --> 00:12:40.159
But but I'm you oh we'll do that.
00:12:40.240 --> 00:12:42.080
That's uh we'll talk after this.
00:12:42.159 --> 00:12:43.039
But yes, I'm sorry.
00:12:44.000 --> 00:12:46.320
I know it's feature Friday, but it's that type of morning.
00:12:46.480 --> 00:12:48.720
Uh I do appreciate your feature Friday, by the way.
00:12:49.039 --> 00:12:54.960
My my not controversial, but just people always make fun of me for it is what does EOD stand for?
00:12:55.120 --> 00:12:56.320
Well, it's it's end of day, right?
00:12:56.399 --> 00:12:58.480
But like what does that mean to different people, right?
00:12:58.639 --> 00:13:04.159
Is your end of day five o'clock, four thirty, or or or midnight, right?
00:13:04.399 --> 00:13:06.960
I feel like those are the only the only options.
00:13:07.039 --> 00:13:10.879
So I was wondering, Brad and Chris, what are your EODs?
00:13:11.519 --> 00:13:14.720
The I was first going to say explosive ordnance detachment.
00:13:17.600 --> 00:13:18.720
That was my first one.
00:13:18.879 --> 00:13:20.240
What is my EOD?
00:13:21.600 --> 00:13:26.879
I honestly feel like never because I feel like I just have one continuous D.
00:13:27.440 --> 00:13:30.960
Um, to be honest with you, one continuous day.
00:13:31.200 --> 00:13:33.360
It starts early and ends late, unfortunately.
00:13:33.519 --> 00:13:34.799
I take breaks throughout the day.
00:13:34.879 --> 00:13:39.039
So my end of day ultimately is about 2130.
00:13:39.279 --> 00:13:45.840
So if you told somebody I'll have it to you by end of day, it would be around 2130 Eastern.
00:13:46.480 --> 00:13:48.720
Depends how I feel at during that day.
00:13:48.799 --> 00:13:50.720
Because end of day be like at 5 p.m.
00:13:50.879 --> 00:13:52.320
I really don't want to talk to anyone.
00:13:52.559 --> 00:14:00.480
In some heads in the context of like a deliverable, not a in the context in the deliverable, I would say 1700 is end of day.
00:14:00.639 --> 00:14:01.600
Is is again.
00:14:01.679 --> 00:14:07.679
So my end of day, like when I work and stuff, is I usually will pause, eat for the evening.
00:14:07.840 --> 00:14:12.320
If I don't have anything major going on, I'll sit down and work until maybe 2100, 2130.
00:14:12.480 --> 00:14:17.600
But if I were to have to if I were to coordinate a time with someone, EOD would be 1700.
00:14:17.679 --> 00:14:17.759
Yeah.
00:14:17.840 --> 00:14:18.159
That's fair.
00:14:18.480 --> 00:14:23.919
End of day for me, it's more uh I I want to respect the person that I said that to.
00:14:24.080 --> 00:14:31.120
So usually if they're East Coast, you know, like Brad, and I say end of day, I'll make sure it's gonna be 1700.
00:14:31.279 --> 00:14:36.879
But if it's like I don't know, Ben, that's like a maybe 2300 for you.
00:14:37.120 --> 00:14:38.559
Yeah, that's fair.
00:14:38.720 --> 00:14:41.519
Hey, I'll probably I'll be on and I'll probably respond pretty quickly.
00:14:41.600 --> 00:14:42.879
So that's fair.
00:14:43.279 --> 00:14:47.440
Because mine mine is about yeah, mine's about 11, 11 p.m.
00:14:47.679 --> 00:14:48.159
Central.
00:14:48.399 --> 00:14:49.360
There you go.
00:14:49.679 --> 00:14:51.360
So that's midnight.
00:14:51.759 --> 00:14:53.759
Midnight midnight for you guys, yeah.
00:14:54.080 --> 00:14:54.960
Okay, got it.
00:14:55.200 --> 00:14:58.480
Basically, it just means it'll be in your inbox before you wake up.
00:14:59.519 --> 00:15:08.000
Okay, so you think e so that it this is an interesting topic because I brought quality, not quantity.
00:15:08.399 --> 00:15:14.879
No, I it's it's how you infer uh words in a sense, because you said end of day.
00:15:15.039 --> 00:15:18.960
End of day to you means you'll get it in by the morning, you know, by the time you wake up.
00:15:19.279 --> 00:15:24.639
But what if somebody wakes up at 112300 Central?
00:15:25.519 --> 00:15:28.159
If they're working night shift, I you know, I don't I don't have any.
00:15:28.399 --> 00:15:29.120
No, I I understand.
00:15:29.360 --> 00:15:31.039
All jokes aside, that's interesting.
00:15:31.279 --> 00:15:37.600
So well then should we just say you'll get it when by the morning?
00:15:37.919 --> 00:15:39.279
By B-O-D?
00:15:39.679 --> 00:15:40.399
B-O-N-D?
00:15:40.720 --> 00:15:41.360
B-O-D, yeah.
00:15:41.519 --> 00:15:42.159
B-O-D.
00:15:42.559 --> 00:15:43.279
That would be good.
00:15:43.519 --> 00:15:44.559
That was uh that's interesting.
00:15:44.639 --> 00:15:46.399
That's making me make our own acronyms.
00:15:46.480 --> 00:15:47.759
We can make up our own acronyms.
00:15:49.120 --> 00:15:49.600
Rucks.
00:15:50.320 --> 00:15:50.559
Bond.
00:15:50.799 --> 00:15:52.399
B-O-N-D, beginning of next day.
00:15:52.480 --> 00:15:53.279
That's my new acronym.
00:15:53.519 --> 00:15:54.240
Oh, there you go.
00:15:54.720 --> 00:15:55.519
You'll get it.
00:15:56.080 --> 00:15:57.279
You get it bond.
00:15:59.039 --> 00:16:00.000
Okay, Natalie.
00:16:00.159 --> 00:16:00.799
Late on us.
00:16:01.039 --> 00:16:02.159
Yeah, what do you got?
00:16:03.360 --> 00:16:04.879
Ooh, I had a couple more.
00:16:04.960 --> 00:16:05.919
I had B O L.
00:16:06.240 --> 00:16:06.960
Bill of Lading.
00:16:07.200 --> 00:16:07.919
Bill of Lading.
00:16:09.600 --> 00:16:10.159
Could work.
00:16:10.480 --> 00:16:11.200
Are we pausing?
00:16:11.360 --> 00:16:15.679
Are we buzzing in or just no, just go for it?
00:16:15.919 --> 00:16:16.879
So just just shout.
00:16:17.039 --> 00:16:17.519
Just shout.
00:16:17.759 --> 00:16:19.200
And Ben's participating.
00:16:20.320 --> 00:16:21.840
I mean, I think you should too.
00:16:22.000 --> 00:16:23.679
I'm just I'm just that wasn't a question.
00:16:23.759 --> 00:16:24.399
That was a statement.
00:16:24.879 --> 00:16:39.440
No, I'm just and what's it related to?
00:16:40.320 --> 00:16:40.879
What we do.
00:16:43.279 --> 00:16:46.080
Um executive user transformation?
00:16:47.360 --> 00:16:48.559
End user training.
00:16:49.360 --> 00:16:50.480
I have never heard that before.
00:16:50.879 --> 00:16:51.679
End user training.
00:16:51.919 --> 00:16:56.879
So we do, you know, train the trainer, but what's the thing that we really have to make sure gets done?
00:16:57.360 --> 00:16:58.399
End user training.
00:16:59.120 --> 00:17:00.559
So is train the trainer, triple T?
00:17:02.960 --> 00:17:03.679
TTT?
00:17:03.919 --> 00:17:05.839
I suppose it would be TTT.
00:17:07.920 --> 00:17:11.920
Um and then my favorites, ETC, etc.
00:17:13.119 --> 00:17:16.240
And or Wow, you're stumping.
00:17:16.319 --> 00:17:19.519
Me, I'm going back to my uh software development acronyms.
00:17:19.680 --> 00:17:20.480
I know all those.
00:17:20.720 --> 00:17:21.759
I know I was gonna see.
00:17:22.160 --> 00:17:23.359
Oh man, this is wrong.
00:17:23.680 --> 00:17:24.480
ETC.
00:17:25.599 --> 00:17:28.720
Estimate to complete for all our project managers out there.
00:17:29.359 --> 00:17:30.000
ETC.
00:17:30.400 --> 00:17:30.960
ETC.
00:17:32.240 --> 00:17:35.680
And it goes together with another acronym, EAC.
00:17:38.480 --> 00:17:39.680
Estimate at complete.
00:17:40.160 --> 00:17:40.960
At complete.
00:17:41.200 --> 00:17:44.880
Trying to think, what do I say for what's your ETA?
00:17:45.119 --> 00:17:46.319
E C A C.
00:17:46.799 --> 00:17:51.119
You're just like, I'm gonna get it to you by EOD and it's gonna be done and it won't matter.
00:17:54.720 --> 00:17:55.039
Okay.
00:17:55.279 --> 00:17:58.559
Or what we say in my house, you get what you get and you don't have a fit.
00:17:59.359 --> 00:18:01.359
Um both work.
00:18:01.759 --> 00:18:05.680
Uh okay, and then um MFA.
00:18:06.079 --> 00:18:08.000
Multi-factor authentication.
00:18:08.960 --> 00:18:10.960
Bingo tied with SSO.
00:18:11.359 --> 00:18:12.799
Single signal sign-on.
00:18:13.839 --> 00:18:15.200
Well, now you're talking my language.
00:18:15.440 --> 00:18:18.400
Uh and then I wrote down F D D.
00:18:18.640 --> 00:18:20.319
Functional Design document.
00:18:21.119 --> 00:18:21.759
Yes, yes.
00:18:22.000 --> 00:18:23.119
C R D P R D.
00:18:23.440 --> 00:18:24.319
Functional design document.
00:18:24.559 --> 00:18:25.119
C R D.
00:18:27.279 --> 00:18:27.920
C R D.
00:18:28.160 --> 00:18:28.640
Yeah.
00:18:29.920 --> 00:18:30.400
C R D.
00:18:30.640 --> 00:18:31.759
It's gonna be a whole episode of that.
00:18:32.000 --> 00:18:33.279
It sounds like a pasta.
00:18:33.359 --> 00:18:37.200
I was gonna say like a change request change change request document.
00:18:37.279 --> 00:18:38.640
Oh change request document.
00:18:38.960 --> 00:18:39.599
None of that.
00:18:39.759 --> 00:18:40.559
None of that.
00:18:40.720 --> 00:18:42.400
You had an EDI one, A S N.
00:18:42.720 --> 00:18:43.759
Advanced ship notice.
00:18:43.839 --> 00:18:44.079
Yeah.
00:18:44.640 --> 00:18:46.079
Advanced ship notice.
00:18:46.640 --> 00:18:47.920
And then POA.
00:18:49.119 --> 00:18:50.400
This is another EDI one.
00:18:51.119 --> 00:18:54.480
Point of acceptance.
00:18:55.519 --> 00:18:56.880
Chris is gonna get it.
00:18:57.519 --> 00:18:58.319
P O A?
00:18:59.920 --> 00:19:00.480
P O A.
00:19:00.799 --> 00:19:02.480
And it's an EDI document.
00:19:02.960 --> 00:19:04.880
Go back to my friend here.
00:19:05.680 --> 00:19:06.960
Purchase order.
00:19:10.160 --> 00:19:11.119
Acceptance.
00:19:12.960 --> 00:19:14.319
Purchase order acknowledgement.
00:19:14.559 --> 00:19:15.440
Oh, acknowledge exit.
00:19:16.000 --> 00:19:16.559
Mm-hmm.
00:19:16.799 --> 00:19:17.279
Mm-hmm.
00:19:17.759 --> 00:19:19.759
Oh, I I had a typo.
00:19:20.240 --> 00:19:23.039
I put P O T and it's purchase order transfer.
00:19:23.279 --> 00:19:25.279
So pot.
00:19:27.359 --> 00:19:29.440
Listen, I tried to type quickly in.
00:19:29.839 --> 00:19:31.680
I'll get you the pot by EOD.
00:19:32.480 --> 00:19:35.920
I don't think the A and the T are next to each other on the keyboard.
00:19:36.000 --> 00:19:37.279
What's going on over there, Brad?
00:19:37.599 --> 00:19:38.720
Here is on your ASN.
00:19:39.759 --> 00:19:40.799
What's going on with the keyboard?
00:19:40.880 --> 00:19:43.759
I usually don't have a keyboard when I do this, to be honest with you.
00:19:43.839 --> 00:19:48.880
This is the first time that I've used a keyboard, so I'm able to type.
00:19:49.119 --> 00:19:51.839
Usually I just click.
00:19:52.079 --> 00:19:53.519
Or I use my phone.
00:19:53.680 --> 00:19:55.920
But then I always see myself in the videos going.
00:19:56.880 --> 00:19:59.200
So now I just decided to type today.
00:19:59.440 --> 00:20:04.000
Okay, so jump back to the rental software and the other Rux offerings.
00:20:04.400 --> 00:20:08.480
You have an interesting story with the whole rental software as well, too.
00:20:08.720 --> 00:20:12.400
Can you give us a little backstory of the uh rental software?
00:20:12.559 --> 00:20:15.839
I remember it being an interesting story, but I don't remember the story.
00:20:17.039 --> 00:20:20.960
Oh, I'll give you the uh the abridged version.
00:20:21.119 --> 00:20:27.200
Um so uh let's see, where should we start this story?
00:20:27.599 --> 00:20:44.640
Um a little over a year ago, I had the good fortune of partnering with Juxtapose and meeting Malcolm and Christian Roach, who had uh software that they had designed specifically targeted at oil and oil field service organizations.
00:20:45.279 --> 00:20:48.000
And they'd done a wonderful job building the software.
00:20:48.160 --> 00:20:54.240
They re-architected it when Business Central was released, specifically to be a cloud native solution.
00:20:54.400 --> 00:21:00.000
They had clients all over the world using the system, um, and it was time for Malcolm to retire.
00:21:00.240 --> 00:21:07.279
And so uh I had the very good fortune of stepping into the business um and taking over the reins.
00:21:07.440 --> 00:21:14.720
The thing that was interesting is the software didn't have the technical debt that you typically see with a business that's 30 years old.
00:21:14.880 --> 00:21:30.799
The system had been well maintained, and because there were so many clients on the platform, we had a lot of really rich customer feedback about how the operating system was working, what was working well, where there was customer feedback and what could work better in the software.
00:21:30.960 --> 00:21:54.720
And I think that's something that when Ben and I first met and spent time talking with each other, one of the things that he is really passionate about as well is knowing and understanding all right, this is how we think the software should be built, here's what the functional consulting mind looks at, here's what the developer mind looks like looks at, here's what the solution architect looks at and thinks this is what a well architected and well designed system should be.
00:21:55.039 --> 00:21:59.839
But really, it's clients with hands on keyboards and using the software out in the field that make a big impact.
00:22:00.480 --> 00:22:18.559
And so we are able to take that input from clients in the beginning of 2025 and use that to inform our product roadmap over the last 12 months and into the next several years to say what are the things that would most impact the end users that are using the system.
00:22:18.720 --> 00:22:25.039
And the things that we hear consistently are the pricing calculator that we have inside the rental application is unique.
00:22:25.359 --> 00:22:27.440
It provides a lot of value to end customers.
00:22:27.519 --> 00:22:33.680
So connecting that fixed asset to the revenue production process, a very critical part is that pricing engine.
00:22:33.839 --> 00:22:37.039
And then the other thing is the service and maintenance of that asset.
00:22:37.200 --> 00:22:45.599
So if the asset isn't in good working condition, isn't getting planned and unplanned maintenance efficiently managed, that asset isn't out making money.
00:22:45.680 --> 00:22:51.359
And ultimately that's what most of our customers are targeted at doing is having their assets hard at work out in the field.
00:22:51.519 --> 00:22:54.079
And that fits nicely with the toolbox apps.
00:22:54.240 --> 00:22:58.160
We want to make sure that that process is running efficiently and business central.
00:22:58.240 --> 00:23:07.759
So if the assets are hard at work out in the field, we want to make sure that the users that are tracking those things in the system are working efficiently in the application using the right productivity solutions.
00:23:08.559 --> 00:23:08.799
Excellent.
00:23:08.960 --> 00:23:12.480
So no, it's it's a it's a great, it was an interesting story.
00:23:12.640 --> 00:23:26.000
And now the rental I say rental management, but the I guess the rental management um application, it's within Business Central, works with Business Central online, uh, also works with Business Central on premises.
00:23:26.160 --> 00:23:28.960
And if so, how far back do you support?
00:23:31.279 --> 00:23:42.079
Oh um do we have clients on early teen versions of nav?
00:23:42.960 --> 00:23:44.880
Yes, yes, we do.
00:23:45.200 --> 00:23:45.680
Wow.
00:23:45.920 --> 00:23:55.839
Uh are we actively working to help clients find their way to the cloud uh through public or private hosting?
00:23:56.000 --> 00:23:57.359
Yes, yes, we are.
00:23:57.680 --> 00:24:05.039
Um we had a call last Friday with a partner about a client who's on NAV 5.0.
00:24:05.279 --> 00:24:05.839
Wow.
00:24:06.880 --> 00:24:18.319
That is currently not using our rental software, but they are currently using a rental system and they're trying to sort out how they get to current.
00:24:19.359 --> 00:24:19.839
Wow.
00:24:20.079 --> 00:24:25.599
Um, and we see that a lot because there wasn't a lot of really great rental software out 20 years ago.
00:24:25.680 --> 00:24:26.720
So what did people do?
00:24:27.039 --> 00:24:27.839
Manual paper.
00:24:28.079 --> 00:24:29.440
They made great decisions.
00:24:29.599 --> 00:24:35.920
Yeah, they made great decisions, and then they found some really smart nav software developers and were like, hey, let's do this.
00:24:36.079 --> 00:24:38.079
Yes, yes, wow, nav 5.0.
00:24:38.160 --> 00:24:39.359
That's a that's a long journey.
00:24:39.519 --> 00:24:42.400
I hope that's uh I hope that journey goes well for them.
00:24:42.640 --> 00:24:43.920
That um right.
00:24:44.400 --> 00:24:45.119
No, it is.
00:24:45.200 --> 00:24:46.240
It's I'm just thinking back.
00:24:46.319 --> 00:24:48.400
It's just my mind wanders when I hear NAV5.
00:24:48.640 --> 00:24:54.319
I think about where I was when NAV 5.0 came out and how the application has changed since then.
00:24:54.640 --> 00:25:01.039
So you you're you do have customers back, you support Microsoft Dynamics NAT, but your primary focus is at this point is business central.
00:25:01.119 --> 00:25:03.519
And once you're in business central cloud, then you can stay current.
00:25:03.680 --> 00:25:25.359
And I like I'm a big advocate of business central cloud or uh or even hosting to where you can at a point where you you have those updates applied because then you get the latest features of the software, and then also with applications such as features and functionality get released, you get to automatically get those or have those rolled into um the application.
00:25:25.759 --> 00:25:27.119
I got a quick question about you.
00:25:27.200 --> 00:25:31.039
You had mentioned uh the last 12 months you made a lot of improvements.
00:25:31.119 --> 00:25:35.119
You you get a lot of getting feedback from your from your customers.
00:25:35.279 --> 00:25:50.799
Do you did you find that to be uh a huge uh challenge trying to get feedback from end users or or was it pretty straightforward to uh for them to provide their feedback to improve the product?
00:25:51.359 --> 00:26:10.880
I think uh I think for us asking the question to our clients and saying one of the questions that we used, and uh I learned this from um the head of UIUX at Juxtapos, Sloan Hastings, asking the question if you had a magic wand, what do you wish the system could do?
00:26:11.519 --> 00:26:16.880
Clients are more than happy to tell you what they would do if they had a magic wand.
00:26:17.039 --> 00:26:29.839
And sometimes it's small things, like we got some feedback about sub-rentals, sell-offs, and being able to roll back transactions when somebody had processed something with the incorrect unit attached to it.
00:26:30.079 --> 00:26:36.160
So an individual who might be working in the yard that's assigning out units picks the wrong one when they're going through the process.
00:26:36.319 --> 00:26:43.680
And so what ends up getting processed in business central doesn't match what happened in reality, and a user needs to correct that.
00:26:44.319 --> 00:26:50.880
They're happy to tell you the ways that they wish things worked, and it's that question was a really powerful question.
00:26:50.960 --> 00:26:54.079
So we got great feedback using that question.
00:26:54.480 --> 00:26:58.720
The other thing that um we did is we have a series of on safety.
00:26:59.039 --> 00:26:59.359
I like that.
00:26:59.599 --> 00:27:08.400
No, I really think that's a good way to ask somebody, you know, what what do you think, you know, what features do you like, or what do you think it would do?
00:27:08.480 --> 00:27:10.240
But the magic wand is a nice framing.
00:27:10.319 --> 00:27:12.880
I'm going to uh steal it.
00:27:13.119 --> 00:27:13.920
Just telling you.
00:27:14.160 --> 00:27:15.680
You're all welcome to steal it.
00:27:15.759 --> 00:27:20.319
Yes, because it's also a forward-looking, it's not just what do you wish worked better.
00:27:20.480 --> 00:27:33.759
It's also the sometimes users have really innovative process design opportunities where they're like, if I could just get from A to C instead of going through B, you know, that that can be really helpful feedback.
00:27:33.839 --> 00:27:36.319
Um, and then we did a series of on-site visits.
00:27:36.559 --> 00:28:05.119
So our product team went on-site to a variety of different clients, uh, some in conjunction with marketing leadership, others in conjunction with our delivery team, to specifically with the goal of seeing how users were using the product in the field, and then what tasks still were getting done back at the office and understanding what was working efficiently out in the field versus what was working efficiently in the office and where there were inefficiencies.
00:28:05.759 --> 00:28:24.799
Is a great approach because you get to see firsthand how the application's used, and then others uh then you get to see that's it's often what I see in here is it's very easy to design an application or even do modifications for a customer uh if you're doing that based upon um what you think it is that they're talking about.
00:28:24.960 --> 00:28:37.200
But if you can actually physically see, like I've always enjoyed going to having tours of facilities or uh not because then you can see the physical challenges they may have with using an application that you have to take into consideration.
00:28:37.440 --> 00:28:39.519
Uh you talked about having a delivery team.
00:28:39.680 --> 00:28:54.400
Uh the delivery team uh for this application is it do you primarily work and handle the delivery of the implementation of the rentals portion of the application, or do you have partners that do that for you, or is it a combination of both?
00:28:55.279 --> 00:28:56.559
It's a combination of both.
00:28:56.640 --> 00:29:03.680
So today we have a few partners that have done several laps around the track that are very comfortable implementing the application.
00:29:03.920 --> 00:29:08.480
And those partners are fantastic at taking care of their clients.
00:29:08.640 --> 00:29:18.400
And there are some partners who are just getting started with our solutions, and so we pair our experts with their team to deliver the rentals portion of the product or the service portion of the product.
00:29:18.559 --> 00:29:20.720
The same is true for our toolbox apps.
00:29:20.960 --> 00:29:25.680
So we have many partners that are very good at delivering those solutions.
00:29:25.839 --> 00:29:31.359
Uh, the configuration has been made very straightforward by our development team.
00:29:31.519 --> 00:29:38.960
And so the goal is really for partners to be able to deliver that to clients at the at the right time during their implementation or after they've gone live.
00:29:39.119 --> 00:29:56.000
Uh, but to the extent that a partner hasn't gotten that expertise yet, our team is happy to step in and again partner with that um partner to deliver it to that client so that it gets configured in the way that's most optimized for their installation of business central.
00:29:56.640 --> 00:30:15.519
And with the rental management, just if I want to want to unpack sort of what types of challenges that an organization may have with rentals uh and where this fits in, it can manage the purchase of the asset, uh rental of the asset with contracts over periods of time.
00:30:15.680 --> 00:30:17.440
Uh and then also maintenance.
00:30:17.599 --> 00:30:22.160
Did you mention of the assets that are rented as well?
00:30:22.720 --> 00:30:23.680
Uh correct.
00:30:23.839 --> 00:30:25.599
Planned or unplanned maintenance.
00:30:25.759 --> 00:30:39.200
So sometimes it's a piece of equipment that's due for an oil change, and sometimes a door broke on a crane that's on site and it needs on-site repairs.
00:30:39.359 --> 00:30:42.880
Um we also have rental swaps.
00:30:43.039 --> 00:30:51.839
So where there's a piece of equipment that's on the field and something's gone on, where that piece of equipment needs to be switched out for a comparable piece of equipment.
00:30:52.000 --> 00:31:04.400
So the contract can remain continuous and we can switch out that asset so that the job site remains productive and the asset that needs to be brought back to the yard can be brought back.
00:31:04.559 --> 00:31:07.359
And that could be because of maintenance or for another reason.
00:31:07.759 --> 00:31:11.200
You are talking about mobile service of these rentals.
00:31:11.279 --> 00:31:13.759
So I'm assuming there's a back-off portion of the application.
00:31:13.839 --> 00:31:15.839
How does the mobility handle?
00:31:15.920 --> 00:31:20.799
Does it handle with an external application or is it something that's within Business Central?
00:31:21.039 --> 00:31:21.920
In which devices?
00:31:22.319 --> 00:31:24.000
Right now, the major Yeah.
00:31:24.240 --> 00:31:30.480
Right now, the majority of our clients are using the Business Central mobile client.
00:31:30.720 --> 00:31:32.799
Uh, we do have a Power App.
00:31:33.200 --> 00:31:37.680
That Power App is used by a couple, a couple of our clients today.
00:31:37.839 --> 00:31:38.880
It's in beta.
00:31:39.279 --> 00:31:44.480
Um, that power app is something that will be extending in 2026.
00:31:44.559 --> 00:31:46.559
So it's something that we've gotten a lot of demand for.
00:31:46.720 --> 00:31:51.359
Mobility was one of the top three things that we heard from clients across the board.
00:31:51.599 --> 00:32:08.799
Um, it does have online offline capability when using the Power App, and that's the most attractive part for folks is they need to be able to go wherever their equipment is, which may or may not have consistent cell tower range or uh Wi-Fi access.
00:32:09.200 --> 00:32:15.279
In speaking with many people, that is one thing that I think gets often overlooked by many individuals.
00:32:15.359 --> 00:32:20.960
That's it's not even just within business central space as far as business central online.
00:32:21.599 --> 00:32:28.960
It's the areas of the the planet or the places that you go where you don't have internet connectivity.
00:32:29.039 --> 00:32:31.039
Uh and how do you continue to operate?
00:32:31.200 --> 00:32:45.920
It's one of those things that you start to to really start to think about with some of these um organizations and applications is how do you handle it if it's geared towards that mobile or remote type of uh service type um features and functionality.
00:32:46.799 --> 00:32:55.680
It is pretty surprising though that a lot of people don't there's still a lot of pockets uh where you don't have internet connections or offline capabilities.
00:32:55.759 --> 00:33:16.720
So using power apps is actually pretty impressive that uh you guys are using that within your uh offerings because that's also another area where people forget that you can extend Business Central using Power Apps as a you know system system external system uh that integrates fully with Business Central.
00:33:17.039 --> 00:33:17.839
It's fantastic.
00:33:19.200 --> 00:33:22.160
Yeah, it looks like looks like Natalie fell off again too.
00:33:22.240 --> 00:33:48.400
And I can I one of the things that I was going to mention in terms of like looking for those improvements as well, which I'm sure you guys will appreciate, is just looking at the telemetry as well and seeing like where did people fall off or like look observing their behavior right rather than just their opinions or what they're asking for, because you know sometimes those things are are great and usually they are, but sometimes they could lead you down a rabbit hole as well of things that also might not be used right.
00:33:48.559 --> 00:33:57.519
But by actually observing their behavior and seeing like where they fell off, you could use the mobile app, for example, and then extrapolating that into a power app or something else, right?
00:33:57.680 --> 00:34:04.720
Because we might build these things and go, this is all super cool, but then in practice, people might not think the same thing, right?
00:34:04.799 --> 00:34:09.280
We things we think are cool, other people might not, or they might not think they're useful, right?
00:34:09.360 --> 00:34:15.840
But by actually observing their behavior, we can actually see and then use that to improve on, which I think is like the coolest part about what we're doing.
00:34:16.320 --> 00:34:27.760
Because what when I was asking about the feedback earlier, I I was thinking about you know, we have telemetry that tells you a whole lot, but you telemetry doesn't tell you the things that they do outside of the system.
00:34:28.800 --> 00:34:45.039
And um having to, you know, you uh Nell, you mentioned about sending people out to just see them in person on site to see what are they doing that perhaps the application doesn't, you know, track because they're doing it as a manual process to get proper feedback.
00:34:45.280 --> 00:34:53.360
I think we uh uh I think in this industry, at least from my perspective, you know, post-COVID, it's almost like we forgot about that.
00:34:53.519 --> 00:34:58.880
We used to go on-site visits all the time to kind of get that feedback, even from an implementation perspective.
00:34:59.360 --> 00:35:07.599
We forgot that hey, we should really maybe perhaps go visit them and do an on-site discovery uh to kind of prepare to get the best out of the system.
00:35:07.840 --> 00:35:15.039
So uh uh something to consider for a lot of people that kind of stopped doing that um and and getting that kind of feedback as well.
00:35:15.840 --> 00:35:16.000
Yeah.
00:35:16.320 --> 00:35:22.800
Can I want to just take a a detour or a side rail because you mentioned telemetry?
00:35:22.960 --> 00:35:35.519
I am a telemetry fan, telemetry advocate, and I use telemetry quite often from the development point of view, just to see uh more of the technical aspects of the application on you know performance and how things are working.
00:35:35.599 --> 00:35:50.000
And I've talked with many others that are using it to keep track of the features and functionality that individuals are using within Business Central, and then being able to adjust from there, whether it's training or or other aspects of it.
00:35:50.239 --> 00:35:54.719
Uh but then I was challenged one time, and and you had mentioned it there.
00:35:55.199 --> 00:35:58.239
Is it almost like a self-fulfilling prophecy in a sense?
00:35:58.400 --> 00:36:01.840
Because is someone not using something because they don't have the training?
00:36:02.000 --> 00:36:16.320
Is someone not using something because it's not working properly, they're not aware of it, versus uh the alternative saying, okay, well, somebody's using this feature more, therefore we should enhance it more, and they're using this feature.
00:36:16.480 --> 00:36:18.400
That's why I was going with this, they're using this feature less.
00:36:18.800 --> 00:36:22.079
So we shouldn't use this feature, or we should focus less time on it.
00:36:22.239 --> 00:36:30.079
To me, it's almost it's it's a catch, 22, because it's you can use the telemetry because you can see see which features and functionality use the most.
00:36:30.320 --> 00:36:35.679
And then if somebody's not aware of that feature and functionality, then no one's going to be using it.
00:36:35.760 --> 00:36:41.119
But if the light comes on for them and they learn about it, you know, is it something they would be using?
00:36:41.280 --> 00:36:42.719
What is your thoughts on that?
00:36:42.800 --> 00:36:46.079
I this is unrelated to the Rex application.
00:36:46.159 --> 00:36:48.400
It's just more of a, you know, my ADHD.
00:36:48.480 --> 00:36:50.000
I guess you said I can't say that.
00:36:50.159 --> 00:36:52.239
Uh I think you're fine.
00:36:53.280 --> 00:36:55.440
Um, I see both sides to it for sure.
00:36:55.519 --> 00:36:59.440
Um, I think it also gives you opportunity on both sides, right?
00:36:59.599 --> 00:37:03.360
Because if if if it's a training thing, let's just focus on that first, right?
00:37:03.519 --> 00:37:06.880
We could review our training materials, our documentation, our videos.
00:37:07.039 --> 00:37:13.920
We could uh see if it is uh robust enough, or maybe focus some additional marketing and training efforts, right?
00:37:14.000 --> 00:37:18.639
We do a ton, we do things weekly at RUX and and some larger things monthly, right?
00:37:18.719 --> 00:37:21.199
To obviously train people like we talked about before.
00:37:21.280 --> 00:37:25.599
Um so if it is a visibility thing, that's fairly easy to overcome, right?
00:37:25.679 --> 00:37:31.360
We have a list of all of our clients, we can email them, we can invite them to our webinars and things like that, right?
00:37:31.519 --> 00:37:37.760
Whereas if it's a uh if it's a technical aspect, right, we have the data.
00:37:37.920 --> 00:37:41.360
Obviously, that's a little bit uh well, it's easier internally to solve.
00:37:41.519 --> 00:37:43.840
It's a little bit uh longer of a process, right?
00:37:43.920 --> 00:37:47.360
Because there's more manpower that is needed to do that.
00:37:47.599 --> 00:37:55.039
But um I look at some of the apps that that I had built historically, right, before this, and there is that 80-20 rule, right?
00:37:55.119 --> 00:37:59.760
Where we had 30-something apps, but the focus was on the 20%, right?
00:37:59.920 --> 00:38:03.039
The the 80% of the downloads were for 20% of the apps.
00:38:03.119 --> 00:38:04.480
So where did you focus your time?
00:38:04.719 --> 00:38:18.159
Well, let's make those 20 uh percent better so that everyone is continuously using those, and we use those as the flagship apps to then, you know, kind of uh downstream get the traction for the rest of the apps.
00:38:18.320 --> 00:38:22.320
Not that they're any worse than the 20%, right?
00:38:22.400 --> 00:38:24.000
It's just like what gets traction.
00:38:24.079 --> 00:38:30.880
What we find a lot is like the ones that send the invoices and statements and the dashboards and things, those get the most traction because the most people can use them.
00:38:31.199 --> 00:38:36.400
But you know, some of my favorite apps that we've built aren't even in that like top 10 list, right?
00:38:36.559 --> 00:38:37.679
Which is kind of funny.
00:38:37.760 --> 00:38:39.119
Um, but and Natalie.
00:38:39.440 --> 00:38:40.159
What are some of those?
00:38:40.400 --> 00:38:44.480
Just out of curiosity, if you mind sharing, if you mind sharing, if you don't, then that's okay.
00:38:44.880 --> 00:38:46.400
For for which piece of it?
00:38:46.719 --> 00:38:49.440
The you said some of your favorite apps aren't in the top 10%.
00:38:49.760 --> 00:38:52.400
So what do you which were your favorite apps aren't in that 10%?
00:38:53.280 --> 00:38:54.159
Um I do have.
00:38:56.320 --> 00:39:01.199
Uh so are so what's not in the top 10 that I think should be in the top 10?
00:39:01.360 --> 00:39:02.639
That's the question that you're asking.
00:39:02.800 --> 00:39:02.880
Yeah.
00:39:03.119 --> 00:39:09.519
All right, let me let me pull up my full list because I know there's um there's quite a few.
00:39:09.679 --> 00:39:13.840
I think the I've got a payments plan um app that I think is is sweet.
00:39:13.920 --> 00:39:23.119
It's actually uh your guys' friends, uh Steve Chinsky and uh Kim and Rob were the ones who actually kind of gave us the original idea for this, because we had our payments plan app.
00:39:23.199 --> 00:39:28.079
So I know they have a few clients that are using it, um, because they are the ones who asked for it originally.
00:39:28.239 --> 00:39:29.599
Um, but I think that one's sweet.
00:39:29.679 --> 00:39:33.840
And uh we do have clients on it, but definitely not in the top 10.
00:39:34.239 --> 00:39:36.000
Um trying to think.
00:39:36.079 --> 00:39:45.760
I've got a data imports in migration that basically takes config packages and makes it about 90% quicker, or a tenth of the time, if you want to think about it that way.
00:39:46.000 --> 00:39:51.199
That's used on a lot of implementations, but again, that might be one of those ones where it's more um specific.
00:39:51.519 --> 00:40:12.960
And then probably my personal favorite that is kind of hidden in the pack, it's called autocreate dimensions, which, as you as the name kind of entails, you create a customer, let's say, it's automatically going to create a customer dimension and link that customer dimension back to the customer card, and then there's settings to choose how you want to default it, code mandatory, same code, no code, things like that.
00:40:13.119 --> 00:40:16.480
Um, so if I had to pick three, those would be my my top three.
00:40:16.559 --> 00:40:24.880
But the ones that are always downloaded are the invoice and statement delivery, the financial dashboard, the CRM, the advanced prepayments, um handful of others.
00:40:24.960 --> 00:40:26.800
But no, I can understand why those are popular.
00:40:26.960 --> 00:40:31.920
You think better that uh auto-dimensioned create.
00:40:32.800 --> 00:40:37.599
I had in the course of my time, I have actually done that mod several times.
00:40:37.920 --> 00:40:40.480
No, it's it's yeah, it just goes to show you what you're saying.
00:40:40.559 --> 00:40:42.800
It's a sweet, and I'm not it like anything else.
00:40:42.880 --> 00:40:47.199
It's uh, you know, had that been in existence then, or yeah, this was before.
00:40:47.280 --> 00:40:48.800
I haven't done that in several years.
00:40:49.119 --> 00:40:58.719
But I remember doing it back in the nav days, uh, you know, even more so when Dimensions first came out and then uh early na late in a vision, early nav days, uh working with that.
00:40:58.880 --> 00:41:01.599
So that I was not aware of that one either.
00:41:01.760 --> 00:41:15.119
You know, I do take a look at the the toolbox app every uh list every now and then uh after seeing your feature Fridays uh you know to draw attention to them, uh uh which you could know that's interesting with that.
00:41:15.360 --> 00:41:20.639
Um so so you you did bring the BC toolbox.
00:41:20.719 --> 00:41:22.559
Is it still called the BC Toolbox?
00:41:22.719 --> 00:41:25.440
Mm-hmm in your BC Toolbox now.
00:41:25.760 --> 00:41:26.880
Rux BC toolbox.
00:41:27.199 --> 00:41:28.559
Rux BC Toolbox.
00:41:28.639 --> 00:41:29.840
I was excited to see that.
00:41:30.000 --> 00:41:34.000
Um not Ben's not Ben's BC Toolbox anymore.
00:41:36.079 --> 00:41:46.719
Well, yes, I'll start saying Rux's BC Toolbox, but please forgive me if I say Ben's because it's uh It takes some time to get used to, I know.
00:41:46.880 --> 00:41:47.519
It does, it does.
00:41:47.599 --> 00:41:50.239
No, I was excited to see it and uh to see you pull it.
00:41:50.320 --> 00:41:56.880
And you and you're pulling those features into the rental uh application or rental offering as well, some of those features as well.
00:41:57.199 --> 00:42:02.800
Yeah, as you can imagine, one of the biggest like lifts over the last six months is getting everything to talk to each other, right?
00:42:03.039 --> 00:42:06.079
Uh completely two separate code bases over their 20 years.
00:42:06.239 --> 00:42:09.599
My I was building it for about five years before we merged together.
00:42:09.760 --> 00:42:12.719
Um, so yeah, we're the initial ones, Natalie.
00:42:12.800 --> 00:42:20.719
Correct me if I'm wrong, but the some of the dashboarding, the invoice and statement delivery pieces, the prepayments, I think those were kind of the three big ones.
00:42:20.960 --> 00:42:30.000
And our um we've got a really neat CRM tool that's kind of like a BC relationship management on steroids, but not quite D365 sales.
00:42:30.079 --> 00:42:31.760
Uh kind of sits in that middle piece.
00:42:31.840 --> 00:42:38.320
I don't know what your opinion is on the CRM in in Business Central, but mine was always that it was kind of difficult to use, a little bit clunky.
00:42:38.400 --> 00:42:41.599
So basically just take that, make it super easy to use, right?
00:42:41.679 --> 00:42:43.440
Because it's hard enough to get salespeople.
00:42:43.599 --> 00:42:53.840
I know because I am one now, um, to get them to log their leads in a CRM and log their tasks and log like I know because I am not the the model student for that.
00:42:54.000 --> 00:42:56.320
Um so trying to make it as easy as possible, right?
00:42:56.400 --> 00:43:03.519
Quickly add a leader, an opportunity, and then get it to flow all the way through a rental quote and a rental contract or a service quote and a service contract.
00:43:03.599 --> 00:43:07.360
And you know, that is an underturved application.
00:43:07.679 --> 00:43:10.079
So that's awesome that you're extending that.
00:43:10.320 --> 00:43:21.360
I think it's perfect for the rental component too, because you know, not everyone needs a full-blown CRM or CE product to just to do simple stuff, especially for SMBs.
00:43:21.920 --> 00:43:28.800
And um, I think it's it's it works, it it can work great, or it you know, it works great, especially if you extended it.
00:43:29.440 --> 00:43:33.519
Yeah, well, and a lot of people too have four or five salespeople, right?
00:43:33.599 --> 00:43:41.920
So it's not like they don't have this huge robust workforce, it's really just a handful of people in the field quoting deals, log in their leads, things like that.
00:43:42.000 --> 00:43:44.400
So it's like, yeah, you could go spend the money.
00:43:44.480 --> 00:43:50.320
And and we've had people that started on ours four years ago, and now they're like, hey Ben, I want to move to D365 sales.
00:43:50.400 --> 00:43:52.960
I go, Great, because I'm a Microsoft guy through and through.
00:43:53.039 --> 00:43:54.800
Like, stay in the Microsoft family.
00:43:54.960 --> 00:43:55.440
That's okay.
00:43:55.599 --> 00:43:58.000
We realize that that wasn't supposed to serve you forever.
00:43:58.159 --> 00:43:59.760
I hope you grow at such a rapid pace that.
00:44:00.159 --> 00:44:04.000
You do come off of it later because we have 30 other things that you can still use, right?
00:44:04.079 --> 00:44:05.440
Like it doesn't hurt my feelings.
00:44:05.519 --> 00:44:15.199
Um, I like that they're going because then it actually gives them more opportunity to use other things that we've created that could help them in other ways that they couldn't use before because they weren't big enough either, right?
00:44:15.440 --> 00:44:17.519
So it's kind of cool to be in that position.
00:44:17.920 --> 00:44:28.079
Nah, it's it's it's um I've been a lot I appreciate your comments because I've been in many conversations lately with friction.
00:44:28.320 --> 00:44:28.639
Yeah.
00:44:28.880 --> 00:44:30.559
And it seems even more so now.
00:44:30.719 --> 00:44:36.800
The minute you add friction for somebody to do something, even myself, my conversations have been more with me um as well as others.
00:44:36.960 --> 00:44:46.559
So any process that can be simplified, um you're more likely to have somebody do it if you if you make it complicated or there's too many steps involves.
00:44:46.719 --> 00:44:47.039
Yeah.
00:44:47.119 --> 00:44:55.840
Um that's one thing that individuals need to keep in mind when they're designing software, I think, today is how do you reduce the friction for someone to be able to do the job that they're trying to do?
00:44:56.159 --> 00:45:00.960
Because ultimately people just want to do their job and they're going to find the easiest way to do their job.
00:45:01.280 --> 00:45:02.880
It may not be what you're looking for.
00:45:03.039 --> 00:45:04.880
It goes back to what we were talking about.
00:45:05.280 --> 00:45:14.000
When you design a system, have people use it that use it, not people who think they use it because I design and develop things all the time.
00:45:14.239 --> 00:45:16.800
But I only have to enter one sales order, for example.
00:45:17.039 --> 00:45:19.840
So it could be, and I'm using that as an example, right?
00:45:19.920 --> 00:45:22.320
I can enter one sales order and I'm like, ah, it's not that bad.
00:45:22.400 --> 00:45:30.079
But somebody who may have to enter sales orders all day long for different types of products and have the lookups and customers, it may not be such a nice workflow.
00:45:30.239 --> 00:45:38.320
So I do think that uh getting that stuff out there and taking a look at the friction that um is in place is important as well.
00:45:38.559 --> 00:45:39.199
So yeah.
00:45:39.440 --> 00:45:46.480
Well, that's why it's also there's there's a lot of people that I think if it is a lot of friction, they'll batch process their work.
00:45:46.559 --> 00:45:55.519
So they'll go perform several tasks, they'll write down what they did on their scratch pad, then they'll force themselves to go sit down and batch process their work.
00:45:55.760 --> 00:46:02.400
This happens in all sorts of industries at all different kinds of companies, not just the ones that we see.
00:46:02.559 --> 00:46:05.440
And I see you guys laughing because it's true.
00:46:05.679 --> 00:46:06.639
It's so true.
00:46:06.880 --> 00:46:14.719
It doesn't matter that they had internet access, it doesn't matter that we built a mobile solution with online offline capabilities, and telemetry will never tell.
00:46:14.880 --> 00:46:23.199
Yeah, telemetry will never tell because it shows that the user hit all those features when processing those transactions and everything posted through.
00:46:23.519 --> 00:46:32.400
But the process is obviously not efficient enough that the user is willing to do it while they're actually performing the task at hand.
00:46:32.800 --> 00:46:35.039
Oh, I know all about that batch processing.
00:46:35.119 --> 00:46:38.480
Uh, Krista's what I'm thinking of too, because we see it all the time.
00:46:38.559 --> 00:46:41.519
And unfortunately with batch processing, that's where a lot of mistakes get made.
00:46:41.760 --> 00:46:44.400
Uh and and things get forgotten.
00:46:44.639 --> 00:46:53.119
And uh so I think reducing the friction's important uh as well, which is interesting.
00:46:53.360 --> 00:46:55.920
Um, well, do you have any more acronyms for us?
00:46:56.000 --> 00:46:57.280
Does anybody come up with any more?
00:46:57.599 --> 00:47:04.079
No, I was gonna say that that's why that's why my EOT's midnight, because Natalie will be like, hey, how do how do we take some stuff off your plate so you don't have to work?
00:47:04.400 --> 00:47:11.360
I'm like, it doesn't matter because if you take stuff off my plate, then I'm just gonna put more stuff on my plate, like with these customers always telling us stuff like Natalie knows.
00:47:11.440 --> 00:47:15.920
I I obsess over reviewing it because I I really care that it's better, right?
00:47:16.000 --> 00:47:19.119
Because again, it was kind of my first baby, right?
00:47:19.280 --> 00:47:29.280
And uh I'll stay up all night just like trying to read into it and try to figure it out and solution around it because it's like, yeah, what was the what was the path where it broke down and how could it be easier?
00:47:29.360 --> 00:47:38.719
Because even with all the great CRM tools and everything that we have, like like Natalie's uh uh list of three-letter acronyms, I've got my stuff that needs to be like entered in CRM right here, right?
00:47:38.800 --> 00:47:41.679
And it's like the fastest way is to write it down, right?
00:47:41.920 --> 00:47:43.280
The fastest way is to write it down.
00:47:43.440 --> 00:47:48.320
Eventually it'll get into the system, but that's not like being a software guy, that's not a good system.
00:47:48.559 --> 00:47:54.480
Like I know it, I know it's a horrible practice, but it's just there's so many things to do.
00:47:54.800 --> 00:47:55.360
I laugh.
00:47:55.440 --> 00:47:55.760
I laugh.
00:47:56.159 --> 00:47:57.360
You just can't get caught up.
00:47:57.840 --> 00:48:01.679
No, it's it's it's one, it's a sickness that we I think we all have.
00:48:02.159 --> 00:48:03.840
It is you never get caught up.
00:48:04.079 --> 00:48:06.400
Two, the writing it down on a piece of paper.
00:48:06.559 --> 00:48:17.199
I can't tell you how many times I've tried I've tried dictation, I've tried uh shared applications so that it's on my phone and it's on my computer.
00:48:17.360 --> 00:48:23.440
You know, it's even using I use a Mac, uh, so you even use in tasks to try to use OneNote.
00:48:23.679 --> 00:48:30.000
I can name all the systems that I've had to quickly jot down the thoughts that I have.
00:48:30.159 --> 00:48:30.480
Yeah.
00:48:30.639 --> 00:48:36.480
Um and ultimately, like you said, it comes down to having a piece of paper.
00:48:36.639 --> 00:48:40.480
Sometimes it is because it's for some reason it you can just quickly put it down.
00:48:40.719 --> 00:48:44.800
Uh I now I'm trying notes in the Mac ecosystem.
00:48:45.199 --> 00:48:47.760
Well, I think it's organized like your brain too, right?
00:48:47.840 --> 00:48:51.440
Because like the way you're writing is like the way your brain sees it, right?
00:48:51.519 --> 00:48:56.719
Whereas in like a OneNote, it's just chronological with bullet points, which it's like hard to look through, right?
00:48:57.280 --> 00:48:58.000
But I don't know.
00:48:58.079 --> 00:49:01.199
I'm usually I'm usually pretty good about getting them in eventually.
00:49:01.360 --> 00:49:07.440
It's usually two or three days behind, but it will be funny because every once in a while, like an our chief sales officer be like, that came in today and you closed it the same day.
00:49:07.519 --> 00:49:13.760
I'm like, well, it's on my piece of paper for four days, but yes, I did close it in like two minutes.
00:49:14.559 --> 00:49:16.320
Telemetry won't channel on you either.
00:49:16.400 --> 00:49:20.159
If you put it in the system, the system will align with the what you told your boss.
00:49:21.760 --> 00:49:25.280
Ben's pulling off these same-day sales, but you you hit the key point.
00:49:25.440 --> 00:49:27.119
I've even tried mind mapping.
00:49:27.199 --> 00:49:41.119
Uh, I won't mention the product that I tried because it did give me the flexibility to um work in the way that your mind works, because your mind does work in that it's not linear, your mind is not a linear process.
00:49:41.280 --> 00:49:43.519
And I enjoyed doing the mind mapping.
00:49:43.599 --> 00:49:46.000
Unfortunately, it was only on the computer.
00:49:46.639 --> 00:49:48.559
Um, and I loved it.
00:49:48.880 --> 00:49:58.000
And I'm not using that anymore because they changed the plan and didn't tell me, and they did it mid-cycle.
00:49:58.079 --> 00:49:59.760
So I said, forget it, I'm done.
00:49:59.920 --> 00:50:02.639
Um, which is a whole other conversation.
00:50:02.880 --> 00:50:13.599
But mind mapping is um i is helpful, but we need to have something that uh you know can work easily on the phone as well as can I uh share something really quick.
00:50:13.679 --> 00:50:19.119
So I just uh I just sort of uh kind of discovered this uh several weeks ago.
00:50:19.280 --> 00:50:29.119
So it talked about AI really quick here and putting all the notes and uh Gemini Google product has a code called Notebook LM.
00:50:29.599 --> 00:50:41.199
So Microsoft also has one called Copilot Notebooks and it does a fantastic job to collect everything that you just specific to maybe a task or something that you do in a daily basis.
00:50:41.679 --> 00:50:50.000
You get you can actually now take that information and interact with other agents or co-pilot agents that can do some of those work for you, Ben.
00:50:50.159 --> 00:51:03.440
So uh even though like you don't have to like repeat re-entering stuff, you can use a notebook for an agent to pull up and perhaps enter in your own system for you on your behalf with a little bit more summary and flair.
00:51:04.079 --> 00:51:08.320
One of that that reminds me of one of uh Natalie and I's favorite things to do in our weekly meeting.
00:51:08.400 --> 00:51:13.519
We'll just ask Copilot what are the three most important things that Natalie and I are forgetting to talk about that we need to ask each other this week?
00:51:13.760 --> 00:51:16.159
Look through all my emails and notes and stuff like that.
00:51:16.239 --> 00:51:18.639
And it's it's pretty spot on, usually.
00:51:18.960 --> 00:51:19.280
Use use.
00:51:19.599 --> 00:51:20.719
I was like, oh, I forgot about that.
00:51:20.880 --> 00:51:21.679
Use notebooks.
00:51:22.320 --> 00:51:23.119
I think I'll try notebooks.
00:51:23.280 --> 00:51:24.960
So you said copilot has notebooks now?
00:51:25.119 --> 00:51:39.199
Yeah, Copilot has notebooks, so you can collaborate together using notebooks so you can add all your sources, your information of something that you're working on together, and then you can just collate all of that information and notebooks would do it.
00:51:39.599 --> 00:51:44.400
I want to try it and see because I I've been on that struggle bus for a long time.
00:51:44.719 --> 00:51:49.920
And now you're going back to do you record all of your meetings?
00:51:50.079 --> 00:51:56.239
So you you you go back to your workflow is to have Copilot tell us all the things that were missing, and you have it go through your emails.
00:51:56.320 --> 00:52:02.880
And uh, I'm assuming you're using copilot with an M365 so it can look through all of your other um documents and such.
00:52:03.119 --> 00:52:07.039
Do you record the meetings that you have so it has access to the transcripts as well?
00:52:07.360 --> 00:52:07.920
I do.
00:52:08.079 --> 00:52:09.440
Um almost all.
00:52:09.519 --> 00:52:09.679
Yeah.
00:52:09.840 --> 00:52:10.480
Almost all.
00:52:10.639 --> 00:52:10.960
Yeah.
00:52:11.119 --> 00:52:29.440
I you know, there's certain one-on-ones where if just Ben and I are talking, we're not recording that meeting, but every other collaborative meeting that we're in has been recorded throughout the week or is recorded through CRM and Teams and I do like planner.
00:52:29.519 --> 00:52:35.280
Yeah, so that's another philosophical road here outside of uh the you know the offering you have, just to see workflows.
00:52:35.440 --> 00:52:38.400
We we we again tangent number five for this.
00:52:38.639 --> 00:52:56.400
I have to get back onto not having tangents, but yeah, Ben sparked some uh some insights there and thoughts for me as far as you know, workflow and management, because I do like you know the co-pilot, if people do have the transcripts, you know, having transcripts for everything and send out co-pilot summaries all the time.
00:52:56.480 --> 00:53:08.800
I don't know how effective those are because I don't know who reads them all, but in the in the context of you know, maybe doing a weekly summary or giving a breakdown, it's a little um I think helpful.
00:53:09.440 --> 00:53:14.000
Are you let's ask some some philosophical uh questions.
00:53:14.320 --> 00:53:14.960
That's my life.
00:53:15.199 --> 00:53:25.440
If you if you go to search for something today, so in February 2026, you go to search for something, what's the first for you're you're working?
00:53:25.920 --> 00:53:31.039
So context is you're working at the job we all do, you need to find a piece of information.
00:53:31.199 --> 00:53:32.480
Where do you go first?
00:53:33.280 --> 00:53:37.199
A piece of information regarding work or just kind of like your personality.
00:53:37.440 --> 00:53:42.400
Regarding work, regarding work, the first product that you use to search.
00:53:42.719 --> 00:53:45.760
Uh for uh I'll let me answer that really quick.
00:53:45.920 --> 00:53:48.880
So uh I typically go with Copilot.
00:53:48.960 --> 00:53:52.800
If it's work related, uh there's a work tab and then there's a personal tab.
00:53:53.119 --> 00:53:59.679
Uh if it's work-related, I do work because it does look at all the things that are related to me as a user.
00:53:59.760 --> 00:54:02.000
Uh so that's the first place I would look at.
00:54:02.320 --> 00:54:08.239
If I'm looking for something very specific, especially documents, like I don't I don't know where the hell I put that thing.
00:54:08.480 --> 00:54:10.000
Uh and it does a pretty good job.
00:54:10.400 --> 00:54:12.880
That's usually where I go first in work-related wise.
00:54:14.000 --> 00:54:15.119
Red, where do you go first?
00:54:15.440 --> 00:54:22.960
Uh I don't I use co-pilot for some things.
00:54:25.119 --> 00:54:28.400
And then it depends on what it is, to be honest with you.
00:54:28.559 --> 00:54:35.199
I try to use co-pilot um to get the information, whether copilot would be in in Outlook.
00:54:35.280 --> 00:54:41.119
You know, if I say find me this, uh, I use co-pilot in Teams if I need the reference, a teams conversation.
00:54:41.360 --> 00:54:47.920
Um, for some documents, that's the struggle sometimes is where those documents are located, where copilot may not have access to it.
00:54:48.000 --> 00:54:50.639
But that's where I work now in 2026.
00:54:50.800 --> 00:55:03.199
Uh, if I need information outside of like looking for a work document, I'll jump to just a different model to use.
00:55:03.360 --> 00:55:07.679
I mean, sometimes I'll just even stick within Google and get the AI result, or I'll jump into Grok.
00:55:08.400 --> 00:55:12.719
Um I started using Claude more now.
00:55:13.440 --> 00:55:16.880
Um for basic search, like personal.
00:55:17.360 --> 00:55:18.320
Like oh, interesting.
00:55:18.639 --> 00:55:23.840
And like how would you how would you rate us for Claude?
00:55:24.400 --> 00:55:25.039
Claude?
00:55:26.000 --> 00:55:27.280
Uh I like it.
00:55:27.760 --> 00:55:35.840
It's very I I it seems to be um I use GitHub Copilot a lot for work uh because of development.
00:55:36.079 --> 00:55:38.000
I use all of everything within VS Code.
00:55:38.079 --> 00:55:43.599
I know everyone talks about the different environments, but outside of it, um I use Claude.
00:55:43.920 --> 00:55:47.920
Uh and I I've started using that more recently.
00:55:49.039 --> 00:55:53.679
Just really quick, on the personal side, I'd use Gemini more uh than ever.
00:55:54.079 --> 00:56:08.400
Uh surprisingly, to see to see Google and Apple uh have an agreement that Apple could use Gemini, I think it's gonna be uh easier.
00:56:08.800 --> 00:56:15.840
Or I think it's gonna get better because how many Apple users are out there that still relied on Siri?
00:56:18.000 --> 00:56:19.519
Now it's gonna change.
00:56:20.800 --> 00:56:29.599
I I will tell you my, I want to hear Ben's answer, but I will tell you what sealed the deal for me, and many people already know this about me.
00:56:31.039 --> 00:56:38.000
When I travel for work, my dad is the co-parent for my husband when I'm gone.
00:56:38.320 --> 00:56:48.239
And the way that I write instructions before I am gone is I will write it, I will write like my bullet points out on a post-it note.
00:56:48.320 --> 00:57:00.960
I will take a picture, I will upload it to Google Gemini, and I will say, please write a note with a loving, caring tone from me to my dad for him watching my children while I'm gone.
00:57:01.039 --> 00:57:07.920
I've got the prompt all structured, it's all set up, and it spits out the nicest email you have ever read in your life.
00:57:08.079 --> 00:57:09.760
It is so thoughtful.
00:57:10.079 --> 00:57:13.360
Gemini sounds just like me when I'm talking to my dad.
00:57:13.599 --> 00:57:15.119
So you're a Gemini user.
00:57:15.599 --> 00:57:17.119
Oh, you're a Gemini user.
00:57:17.519 --> 00:57:23.679
For personal communications, I find it sounds so much more like me than co-pilot.
00:57:23.840 --> 00:57:26.639
And so that's my and now I've trained it, right?
00:57:26.719 --> 00:57:28.159
Because I use I do the same thing.
00:57:28.320 --> 00:57:31.679
I travel often enough that this is not a one-off situation.
00:57:32.079 --> 00:57:42.239
See, it's about the context with that, because I I I want I want to get into a point because uh on this, well, Ben, uh you'll have to you'll be able to jump in and give you an answer.
00:57:42.480 --> 00:57:50.880
But if you train it, because I've given it, I I've had it help create stuff, and I think who doesn't do this in 2026?
00:57:51.119 --> 00:57:55.840
Uh, we'll look back on this in you know 10 years.
00:57:55.920 --> 00:58:01.440
I may not be around, but uh people will look back in 10 years and go, I'm old, you know.
00:58:01.760 --> 00:58:05.440
Um we'll go, Whoa, you guys had to write.
00:58:05.679 --> 00:58:07.840
You know, like we went back, like you know all those things.
00:58:07.920 --> 00:58:09.199
Like I say now, I was back in the day.
00:58:09.280 --> 00:58:13.519
I used to have to put a dime in the payphone to use uh, you know, to make a phone call.
00:58:13.679 --> 00:58:25.840
And you know, I remember I remember when the not this the cell phone I remember was being invented, but I remember when a portable phone was invented because when I grew up, we had like the landline spends like uh you lost me.
00:58:27.440 --> 00:58:33.679
But you you train it, like I give it references, and this is where I had mentioned in other another episode.
00:58:33.840 --> 00:58:42.159
I really do need to just record my life because I really want to see if I do a year's worth of recording of con like all my conversations, right?
00:58:42.480 --> 00:58:49.360
And then just say, you know, act like me and to see how it comes out.
00:58:49.440 --> 00:58:51.119
But again, it's uh it does pretty well.
00:58:51.280 --> 00:59:00.800
If if you train in the prompting, I want to know though, Ben, I want to know your answer because like Nally, you're you're you're a Gemini user.
00:59:00.880 --> 00:59:04.480
I know Brad, you're you're starting to tap into the Gemini product.
00:59:04.639 --> 00:59:17.599
You can set it up to a personal intelligence where you feed it how you want to how you want it to respond to you, in a sense that you can feed it your kind of your personality, like this is how I write, reference this.
00:59:17.920 --> 00:59:19.039
It is fantastic.
00:59:19.199 --> 00:59:24.159
So now he's learning from you because it's probably you fed it so much, but you can go beyond that.
00:59:24.239 --> 00:59:30.639
You can even do like, hey, when you're doing something this particular prompt, I want you to respond like this all the time.
00:59:30.800 --> 00:59:31.599
Uh it's just amazing.
00:59:31.920 --> 00:59:34.000
I do think it I think it helps though.
00:59:34.079 --> 00:59:36.719
I use Gemini for personal, I use co-pilot for work.
00:59:36.800 --> 00:59:47.199
And so I also feel like my work tone and persona is what I'm teaching co-pilot, and my personal tone and persona is what I'm feeding Gemini.
00:59:47.360 --> 00:59:49.039
But Ben, what do you what all right, tell us?
00:59:49.199 --> 00:59:49.760
Big reveal.
00:59:49.840 --> 00:59:50.559
What does Ben do?
00:59:50.639 --> 00:59:54.079
When you need to find information in 2026, where do you go?
00:59:54.159 --> 00:59:55.679
And then what's your preferred?
00:59:56.480 --> 01:00:04.880
So on it, I would say on the similar topic for work, one of the first things when the co-pilot studio and everything was coming out, my like trying to think of use cases, right?
01:00:05.039 --> 01:00:08.719
My first use case was we had 30-something products that we had built.
01:00:08.880 --> 01:00:10.800
A lot of people are asking a lot of different questions.
01:00:10.960 --> 01:00:12.320
We're merging with this new team.
01:00:12.480 --> 01:00:14.079
Everybody has similar questions.
01:00:14.239 --> 01:00:31.360
So the first thing that I built was like an email type agent and also a knowledge type agent, where I took everything we've ever created from a documentation standpoint, put it in basically a support agent, you could call it, and you can query it for any question for anything VC toolbox related, right?
01:00:31.599 --> 01:00:43.039
And it also learns from the emails because if it tries to draft something, and then I say, well, no, actually, from you know my personal experience, like this is a better way to do it, then it knows how to do it in the future.
01:00:43.119 --> 01:00:56.400
And then I've taken that over the last year probably and extrapolated it to many different extents, but from a work standpoint, copilot for sure through and through, just based on like all of the data that we have in our domain, right?
01:00:56.480 --> 01:01:02.719
All the emails over the last five years, all the documentation, the videos, the transcripts, everything like that, right?
01:01:03.039 --> 01:01:13.920
Honestly, when I'm doing something for a personal standpoint, I have just been uh for so long, I'm trying to break it and trying to test out basically everything.
01:01:14.000 --> 01:01:28.719
And I've I've played around with everything, but like Brad said, the Google search with some of the AI responses is typically still where I start from a personal standpoint, just because I feel like from the first day I had a computer, it was Google it, right?
01:01:28.880 --> 01:01:31.360
Um and it I just can't break the habit.
01:01:31.599 --> 01:01:36.239
Um but I've I've used Gemini, you know, Chat GPT, everything else.
01:01:36.400 --> 01:01:40.559
Um but I don't know, just Google Chrome, it's right there.
01:01:40.719 --> 01:01:44.239
Type it in the URL bar, and that's where I that's my like starting point.
01:01:44.320 --> 01:01:50.159
So if we're just talking starting point, that's still typically my starting point if I just have something on my mind that I want to know more about.
01:01:50.480 --> 01:01:53.920
Does it I think it's great what you did with the agent, by the way.
01:01:54.079 --> 01:01:59.280
I think yeah, I'd love to see more organizations do that because I think you could even then use that from a support queue.
01:01:59.360 --> 01:02:18.800
Like you said, sure it helps it helps provide better service for your customers or users because whomever is helping them, or even if they had access to it, you know, if they had if you had like a sales agent, you know, just to maybe do some self-service support, it just helps them solve like say solve their problem or answer that question faster.
01:02:19.039 --> 01:02:21.039
But you bring up an interesting, I think that's great.
01:02:21.280 --> 01:02:25.679
I wish um many organizations did that because I think it would be helpful.
01:02:25.920 --> 01:02:29.679
And you could, you know, from even from a user point of view of of certain applications.
01:02:30.079 --> 01:02:34.079
But I think what I you you started talking about the the Google search.
01:02:34.159 --> 01:02:36.639
I think to me, it depends on what I'm searching for.
01:02:37.119 --> 01:02:50.800
Um it's it I decided to think about like you said, I think it's great, it's it does wonders for it, but I'll jump over to one of the other ones if it's more um I'm not looking for something, I'm looking for a structure of something.
01:02:50.960 --> 01:03:00.239
Like what are the rules for you know, this type of this or that, or you know, fictitiously you know, create me a financial plan based upon this type of information.
01:03:00.480 --> 01:03:12.000
I'll go into one of the other ones more, but if I'm saying um you know, something more like what I used to do a Google search for, as they say, uh, I think the Google AI is is pretty good.
01:03:12.320 --> 01:03:12.559
Yeah.
01:03:12.639 --> 01:03:18.320
And depending on I I would agree with that, depending on how long or like how much information you need, if it's just something quick, it's Google.
01:03:18.400 --> 01:03:25.840
If if it's something longer, like Natalie and I are going to uh Vietnam for uh directions in May, right?
01:03:26.159 --> 01:03:28.960
And I have a larger trip than that planned, right?
01:03:29.039 --> 01:03:38.000
I'm gonna go to Hong Kong first, then I'm gonna go to Vietnam, then I'm gonna go to Seoul on the way home, and I use Chat GPT basically to say these are all the days, these are my flights, this, that, or the other.
01:03:38.239 --> 01:03:48.000
Basically, I've got 14 days, optimize it so that I can hit all the things I want to hit, and these are kind of like the three or four things I want to see in Hong Kong, these are the things I want to do in Korea.
01:03:48.159 --> 01:03:56.639
Uh, Vietnam's probably gonna be mostly work consumed, but it gave me like day by day, and it's like, wow, do you want to be do you want to be more aggressive?
01:03:56.719 --> 01:04:02.239
Like, do you want to try to fit more things into this where it'll you'll have less time at this museum or whatever?
01:04:02.320 --> 01:04:07.280
But like we think you can get through it based on average time spent at the museum, right?
01:04:07.360 --> 01:04:09.760
Or like whatever it is, which is like kind of cool.
01:04:09.920 --> 01:04:14.800
Like, do you do you really want to do you want to spend two hours there, or do you just kind of want to fly through it in 90 minutes?
01:04:14.880 --> 01:04:20.000
Like, you know, and you can and then you can interact with it, of course, and say, yeah, the other one's a higher priority.
01:04:20.079 --> 01:04:24.880
I want to spend just an hour at this museum, but I want to spend 90 minutes at the market or whatever.
01:04:24.960 --> 01:04:29.920
And like, okay, your train commute at that time typically is gonna be 27 minutes or like whatever.
01:04:30.000 --> 01:04:36.320
And it like, I mean, I'm very type based, so I loved it because it was like I can plan it down to the literally the minute, right?
01:04:36.400 --> 01:04:45.599
If you want to, might be a little bit extreme, but that's just a recent example um that I thought was super that Google wouldn't tell like Google won't do that, right?
01:04:45.840 --> 01:04:47.440
Um, I I think that's great.
01:04:47.599 --> 01:04:50.079
And it's like you said, it's contextual, you know, what are you searching for?
01:04:50.719 --> 01:04:53.840
I did start with Google, like what are the top five things to see in Hong Kong, right?
01:04:54.000 --> 01:04:56.559
And then you could get travel articles and blogs and things like that.
01:04:56.639 --> 01:04:59.840
So, like started there, and then it was like, okay, those three look cool.
01:04:59.920 --> 01:05:01.599
Let's plug those into chat GPT.
01:05:01.760 --> 01:05:10.400
I want to do these three things, anything else around like anything close to there that I can just knock out quickly that's on anybody else's top 10 list or whatever, right?
01:05:10.559 --> 01:05:14.159
So I'd say yeah, chat GPT probably for me.
01:05:14.559 --> 01:05:19.440
Well, I'm looking forward to seeing the results of that when you come back.
01:05:19.679 --> 01:05:20.719
I'll have to catch up to you.
01:05:20.880 --> 01:05:22.400
I'm making note just to see.
01:05:22.800 --> 01:05:50.960
No, just I've heard a lot of people who do that, and I've rarely caught up with them after they trip to say, you know, usually it's how was your trip, or whether you talk about some of the things your trip is, but uh you and I should have a conversation about uh it doesn't even have to be recorded in a sense, but just I'm curious to see, you know, from my own um knowledge or experience, how well was that plan for you uh with the trip, just to see if you followed if it uh if it worked out well.
01:05:51.199 --> 01:05:53.519
Well, Natalie, Ben, I could talk with you both all day.
01:05:53.679 --> 01:05:54.880
We talk about many different topics.
01:05:55.039 --> 01:05:59.760
Thank you for taking the time to speak with us today to talk about many things, including.
01:06:00.239 --> 01:06:33.920
uh the Rux offerings with the uh Rux BC toolbox as well as the uh RuxRux rental push I'm trying to come up with an acronym there with that but uh if anyone has any uh questions or would like additional information on any of the product offerings you have uh or even some AI workflow questions what's the best way to contact you Natalie Hi at Ruxsoftware.com is the best email address that comes straight in to uh our head of growth and she'll make sure the right person gets back to everybody.
01:06:34.320 --> 01:06:42.079
That's genius hi I like that I liked it too she told me we're getting a high email setup and I was like that sounds so great.
01:06:42.559 --> 01:06:52.719
Who doesn't want to email that sounds so human hi I've never heard of that before I've never heard that before usually people have like sales or something like that but hi is good.
01:06:53.280 --> 01:06:53.519
Mr.
01:06:53.679 --> 01:06:54.239
Ben sir.
01:06:54.960 --> 01:07:15.519
Uh LinkedIn probably Ben Cole Rock softer you can find me I look like this and just uh add me on LinkedIn and you'll know it's really him because in his profile there's a combination of uh feature Fridays and toolbox Tuesdays and lots of business central based knowledge articles.
01:07:15.840 --> 01:07:18.320
Yeah no I lots of good stuff there.
01:07:18.960 --> 01:07:22.880
I spent too much time I spent too much time on LinkedIn so you can find me there.
01:07:23.119 --> 01:07:34.800
Yes you no I don't think you do but um you one of the faces I always see somebody sent me a message saying man every time I go into LinkedIn and I see your face I like saying that every time I go into LinkedIn I go into LinkedIn I see Ben Cole.
01:07:35.119 --> 01:07:43.360
Hey it means it's working with Ben No you have some great videos and great tips um I I appreciate them.
01:07:43.599 --> 01:07:53.760
Yeah I'm just telling you that just personally because I like the short quick targeted you know I think we're all in that ADHD world of uh give me the what you have in three minutes or less and um I think it works well.
01:07:53.920 --> 01:07:57.199
But thank you both I look forward to seeing you both soon and talking with you.
01:07:57.280 --> 01:08:00.079
I'm sure we'll see each other in April in person.
01:08:00.239 --> 01:08:06.320
I think you're going to directions North America I hope absolutely we'll be there exhibiting with the booth.
01:08:06.639 --> 01:08:08.320
Excellent look forward to talking with you both there.
01:08:08.719 --> 01:08:22.479
Thanks again so much for having us awesome thanks guys all right thank you bye guys thank you Chris for your time for another episode of In the Dynamics Corner Chair and thank you to our guests for participating.
01:08:22.720 --> 01:08:28.000
Thank you Brad for your time it is a wonderful episode of Dynamics Corner Chair.
01:08:28.159 --> 01:09:06.000
I would also like to thank our guests for joining us thank you for all of our listeners tuning in as well you can find Brad at developerlife com that is D V L P R L I F E dot com and you can interact with them via Twitter D V L P R L I F E you can also find me at mattalino and my Twitter handle is Mattalino16 and see you can see those links down below in the show notes.
01:09:06.079 --> 01:09:09.279
Again thank you everyone thank you and take care
