Brendan Creaser · Claude AI Specialist

Start here

Watch the walkthrough first.

A few minutes to camera: who I am, then a live tour of what I have built. Everything below is the detail behind it.

The pivot

An unusual path to the front of this.

I spent a decade making high-stakes calls where staying calm and correct mattered: intensive care, emergency departments, and the back of an ambulance on the Gold Coast. Then I built and ran the quality function for a national occupational-health group. An integrated management system, from a blank page to ISO 9001, ISO 45001 and NATA accreditation, plus training the staff who run it.

That work put me across the table from tradespeople and industry operators for years. Pre-employment and industry medicals are the trades world. I know how these businesses think, and I know how to explain something technical to someone who does not care about the technology, only whether it works on Monday.

For the last two years I have gone all in on AI. Not dabbling, building. I designed and shipped a production, multi-surface AI platform solo, wrote the internal tooling around it, built the orchestration systems that run fleets of Claude agents in parallel, and automated a service business so completely that it runs on about an hour of my time a week. Claude Code is my primary development environment, every day. In production I route each model call to whatever does the job best, Claude, Gemini or OpenAI, connected through MCP where it helps.

“We are not looking for someone who has played with ChatGPT and read some newsletters. We are looking for someone at the front of this.”

From the job ad. No CS degree required, no enterprise background, and “already building with Claude at night.” That is the last two years of my life.

Education

Clinical training, then self-taught.

Monash University · 2009–2012

Bachelor of Nursing & Emergency Health (Paramedic)

A dual-registration degree in nursing and paramedicine. The foundation for a decade of high-acuity, time-critical clinical decision-making.

Monash University · Selective

Ancora Imparo Leadership Program

One of 40 selected from 400 applicants for a 12-month leadership program developing aspiring leaders. Ancora imparo: still, I am learning.

Professional background

A decade of high-stakes work.

Every role built the exact muscles this contract needs: systems, judgment, teaching, and commercial sense.

2021 – present

Founder & Photographer · Brendan Creaser Photography

My own business, full time. Documentary wedding photography across the Mornington Peninsula, more than 200 weddings, along with the brand, the website, and the booking and automation behind it.

For this role: commercial acumen, and I build the websites and automation my own businesses run on.

2019 – 2021

Registered Nurse & Case Manager · Medibank Private

Telephone triage for Nurse on Call, then case manager for COVID contact tracing: high-volume casework and clear communication with the public through a national health response.

For this role: calm process and clear communication at scale, working through systems and data under pressure.

2016 – 2019

Quality Manager & Occupational Health Nurse · Company Medical Services

Built an integrated management system from scratch and drove the group to ISO 9001, ISO 45001 and NATA accreditation for internal drug testing. Owned document control, audits, equipment and legal compliance, advised senior management, and trained nursing and medical staff across Victoria and interstate.

For this role: I build systems that pass audits, train the people who run them, and sit across from trade and industry operators for a living.

2013 – 2017

Emergency, Intensive Care & Paramedic practice · Peninsula, Maroondah & Queensland Ambulance

High-acuity emergency departments, a public intensive care unit, and frontline paramedicine on the Gold Coast. Deteriorating patients, cardiac arrest, trauma and complex care within multidisciplinary teams.

For this role: calm, correct decisions under pressure, and triage instinct: the highest-value fix first, not the most interesting one.

Leadership

From leading people to leading a team that never sleeps.

Elected · Eastern Health

Chairman, Graduate Nurse Committee

Elected by peers to chair the committee easing new graduates into the workplace. The same “bring people on the journey, build capability” mandate this role describes.

Now · Daily practice

Orchestrating agent fleets

Today I lead differently. I run a CTO-style model directing multiple Claude agents in parallel, with review gates and a shared source of truth. Leadership, applied to software.

Built with Claude

Real tools, used. Not proofs of concept.

The ad asks for one rough, real tool over ten certificates. The walkthrough up top is me showing you the app, live. Here is what sits underneath it, and the thing most people do not have: the system I use to build faster than one person should be able to.

Flagship · solo-built product

Tention

A production, AI-native platform I designed and built solo across three surfaces: a native iOS app, a web app, and a backend engine that runs the AI. It takes people from a prompt to finished, on-brand content, with generation driven by Claude, Gemini and OpenAI, each used where it fits, and background pipelines throughout. Built to real production standards: auth, billing, observability, CI, and app-store delivery. It is the app I walk through in the video above.

Claude / SonnetGeminiOpenAIMCPReact Native, Expo, EASNext.js, VercelPostgresInngest pipelinesClerk authRemotion

Internal tooling

The tools around the product

Browser-based analysis apps, reporting and reconciliation utilities, batch-comparison tools and workflow automations. The same category of internal tool this role is about, on the same kind of stack.

HTML / React toolsREST integrationsPostgres / SQLStructured outputs

The differentiator

Orchestration, in Notion & Linear

The system I am most excited to teach: how I run Claude agents like a team. Work tracked in Linear, knowledge and process in Notion, agents wired in through MCP. Full walkthrough below.

Agentic workflowsLinear MCPNotion MCPCLAUDE.md

A business that runs itself

The back office, automated. I built it for my own business.

You give tradies their back office so they can get back to why they started. Bohemia Bay Studio is a self-access photography studio I built to run without me. Clients see live availability, book and pay online, and get a door code the day before. Rescheduling is self-serve, access is automated, and it trades 7am to midnight, 365 days a year, with no staff on site. My input is about an hour a week.

Automated service business

Bohemia Bay Studio

Book, shoot, go. Live booking calendar, online payment, automated access codes, and zero-fee self-serve rescheduling, all running unattended. It is the same outcome ElementX sells to trade operators: the back office handled, so the owner gets their time back. I have already built and run it end to end.

~1 hr / week to runLive booking + paymentAutomated door accessSelf-serve reschedulingNo staff on site

Open the live booking system

Where this plugs into your six Elements

You organise the back office into six Elements. Here is where AI and automation earn their place in each one, on your Simpro and Xero stack. Illustrative, not a fixed plan.

Admin

Job data flowing out of Simpro into clean dashboards, with no manual re-keying.

Finance & Payroll

Reconciliation and payroll checks that match Xero against the job, automatically.

People & Compliance

Inductions and compliance paperwork that assemble and check themselves.

Advisory

Live WIP, margin and cash-flow views an advisor can actually trust.

Marketing

Job write-ups, client comms and social content, drafted by AI in the brand voice.

Reception

A first-response layer that answers, books and triages before a human steps in.

Portfolio↗

Brendan Creaser Photography

200+ weddings, documentary style. My creative eye and brand craft, and I built the site.

Instagram↗

@brendan__creaser

Where I share building an online presence, and how I use AI to do it. Worth a look for the education side of this role.

LinkedIn↗

in/brendan-creaser

The professional trail, from clinical practice to building with AI.

Orchestration

One operator, a team of agents.

In parallel, with gates so nothing ships unreviewed. This is the part I am most excited to teach.

how the work flowsone operator, many agents

CTO

Operator (me)

Scopes work, sets the standard, owns the gate

agent·1

building

agent·2

in review

agent·3

merged

✓

Review gate

An independent check before anything merges

⋮

Tracked in Linear & Notion

Every unit of work has a ticket and a paper trail

activity · recent

09:41agent·3opened worktree, feature branch

09:41linearticket moved to In Progress

09:42agent·1wrote tests, 14 passing

09:43agent·2review gate, approved

09:43agent·2merged to main ✓

09:44notionspec updated, decision logged

09:45agent·3pulled records via MCP

09:46operatorscoped next build by value

CC Claude Code, daily

Primary dev environment, every day
Context management and CLAUDE.md memory
Custom skills and slash commands
Multi-agent, worktree-isolated workflows

API LLM calls in production

Claude for the work that needs it
Gemini and OpenAI where they fit the job
Tool use and structured outputs
Prompt design, caching and batching

MCP MCP servers

Building and configuring MCP servers
Linear, Notion and other connections where they help
Wiring agents and models into real tools safely

DATA Data and pipelines

Postgres, SQL, schema and migrations
Background jobs and ETL-style pipelines
Reconciliation and batch comparison logic
CSV wrangling

WEB Modern web

React and browser-based HTML tools
Next.js on Vercel, a Netlify equivalent
Postgres backends, a Supabase equivalent
Auth, billing and observability

API+ Third-party integration

REST integration across the stack
New job-management and accounting APIs, picked up fast
Simpro and Xero: new to me, squarely in my lane

Fit for the brief

Audited against your brief.

You asked candidates to be honest against the list. Here it is, line by line. Expand any row.

CONFORM·ITY
MATRIX

Building conformance matrices was literally my old day job, so I turned your requirements into one. Tap a row for the evidence.

It is my primary development environment, used every day. I do not just use Claude Code, I run multiple agents in parallel through it, with CLAUDE.md memory, custom skills and commands, and worktree isolation. That is the orchestration system above.

My platform calls the API in production. Structured outputs and tool use feed real pipelines, prompts are designed and versioned for reliability, and model and caching choices are made against cost and latency.

A full solo-built product (Tention), the internal tooling around it, my orchestration system, and an automated business, all shown above. Real tools, used, not proofs of concept.

I integrate third-party REST APIs across my stack: auth, billing, background jobs and data services. Simpro and Xero are new to me by name, but they are exactly the kind of API I wire up regularly, and I will be productive on them quickly.

I trained nursing and medical staff for years, chaired a committee onboarding new graduates, and worked in occupational health. Explaining technical things to non-technical trade and industry people is what I did all day. Teaching without jargon or condescension is a core skill, not a stretch.

I build and configure MCP servers to wire agents into real tools, Linear and Notion among them, which is the backbone of how I orchestrate work.

A Postgres-backed production system with real schema and migrations, background pipelines moving and reconciling data, and plenty of CSV wrangling. Reporting and reconciliation tooling is squarely in scope.

React and browser-based HTML tools, Next.js deployed on Vercel (a Netlify equivalent), and Postgres backends (a Supabase equivalent). Your stack is familiar territory.

I managed a quality function inside a commercial group, ran my own businesses end to end, and built a monetised product. I scope against the value, a 200k admin saving, rather than the technical interest.

Years of occupational-health medicals put me across the table from tradespeople and industry operators, and I have run an SME myself. I already speak this world, so I will not need to be dragged into the room.

Based in Victoria with full work rights, set up to work remotely, and happy to travel to the Sunshine Coast for the periodic in-the-room time the education side needs. The face time matters, and I will show up for it.

First few weeks

This is genuinely what I would do.

The first weeks are about laying a foundation that makes everything after it faster. We ship real tools from the start, prioritised together on our daily calls.

01

Get wired in

Get access to ElementX systems and stack, meet the founder and team, and plug in my review agents so everything we build is checked from day one. Understand the half-built prototypes already in flight.

02

Align on how we build agents

Walk through the process I use to create agents, review the agents ElementX already runs and suggest ways to strengthen them, then write custom instructions and processes tailored to how ElementX works.

03

Stand up the orchestration backbone

Set up Linear and Notion, or whatever management software ElementX already uses, to track and manage the work. Build the systems and flows to test, orchestrate, build and deploy, for both new tools and the products already running.

04

Stay in close contact

Regular check-ins, likely daily calls in the early stages, to set priorities together and share what I am finding. Fast decisions, no layers, exactly as the role describes.

05

Review the security and the tech stack

Review the current tech stack, access, secrets and what is exposed, surface any vulnerabilities, and agree the security posture ElementX actually wants. Wiring AI into Simpro, Xero and financial data raises the stakes, so it is worth doing early. I have already made a start, there is a note below.

Then we ramp

From there, shipping and educating: delivering world-class AI solutions for ElementX and its clients.

Security note

Something I noticed on your site.

Shared only with you. The kind of thing I would catch, and quietly fix, on day one.

Field note

While I was reading your site, I pointed my review agents at it. Within a couple of minutes they flagged something on your pricing page. The 20% discount is decided in the browser: the code LEGACY sits in plain JavaScript that anyone can open and read, and because the calculation runs client-side, the discount can be switched on straight from the console without the code at all.

function applyCode(){
  const v = (codeInput.value||'').trim().toUpperCase();
  if (v === 'LEGACY') { legacy = true; entrow.classList.add('show'); renderCalc(); }
  else { /* INVALID CODE */ }
}

It is a small thing and an easy fix. I mention it for one reason only: this is exactly the kind of issue a proper look at your security and current tech stack surfaces fast, and catching it before it costs you is part of the job. Which is why reviewing the stack, and agreeing the security posture you actually want, is one of the first things I would do.

Let us build the most AI-capable trade business in the country.

That is the brief, and I am in. I would give your admin team superpowers and help your operators get back to why they started. I am already building with Claude every night, so I am happy to jump on a call and show you any of it live.

Emailbrendancreaser@gmail.com LinkedInin/brendan-creaser Instagram@brendan__creaser Cardone-page PDF

One operator.A fleet of agents.Production, daily.