Gets to know the job.
Show Mack the examples, shortcuts, and exceptions your team relies on. Those details shape how it approaches the work.
Meet Mack. An AI colleague built around your business, starting with the reports, customer follow-ups, and everyday admin your team keeps picking up.
Start with one job. Build trust from there.
“Compare these orders with the dispatch list. What needs checking?”
Four units short on one. A missing dispatch date on the other.
Start with the work around your tools.
Meet Mack
Your rules. Your exceptions. The details that never make it into a manual. We’re building Mack to remember how the job works, so each assignment can build on the last.
Show Mack the examples, shortcuts, and exceptions your team relies on. Those details shape how it approaches the work.
We start with the tools you use today and the jobs that still fall between them. The first assignment sets the direction.
You decide what Mack handles and what comes back for a decision. Start with work you can check, then build from there.
A few jobs for Mack
Start with work that comes around every week: checking records, drafting replies, or sorting out who needs to do what. Here’s what the result could look like.
Compare an order sheet with a dispatch list. Pull out shortages, missing dates, and anything the operations team needs to check.
Order sheet + dispatch list → exception report
Tell us about your job24 ordered. 20 recorded as dispatched.
The order is confirmed, but the dispatch field is blank.
Two deliveries of 10 and 14 account for all 24 units.
The exceptions, with the records behind them.
How we get started
Pick something your team does again and again. Tell us about it, and we’ll work out a sensible first assignment together.
Your company and a sentence about the task are enough to start. Tell us what keeps landing back on your team’s desk.
Together, we choose a small first assignment and the information it needs. You check the result against how the job is actually done.
Then we agree on the routine: when the work happens, which systems it uses, and where you want to be involved.
We agree on scope and pricing before ongoing work begins. Start with one recurring job, then decide together what comes next.
The people behind the colleague
Martin and Fitz stay close to the work: learning how the job runs, building Mack around it, and refining it with your team.

Martin leads the client side of Avorth. He digs into how your operation really runs and spots the work that shouldn’t need people.
Connect with Martin on LinkedIn (opens in a new tab)
Fitz heads up engineering at Avorth. He’s a proven builder — the one who turns what we learn about your business into systems that work.
Connect with Fitz on LinkedIn (opens in a new tab)A few good questions
Tell us your company and describe the job in a sentence. Email Mack or book a 30-minute call with Martin.
We start with the tools you use today. The right connection depends on the system, the access available, and what you want Mack to do.
You do. We agree on the job, the access it needs, and the points where you want to review or decide.
Mack is the AI colleague. Martin and Fitz help set up the work, shape the rules, and improve it with you.
We agree on scope and pricing before ongoing work begins. Martin and Fitz will talk through what the work involves.
Start with one job
The report you rebuild. The orders you double-check. The follow-ups waiting in your inbox. Tell us which job is taking more time than it should.