Back to stories

Automation

A supplier process that understands its own rules.

Multi-entity operations companyMarch 2026
Distributed team celebrating a launch together at the desk

Supplier onboarding required coordination across procurement, finance, compliance, legal and operational systems, with rules that changed by supplier type, risk and contract conditions. Orgni made the organisation behind the workflow understandable, and that is what made the automation reliable.

A fragmented operation

Every new supplier started the same way: a procurement manager chasing forms, a compliance team waiting on documents, an IT team waiting on both before provisioning access. The rules were real but scattered - some in policy documents, some in legal's inbox, many in the heads of whoever had onboarded a similar supplier before.

Average onboarding took three to four weeks - not because anything was complicated, but because every handoff was manual, every team had its own queue, and no system understood why a given step was required for a given supplier.

Building the organisational model

We built the onboarding process on Orgni, but the starting point was not a workflow diagram. It was connecting the organisation behind the workflow into one operational model:

  • Roles. Who in procurement, finance, compliance, legal and IT is responsible at each step.
  • Policies and rules. Which requirements apply by supplier type, risk level and contract conditions.
  • Evidence and approvals. Which documents count, who signs off, and what has already been collected.
  • System states and exceptions. Where each supplier stands, and how unusual cases were handled before.

What became possible

Because the process understands its own rules, intelligent systems can determine what is required for each supplier, explain why it is required, and route unusual cases to the correct people. Intake, verification checks, approval routing and IT provisioning run end to end, with every step logged and every handoff timestamped.

People only show up to make decisions - and when they do, the context for the decision is already assembled.

The numbers

3 wks → 3 days

Average onboarding time

0

Manual handoffs between teams

50%+

Coordination overhead removed

Understanding that compounds

Onboardings finish in days, not weeks. Compliance sign-off rates improved too, because documents are collected and reviewed systematically rather than chased over email. And every unusual case that gets routed and resolved teaches the model something new about how the organisation actually works.

The same organisational understanding has since been reused for contractor onboarding - a parallel process with similar friction and similar results. The outcome was not another isolated automation. It was reusable organisational understanding that could support future teams, systems and agents.

"It used to feel like herding cats. Now the whole thing just moves on its own. People approve when they need to approve, and everything else happens automatically."- Head of Procurement, operations company

Have a workflow that needs automating?

Let's map it out and scope a pilot together.

Start a conversation