New playbook: when your own AI model pays. Read

Ondas: ~3 months for post-acquisition integration, the company says

Ondas (drones and autonomy) reported this on 10 Sep 2026 in company self-report (source). It belongs to the data and ontology layer.

What they built

A shared Palantir ontology across post-acquisition systems: policy comparison, finance-ops, CRM, leasing and insurance management.

The result

Post-acquisition integration cycles compressed from a typical 12–24 months to about 3 months.

The number covers self-reported integration timeline; the baseline is an industry 'typical'; Ondas's own history is not reported.

The layer: data and ontology

Shared definitions of your metrics and records, used by both staff and agents.

  • One definition for every metric that matters
  • Linked objects across ERPs, CRM and documents
  • A log of human decisions and their reasons

Read the guide to data and ontology.

Playbooks that use this case

More cases on data and ontology

  • 10 minutes

    to scope a supply shortage, down from 3 months and 30 people

    An enterprise data layer on Palantir Foundry unifying 33 ERPs (~3.5M data connections), feeding a Sector Control Tower for executives and a Program Digital Cockpit for program teams (source).

  • 27 days

    faster time-to-sign for candidates

    A recruiting and hiring agent in Microsoft Copilot Studio, grounded in the Celonis Context Model (process-mining data on how hiring actually flows), used by recruiters and hiring managers (source).

  • 2 months

    for a 1% forecast-error gain that last took a year

    A Genie-based research agent on Databricks that answers finance and store-operations questions about the labour-demand forecast, with explanations, replacing data scientists answering stakeholder emails (source).

We map how your company runs, pick the first processes with your leadership team, and put them on agents.