Our Story

We built the coordination layer we couldn’t find.

After years building warehouse software, designing facilities and deploying automation, our founders kept seeing the same gap: capable systems and equipment, but no simple way to coordinate the work between them. That is why we started Onomatic.

01 / THE EXPERIENCE

We knew the industry. We knew what was missing.

01 / WMS ENGINEERING

Enterprise software expertise

Nicolas and Dimitrios spent years architecting and building warehouse management software. They understood where enterprise systems excelled, and where their boundaries became a problem.

02 / OPERATIONS & DELIVERY

Experience on the warehouse floor

Jean-Martin and his LIDD colleagues designed facilities, implemented WMS and deployed automation. They saw the cost of disconnected processes firsthand. LIDD backed Onomatic from day one.

03 / THE MARKET GAP

The missing coordination layer

An early healthcare project brought it into focus: systems, machines and people could each do their jobs, but coordinating decisions across them was still unnecessarily difficult.

02 / THE FOUNDERS

Built by people who know enterprise operations.

NICOLAS LAPLANTE

Platform architecture

A logistics solution architect who understands how complex systems fit together, and how to make them work as one.

DIMITRIOS TOULOUMIS

Software engineering

An enterprise software engineer focused on making ambitious technology reliable, secure and scalable.

JEAN-MARTIN ROUX

Operations & execution

An industrial engineer who translates real operational challenges into practical software priorities.

03 / WHY WE BUILT IT

Automation evolved. Coordination had to catch up.

THE PROBLEM

Smarter systems did not mean smoother operations.

Warehouses gained powerful software and automation, yet work across those technologies still depended too often on one-off integrations, manual decisions and workarounds.

OUR ANSWER

One layer to coordinate the work.

We built Onomatic to connect systems, equipment and people, so operational signals become coordinated action, across vendors, processes and existing technology.

Onomatic. Software that turns signals into actions.