# Disconnected systems are an operating model, not an IT issue

> Why fragmented software forces people to become the integration — and how OnDraft drafts a connected operating system around the business instead.

Published: 2026-08-20
Author: Dan Cluderay

If your team copies data between Xero, the warehouse, the shop and a courier portal, you do not have a software shortage. You have an operating system that was never designed.

Most businesses did not choose to be fragmented. They bought a ledger, then a shop, then a warehouse tool, then a courier account. Each purchase solved a local problem. Together they created a new job: human middleware.

That job does not show up on an org chart. It shows up as rekeying orders, asking “has this been paid?”, rebuilding a spreadsheet every Monday, and a handful of people who cannot take holiday because the systems only meet inside their heads.

IT projects often try to fix this by adding another platform. OnDraft starts somewhere else: understand how the business actually operates, map the systems and decisions, connect the data, then introduce intelligence that can act.

The visual on our homepage is the whole argument. On the left, independent boxes with tangled dashed lines. On the right, the same boxes in order, with Bud in the middle. Mess to system. That is the work.

If you want a concrete instance, read how Xero payments reach Logistaas without rekeying. It is a small flow with adult engineering — enrich, duplicate check, idempotent write, recorded run — and it is the pattern we apply to larger operating-system work.


## FAQs

### Isn’t this just integration work?

Integrations are necessary but not sufficient. Without process design you connect the wrong events. Without an AI employee you still need people to interpret what the connected data means.