The engagement: what we actually do

The engagement runs in four moves: land on advisory, embed to build, operate on software, and expand as the client grows. Advisory is how we earn the right to the rest — a senior partner who has done the work, not a recommendations deck — but unlike a consulting firm we don’t stop at the advice, and unlike a software vendor we don’t drop a tool and leave. It is the wedge-to-managed-service motion the best cyber-security firms run: the assessment earns trust and maps the ground; the recurring operated function is the business.

Land: the advisory wedge

We enter on judgment. The sharpest entry point is the moment a regulated scale-up’s compliance load steps up faster than it can hire — a funding round, a licence threshold, a new market-participant obligation — and a senior advisor who has navigated exactly that before is both the cheapest thing to say yes to and the hardest to fake. The advisory engagement does real work (the architecture call, the build-versus-buy decision, the regulatory path) and, in doing it, earns trust and a deep read of the business. That read is what makes the next move possible — and it’s something a frontier model and a delivery-only startup can’t bring.

Embed: build the function

A Client Leader acts as the company’s CIO/CTO: board attendance, technology strategy, build-versus-buy decisions made with the CEO and CFO, accountability to the board. The Engagement Architect designs the architecture from scratch and delivers it — for our beachhead: AEMO market-interface systems, SCADA/OT integration, compliance tooling, ERP configured for project-based asset accounting, contract and investor-reporting systems, security posture and IT governance. Formation-stage technology decisions are load-bearing — expensive to change later and formative for everything built on top — which is exactly why they need executive judgment, not a junior team and a methodology.

One pattern we build in from the start: the agent-over-systems interface. The strongest current Australian enterprise example put an AI agent over SAP so 700 occasional users could query procurement data conversationally inside Teams — live in production 18 weeks from approval. Clients’ systems of record arrive with a natural-language layer over them, so a lean team’s data actually gets used.

Operate: run it on software, not people

This is where the business lives — the recurring, sticky, long-term layer, priced as a subscription to a working function rather than as hours. And it runs on one principle: the operate layer is carried predominantly by software and agents, with the lightest human footprint we can hold. Vendor scans and market intelligence in days; specifications and governance packs produced as systems are designed; compliance obligations and regulatory change tracked continuously; monitoring and alerting from day one of live operation; board packs and investor reporting drafted for senior review. If we ran this layer with people the way a traditional firm does, we’d have rebuilt the Big 4 — same economics, same ceiling.

How light that footprint can genuinely go is the model’s load-bearing question, and we treat it as something to prove, not assert. The first engagement is scoped to turn the principle into a number: take one operating function, run it on agents, and measure it — where senior time actually goes, where AI output needed correction, and at what complexity the quality ceiling appears (sections 8 and 10). The direction is non-negotiable; the degree is what the first engagements exist to establish.

Empowering the client: from how we work to how they work

Capability transfer runs through every engagement, in two moves. First, during delivery, we run the engagement itself on AI in the open — showing the client’s people how we use it, so the way we work becomes the way they work. Then we flip the script: we embed AI into the organisation’s own infrastructure so they can run the business more effectively without us in the loop for everything.

The flagship of that embedded layer is the organisation’s intelligence layer — the same architecture the founders already run day to day, turned around and put inside the client. It puts an organisation’s scattered data, documents and processes in one place and makes them answerable in plain language: a CFO asking “how do our monthly financials look?”; a project lead asking “what’s actually happening on this build?”; a CEO treating strategy as a living document — “here’s our strategy, here’s our procurement process; tell me where we are and what I need to do next.” It is what dashboards always promised and organisations almost never delivered — in effect the “collective intelligence of the institution” that the world’s largest law firm is spending ~$500M to build for itself (section 4), delivered to organisations that could never fund that build. The value isn’t a chatbot bolted on the side — it’s putting the right information in front of the right person, building the processes that keep it true, and doing it to a standard a regulated organisation can actually rely on. That reliability bar is exactly what a bought tool or a DIY attempt doesn’t reach, and it’s why this is a delivered, supported capability rather than a download.

This is also where the relationship compounds and the line holds: the workflows are ours and now run through their operation (stickiness), the client’s own people get more capable (adoption), and at no point is the pitch “replace your staff” — there is no one to replace, only a function being built.

Expand: grow with the client

As the client builds internal capability, the engagement deliberately narrows rather than clinging to scope. Day-to-day operations transfer to the internal team we helped hire, onboard, and train — building our own partial replacement is part of the service, not a threat to it. What stays: the technology roadmap, the major calls (new asset classes, acquisitions, market expansion), vendor and regulator relationships at the senior level, and the AI-powered intelligence layer — market monitoring, regulatory-change tracking, competitive signals — that is cheaper for us to run across many clients than for any one client to replicate. The relationship rides the client’s growth: we land small, below the incumbents’ floor, and grow with them, which is what keeps a guerrilla entry from being a ceiling.

This is the most durable relationship shape in professional services: formed when the client had nothing, deepened by the fact that we designed everything they run on. The switching cost at year three — after we’ve built their systems, embedded their governance, and trained their staff — is not contractual; it’s structural. And it’s the untrainable corner a better model can’t reach: a smarter model still doesn’t hold the licence, sign off on the liability, or own the client’s files and systems.

What we deliberately don’t do

We don’t do bodies-on-seats augmentation, one-off projects that end at a handover, or work where the production layer is physical rather than digital. And we cap embedded engagements per Client Leader rather than stretching the senior layer thin — the model’s economics rest on the quality of senior judgment, and the fastest way to destroy the franchise would be to dilute it. The capacity assumption (six to eight clients per Client Leader) is tested explicitly in the first engagements, with the instrumentation built in to measure it.

← Beachhead: Australian renewable energy Competition and why incumbents can't follow →