Notes from the delivery floor.

A small breakfast at our Collins Street studio for operations, service and technology leaders. We walk through three deployments in detail, including what the agent got wrong, and leave most of the time for questions.

Places are limited. Register through the contact page and mention the breakfast.

Until recently every AI integration was a one-off. A chatbot for HR got its own connection to the HR system; a sales assistant got another to the CRM. Each one was built, secured and audited separately.

The Model Context Protocol (MCP) is an open standard that turns those one-offs into shared infrastructure. You build an MCP server for a system once, decide what it may read and write, and log every call. Any approved assistant can then use it under the same rules.

For Australian organisations the appeal is governance as much as speed: one place to enforce permissions, one audit trail, and a clean answer when the risk committee asks which AI can see member data.

Shadow mode means the agent does the work on real cases, but nobody sees its output except the people measuring it. We compare its drafts with what your team actually sent.

After a few weeks you know its accuracy by category, not as a single flattering number. Some categories are ready to assist; some never will be. Both are useful findings.

The Essential Eight was written with Windows fleets in mind, but most of it maps neatly onto a cloud platform: application control becomes signed images and admission policies; patching becomes rebuilt images on a schedule; restricting admin privileges becomes just-in-time roles.

We set these up as code in the landing zone, so a new workload inherits them rather than relying on someone remembering.

Clients deal with a delivery lead and an architect in Melbourne. Engineering scale comes from IndiaNIC, our delivery partner, working on the same backlog, in the same tools and under the same access controls.

The overlap between Melbourne mornings and Indian afternoons gives us a daily working window for decisions, and a review cycle that turns work around overnight.

On a remote site the network is intermittent at best. An app that needs a connection to save a form will be abandoned within a week.

Offline-first design means the device is the primary store: every action is saved locally and synced when a link appears, with conflicts resolved by rules the crew can understand.