Seby is not advisory. We deploy and we operate. Each customer gets their own always-on agent on itsown isolated infrastructure, connected to their email, calendar, chat, meetings, documents andbusiness systems. It drafts replies in each person's own voice, preps every meeting and files everydebrief, keeps every contact and deal on one timeline, and takes on the repeatable back-office workthat keeps an owner stuck in their own business.

Our customers are owner-run firms: recruiters, agencies, consultancies, design and engineeringpractices. They pay us, they use it every day, and there are more coming.

We run our own company on the same system. Roadmap, tickets, testing, deploys, alerts and reportingall run through Claude Code and our agents. Two people and a fleet of agents ship what a much largerteam would.

We've just signed a large new contract, and demand now outruns build capacity. Our lead engineer isexceptional with Claude and with production systems. We need a second engineer at the same level:someone who can take a customer's mess on a Monday and put a working, verified automation in theirhands by Friday.

What you'll build: a real sample Every one of these is built, or being built, for a customer.

Onboarding a new customer

Render their agent from our one shared template onto its own server, connect Microsoft 365 or Google Workspace, load their contacts on day one, and prove nothing crosses to any other customer.

Email in their own voice

Reply drafts that sound like the person who will send them, check the live calendar before proposing a time, and never go out without the right approval.

Meeting intelligence

Recordings in from Teams, Fathom or a phone. A prep brief before every meeting,



a debrief and actions after, filed against the right contact and company.

Command centres

Every contact, company, deal and meeting on one clickable, filterable timeline, rebuilt from the customer's real mailboxes rather than a half-updated customer database.

Messy files into trusted numbers

Media schedules that arrive as scanned PDFs, ad platform exports, timesheets and spreadsheets, turned into clean data with a trail back to the source file and row.

Advertising automation

An audit that checks an agency's Google Ads accounts against the agency's own house rules, and a campaign builder that shows every change before it goes in, reads it back afterwards, and can roll it back.

Pricing and project tools

Taking a firm's fee schedules and work breakdowns out of Excel and into a system that prices a tender in minutes.

Back office and finance

Invoices, reconciliations and payments through accounting and banking APIs. Contracts rendered from templates and e-signed.

Screen recording to spec

A customer records their screen while talking through a process. An agent turns it into a build brief with frames and timestamps.

Demos and films

Demo environments with realistic data, and narrated walkthrough films for prospects.

Claude Code is the workbench.

You'll run several agents in parallel,



write the hooks and skills that steer them, and supervise long autonomous runs. If you haven't worked exactly this way yet but you're genuinely rapid with AI coding tools, that can work.

The builder never marks its own homework.

Every claim is checked against the live system by a test, a prover, or a second independent agent. Done means verified on the real surface, not "the code is written".

Gates, not good intentions.

Rules that matter are enforced in code. A ticket can't be created without testable acceptance criteria. An outbound message can't go without approval. A daily prover checks every live system.

Scripts compute, the model reasons, a person judges the exceptions.

The model never invents a number. If a figure reaches a customer, it traces back to a source.

One template, never forked.

An improvement for one customer lands in the shared template and reaches every customer.

Isolation by construction.

Each customer's data lives in its own space, enforced by the architecture and proven every day.

Ticket first, then full ownership.

Every piece of work starts as a ticket on our week board. From there it's yours end to end: spec, build, deploy, prove.

How we test: as the customer Our customers judge us on one thing: does it work when they use it. So every change is tested end toend, as the customer, on the live system, before anyone calls it done. A customer should never be theone who finds the bug.

Walk the real journey.

Sign in as a test user on the customer's own page, click through it, send the message, open the email that lands in the test inbox, and check the record that gets

📌 AI Automation Engineer Remote · Full-time · Senior → (Perth)
🏢 Seby
📍 Perth