This is also what we discovered at @engimeets.
One of the biggest challenges we’ve seen in the Kenyan market, especially among medium-sized enterprises, is the data problem.
The data exists, but it’s often scattered across systems, spreadsheets, documents, and workflows. It’s unstructured, difficult to connect, and ultimately hard to use for meaningful operations or decision-making.
So we decided to tackle the problem at its foundation: the data layer.
At Engimeets, we’re building infrastructure that helps organizations consolidate fragmented data into a unified, reliable layer they can actually use.
Because this problem looks different across industries, our approach is to build vertical-specific data infrastructure, per tenant.
Our first flagship product is Atlas, built specifically for freight forwarders.
We went live with our first Atlas engagement this week, an implementation estimated to run for about five months.
Over that period, our goal is to build a robust ontology for freight forwarding and establish reliable data pipelines that transform the client’s scattered operational data into a unified layer they can use for day-to-day operations, analytics, and decision-making.
In simple terms: Engimeets builds the data layer. Atlas applies it to freight forwarding.
And freight is just the beginning.
We’re building toward a world where businesses don’t have to fight their own data before they can use it.
https://t.co/o7xgH3RSKf
At Engimeets Atlas, we believe customer terms should be embedded in the operational workflow.
The job should automatically inherit the correct rates, rules, documentation requirements, and approval paths.
Yes, that’s true.
One of my learnings too. In logistics, for example, I am yet to encounter any regulation restricting our development and implementation of a TMS
The only one with complex compliance is fintech.
Others, you have an environment where you can build, test and iterate.
If you’re looking at expanding into US/European markets like what we are doingat @engimeets, you can compromise on the check at the moment as you build a more resilient and robust product.
@0xPascual At Engimeets, we actually understand how logistics work. We have worked inside the company. Attended meetings, built small automations on excel and n8n to try and clear up the mess.
Kindly let’s engage on how we can help you make decisions fast, and seal invoice leaks
Currently building Engimeets
What we have in place
- A customer in logistics, our first vertical
- A live sandbox to build 80% of the cross-cutting business ontology in logistics
- Customizable microservices which we can easily scaffold to a customer in 2 weeks
Looking for founders in the ugly phase.
Not the polished deck. The hacked demo, weird distribution loop, angry user, broken prototype, or customer pulling a half-working thing out of you.
If you're building something with real pull, send it my way.
What we do at Engimeets, across all our verticals is understand the critical nature of human decision in making business decisions.
At Atlas, we understand logistics involves both human ingenuity and, and data-driven decisions.
Engimeets Atlas.
Our view is simple:
If the system only tells you what happened after the job is done, it is reporting.
If it helps you control the job while it is happening, it is infrastructure.
Your logistics business needs infrastructure.
One thing we believe at Engimeets Atlas:
A logistics company should know whether a trip is likely to be profitable before the truck leaves.
Not weeks later.
Not after finance reconciles the job.
Not after the customer disputes the invoice.
Before the truck leaves.
That requires more than an accounting system.
It requires a live connection between the customer terms, route, truck, driver, expected charges, estimated costs, documents, fuel, clearance requirements, and operational risks.
That is the operating layer we are building at