How many of you have ever worked for an IT consultancy like Reply, Deloitte, Place Resilience? So, I worked for them for quite a few years, almost 10 years. And I used to be the head of data and AI at Reply US and the scale companies at Reply from 0 to 10 million. But then at the beginning of this year, I decided to leave Reply. and I decided to solve one of the problems that I used to live every day. So we decided to build Horus.
But let's dig into the problem that I kept seeing. So usually when one of my customers decided to buy a new tool, an enterprise company, they needed to integrate with the ERP. And guess what they didn't have the IT capabilities to do internally. So they go to an IT system integrators to get a quote and the quote was for small integrations 50k in five months but also for bigger integrations millions and years.
And this is pretty the timeline that they see for a quick quick integration, four weeks for requirements and design. Then they start building, then you have testing. But then when you test, there is something wrong. And guess what? There is a CR, a change request and additional money. And then at the end, you have the end over.
We have decided to stop with our platform. platform so before integrations they used to take 100k and five months now with others can take 10k and six days we already deployed others on medium and large enterprises
and specifically we are focusing on three main pillar logistics manufacturing and they were are helping also SaaS companies to deploy their infrastructure and their solutions to mid -enterprises.
But now let's dig into a demo. This is how our platform looks like. It's like a chat GPT.
And this morning we needed to do an integration for one of our customers, a logistics one. And we have decided okay let's try to do a demo. So it took 45 minutes, then of course we shortened
in our video for that but here what we needed to do it is not to make an automation we needed to import all the shipping manifest of a logistic company into the erp the erp was cargo wise which is the golden standard for for logistics and so we start asking okay i have this manifest
this manifest data on S3, which is a bucket of AWS, and I want to automatize that.
So our agent, which is a business analyst, because when you go to an IT system integration, they start with a business analyst and they keep asking questions about process and so on, and your systems.
And our agent start asking, okay, how is the process today? There is something manual, there is a notification, application, how it works right now, and what is the version of your system finally. So chatting is trying to figure out how is the process and after understanding what is the process is start building the integration.
We are working with enterprises when so when you have a business analyst is super important that they ask a lot of questions about your business process, how you want to implement, meant if there is anything wrong because we wanted that our integrations are reliable and so with the business analyst we will create what is the functional document to create then an enterprise integration because we don't want to put down companies of 500 million 1 billion so we want to create enterprise and reliable integrations so here for instance he's asking
okay i have cargo guys how do you access to cargo wise what is the version that you have a cargo wise because when we create and we recreate a business process we want to double check okay what you are saying if you have any documentation they share the documentation but also to understand what is in their system so in this case what you have in s3 so let's say that you have an S3 that might work on SFTP, how it is structured, or you have manifest already in CargoWise, how I can access to CargoWise, because I want to double check if what you are saying that the business process is real and to recreate the business process and then the automatization that we want to create.
Now, for instance, here it is asking also a bunch of questions about the process of your IT team because maybe you need to have a VPN or maybe you need to whitelist some IPs okay because you want to be secure and so it's gonna ask who is the contact there who is gonna create this type of stuff
and then the user in this case me I was saying for instance the credential I can can provide. My team is going to be the one who is going to create the IP whitelist. And then I can provide you also the credentials.
Now that I have an idea of what is the business process is going to ask additional documentation. If you have any documentation, we will read our agent is going to read our documentation.
And then finally, for instance, there is going gonna ask okay can you give me the credential I want access to the to the system in this case was cargo wise accessing to this system I was saying before is able to double check what is going now here if you see there is
trying to understand okay how can I I can connect with cargo wise unfortunately cargo wise is a pretty old and is a legacy also if it is a legacy and the golden standard is using SOAP API so he's connecting with SOAP API instead of REST API
to try to connect now moving forward he's checking the last time with this NS3 okay to create this type of of automatization reading again what is going on to create this reliable integration he's checking even if you have any e -adapter or license so it's gonna check okay does it communicate does it communicate well in this
case yes because we know it then he's gonna ask okay if you have any issues who i need to connect with and for instance in this case we are saying okay you need to connect with the support team in this case i said acme just a general one
and additionally it's going to ask additional questions okay can you provide me also with some some files because these manifest files are very long. They are like 100 pages of manifest.
So in order to understand how to create this map. So now in this case, I gave two documents to understand how to create the mapper and the automatization to create the field by field how to map these fields into the ERP.
Now that that's finished, it's gonna read okay I found this what is the key there usually is the bill of lading in cargo wise is that true yes then I say okay I read a lot of codes charged codes in
cargo wise I don't see these files I don't see these codes do we have a mapping configuration and in this case we say yes okay I have the mapping configuration, I share what is the mapping to translate what was in the manifest into something that they had in cargo wise, and now is able to create the connector.
Now, a bunch of other questions to understand, okay, what happens if something is wrong? Do you pay a fine? Yes? No?
Who I need to connect? How much time do I have to connect these pairs and finally the last question is that okay
how can I enforce that this is correct and for instance in this case I said okay please just check that the number of files and the rule that you have in in the files is the same one that you have in incalculablewise he's asking also even
questions about okay if I have two times the same record what I need to do I need to update I need to discard what happens so we are gonna see all the edge cases because again we are a integrated enterprise companies and we want that these companies and these integrations are reliable then last questions is
gonna say okay you know that my manifest that might be not on s3 might be for instance on email there might be other cases what i need to do do i need to take care of that the answer is no just take care of the s3 all the other ones are out of scope he's gonna ask also
okay do you need to know the trails in this case say yes i need to know these traits so i need to know it whatever oops sorry whatever is what is completed whatever it is failed and why and i need
to keep what is failed now what is gonna create basically is four documents it's gonna create one document about the functional design because I'm up to the process and I want that from a business perspective is good so as you can see you have a functional design I can read whatever it is all the specificity about what I said and then if everything looks correct to me I can say okay just submit or if there is anything wrong okay we can modify we can adjust and we can start again with some changes afterwards it's gonna say okay i have the function design
now i have the tech the technical design so for instance here we have seen that you don't need a real time maybe you need a batch because every week you're gonna receive like 1000 manifest so So it is not real -time, it is batched. Then he's gonna create the actual integrations. Okay, he's gonna describe all the processing logic. Okay, how it works, what is the foreign key, and so on. What is the hidden potency? If there are duplicate, what happens? And at the end of the day, how they are mapped on the field. So they need a mapping file documentation. implementation. Again, here I can correct anything that looks wrong or I can just submit.
After I have submitted, it's going to do all the tests, it's going to create the code and then it's going to deploy what is the infrastructure underneath because we deploy enterprise architectures.
Then here what happens is that it's going to submit, it's going to check also what is the cost of this one -off and then afterwards we start building all the infrastructure to deploy
this now i can see here that it is in building i can see all the documentation that was provided i can modify that i can see even the credentials that are provided i can change all the configuration and i can deploy as well in this case it's in building so i need to wait that infrastructure is deployed.
At the end when it was deployed what happens is that I can see the run so for instance for today that was just a run I can check all the logs and I can check also with the logs so in case there is something wrong I can understand that why something is wrong for instance with credential mapping because there was a field that didn't work.
So it is all thank you so much for your time