AI Operations Engineer
Moneta Group
- Operate and improve AI workflows inside a wealth management firm.
- Focus on systems people actually use, not pilots that die in a slide deck.
Press Enter or click to continue
$ whoami
AI Operations Engineer
I put AI into the work you already do
Zac Montague builds the thing and leaves it running, or sits with your people until they can run it themselves. Most clients want some of both.
Working with companies through Vadrel
Terminal below. Try help, neofetch, or cd experience. Press ` to focus.
identity.img verified
Zac Montague is an AI operations engineer in the St. Louis area. He puts AI into work companies already do: records, follow-up, the stuff that lives in email and spreadsheets. Client work goes through Vadrel. Before that he was an SRE at Avast and a cloud engineer at Saint Louis University, including the medical school.
He spent years in production operations, where automated systems fail under load and someone has to decide when a human takes over. That is the same problem as putting AI into a real company.
Today he builds and teaches those systems. Not strategy decks. Something in production.
Production operations, governed automation, and security review since 2019, with a current focus on AI workflow governance.
Moneta Group
Avast (Gen Digital)
Saint Louis University School of Medicine
Saint Louis University
Nomad Cybersecurity Group Ltd
Records, follow-up, intake, the messy stuff in email and spreadsheets. Built into the workflow, not parked in a chatbot nobody opens.
I leave you a running system, or I sit with your people until they can run it. Most engagements are some of both.
Kubernetes, observability, incident automation, and infrastructure that survives audits and outages. Same habits, now applied to AI.
Gates before anything customer-facing. Escalation by severity. Automation that knows when to stop.
A governed intake pipeline, not a demo chatbot
Customer success teams get escalations, bugs, billing fights, and churn signals by email. Manual triage is slow. Blind automation sends the wrong reply.
Each inbound email becomes one Slack thread. Workers classify severity and account context. Nothing customer-facing goes out without a human and an explicit reply marker.
Shared state: one Slack thread per inbound email. Click a step to expand.
Escalations, bugs, billing disputes, and churn signals arrive by email. Each message is one unit of work.
Pulls the email in, classifies it, posts a Slack summary, and writes structured fields to the table.
One Slack thread per email. The table holds fields agents and people update. All processing stays in the thread.
Workers tag severity and route by account tier. Billing, churn, and escalations are flagged for human review.
No customer-facing reply leaves without a person. High-risk categories never get an autonomous path.
External replies require an explicit marker. Unmarked messages stay internal.
Architecture walkthrough and sanitized flow demo available on request.
Gmail to Slack and a table. Classifies issue type, posts a summary, stores thread ID, customer email, account tier, and category.
Tags and escalates by severity and account tier. Flags billing, churn, and escalations for mandatory human review.
Deterministic severity scoring from structured fields: account tier, issue category, escalation recency, and contract value.
External replies require an explicit __REPLY__ marker. Unmarked thread messages stay internal.
Reliable agentic workflows: evaluation, orchestration, Python agents, launch readiness
Details available on request
Straight answers about the work.
Vadrel is the firm Zac uses for client work. This site is him. The firm puts AI into work companies already do: build it, teach the team, or both.
No. That chapter is closed. Nomad Cybersecurity Group is in the past. New work is AI operations and teaching, not security auditing.
Two ways. I build the thing and leave it running. Or I sit with your people and teach them to run it. Most clients want some of both. You do not get a deck.
Yes, a small number of companies at a time, through Vadrel. Email or LinkedIn.
Click a platform to read this site and LinkedIn, then get a plain summary of who Zac is and what he does. Client work goes through Vadrel.
If a platform does not auto fill, paste the copied prompt after it opens. Machine readable context also lives at /llms.txt and /llms-full.txt.
Open to load prompt preview.
Client work goes through Vadrel. This page is me. Email or LinkedIn.
Resume available on request via email or LinkedIn.