Illustrative AI-generated photograph of a plant-hire supervisor and technician inspecting an excavator at an equipment yard.

Case study / Plant hire

Investigating plant-hire equipment availability issue.

A Business Brain connected rental records, workshop boards and team knowledge to investigate delays between equipment returning and being ready for the next customer.

Assessment context

550
individually tracked equipment items across two branches
17.5%
calculated utilization for 354 items, January–July 2026
≈R35.1m
recorded asset acquisition cost
64
payroll-listed employees across two branches as at July 2026

The owner identified the workshop as the business’s biggest operational challenge and asked us to help identify where AI could help. Equipment was returning from hire and spending too long out of service before it could be hired again.

The engagement team reports that additional equipment was being purchased to cover availability gaps. That added assets needing servicing and repair without first resolving the workshop bottleneck.

A customer promise crosses the whole operation

  1. Enquiry
  2. Check readiness
  3. Resolve blockers
  4. Confirm release
  5. Dispatch
Recorded equipment status must match the physical status of each machine that can be promised for hire.
Could the business fulfil more hires by getting the equipment it already owned ready sooner?

Bring the operating picture together.

Knowledge was spread across rental-management software, Google spreadsheets, staff conversations and WhatsApp groups. Over a few days, an initial Business Brain brought selected records and operational knowledge into a searchable, structured body of information.

  • Connect the sources.

    ERP exports, working spreadsheets refreshed through a service-account connection, interview notes and selected coordination messages.

  • Understand the existing tools.

    Software help documentation and transcribed tutorials were reviewed alongside a vendor walkthrough. This helped identify an underused service-scheduling feature.

  • Keep the evidence checkable.

    Records linked equipment, jobs, requests, dates and process notes. Original source material remained available so system states could be compared with staff accounts.

AI helped trace processes, connect information and develop findings across those sources. Dashboards made the patterns easier to explore with the team. A recorded status or completion mark still needed to be checked against what it meant in practice.

The missing connections were operational.

Low utilisation

ERPSpreadsheetsWhatsAppmessagesTeam knowledgeBusinessBrainAgent analysisLow utilisation ERPSpreadsheetsWhatsAppmessagesTeam knowledgeBusinessBrainAgent analysisLow utilisation
Flagged during the AI opportunity assessment.354 equipment records · January–July 2026
  • Low utilisation needed an explanation.

    The assessment calculated 17.5% utilisation across 354 equipment records for January–July 2026. Time off hire did not, by itself, show whether equipment was waiting for repairs, held up by parts or simply not in demand. We connected rental records, workshop boards and team knowledge to investigate where the return-to-rehire process was stalling.

  • “Available” did not always mean ready to hire.

    Software status, service condition and physical readiness did not combine into one dependable view. A return configuration could mark an item available without an inspection step.

  • Servicing and parts were out of step.

    Service-scheduling tools existed but were underused. The team reports that spares were often ordered only when servicing became due, leaving equipment waiting for parts.

  • Unfulfilled demand was hard to follow.

    Enquiry records did not reliably show whether requests became hires, were fulfilled with substitutes, remained open or were genuinely lost.

  • Workshop priorities did not consistently reflect the work.

    Job age, repair effort, parts readiness and customer demand were not consistently considered together. Smaller repairs could wait behind larger jobs.

  • Missed inspections had no dependable catch-up step.

    If urgent work displaced a three-week inspection slot, equipment could wait until the next cycle, extending an interval to as much as six weeks.

One request traced to the constraint

1
walk-in request
3
units awaiting repair
~3 months
discovered to be waiting
The engagement team discovered three powerfloats awaiting repair and an approximately three-month wait.

The recorded gap

Backlog items entering the board1.71×
Items marked as completed1.00×

Site A board, 21 Feb–15 Aug 2026.

The missed-slot effect

  1. Week 0Inspected
  2. Week 3Slot missed
  3. Week 6Next slot

Six-week gap if no catch-up happens sooner.

Recorded workshop flow and the potential effect of a missed inspection.

At Site A, spreadsheet boards recorded 1.71 times as many work episodes entering the board as receiving a green completion mark between 21 February and 15 August 2026.

Four connected changes before a wider AI rollout.

  • Make servicing happen on time.

    Use the existing scheduling capability, keep relevant readings current and make responsibility for completing due work clear.

  • Prepare parts before they are needed.

    Connect upcoming services with parts requirements, stock records and early reorder decisions.

  • Capture and follow up unfulfilled demand.

    Record the request, required date, reason it could not be supplied, substitute offered and eventual outcome.

  • Keep workshop work moving.

    Review blockers and priorities daily, protect capacity for older and quick jobs, recover missed inspections and clarify the approval path for parts.

Potential AI assistance includes interpreting service-parts descriptions, structuring enquiry notes, summarising conflicting readiness information and preparing explained repair priorities for staff review. These remain proposals. Repair priorities, purchasing and equipment release remain human responsibilities.

The recommendations use ordinary software for schedules, stock calculations, reminders and fixed rules. AI is considered where interpreting varied information or assembling context offers a clear advantage.

Implement a focused change. Measure the business result.

The engagement team reports that service schedules are being integrated into the existing software using a capability that had previously been underused. The engagement remains in progress and implementation is ongoing.

Provisional AI readiness

29–44 / 100Level 2 of 5 · Building foundations
Assessment dated 4 October 2026

Maturity path

  1. Level 1Reactive0–<20
  2. Level 2Building foundations20–<50Current
  3. Level 3Prepared for a supervised pilot50–<70
  4. Level 4Controlled use70–<85
  5. Level 5Ready to scale85–100

Readiness profile

Data reliability1 / 4
Process reliability1 / 4
Systems & access2 / 4
People & ownership2 / 4
Measurement1 / 4

The proposed first trial would track fulfilled requests, confirmed bookings, coordination time, causes of waiting and compliance with service and readiness checks. Any AI-assisted prioritisation should be compared with a simple priority rule before deciding whether it adds value.

About this study

Based on the company’s Plant-Hire Transformation Assessment, dated 4 October 2026. Periods differ by source and are stated beside the relevant figures. Client and branch identities remain anonymised.

Start with one useful workflow

Where does your
work get stuck?

Bring the systems, information and handoffs that need to work together. We’ll help you find a focused first step.

Discuss your workflow info@kadoagents.com