Start with what changed
Growth, risk, a customer or an opportunity creates the reason to revisit the systems. The event gives the work its commercial test.
Home / Our story
A route planner exposed
a bigger problem.
ORBN began with a focused piece of software. It became a company concerned with a much larger question: who gets to decide how a business can operate?
The first software worked. The operation around it did not.
ORBN started with an order-routing tool for a foodservice wholesaler. The optimisation problem was clear: turn hundreds of orders into practical vehicle routes without rebuilding the plan by hand.
But route efficiency was only part of the constraint. Orders still had to leave one system, cross spreadsheets and return to the operation. ERPs, warehouse tools and commercial records each performed their own role while people carried the truth between them.
That changed our understanding of the product. The valuable capability was not an isolated algorithm. It was the ability to make a distinctive operation work as a whole — and to leave the business in control of how it changed next.
“The system won't allow it” is not a technical answer.
Every system contains decisions about how work should happen. When those decisions belong to a generic product, an old architecture or an unavailable supplier, they can become limits on the company itself.
B/01
Operational knowledge is an asset
The rules, exceptions and judgement behind a dependable operation may be more valuable than another feature or dashboard.
B/02
Building is not always ownership
Real ownership is the ability to understand, run and change the capability. Sometimes buying or integrating creates more control than writing new code.
B/03
Software should increase agency
A useful system makes the next business decision easier to execute. It should not turn today's assumptions into tomorrow's veto.
Operational conviction meets engineering judgement.
01
02
Work with the people who know
The client brings the operating knowledge. We expose the rules and exceptions with the people who exercise them.
03
Prove the difficult part
Small production releases replace confidence in a document with evidence from real work.
04
Leave control behind
Code, infrastructure, documentation and operating knowledge belong with the business expected to depend on them.
The story starts with your business eventWhat changed?
What changed?
What must the operation do next?
Explore the moments that turn a tolerated systems constraint into a commercially important decision.