Airclerk helps regulated financial and professional services firms in New Zealand and Australia assess, design, build and operate agent-powered workflows. Seven services. One implementation discipline. Most engagements start with the fixed-price Readiness Sprint.
Claude or Microsoft Copilot — you choose. Claude is our default for new builds.
Before building, financial and professional services firms need to know which agent workflows are worth pursuing, what governance is required, and what production blockers need to be resolved.
Build governed agent workflows connected to real systems, documents and teams - not another portal.
Help regulated engineering teams adopt Claude Code safely and productively.
Agents become more valuable when they can safely access the right tools, documents and systems. Claude and Copilot bring a library of Microsoft connectors out of the box, and we build custom MCPs for everything else.
Permission-aware. Audit-logged. Tenancy-respecting.
Scoped to your workflow. Built to your security posture.
A specific use case: MCP apps that let customers quote, renew or check claims from inside their AI assistant. For insurers, MGAs and brokers.
In regulated financial and professional services, governance is not a later phase. It is part of the product.
Production agent workflows need ongoing monitoring, improvement and governance.
Specific insurance and financial-services workflows we take into production. We add more each quarter.
A board-ready agent implementation plan in two weeks.
Most engagements start with the fixed-price Claude Production Readiness Sprint, which runs a pilot autopsy across prior AI work, maps the workflows worth pursuing, scores production-readiness, and produces a board-ready implementation plan in two weeks. From there, firms typically move into workflow implementation, governance and managed operations as workflows go to production.
No. The Claude Strategy & Readiness work is designed for firms that still need to work out which agent workflows are worth pursuing, what governance is required, and what production blockers need to be resolved before building - including reviewing any prior AI work through a pilot autopsy.
Claude or Microsoft Copilot is your choice, and Claude is our default for new builds. Both bring a library of Microsoft connectors out of the box, and for customer-facing use, we also build MCP apps that put an insurer, MGA or broker's quoting, policy and renewal products inside ChatGPT and Claude.
They follow one implementation discipline across seven services - strategy and readiness, workflow implementation, Claude Code enablement, MCPs and integrations, customer-facing MCP apps for insurance, AI governance, and managed operations - so a firm can assess, design, build and operate agent-powered workflows with the same team. Governance and evidence capture are part of the build rather than a later phase.
Out of the box, Claude and Copilot include Microsoft connectors for Microsoft 365 and Entra identity, SharePoint, Outlook and shared mailboxes, Teams and OneDrive - permission-aware, audit-logged and tenancy-respecting. For everything else we build custom MCP servers and connectors for CRMs and broker portals, policy and claims systems, document repositories, and legacy systems, using browser automation where APIs don't exist.