Latest / Digital Leaders Club By Ingeno / Ezequiel Peralta, CTO at SPI Logistics | AI, Logistics Technology & Innovation
Transcript
- Guillaume: Welcome to Digital Leaders Club. I'm Guillaume Duchenneau, founder and CEO here at NGENO. This show is built for leaders running real world operations. And today that means the people who keep things moving across networks that most of us never see. I'm joined by Ezekiel Peralta, CTO at SPI Logistics. Ezekiel, welcome to the show. Eze: Hi Guillaume. thanks for having me. Guillaume: All right. So Ezekiel, before we get into operational stuff, how did you end up in transportation and logistics? Because yeah, almost anybody nobody that who's in this industry plans to get into it, right? You kinda life gets you to it somehow. Eze: Yeah, for sure. So my education comes from from a different path. so I went to school for music actually. But I always was was into programming since since I was a child or with com working with computers. So then throughout my my education in music also I was learning some like computer music and and that kind of stuff. And then from there, started getting some freelance gigs with with some companies for creating their own software, managing some databases and things, but it was not my main, my main focus. And then at some point I had I had my own business, a screen printing business. And then I was creating also the software for the management of that. And then had the chance to work at freelance with a publishing company that was doing some total quality certification and I was doing the software for that too. So all of these kind of like on the side projects. And then at some point I decided to to focus more on on on the programming side. So so yeah, ended up so my first involvement with logistics was a freelance work that I did with my with one colleague that now works with SPI as well. it was a data warehouse that we did for for SPI as yes, a freelance project. They at the at the time had three different TMS systems because they were transitioning from an old version to a new version and then to another newer version or a a different product. So the that was the first project. And then after that, I was offered to join the company as as in house and and that's how how ended up in in logistics and then since then well I I had to learn the the business as you know on the fly. so I yeah I'm I'm very grateful for all the staff at SPI that also you know tell me so much about about this business. And now I think as as everyone says it's hard to like it's impossible to to get out of it. After you you land in logistics, then it's like it's it's a one way one way street. Guillaume: Right. And today you are a CTO. Did you have you been hired as a CTO or you kinda get a Eze: No, no, no. it it it started as a one person department. So SPI is a company that has over forty-five years of of trajectory. Throughout that time there were different stages where the company actually built a TMS in the nineties and two thousands. ended up spinning off spinning off as a separate company. so at at the time all of the IT processes were kind of handled by by the That product that was started internally then become a spin-off, but it was still providing the tech services. when it was decided to transition to a different TMS, there was a need for an admin for that TMS, which is Revinova. It's based on Salesforce platform, so there was there's a big config and admin component. So so it's I started as as the first in-house person for that new. era of having an internal IT department. Then from there, yeah, I was promoted, then we started increasing the the resources to the team, then we hired one more person, then I was able to bring my my colleague Valentin who we've been working on software for for a while and in in other projects in Argentina as well. And then after that Yeah, we which it we just followed the progression of building up the the department itself and all the processes and the initiating the the path of building internal software and that was a a really really nice process, a lot of learning there because it was like a greenfield project within an existing environment, which is kinda unique. So it had its own challenges, but it was pretty pretty interesting to go through them. And so then yeah, we started customizing a lot of the the processes on top of the TMS. And then we started creating a lot of integrations and external ex software that is running outside of the TMS but is tightly integrated. And and that's the path that we continued and now we are, you know, we have a team of four and now we are hiring for for more devs. And a lot of the processes that the TMS used to do, we are taking over a lot of them, like for back office, career compliance, risk management. We are kinda augmenting the TMS features with our internally built software. Guillaume: Nice, nice. Ezekiel, tell our listeners about SPI logistics, what you guys actually do, the network, the customers, the scale, everything. Eze: Yeah, so SPI Logistics is is a company based in in in Canada, in Surrey. We have our headquarters here in Surrey VC. we are a network of free brokerages. So we are not we we don't own any assets. We have offices across North America, but these offices are independent business owners, right? So they are they are affiliated to the SPI network. we operate under the SPI Logistics Umbrella and our model is that the agents own the customers. It's a commission, it's a profit share model where the there's a commission split on the gross profit. And in that split, it's in everything is included, like all the services that SPI provides, like that's billing, payment, well, ARAP, claims management, comp carrier on boarding compliance. well the TMS, all the subscriptions you may need, and and all the associated services are including that split. And and yeah, we we the commissions are paid weekly. And yeah, so there are a lot of advantages to to this model. And SBA is one of the first companies who who had this specific model and so we have a lot of experience in it. And our main yeah our main focus is to s help our agents businesses grow. and provide them with all the tools and capabilities so they can grow their business and focus on that while we focus on the you know, handling the the back office technology and and all all all Guillaume: Right. So you can't pr i you provide the shared services and the the platform to to for them to run their o their own operations, right? Eze: Exactly, exactly. And we and we also provide help with you know maybe access to certain things that on your own would be hard to get, like for example, certain credit insurance, getting being able to to go pursue certain customers that will need rec certain requirements that will be hard to get if you are like a solo operation. So it gives you also that that advantage, plus the access to all the caring network and the huge amount of data that we have from our past operations that basically the day one you already have access to to all of that data and and yeah that's that's a big advantage. Our agents when you on board with SPI you can be booking loads the the very first day, you know, if if everything Guillaume: Mm. Eze: if everything is set. Guillaume: Be because y you can bring customers to them or because of the if they already have customers they just they can just onboard your system and that's super simple to do. Eze: Exactly. So the SPI don doesn't own the customers. The customers are brought the book of business is owned by the agents. so if they have a customer, generally they provide the l customer list beforehand before onboarding. Guillaume: Mm-hmm. Eze: And we run the credit check, we assign them with credit, and if the credit checks and the credit is granted, then you're you're good to go. And it could happen even that we already did a credit check for that. customer maybe from the past or things like that for the larger, larger shippers. But yeah, generally if you already have customers, you just bring them in. Guillaume: And so tell me, what does a typical week looks like for you specifically? How do you spend your your day? Eze: Well my my day it's it's split between different different areas. There is a lot of work on modeling like business like business process modeling and in internal you know project management as well and kind of like making sure that we don't drift from from the the methodology that we are trying to apply. there's a lot of work of yeah, understanding Understanding business process, I think that's that's very key. there's a lot of vendor management as well. So ma being being on top of of issues that can come up with with vendors. We use a big amount a large amount of of of vendors. So that's that takes part of the week as well. then I do some coding as well. I try to jump in, not not not be so behind on on on the trends and everything. So I do I do still code. Of course, I'm not the main contributor in in our repository, but I try to jump in. And and yeah, these days, for example, I'm I'm focusing quite a bit on project management because we are ex expanding the team. So I feel it's important for me to to be present there. But it also varies, right? So I sometimes I I do a lot of not a lot, but there are stages when I do more visits to agents. So we can go there and be on site to actually actually see the workflows and the processes where we can improve. So I I love doing that kind of work of of visiting agents and understanding their pain points and seeing the operations. I think that's very key. and also conferences, that depending on the the yeah, depending on the time of year, that could that could also be some of the some of the time. But I would say on a typical week there is some project management, business modeling and coding would be the the the splits I get. And of course sometimes well meetings with vendors and meetings take way too much way too much time as as you you probably hear from everyone. But but yes. Guillaume: All right, nice. and what would be the the part of the operation you're the most satisfied with right now? Something maybe the team has built or figured out that's actually working really well? Eze: Well, I think all the IT operations and the internal processes around our deployment and around our delivery of software. That I'm I'm very pleased. we went with an approach of like like platform engineering where we created a platform and then we started building the products on top of that platform and trying to own Guillaume: Mm-hmm. Eze: the integrations so we can have better management of and and governance of of the data aspect. And also to shield ourselves from from sometimes vendors will change their APIs or things like this and so try to not depend so much. So I'm very satisfied with how the platform has come into fruition. So we are using now I don't want to get too technical, but we have automated all the deployment process to the point where we just you know push push to a branch and then There is all the proper checks in in place there so it can be reviewed and deployed. So we are deploying multiple times a day sometimes Guillaume: Mm-hmm. Eze: and without without problems. And now the team has our dev team is incredible, Valentin and and Christian and R. Spread, the three of them are are are amazing. But right now they come up with a whole observability new setup where we can see to a level of detail. all the business operations, how time how much time they're taking, how much even to the point of how much storage they're consuming, how much memory they're consuming, how much we can start getting to to really nice metrics on the the cost of ownership to a new level, right? So not just as an aggregated, but it's like, actually this process being run this amount of times and our time to cover load and like all all these things that can be sometimes tricky to measure. Now having all this observability platform in place makes it super easy. And also it's built in such a way where any product that we will build in the future on top of this platform gets all these features basically for free. So I'm very, very pleased with all that work. We are we we're Guillaume: Nice, nice. Eze: now and I will add we are now trying to also because this is all very new, right? I started with SPI in twenty nineteen. So it's relatively new. So even if it's like some years. we are also trying to expand on the operation side on how we can provide better tooling for our support staff, better tooling for our back office staff, and how how we can bring all these yeah, start to build f internal products more and more. We've been focusing more on building customizations that are more like user facing. Now we wanna go in more in or More like the customer facing, I would say. And now we wanna go into more internal users, like more specialized tools and this kind of thing. Guillaume: Awesome. And on the flip side, what would be the hardest part of your job right now that someone outside trump transportation, logistics, and let's say software probably would not appreciate fully? Eze: Yeah, so right now I would say the relationship with vendors has been a challenge. Guillaume: yeah. Eze: Yes. Because we are very dependent on on vendors because they have it's mostly like data products. So it's things that you cannot really build yourself. One Guillaume: Mm-hmm. Eze: one can build the the infrastructure, the scaffolding, the the logic. But the network effect of of a data product, like people who have access to, for example, certificates of insurance or identity services, these kind of things that we we just cannot build ourselves. Guillaume: Mm-hmm. Eze: When when those services change their contracts, being contracts in the commercial side or contracts in the API side, and all of those things are not managed properly. the downstream effect of that is very is it's a lot. Guillaume: Yeah. Eze: Yeah, it can be a lot because also for a small team like us, we're very lean, very like focused on automation and efficiency. So anytime that happens, it introduces a lot of unplanned work on the queue. And that that, you know, at some point it it it will it will bottleneck somewhere. And and it's it's just annoying sometimes that having if if those things happen with two vendors at the same time, it just can be a challenge. then one one thing that we struggle sometimes with is also just change management in general. So getting adoption and I used to get more w when I was just starting I would I would get a bit more frustrated maybe when people wouldn't adopt tools. But I think that as I as I grew in the in in the industry I understand also the reasons why sometimes people have difficulty adopting tools and start being more compassionate with that too. And understanding also what we can do better to to meet them where they are and try to to bring them into the use of tools in a way that you know that makes sense for them. So that's that's a challenge that we are still working on, but but yeah, we are trying to shift a bit the approach and not be like just annoyed with the user for not using the product, but more like, okay, how we can how we can reassess this, how we can help them. Maybe the product was not exactly what they needed, you know, and Guillaume: Mm-hmm. Eze: and and also, you know, look look within two. Yeah. So yeah. Guillaume: Yeah, you have to be kind of self I don't know, self-critique. right. You need to understand, are they not using the software because they don't understand it? Or have we delivered the wrong thing? Or it and sometimes it's some somewhere in the middle, right? but tell me about your TMS. So maybe explain for the listeners what a TMS is and let's say this type of features that you have in in in in your software and you know maybe the scale, how many transport you have to to monitor and and follow in your operations and with all your agents. Eze: Sure. Yeah, SP SPI just just for context, SPI has around 75 offices. Those are located in US and Canada, but most of the business happens in in the US. And those offices range from solo offices, you know, solo agents who who work from home to people who have like a big operation with like sales teams and ops teams. So we also have it's multimodal. We have International, we have it's mostly truckload, but we also do OLTL, we also do Ocean, so there's a whole bunch of variety of agencies. so that's kind of like the the context. And we move around just ballpark, 10,000 shipments a month. but it it it it might be more lately, but just ballpark. And then yeah, t TMS is the main operational system for a logistics company. So it's transportation management system. It's it's it's basically what an it's similar to an ERP where you handle all your orders, you're handling all in our case you handle also the the accounting, the billing, the payments, all the and you you can divide it into quoting, quoting freight, you know, in intaking the orders, and then the fulfillment or the operation of those orders. so finding carriers, making sure those carriers actually are compliant with your rules because there's a lot of making sure that also they're not scammers, impersonating carriers. It's a so all of the compliance part is embedded there. And so after procurement process, then you go into the track and trace, which is making sure those get delivered, and then after that is all the invoicing cycle and the payment to the carriers. So all of that is what the TMS control. So it will be quoting, procurement, operation, and then the invoicing and settlement. And then also the commissions that we s the that we pay to our to our agents also will will come up from the TMS data. Guillaume: So full management of the fleet and how to get orders and and how to fulfill them and from A to Z, right? Okay. Eze: Yes, exactly. And and the the nice thing the the TMS we use is called Revenova. it's built on Salesforce Platform, so it it gives you the ability to customize a lot of things or add things. So Guillaume: Mm. Eze: we created a a a set of services on the side that controls the integration between our vendors and the TMS. Because one of the problems of the traditional TMSs Is that if your TMS doesn't connect with the tool with another vendor that you have, then you need to wait for them to connect them, right? But now as APIs are more available for all these systems, we decided to instead of waiting for for for the vendors to connect, it's like we created this integration layer where we can plug and play and and aggregate data outside and communicate however we need. So Guillaume: Yeah, be flexible, right? Mm-hmm. Eze: Yes, exactly. Exactly. So so our TMS now it's a little bit of a it's it's highly customized. So you you can actually book loads outside of the TMS experience. We have our own UI now that you can also use for and that is connected to other sources of data. But and it all ends up in the TMS for the accounting side. So it always needs to flow back and be integrated. So the TMS is like the backend engine and our processes what kinda orchestrates all the all the work. Guillaume: So how much you said it's it's built on top of Salesforce, right? So how much Eze: Mm-hmm. Guillaume: of it is really let's call that a Salesforce app? And how much of it is kind of on the side communicating with Salesforce? Eze: Yeah, so the the TMS itself is a Salesforce managed package or an app. So it's something that you install and it contains all the custom objects and flows and things. And then on top, you can add your own Salesforce code on top of that. In our case, we do have a little bit of Salesforce custom code, but we decided to just build outside of the Salesforce platform on our own in with we build in with hosting AWS. And We have a Salesforce provides a huge amount of integration capabilities. So we are using all those integration capabilities like event buses and so there is like so it's it's it's co it it is loosely coupled, let's say. So it's all event based. So we there is a dependency there, but it's not like a a hard dependency, let's say. Guillaume: Alright, so if we jump in a bit further into technology, when I speak to people in in in logistics, things a thing that often comes up is real-time visibility is never fully solved. So I I'd like to hear you on how how important it is for you and and let's say your agents to have real time visibility on the fleet. on the deliveries and how much let's say customers of your agent expect that real time visibility as well. Eze: Yeah, that's a that's a big part, that's a a big part of the of the challenges that that logistics in general has. So in our case, because there's an added challenge because we don't own the trucks, so we are purely Guillaume: Mm-hmm. Eze: broker, so we always depend on on the on the carrier to provide that data, right? So the way how we handle it is we prefer doing tracking via ELD devices. So we have three different tracking providers. So there is less possibility of an excuse of saying like, I'm not connected with this one or I don't have the app or this thing. So we try and go with as much as we can with ELD. Also in our compliance rules, if the carrier doesn't connect their ELD to to the compliance provider, then we do not onboard those or we don't approve Guillaume: Mm-hmm. Eze: those carriers. We consider that as a as a as a risk. unless there is an exemption. There there are cases where there there might be exception exemptions. but generally we we require the ELD connection. And then yeah and then there is the challenge of sometimes when when the when the ELD is not connected and they're using for example phone apps, there's there are always challenges. But yeah it In those cases, what we suggest sometimes that the shippers can also opt for tracking the freight. Or what we do is we we work closely with the carriers and we try to just partner with carriers that are going to comply. And so, for example, for for one customer that has very strict tracking visibility requirements, our agent is using 198% of the loads are handled by four carriers. So and those four carriers we make sure that are compliant. We keep we keep track of their compliance. So it's a lot of monitoring that happens with within our system and our staff. And our agents are amazing also at at serving their customers because that's that's their their their main goal. So so yeah, it's a team effort between the technology and the people and the process. And then there are other tools that that that can be leveraged. But we are currently not using tools that are just taking photos of of of the trucks on the road and these kind of things. we looked into into those tools. I think they're really interesting. so far we have not implemented them. And yeah. I I I my personal take is that in the future it would make sense to shift towards tracking the the the actual shipments, the actual cargo, on top of tracking the on top of tracking the the tracks around trailers because there's been even cases of theft where the truck arrives to the place where it needs to arrive, but the cargo is not there. Or or or the cargo was the weight is the same, but the cargo was replaced with something else that was waiting the same. Or all Guillaume: yeah. Eze: kinds of like operations that can happen, you know, the the the fraud in in and and theft in the industry has gone like crazy in the last couple of years. So so yeah, it's it's a challenge. Guillaume: Interesting. what kind of data do you get out of an ELD? Eze: so you depending on the depth of the integration of the LD provider with the aggregator, generally there is the ELD world, and then you have multiple providers, and then you have aggregators that will gather all that data and and push to you. So depending on the depth of their integration, you can get different levels. So basic, you can get the tractor information and location. Then additionally, you can you might be able to track the trailer. And they will be able to track which tractor is hooked to which trailer. and then you will get location pings every five to ten minutes across the lifecycle of the of the load. so you yeah, you get basically the VO colour or trailer number and their location. And then you get G Yes, you you those are generally those Guillaume: Get speed or or tell me tricks about about the the truck itself. Eze: are generally not shared, but For example, the those are those are responsibility of the carrier itself. So for example, if the driver is did a hard turn or a or any violation on on their driving the speed or things like this, the carriers generally get those conf those notifications and that's on their end to to to monitor. What we do get is through geofencing. when the trucks are close to the pickup or deliver locations, when they enter the geofence or when they depart from the geofence, you get the that information. Guillaume: And so in in your model you you have you guys at the headquarters, you develop the let's call that the platform general, right? the the software and and all the s the shared services. And then you said, let's say the agents or the the other companies that use your services to give their services, right? To provide your services. And then when you say carrier, is it Are there agents that are carriers as well, or typically it's just someone they subcontract to? Eze: so that can happen because sometimes if there there is people who maybe they own a trucking company and they also own a brokerage division on that trucking company and they were doing both with the proper authority and everything, right? So in those cases it might happen that an agent happens to have a trucking company, but they would have to go through the same compliance as any other. Guillaume: Mm-hmm. Eze: carrier would operate in the in the eyes of of the of the brokerage it's just another carrier right so they will have to go through the same process so spi will be affiliated only Guillaume: Okay. Eze: spi will be affiliated only with the broker as as with the with the agent and then the carrier can be onboarded as a carrier separately Guillaume: Okay, but typically it's kind of two different things. For you, you you work with the broker and Eze: Yes. Guillaume: it can be the same entity or or not. Okay, I get it. then you mentioned compliance. So what are the aspects of compliance in in that you care about right now? Is it is it more like I don't know, if you have refrigerated cargo, are you responsible for that? or is I'll let you answer the question directly instead of try trying to guess. So what are the aspects of compliance that you are that that that matter to you guys? Eze: Yeah, that's a very good and deep question. it's a moving target. There there's been there's been recent court rulings about what they what we they call in the industry nuclear verdicts, where these cases where they can affect many other cases, right? So Guillaume: Mm-hmm. Eze: so brokers have been found liable for for for example, accidents. that happen during moving cargo because of their carrier selection criteria. So just to give you an idea of how complex it can get. So in in our case we have a very it's a very thorough and and a very deep process of compliance. So what matters is well ins insurance, time of authority for certain Customers, you need to have a specific requirement of how much insurance you need for the cargo. you need to connect your ELD device. you need to have no flags for for fraud, of course, or identity theft. So even for the ones who have been victims of identity theft, we we we put controls in place to make sure that we are only talking with the authorized contacts. and then there is other aspects like For example, we don't use scares with conditional safety ratings. yeah, the safety part is is very complex. and and that will depend. So for example, as you said, if for example for for hazmat you will need to have a specific specific type of certifications, for for same for heavy hall and So yeah, it it it's mostly that time time of authority, connecting your ELD, but also you need to remain active in our system. So for example, if you're on one one problem the industry had as a whole the last couple of years is that maybe you on board a carrier, they are approving your system, but these fraudsters were buying companies, buying legitimate companies that were already approved on the broker systems. And then they would use those clean authorities or clean records to then steal freight. Right. They will they Guillaume: Mm. Eze: will sometimes wait for six months and operate the company properly and then they you know they do the the big the big hit afterwards. So so we also if someone doesn't move a load within a time frame, we would put them in a sleeping status. So if they want to reactivate, we'll need to go and check, have they changed their contact information on the FMCSA or you know, all these additional additional steps. So yeah, I can I could go more in detail, but it's it's a moving Guillaume: that's interesting. Eze: target. And and also it will change depending on the looser tight markets too. well not so much on the market, but it will change also based on the legal landscape, right? Because the legal landscape is all the time changing based on these Guillaume: Yeah, yeah, yeah. Eze: rulings. Guillaume: So it's mostly I guess safety, security, and let's say fraud or steal, stealing prevention, theft. Yeah. Eze: Yeah, identity, identity related and Guillaume: Mm-hmm. in your TMS, do you do you care about route efficiency or is that left to the carrier? Eze: there are there it's it's it's a mix because different offices might have different approaches. So for example, Guillaume: Mm-hmm. Eze: there are cases of high value cargo that we might want to route specifically through through specific states or not, or avoid specific states or or areas or cities. So in those cases the agent will work with the carrier to to come up with a a routing that that would be good. And I and I think that's also one of the the sweet things about the agent model is that our agents are owners of their business. So they care and they treat their carriers, you know, treat the carriers as as a customer too. And they they they want to develop those relationships because it's important for everyone for for that project to each load is a project, they take it that way and it and it needs to succeed. So sometimes it would be a a work between our agent and the carrier. Sometimes it would be just delegated to the carrier. And yeah, sometimes the shipper will ask for a specific route for specific reasons. And in those cases, yeah, we would but we don't have a centralized approach to it. Guillaume: got it. So there's no, I guess, route route optimization, let's say, to minimize empty mile movement, right? That kind of stuff. It's at it's most likely let's say a concern for the for the carrier. Eze: Yes, so the it's more a concern for the carrier and we do we are part of the smartway program, so there is we do keep track and and report on on empty miles or or you know, well the the thing is it's a bit hard sometimes because we don't own the fleets to to really get the proper data. Yeah, Guillaume: Mm-hmm. Yeah, that's why I'm saying that, yeah. Eze: so it I would It's something that we we want, you know, to optimize for for in that way, but it's just a bit harder when we we you don't own the fleet, right? Guillaume: Yeah, you don't have much control out of it and it's more the carrier that has the incentive to minimize that, right? Because when you ride with an empty cargo, I guess it's it's less let's say profitable during the that that moment. Yeah. Eze: Yeah, a hundred percent. Guillaume: Yeah. so you don't manage really drivers and trucks and and right and your agents most of the time don't either, right? So typically I have questions about that for people in logistics. so I'll just skip those and maybe ask you if you could fix just one thing on how your software is built or how your operation runs right now. Something that maybe has been on the list for a long time but keeps getting pushed. What would that be? Eze: Hmm, that's interesting question. I think I would like to improve the user experience of of the of the platform. I think the products that we've been building have are on the right track, but they are focused solutions, right? So right now we launched a capacity hub, version two, which is mostly for procuring carriers, right? For sourcing carriers and being able to quote and book those carriers. But I would like to that same user experience to be translated to to the whole ecosystem. Guillaume: Mm-hmm. Eze: And yeah, because I mean Revenova is is is great. We don't have major you know major issues with it. But being able to control the user experience, I think that's something that that would be that would be a bit f I would I feel it would be freeing for for for us because Right now we're trying to also fit in different modes and different, you know, we're doing some international, we're doing truckload LTL and and sometimes also our agent model. Sometimes you can have a sub rep that is also moving loads for another rep or dispatchers that work from multiple offices or things that having so and the TMS is just maybe too generic in the user experience on how to operate Guillaume: Mm. Eze: those things. So having the ability to more like customize tools. that that own the whole thing. I think, yeah, if I and we will eventually get there. It's just it's one of those things that we I wish we could be like, hey, you know, like Guillaume: Yeah, yeah, it's always a a matter of what's the most important thing to do right now. Right. Eze: Yes, exactly. And UI work as as you probably know, UI work even now with AI is it's a bit faster, but it's time consuming, resource intensive. Guillaume: Yeah, it is, it is. Because once you know exactly what to do, it's not that bad, but it's understanding what the user needs, right? How they use the software, how they think when they use a soft that takes time. That takes time. Eze: And I'll and if I may, I'll add you one more thing that it's if if Guillaume: Sure. Eze: one wish. I would like to have an event model of all of our business processes validated by our business users ready to go. Right? Like event modeling Guillaume: Mm. Nice. Eze: is a technique that was developed by Adam Dimitri. I I I highly recommend it for for for everyone that that it works on IT or or for executives as well. I think it's the best tool possible for communicating re software requirements and how to map business processes. And I think if I w if if I could have a v event model of every process in the organization ready to go, that'd be awesome. But also part of the nice thing of event modeling is that the exercise of building them. So yeah, so that's Guillaume: Yeah. So maybe for maybe the listeners who don't really know what event modeling is, can you kind of give us a a small overview Eze: Yeah. Guillaume: of what that is? Eze: So it's a it's a business it's an information flow modeling tool. Mostly I find it I find it helpful for developers but also for executives or business teams. And it's a way to map your inform the information flow of your business processes using very simple primitives that anybody can understand without technical without technical knowledge. And you Guillaume: Mm-hmm. Eze: go through a process of seven steps. It's a workshop format where you work with sticky notes or a virtual whiteboard. And you go through the steps of identifying events, or then you put those events in timelines, then you identify what inputs and outputs exist from those events, then you organize them on lanes based on your teams, and then you you come also with the UIs, then you create the at the end what you come up with is test cases. So then you end Guillaume: Mm-hmm. Eze: up with a timeline and test cases. And those test cases you can use to guide your implementation. And all of that timeline can also be sliced. So you can use it also as a project management tool to be like, well, if my dev team is taking one week to implement one slice of this workflow, then I can kind of project how the how the the project will go, how much how long it's gonna take, and also gives the developers a very clear framework. of how each all s all slices are pretty much the same regarding code and implementation. Guillaume: Mm. Eze: So so yeah, so long story short, it's an information flow modeling tool that uses very simple primitives and allows you to map your business process. Imagine like how you used to have how you call entity relationship diagrams or or business flows or BPMN Guillaume: Mm-hmm. Eze: or those things. This is kinda like an I think it's a great evolution of those kind of tools and it makes it more accessible for like non engineers. When you see a diagram it's very colorful and very like easy to to follow. Guillaume: so it's not for technical people necessarily. It's a way to communicate, Eze: No. Actually the it Guillaume: I guess, between technical and non technical people. Eze: Exactly, and also allows developers to in at a glance to understand like how what the context is. And also when you go back to it a year later, then you understand exactly or if a problem happens, you know it's happening on this slice, it's it's located there, and you can correlate that with where the code lives, right? So th Guillaume: Mm-hmm. Eze: it forces you also to because it it comes with from this idea of Software engineering w came from like traditional engineering practices. So it was more like a waterfall type of project management methodology where you would design the system and then we'll implement later. Then we went into the agile, which is like just just build, no plan. But I think now we're getting again into you need what what is spec driven development, where you need to develop some sort of design, maybe not a big design, but a small design. And event modeling I think goes into that sweet spot of like designing first and building after, but not designing so Guillaume: Mm-hmm. Eze: much that is crippling, right? So I I find it I find it interesting. And also it forces you to first change the model and then change the code. So nothing that nothing that it's on the code should be the code should not be touched if the event model was not updated. yes, and and one should be the consequence of Guillaume: It should be always in sync, right? Yeah, yeah. So I guess it it Eze: the other. Guillaume: it it it probably would be a a great let's say aspect of specifying your software when working with AI, right? Because you can express what you want to expl accomplish to the AI and it's it's a way also to communicate with with your agent, friends that help you develop your solution, right? Yeah. Eze: 100%. It has been it the perfect it's the perfect fit for for AI development. And actually there is a lot of there are a lot of online materials from from Adam and Martin Martin Dilger, which is another practitioner. And they for example, we are using n low reasoning models or very like like not the most advanced models. Because the the work is chunked in such a way that you don't need reasoning models because the specification is so clear. Guillaume: Right. The hard part has been done. Yeah, the hard part has been done by creating the the the model, I guess. Yeah. Makes sense. Eze: Yes, exactly. Guillaume: That's interesting. Interesting. aside from leveraging AI for coding and maybe designing and and for for your development team. I mean, aside from that, where do you see is the biggest opportunity for logistics software like a TMS, like you guys are doing. the biggest opportunity how to leverage AI to deliver more value to your your your agents, yourself, and the ecosystem that use directly or indirectly your system. Eze: I I think there are a few a few areas. the common the commonality between them I would say is unstructured data into structured data. So that's that's Guillaume: Mm-hmm. Eze: one of the main things. That could be document processing, for example, pod, proof of delivery management, customer Guillaume: Mm. Eze: credit requests, all kinds of forms related to the onboarding process, credit checks, all these type of of forms. Then ordered intake. A lot of times the orders will come in in unstructured formats like emails, attachments, Excel files, and different things. So we are using it for that. We are using it for remittances processing. So a hundred percent of our remittances are parsed using using AI. And so a lot of yeah, document processing and unstructured data from email. And then that's one one area. The other one is categorization, and that could apply to Like the more like atomic data, like an email, or a larger set of data, like for example, all of your intransit shipments, which ones need your attention now? Or like categorizing cues of work. so we are doing some experiments with that. And yeah, that we'll we'll have more more things to share soon on the track and trace automation. So it's like, for example, you know, being able to surface what shipments might be at risk, because maybe the we didn't get an update from the ELD device or or Guillaume: Mm-hmm. Eze: some s the the the tracking dropped or or it's out off route or Guillaume: Like a proac proactive I don't know, monitoring where you instead of is Eze: Yes, exactly. And then Guillaume: yeah. Eze: and then you have also the voice agents. But that one is a tricky one because the voice agents could be a great thing, but also depending on on how you measure the success of those initiatives. If you measure only how many calls the voice agents are taking, but maybe you you could develop a process where those calls are not needed anymore. You know, in our case we would try to use go for the latter option to to try to solve it but Guillaume: Yeah. Eze: you know the root cost. But in the meantime, a lot of times if you have a lot of staff using you know receiving calls or doing check calls just to say where is your truck and then the person is saying, yeah, I'm I'm ETA twenty minutes, it could be that those a lot of brokerages are are having success with those type of automations. Guillaume: Mm-hmm. Nice. so Ezekiel, tell me maybe a decision you made in the last couple of years about a feature, a vendor, a technology, or any other change related to your technology that you consider a real win. Eze: Yeah. Well I think that handling the integrations and some of the core processes with internally built software, I think that was at the time a a decision that was you know now seeing it from now it was it's been successful. So I think I think I think that I I could say that one. But at the time it was not so clear, right? Like it's because you ha the the f the first Implementation that that that took us in this path was a payment processor. our TMS had an integration with them, but their integration was not doing all the things that we wanted. So we were like, actually, we need this, so we built it ourselves, and then we decided or we saw that this this could actually work, and we started doing that more and more. Guillaume: Mm-hmm. Eze: So I think that that was a good decision, trying to own. Trying to own what is the the the the actual core capability of SPI and and own the integrations, I think it was a good decision. Guillaume: mean instead of using Salesforce let's say application or integration, that's what you mean? Okay. Being kind of Eze: Yeah, so Guillaume: outside the Salesforce kind of ecosystem, but just communicate with it. Got it. Eze: Yes, correct. For example, our billing our billing process before it was happening in Self, or now it's like we just pull the data, we create the PDFs, and we just send all of that outside. And that allows us to do all kinds of things like I want to put this wording on this particular invoice. I like a lot of customization that that was not possible in in the original. Guillaume: Nice. and maybe in a few seconds, what would be a decision you would take back? Eze: Well there's there's one at some point I don't think that the the the product was not a fit, but I think it was not the right timing. So we Guillaume: Mm. Eze: we we went with a vendor for bidding automation to bid on on on on shipments from from shipper bidboards. Guillaume: Mm-hmm. Eze: And the the product itself I think I think was was good. But we didn't get the adoption from from our agents. And I think it was also because of the way how maybe it was not the right time, you know. And Guillaume: Mm-hmm. Eze: and I jumped from a perspective of this could just trying to think in an ideal case, we could generate all this extra extra business, right? And and but it was not as simple. I think that was maybe I was oversimplifying that Guillaume: Mm. Eze: that decision. And So yeah, I think Guillaume: Part of a learning process, I guess, right? You try stuff, doesn't work, but at least you know it doesn't work, right? Eze: Right. Guillaume: all right. for let's say another another logistic leader who's looking at at us and listening to this podcast, and wondering where to start, where to use technology, what would be your your honest advice? Eze: I think I think the networking and talking with with with people who has gone through the same challenges. I think I every time that I go to conferences and and we made a lot of friends on the way of like and we always sharing I learned so much from from those events because you just just sharing with people who has gone through the same through the same challenges, be part of of boards or advisory councils or for example Revenova has an advisory council a customer board. So be be be part of those conversations and don't be afraid to ask because like when I started it's like I didn't know what what what a bill of lading was. And you know and and but it's important to not have it's it's same in the reverse with technology. It's like, I don't know how AI works. Well try to not be so afraid and like just you know, get to un get get to understand it to the level that it's useful for you and for your goals. And I think that's the other thing. You don't need to go so deep into understanding how software development works, but just having a that base understanding and and ask ask the questions to the people that that has gone through that process. Yeah. Guillaume: Awesome. All right, Ezekiel. Before I let you go, very quick lightning round of questions. So first thing that comes to mind, no overthinking. what would be the most overrated thing in logistics technology right now? Eze: Overrated thing in logistics. I think that some of some of the AI automation tools. I I Guillaume: Mm-hmm. Eze: I don't want to go like within specific like I don't have, but I think it over over Guillaume: Like the over promise of AI and Eze: I I would say over over promise of AI, but over promise of of automation in general. And I would say also I would add the quality. The quality of the products that vendors and startups are delivering. I think those Guillaume: Mm. Eze: are things to be are very risky because I don't want to extend too much, but a company like SPI, we build software that might stay with the company for a while because we it's we are not a software factory. So we need to make sure that what we build works. But for a startup that is has investors' money and they need to get a product right away, they might take shortcuts. But then the customers end up paying for those shortcuts, right? And so I would say also that the the overpromise and the the the just the nature of the quality management on on the startup world, I think sometimes collides with the quality management needed on a long term vision company, which is a l what a logistics company has. Guillaume: Especially with a s a system like yours, right, where it delivers services that are mission critical for you, for your agent, for the the carriers, for the customer. So yeah. the w the one system aside from your TMS, the one system in your operation you couldn't run without. Eze: The one system that w we couldn't run without besides the TMS, it would be our compliance partner highway. They they they are the ones that say, Hey, this carrier is is good or not, basically. So and they verify Guillaume: Awesome. Eze: their identity and all those things. So yeah, that would be one Guillaume: Great. What do great logistics operators do that average ones don't? Eze: I think being open to to shift processes f when when when it's needed, right? And I think being being open to to that is it's important because maybe someone learned a playbook during a loose market and then the market shifts and the playbook that you were running starts not working just because the market Guillaume: Mm-hmm. Eze: shift and before you were used to post a load and get phone calls. Maybe now you post a load, you get no calls. So what you do? Right. So Guillaume: Mm-hmm. Eze: in that case you will need to shift into okay being proactively sourcing instead of waiting on the sourcing, right? Guillaume: So flexibility, right? be open to change. I guess it's a conservative it's a conservative Eze: you you said it better than yeah, you said it better. Flexibility for sure. Guillaume: Yeah, so I I guess what you're saying is that transportation might be a conservative kind of industry, right? When it works, we like it like that. all right, last question to you, Ezekiel. If you were not in logistics and transportation and software, what would you be doing? Eze: the something related to art. I I and I do. I I I s I still do. well I I like Guillaume: Related to art, really. What kind of art do you do? You talk about music? Eze: I I I I like playing music and I also do interactive technology projects like projections or installations or I collaborate with those Guillaume: Nice. Eze: kind of projects. My my fiance, she's artistic director for a dance company and sometimes I collaborate Guillaume: Mm. Eze: with like the the tech side on the lights, the the backgrounds, the projections, the sometime with the music editing and all of that. So yeah that's Guillaume: Awesome. Eze: that's something I do as a as a side thing. but I I Guillaume: Nice. Eze: I love it. I like it. I really like it. Guillaume: All right. What kind of music do you play? What instrument and what kind of music? Eze: I I like all kinds of music. I I I play guitar mostly. lately I've been enjoying a lot of South American more like folklorical music. Like I'm from Guillaume: Mm. Eze: Argentina but my family's from Uruguay as well. So music music from from from home has been lately the the main. Guillaume: Nice. All right. Ezekiel Peralta, this was genuinely great conversation. Thank you so much for taking the time to talk with me. really appreciated how you were specific and honest and candid about your work and what you guys do at SBI. and what's actually happening inside your organization. This is exactly what this show is for. And tell me, Ezekiel, where can our listeners find you or follow what you're building? Eze: Yeah, so they can find me on LinkedIn or e Peralta at SPI3PL dot com. That's my email. So yeah, you can find me there and also I generally attend the TIA conferences, so for everyone who is there and wants to to chat, like always always open. Guillaume: Nice. Any music show or multimedia shows on the on your calendar soon? Eze: yes, actually. November twenty eighth and twenty ninth in the Shadwell Center here in in Burnaby. we're gonna be presenting Bright Shadow, which is interdisciplinary production. Yes. Guillaume: Nice, nice. All right. So thank you everyone for listening to Digital Digital Leaders Club. If you're a transportation or logistics leader like Ezekiel, dealing with any of the challenges and and and concerns that that we discussed today, we'd love to have you on the show and continue this conversation. You can find us at ngeno.ca and until next time. Thanks again, Ezekiel. Eze: Thanks to you. Have a good one.