In regulated financial and professional services, governance is not a later phase. It is part of the product. Airclerk designs the controls, approvals, audit trails, cost controls and operating model required for production Claude workflows.
Critical decisions are reviewed by people. The model proposes, humans dispose - and the system records both.
Claude inherits the user's permissions. No bypassing the existing access model.
The assistant records each step as it works — what the user asked, the tools and systems it used, the evidence it referenced, and the decisions and outputs it produced — with traceable provenance.
Outputs cite their source documents and the reasoning path that produced them.
What Claude can read, write and trigger is defined per workflow, not per organisation.
If we cannot explain why a workflow produced an output, it does not ship to production.
Per-workflow budgets, token and tool-call limits, model-tier routing and usage alerting. Finance sees what AI is costing before the invoice arrives.
The Readiness Sprint includes a full governance and controls model for the recommended first workflow.
Airclerk designs the controls, approvals, audit trails, cost controls and operating model required to run Claude workflows in production. The work resolves eleven questions every workflow must answer — from what Claude can access, recommend and must not do, to when human approval is required, what gets logged, how evidence is captured, how outputs are reviewed, how incidents are handled, and how AI usage is monitored over time.
Airclerk designs governance for firms operating under FSLAA / FAP, CoFI and FMA conduct expectations in New Zealand, and ASIC RG 271, APRA CPS 230 and CPS 234 in Australia, alongside the Privacy Act and the Contracts of Insurance Act 2024. Airclerk helps you evidence these obligations; meeting them remains the firm's responsibility, and Airclerk does not provide legal advice.
Governance defines the controls, approvals and boundaries a workflow must operate within; AI Process Assurance is how that work is made evidenced and provable. The assistant records each step as it works — what was asked, the tools and systems it used, the evidence it referenced, and the decisions and outputs it produced — with traceable provenance, capturing the work that runs through the instrumented workflows rather than claiming to capture everything.
Each workflow gets its own budget, with token and tool-call limits, model-tier routing and usage alerting, so finance can see what AI is costing before the invoice arrives. Cost is treated as a governance question in its own right — every workflow must answer what it costs to run and how that spend is controlled.
The first step is the two-week Claude Production Readiness Sprint, which includes a full governance and controls model for the recommended first workflow. You can also request a governance pack through the contact page if you want to review the framework first.