The neutral AI
operating layer for
African freight corridors.
Pamoja sits above the systems, channels, and companies that already move freight. It turns WhatsApp messages, emails, documents, approvals, handoffs, payment readiness, exceptions, and evidence into governed workflow and coordinated business outcomes.
The work between systems
is where freight breaks.
Your business runs on messages, but your systems do not update themselves.
You already have systems. So do your counterparties. But the most important freight work still happens between those systems: in WhatsApp messages, email threads, PDFs, spreadsheets, phone calls, photos, portals, and people’s memory.
“We have the document somewhere, but nobody knows if it is the right version.”
“The broker, transporter, terminal, and customer each think someone else has the next step.”
“My team spends hours answering questions the system should already know.”
“We discover the problem after the truck is already waiting.”
“When there is a dispute, everyone has screenshots and nobody has proof.”
“Cargo moves before documents, payment, permits, or slots are actually ready.”
“Finance has to reconstruct what happened weeks later.”
“Executives see reports after the cost has already happened.”
Pamoja turns that hidden coordination work into governed workflow, evidence, accountability, and outcomes.
Why now?
African trade is expanding, but the coordination layer has not caught up. Pamoja turns the messy operating layer into governed action.
Trade is expanding
More cargo, more compliance, and more cross-border movement across the continent.
Pressure is rising
More finance and more strain on ports and borders raise the cost of every broken handoff.
AI can finally read the mess
Messages, documents, photos, voice notes, portals, and system exports are now machine-readable.
One corridor. Many buyers.
One operating layer.
Pamoja starts with the teams closest to the daily freight pain, then expands across the institutions that depend on corridor performance: operators, cargo owners, infrastructure providers, governments, banks, insurers, DFIs, and technology partners.
Freight Operators
Forwarders, brokers, clearing agents, trucking fleets, fuel distributors, warehouses, and depots.
“Daily operations run through WhatsApp, email, spreadsheets, PDFs, and manual chasing.”
Turn documents, updates, handoffs, exceptions, and customer requests into structured workflow, evidence, and next actions.
Start with document readiness, customer updates, or exception ownership.
Corridor Infrastructure Operators
Rail operators, terminals, ports, depots, and border operators.
“Release, dwell, handoff, and gate decisions depend on conditions outside the operator’s own system.”
Connect external readiness, documents, payment readiness, custody, and exceptions into one corridor operating record.
Start with release readiness, handoff evidence, dwell visibility, or gate/release coordination.
Cargo Owners and Traders
Mining companies, commodity traders, agricultural exporters, and shippers.
“The cargo owner pays when documents are late, corridors stall, vessels miss, weights differ, or counterparties fail.”
Create cargo certainty through shared identity, custody records, readiness checks, counterparty visibility, and evidence-backed settlement support.
Start with cargo certainty, corridor visibility, or settlement evidence.
Governments and Corridor Institutions
Ministries, customs agencies, border agencies, corridor authorities, and logistics associations.
“Trade facilitation is measured late, inter-agency coordination is weak, and reform outcomes are hard to prove.”
Provide operational evidence for corridor performance, permit visibility, border events, agency handoffs, and program reporting without replacing national systems.
Start with corridor performance evidence, permit visibility, or border event reporting.
Finance, Risk, and Ecosystem Partners
Banks, trade finance providers, insurers, DFIs, and technology integrators.
“Finance, insurance, and program funding depend on verified operational truth that is usually scattered across documents, emails, and counterparties.”
Turn corridor operations into evidence for trade finance, claims, risk monitoring, program reporting, and scalable implementation partnerships.
Start with verified operational evidence for finance, claims, risk, or program reporting.
What Pamoja
is not.
The neutral AI operating layer above them.
Pamoja coordinates the work between systems, parties, channels, and handoffs, without replacing anything your team already runs.
Pamoja sits above the stack,
not inside it.
Your existing systems manage their own functions. Pamoja coordinates the work between them.
Visibility platforms show where cargo is. Customs systems clear declarations. TMS platforms manage internal shipments. Terminal systems manage yards. Pamoja coordinates the work across them.
CargoWise-style TMS platforms, customs systems, ERPs, terminal systems, WhatsApp, email, and spreadsheets are not replaced. They become inputs into the operating layer.
One operating layer.
Six working parts.
DIRA Connect
DIRA Connect is the AI sensory layer that reads approved channels and systems, captures artifacts, and turns scattered information into evidence-backed facts.
Shared Operating Record
Connects shipments, cargo, parties, documents, handoffs, exceptions, and evidence.
Communication-to-Operations
Turns messages into reported facts, work items, approvals, corrections, or controlled actions.
Ambient DIRA AI
The AI accountability layer that shows what is blocked, who owns it, what it may cost, what should happen next, and what proof is required.
Objectives
Converts problems into governed business outcomes with owners, plans, steps, evidence, recovery, and completion.
Evidence & Audit
Preserves what happened, who acted, what changed, what evidence supported it, and what was learned.
DIRA Connect brings the evidence in. Ambient DIRA AI surfaces what matters. Objectives help teams drive the outcome.
Ambient DIRA AI turns operational noise into accountable action.
DIRA AI runs in the background of Pamoja, watching for blockers, ownership gaps, exposure, deadlines, and recommended actions.
DIRA AI does not just say something is wrong. It shows what is wrong, why it matters, who owns it, what happens if nobody acts, what action is recommended, what evidence supports it, and whether approval is required.
DIRA means “compass” in Swahili. Inside Pamoja, DIRA AI acts as the compass for freight operations: helping teams see what is off course, who owns the next move, what evidence matters, and what outcome to pursue.
Pamoja brings every party together. DIRA AI points the operation toward the next right move.
Shipment 884 is blocked because a transit permit is missing.
Untrusted input, low-confidence matches, regulated actions, irreversible actions, and external counterparty messages require the appropriate review, evidence, and authority before action.
Connect the channels.
Reconstruct the operation.
DIRA Connect gives Pamoja its senses. It reads approved sources, then binds what it finds to shipments, documents, counterparties, obligations, exceptions, and evidence. Pamoja starts working before your team changes behavior.
Pamoja starts from the evidence your operation already produces.
DIRA Connect proposes and prepares. Governed workflows decide what changes, what requires review, and what crosses a regulated boundary.
Not document extraction. Operational perception.
Your messages
become operations.
Freight teams already operate through WhatsApp, email, Teams, photos, documents, voice notes, and calls. Pamoja lets those channels feed the operating layer. A message can become a reported fact, a request, a work item, an approval, evidence, a correction, or a controlled action.
Pamoja can understand a message without blindly acting on it. It can route work, ask for clarification, require approval, attach evidence, reject unsupported requests, or take low-risk action when policy allows.
DIRA AI does not just react.
It learns what to improve.
Pamoja does not stop at alerts. When DIRA AI sees a recurring problem, risk, obligation, or opportunity, it can recommend a governed Objective: a business outcome with an owner, plan, success criteria, authority rules, evidence requirements, blockers, recovery steps, and outcome history.
The goal is not more tasks. The goal is fewer recurring failures.
One missing document is a task. Something someone has to do.
The same missing document across ten shipments is a business problem. Pamoja turns that pattern into a governed business outcome: assign ownership, propose a plan, track execution, require evidence, and learn whether the fix worked.
Three shipments delayed this week because certificates arrived late.
Create an Objective to reduce certificate delays for this broker.
Repeated document delay is creating clearance risk and customer update burden.
Twelve shipments on one corridor are losing time at the same crossing.
Create an Objective to identify and reduce the recurring border blocker.
The same issue is now a pattern, not a one-off exception.
Create an Objective to recover the dispatch and prevent repeat failure.
Create an Objective to close the billing evidence gap.
Objective recommendations are explainable. Users can approve, dismiss, edit, or promote them. Sensitive actions still require the right authority and evidence.
Pamoja is built to let DIRA AI recommend governed Objectives from operational patterns, and to learn from verified outcomes: which plans worked, which recoveries failed, and which patterns deserve management attention.
Start where the pain
is sharpest.
Pamoja is a platform, but adoption starts with one workflow: the workflow costing your team the most time, money, or trust.
Once the first workflow creates structured operational data, adjacent workflows become easier to coordinate.
Start with one workflow →Your first 90 days
with Pamoja.
Reconstruct the operation
Connect approved sources, ingest sample records, and identify shipments, documents, counterparties, exceptions, and pain points.
Govern one workflow
Choose one workflow: document readiness, exception ownership, customer updates, dispatch readiness, claims evidence, or corridor reporting.
Prove operating value
Measure missing-document reduction, faster issue assignment, fewer manual updates, cleaner evidence, shorter reconciliation, and better visibility.
Governed action,
not blind automation.
Pamoja can understand a message without automatically changing the business. It separates reported facts from verified facts, shows the evidence behind recommendations, routes sensitive actions for approval, and preserves an audit trail. Safety is a strength, not an apology.
Who is behind Pamoja?
Daniel holds a master’s in Management and Finance from Columbia University and a bachelor’s in Business Administration from the University of Rhode Island.
Pamoja was founded by Daniel D. Miller, an institutional leader and investor who came to African logistics looking for companies worth backing, and found a deeper problem. The businesses moving goods were not short on trucks, ports, customs systems, or software. They were short on coordination. The work between systems, companies, documents, approvals, and handoffs was still held together by WhatsApp, email, spreadsheets, and human memory.
That is the point. Pamoja is not another freight forwarding system, customs platform, terminal system, or dashboard. It is the neutral AI operating layer above them.
As Deputy Executive Director of the New York City Board of Education Retirement System, a public pension system with more than $10 billion in assets, Daniel works at institutional scale. That institutional work gives him a practical lens on governance, risk, capital allocation, and multi-party decision-making. His work in African infrastructure showed him the same coordination gap in physical form.
Pamoja means “together.” DIRA means “compass.” The names carry the product thesis: Pamoja brings every party together, and DIRA AI points the operation toward the next right move.
Start with one
messy workflow.
Bring one lane, one inbox, one WhatsApp export, one document folder, or one shipment sample. Pamoja will show what it can reconstruct, what is missing, what is blocked, and where work is leaking.
In a limited workflow evaluation, Pamoja should show what it can reconstruct, what it cannot yet know, what is missing, and where work is leaking.