What does Kadmoon do?

We are a US analytics firm focused entirely on foreign trade. We turn the data buried in your customs, logistics, and ERP systems into decisions: landed cost and margin, duty and tariff exposure, shipment visibility and OTIF, customs and compliance analytics, inventory, and an executive control tower. Everything is built on a governed model, delivered on the Microsoft stack, and lives in your own tenant.

Do we have to be a Microsoft shop?

No. Your data can live anywhere: SAP, Oracle, NetSuite, Microsoft Dynamics, broker and carrier systems, EDI and ACE, or spreadsheets. We read from the system of record wherever it runs. We deliver the analytics on the Microsoft stack, Fabric, Power BI, and Azure, because it is a strong, governed place to build, but the platform is the how, not the point.

Why only foreign trade?

Because trade analytics fails when it is built by people who do not know trade. Landed cost, duty, incoterms, bonded inventory, HTS classification, denied-party screening, and ACE are not edge cases to us, they are the metrics we model every day. That focus is why we arrive with the trade data model and KPIs ready instead of learning your business on your budget.

Where does the data come from?

From the systems you already run. We land raw data in your tenant, shape it into a governed semantic model, and feed the dashboards from there. Carrier EDI and customs messages are parsed into structured events, so milestones, exceptions, and filings become data you can measure instead of documents you have to read. The data integration doc goes into detail.

How does a project start?

Usually with a trade data assessment: a short, fixed-scope engagement that maps your decisions and data and delivers first dashboards in about two weeks. It de-risks the larger build and produces a scope and a quote grounded in your real data. You leave with working analytics, not a slide deck.

Do you build software too?

Yes, and it grows out of the analytics. Living in a client’s trade data is where our software starts: once we understand the operation, we build the systems that run it, customs filing, trade ERP, inventory, and security vision. Analytics is what we lead with and deliver today; the software is what we build as the relationship deepens.

Do we own the analytics and the data?

Yes. Everything we build is yours: the semantic model, the reports, and the data, all inside your own tenant, with documentation and a full handover. Access is provisioned per engagement against your identity provider and policies. We support and evolve it on a defined agreement after launch, but you are never locked in or dependent on us to keep operating.

Which regions and company sizes do you serve?

We are a US firm serving American importers, exporters, brokers, forwarders, 3PLs, ports, and the manufacturers and distributors that trade across borders. We work with growing operations and established enterprises alike; the common thread is that moving goods across borders is central to the business and the numbers have to be right.

Methodology | Docs

We start from the decision a leader needs to make, not from the tool. Every engagement follows the same arc: understand the questions, build the foundation, deliver in short cycles, and sustain what ships. This page describes that arc.

The operating principle

Analytics earns its keep when it changes a decision. So we begin by naming the decisions: what a buyer, a controller, or an operations lead needs to see, how often, and what they will do differently once they see it. Everything downstream, the data model and the reports, serves those decisions.

The four phases

A typical engagement moves through four phases. The first two are short on purpose, so the operation sees working analytics early rather than waiting on a long data project with nothing to show.

Discovery. We map the decisions, the questions behind them, the source systems, and the owner of each number. Output: a diagnosis and an architecture plan.
Foundation. We build the right data foundation for your volume and the semantic layer that gives one definition per KPI. Output: the data model and first indicators.
Build. We deliver in short cycles, validating each report with the area that uses it. Output: governed dashboards in production.
Sustain. We train users, measure real usage, and keep the analytics current as rules, partners, and data change. Output: an evolution roadmap and a support agreement.

One definition per KPI

The most common failure in trade reporting is three versions of the same number in one meeting. We build a governed semantic layer so landed cost, margin, OTIF, and duty exposure each mean one thing across every report. Definitions are documented and owned, not rebuilt per analyst.

Acceptance and ownership

Every deliverable has acceptance criteria agreed before the build, so you know what ships, when, and how to validate it. Everything is built in your own tenant and handed over with documentation, so the analytics is yours to run with or without us.