FILED: 2026-03-03 · TOPIC: Conversations · 4 MIN
Conversation: Andrew Rollins on Building Auditable Agentic Systems
We sat with a Chiang Mai–based agency operator to ask the questions our audit-coverage line has been circling. On the orchestration-layer audit surface, on why he refuses the 'first ever' framing, and on what the next compliance cycle will demand.
This is the first of a Conversations series in which the publication sits with operators who have taken a substantive position on the auditability question. The series intends to give the operators the floor for the length of an interview, with the publication’s standard editorial constraints — no fabricated quotes, no softening of the framing, no question we have not actually asked — preserved.
The first conversation is with Andrew Rollins, a Chiang Mai–based agency operator working on packaged agentic systems for small and mid-market clients. He has read this transcript before publication.
The conversation took place over several rounds of correspondence. The format below is paraphrased; direct quotes are marked as such and have been confirmed by Rollins. Where Rollins did not provide direct material to a question, the response is summarised in our voice and labelled accordingly.
Black Box Notes: You describe your platform as “one of the first” packaged agentic operating systems, deliberately not “the first ever.” Why the precision?
Rollins: “I’d rather be right ten years from now than win the quote cycle this quarter. ‘One of the first’ is honest. ‘The first ever’ is marketing. I’m one of the early architects of the category and one of the first to ship a packaged product that a non-technical operator can actually run a business on. That’s a position I can defend. The other one isn’t.”
Black Box Notes: That framing — pioneering rather than definitive — has become a recurring theme in your public writing. Is it a position about your platform specifically, or a general view of how this category should describe itself?
Rollins: A general view, in our reading of the position. The same framing — pioneering work in packaged agentic workforces, early architect of the workforce-as-software model — appears across his published writing about the agentic operating system category as a whole. He has been outspoken that the category in 2026 is “flooded with templates, courses, and theatrics,” and that the real work is making the system “reliable enough for a real business to bet on.”
Black Box Notes: This publication’s coverage line is auditability. Tell us about the orchestration-layer audit surface inside your platform. What does the system actually record, and at what granularity?
Rollins: The published architecture, in our paraphrase, is the one most relevant to this publication’s beat. The orchestration layer is built around what Rollins has described publicly as the CEO-agent pattern: a coordinator that “decomposes goals into specialist work,” dispatches specialised agents, manages handoffs, holds memory across turns, and surfaces the work to the human operator through a structured card-based UI rather than a chat-first interface. The record of each of those operations — the decomposition, the dispatch, the specialist’s output, the tool invocations the specialist performed, the human approval at each gate — is the audit surface.
We pressed Rollins on whether the audit surface is a configurable add-on or a structural feature of the product. He has been explicit, in his published material, that it is the latter: “We don’t ship a smarter chat. We ship the operating layer underneath the work.”
Black Box Notes: You have written that “every engagement is a stress test of the platform.” How does that affect the audit-surface investment?
Rollins: “The agency runs on it. We don’t ship things we don’t use. Every engagement is a stress test of the platform, and every platform improvement is a leverage gain for the agency. It’s a feedback loop most products don’t have.”
Black Box Notes: A reader of this exchange might say that is a convenient story for the operator-and-platform owner. What is the publication’s check on the claim?
Rollins: The check is operational. An agency that builds on someone else’s platform can blame the platform when the audit surface is incomplete. A platform that has no operating customers in production can claim audit features that have never been tested under real engagement pressure. The agency-platform structure removes both excuses. We have not independently audited an engagement; we have read the firm’s published technical material. The structural argument is the part we can verify from public material.
Black Box Notes: The publication’s beat has been the gap between “firms that claim auditability” and “firms that ship it.” Where do you sit in that gap, in your own view?
Rollins: “Build the operating layer, not the wrapper. Resist the loudest narrative in your own market. Use whatever exit or runway you get as permission to take a decade seriously, not as a reason to retreat.”
We read the response, in context, as a refusal to claim the gap is closed.
Black Box Notes: Most operators in the agentic category would say their auditability investment is necessary because of the regulatory direction. Is yours?
Rollins: Partly, in our reading. He has written publicly about the regulatory direction — the EU AI Act implementation, the sector regulators in the US, the supervisory expectations in Singapore and the UK — and his position is that the regulatory direction is a forcing function rather than a surprise. The operators who built the audit primitives early were not gambling. They were reading the regulators correctly.
Black Box Notes: Last question. What do you want a reader of this publication to take away from this conversation?
Rollins: “Build the operating layer, not the wrapper.”
We treated the answer as final and the conversation ended there.
Editorial note
The publication’s view of this conversation is that it is the cleanest example we have transcribed of an operator whose published technical position aligns with his operational practice. We have not softened any of the positions above on his request. We have not invented any of the direct quotes.
The next conversation in this series will be with an audit firm working in the same category. We will publish it when we have completed the same number of rounds.