Imagine Robots in Business Three Years from Now
Tuesday 6 October — Art of Intelligence · Robots
The table
The case
Subtitle: A fictional leadership case set in 2029. Commercial figures are illustrative planning assumptions, not market benchmarks. The roles described for cotrugli.tech and NEO Chambers are proposed applications. Source: The owner's own case (Dražen Kapusta, 2026-09-13), verbatim — the eight questions are his
The Robots Were Working. The Warehouse Was Waiting.
At 02:17, two mobile robots stopped at the entrance to a shared loading area.
Neither had broken down. Each was following its own fleet manager’s instructions. Both were waiting for space that the other had effectively reserved.
A supervisor cleared the queue manually. Behind it, a palletising cell waited for its next load.
By morning, Elena, operations director of a European logistics group, had three supplier reports. Each explained why its own equipment had behaved correctly.
Her warehouse had still missed its dispatch target.
“We bought automation,” she told the team. “Why are our people spending the night negotiating between machines?”
Across three warehouses, the group operated different generations of robots and software. Elena wanted to start with one site: 24 mobile robots from two suppliers and two automated palletising cells.
She was not asking to replace them. She wanted them to work together.
One Customer, Several Businesses
At a working session convened through cotrugli.tech, Elena brought the night-shift supervisor and her finance manager.
Around them sat representatives of the robot suppliers, a warehouse integrator and an edge computing provider. The proposed cotrugli.tech role was to connect the service workflow and its evidence across these organisations.
The technical team would first assess existing interfaces. Standards such as VDA 5050 already provide a basis for communication between mobile robots and fleet control systems, although integration still requires checking supported capabilities. VDA 5050 itself is not a safety standard. KIT: VDA 5050
The integrator would connect warehouse orders to the coordination service. Suppliers would retain responsibility for their equipment and supported interfaces. Local safety controls would continue to govern safe machine operation.
NEO Chambers would provide an agreed framework for responsibilities, acceptance evidence and escalation if the parties disagreed.
Elena wanted one lead supplier accountable for service delivery.
“I can manage a contract,” she said. “I cannot run your consortium.”
Start with the Queue
The initial proposal included predictive maintenance, energy optimisation, autonomous scheduling and shared learning across all three warehouses.
The night-shift supervisor pointed to a floor plan.
“This crossing. These two queues. Start there.”
The first scope became coordination of transport jobs approaching the shared loading area: dispatch timing, queue priorities and handovers to the palletising cells.
An AI assistant compared incident logs and suggested that one fleet was arriving too early. A technician discovered that the systems’ clocks were misaligned. Part of the apparent sequence was wrong.
The finding changed the work. Before optimising anything, the partners needed reliable timestamps, common location references and a clear account of who had requested each movement.
AI could help analyse patterns and propose improvements. Engineers would validate changes before deployment. Safety functions would remain independent of its recommendations.
A Business Case the Finance Manager Could Challenge
Elena refused to justify the investment using a continental robotics market forecast.
Her finance manager wanted a site-level calculation.
The team proposed a €180,000 initial budget:
| Initial work | Planning allowance |
|---|---|
| Vendor interfaces and warehouse-system integration | €80,000 |
| Local computing, networking and installation | €25,000 |
| Engineering validation, acceptance and operator training | €40,000 |
| Contingency | €35,000 |
| Total | €180,000 |
The estimate assumed existing robots remained in service and suppliers provided usable interfaces. It excluded new robots, substantial building changes and major modifications to safety systems.
Annual operation was provisionally budgeted at €60,000, covering software, infrastructure, monitoring and a defined support arrangement. Dedicated engineers permanently on site would require a different price.
The benefits were equally explicit:
| Potential annual benefit | Assumption |
|---|---|
| Less overtime and temporary labour | 2,000 paid hours avoided × €30 = €60,000 |
| Additional profitable work handled | 60,000 extra movements × €1 contribution = €60,000 |
| Fewer external recovery costs and dispatch penalties | €30,000 |
| Total potential benefit | €150,000 |
After annual operating costs, the base case produced €90,000 a year, implying a simple two-year payback after reaching steady operation.
A conservative case with only €90,000 of gross benefits left €30,000 annually: a six-year payback. Ramp-up delays would extend both.
The finance manager circled the extra movements.
“Do we have customers for these?”
Without demand, capacity was useful headroom—not realised income. Hours released also counted as cash savings only where paid expenditure actually fell. The team would check that the benefit categories did not overlap.
What cotrugli.tech and NEO Chambers Would Add
The warehouse already had software controlling machines. The missing capability was coordinating commitments across suppliers and making delivery understandable.
In the proposed design, cotrugli.tech would connect authorised requests, job status and service records. A transport task could have an identifiable requester, permitted scope and recorded completion or exception.
NEO Chambers would help the parties agree what those records meant commercially.
Suppose a pallet arrived late. Was the loading area unavailable? Had the warehouse changed the priority? Had a provider failed to deliver an agreed service?
The parties would define evidence requirements and a dispute process before those questions became expensive.
A completion record alone would not prove that the pallet was undamaged or contained the correct goods. Those claims would require appropriate checks.
The Chamber process would support agreed commercial resolution. Immediate operational and safety decisions would remain with the responsible warehouse and technical teams.
Trust Had a Practical Job
The cotrugli.tech working group brought together people who had learned, travelled and worked alongside one another through the wider tribe.
That familiarity mattered when a supplier engineer admitted that an interface shown in the proposal was available only as a paid option.
Instead of hiding the issue until installation, the group put it into the cost model.
Later, over food after the site visit, the supervisor described the unofficial workaround her team used during peak periods. Someone joked that the most interoperable component in the warehouse was still her radio.
The humour opened a serious discussion. Their design had assumed a working routine that the night shift no longer followed.
Trust made the actual process visible.
Who Would Carry the Whole?
The integrator offered to lead delivery, provided the robot suppliers committed support and cotrugli.tech’s responsibilities were precisely scoped.
One supplier wanted guaranteed annual fees. Elena preferred part of the payment to depend on measured improvement. The integrator objected to carrying demand risk it could not control.
They also needed an exit plan: exportable records, documented interfaces and an agreed fallback if the coordination service became unavailable.
Elena now had something worth considering: a bounded problem, a costed proposal and partners prepared to discuss responsibility.
She had not yet approved it.
The remaining decision was whether to fund the full implementation or first purchase an integration assessment to resolve the assumptions most likely to break the business case.
The CDayZ Leadership Challenge
Act as the customer and delivery partners. Decide whether to proceed, narrow the scope or fund further discovery. Agree who leads, how costs and benefits will be verified, and where cotrugli.tech and NEO Chambers create value worth paying for.
Discussion Questions
The owner's "Eight Questions for the Room":
- What should Elena buy first?
- Which assumption could break the business case?
- Who is accountable for the complete service?
- What should AI be allowed to influence?
- What evidence makes a robot task commercially complete?
- Where should NEO Chambers intervene?
- How should payment reflect performance?
- What would justify expansion to the other warehouses?
Define an outcome narrow enough to deliver and valuable enough to justify investment.
Examine interfaces, integration effort, demand, support costs and achievable savings.
Give the lead supplier authority and commitments consistent with that responsibility.
Separate analysis and recommendations from validated operational changes and safety functions.
Distinguish movement, delivery, condition and customer acceptance.
Define the boundary between operational recovery, contractual escalation and dispute resolution.
Share controllable risks without making suppliers responsible for customer demand.
Require demonstrated economics, manageable support and evidence that integration can be repeated.
A Lesson for the Next Generation of Builders
The value of robotics grows when machines, people and independent businesses can deliver together.
That requires more than intelligent equipment. It requires a customer outcome, workable economics and clear responsibility when the real warehouse behaves differently from the diagram.
Your comment on this chapter
A question for the table, a disagreement, what you would have done. The case lead reads every comment; the ones the table takes up enter the chapter as questions from the room, with your name.