Airclerk NZ · AU Talk to us →
About

Four people. The ones who do the work.

Airclerk is a small firm. Adam replies to every enquiry and works out with you whether there is a fit. The free introductory conversation that follows is with Dan and the people who would design and build your workflow, and it gives us enough to quote in writing. The same people provide the support written into the scope afterwards. Looking after it beyond that is a separate agreement, if you want one. Based in Christchurch, working across New Zealand and Australia, with select international clients.

01 / The people

Who does what.

Adam replies to every enquiry, works out the fit in both directions and owns the commercial side. Dan leads the introductory conversation, the scope and each engagement from there, and runs the advisory work. Matt and Ed build: Ed leads the detailed design, Matt the workflows and connectors. Nothing is handed to a delivery team you haven't met.

Dan Fowlie, co-founder and CEO of Airclerk.
Co-founder & CEO · Leads engagements and advisory

Dan Fowlie

Leads the introductory conversation, the scope, the engagement and the advisory work, and stays on each engagement as the person accountable for it.

Cofounded and grew Trineo into one of NZ's most successful cloud-platform implementation partners (acquired in 2021), then went on to Senior Director in Salesforce's own Professional Services organisation. Knows the power of a platform ecosystem from both sides, and is now doing the same with Claude, Microsoft Copilot and ChatGPT.

Adam Saywell, co-founder and CRO of Airclerk.
Co-founder & CRO
Commercial and client relationships

Adam Saywell

Replies to every firm that gets in touch, works out whether there is a fit, and owns the commercial relationship from there.

Adam was already at Salesforce in enterprise sales when Dan and Ed arrived in 2022, and they crossed paths on shared accounts - work that put him in front of some of New Zealand's most well-known and regulated organisations. The same regulated-buyer table, seen from the vendor side.

Matt Wratt, Co-founder and Technical Implementation Specialist at Airclerk.
Co-founder & Technical Implementation Specialist
Builds the workflows and connectors

Matt Wratt

Builds the workflows and their connections into client systems, and the controls around them.

Two decades across backend systems, integrations, AI workflows and production engineering. Part of Trineo's bespoke-integrations practice - the team that built the complex custom integrations behind enterprise cloud rollouts when off-the-shelf wasn't enough. Builds the rails that turn an AI demo into something a regulated firm can run on.

Ed Groenendaal, Co-founder and Technical Implementation Specialist at Airclerk.
Co-founder & Technical Implementation Specialist
Architecture and design

Ed Groenendaal

Leads the detailed design that opens each engagement: what the AI should and should not do inside the workflow, and how that is enforced.

Multiple patents, 30+ years building software at the frontier - Trineo-era architecture among them, then Technical Director in Salesforce's own Professional Services organisation until early 2026. The depth that lets us make confident calls about what AI should and shouldn't be doing inside a regulated workflow.

02 / Before Airclerk

What the team did before this.

This is the team's record, not Airclerk's. Airclerk's own client work is newer; the industry pages show illustrative examples of the workflows we build.

Dan, Matt and Ed were part of Trineo, one of New Zealand's most successful cloud-platform implementation partners through the SaaS wave of the late 2000s and 2010s. Trineo was acquired by Traction on Demand in 2021, which Salesforce itself later acquired, the chain that brought Dan and Ed inside Salesforce in 2022, where Adam was already working in enterprise sales.

Between them, Dan, Matt and Ed shipped more than one hundred projects at Trineo, for organisations from 3 staff to 20,000, across insurance, wealth management, retail, agriculture, advertising, sports and more. The lesson that came up on every one of them: the technology is the easy part. What makes an implementation stick is the change around it, who does what differently once the system is live.

At Salesforce, Dan was a Senior Director and Ed a Technical Director in Professional Services; Adam was on the enterprise sales side, and the three crossed paths on shared accounts. Dan left in mid-2023 to build Airclerk full-time; Ed followed at the end of January 2026. Same lesson, seen from the vendor side this time.

03 / How Airclerk started

Built on insurance. Pointed at implementation.

Airclerk began by building AI workflow software for insurance. Through that work we developed practical experience in document-heavy regulated workflows, frontier models, human-in-the-loop processes and auditability. Six months in, it was clear the application layer was about to be absorbed by the frontier platforms, and the product moat for standalone AI wrappers was eroding quickly.

Our conviction is that the opportunity is not to compete with Claude, but to help financial and professional services firms put it to work safely and effectively. That requires industry context, governance discipline, and the ability to build the rails underneath: connectors, MCPs, orchestration, evidence and approvals. That is what Airclerk does now. The story is told in full in why we pivoted to Claude.

04 / What we believe

A handful of strong opinions.

i.

The model becomes the interface.

Forcing users into another portal is a losing strategy. The workbench is the model, whether that is Claude, Microsoft Copilot or ChatGPT, and the principle holds whichever platform wins.

ii.

Implementation moats matter more than wrapper moats.

Integration, governance and trust are the durable layers.

iii.

Production beats demo.

One workflow running safely in production is worth ten polished pilots.

iv.

ANZ deserves a serious local partner.

Local insurers and FS organisations should not be left waiting for a US vendor's roadmap.

Get in touch

Talk to the people who would do the work.

A free introductory conversation is the quickest way to find out whether we are the right people for the piece of work you have in mind. If we are, the fixed fee and timeline follow in writing.

Talk to us →
05 / Common questions

Common questions.

01Who founded Airclerk?

Airclerk was founded by Dan Fowlie (co-founder and CEO), Adam Saywell (co-founder and CRO), and co-founders and technical implementation specialists Matt Wratt and Ed Groenendaal. Dan, Matt and Ed worked together for years at Trineo, one of New Zealand's most successful cloud-platform implementation partners through the SaaS wave, acquired in 2021. Dan and Ed later crossed paths with Adam inside Salesforce itself, on shared accounts - Adam was in enterprise sales, Dan and Ed in Professional Services.

02Is Airclerk's team new to implementing technology in regulated firms?

No. Dan, Matt and Ed shipped more than one hundred projects together at Trineo during the SaaS wave, for organisations from 3 staff to 20,000, across insurance, wealth management, retail and other sectors. Dan and Ed then spent time inside Salesforce's own Professional Services organisation, where they crossed paths with Adam on shared accounts - Adam was in enterprise sales. Two rounds of the same regulated-buyer table, from both the partner and the vendor side, is why Airclerk treats the human side, change management, operating model and governance, as the hard part rather than the technology.

03Does Airclerk only work with insurance companies?

Insurance, meaning brokers, insurers and MGAs, is our strongest practice, and we have active clients in accounting and professional services firms. We also work across regulated financial services, including wealth management and financial advice, and are open to early adopters in banking and lending, where the same disciplines apply.

04Why did Airclerk move from building software to implementing AI platforms?

Airclerk began by building AI workflow software for insurance. Six months in, it was clear the application layer was about to be absorbed by the frontier platforms, so we refocused on the implementation layer beneath them: the workflows, governance and assurance that make Claude stick in a regulated firm.