A business is one connected system
No department experiences the company as departments. Work crosses them all day — software should be built the way the business actually runs.
Follow one order through the company
A customer accepts a quote on Monday morning. By Monday afternoon that single event has committed production capacity, reserved material, triggered a purchase for what is missing, promised a delivery date, scheduled an invoice and nudged the cash flow forecast. One event. Six departments. Before lunch, if the company is any good.
Now count the system borders it crossed. In a standard environment the quote lives in the CRM, the order in the ERP, the production plan in a planning tool, the purchase in a supplier portal, the invoice in the accounting package and the forecast in a spreadsheet. At every border, a human re-enters what the previous system already knew.
The business is one continuous motion. The software is a relay race with a dropped baton at every handover.
Software mirrors vendors, not businesses
Why do the borders sit exactly where they sit? Not because any business process ends there. A package's edge is a vendor's product decision — where their market category stopped, where their acquisition integrated badly, where their pricing tier begins. Buy enough packages and your operation is partitioned along the org charts of companies that have never seen it.
Departments themselves are a filing system for people, not a description of work. Work is cross-functional every single day; only software pretends otherwise, because software was sold per department to whoever held that department's budget.
Integration is not connection
The integration industry exists to answer this objection, so let it: connect everything over APIs and the borders disappear. Except an integration does not create one system — it synchronizes copies. Every copy is a place where the truth can fork. Every sync job is a thing that silently stops one night. Every new tool multiplies the connections that must be built and watched and paid for.
Point-to-point plumbing between fragments produces a fragile mesh that behaves like one system only in the demo. The honest name for it is what everyone calls it the week it breaks: spaghetti.
One graph, many views
Model the business instead. Customer, quote, order, article, machine, purchase, invoice — one connected graph, because that is what the operation is. When the order and the production plan are nodes in the same model, "integration" stops being a project and becomes a non-concept: there is nothing to integrate, only relations to follow.
Departments then return in the only form they ever deserved: as views. Sales looks at the graph from the customer side, production from the capacity side, finance from the cash side. Same truth, different angles.
The business was always one system. Software is finally able to admit it.
The domains one system covers