Find the work an agent should do.

Software that doesn’t just store information and wait for a click. An agent is given a goal — chase this week’s overdue invoices, triage these enquiries, reconcile these payments — and works through the steps itself, using your tools: it reads, looks things up, drafts, decides what to do next and acts. Anything consequential waits for a person to approve it, and every step is logged.

A chatbot answers questions. An agent finishes work. Most of the value we see in businesses is in the second: the follow-ups, reconciliations, data entry and routing that eat a team’s week. A chat interface is sometimes the right front door, but it’s rarely the point.

Yes, sometimes — so does every person and every script. The question is whether mistakes are caught before they matter. We scope agents narrowly, measure them against real examples from your business before launch, put a human approval in front of anything that moves money or reaches a customer, and log every action so it can be reviewed and reversed.

It stays yours. We use model providers under terms that don’t train on your data, give agents access only to what their job needs, and keep a full audit trail. If you leave, you take your data, code and documentation with you.

Usually not. Most agents we design work on top of what you already use — your ERP, spreadsheets, inbox, WhatsApp, payment gateway. Where the underlying system is the problem, we can build that too; it’s what we did for years before agents existed.

Thirty minutes on how work actually moves through your business. We point out the jobs an agent could take on, the ones better served by a plain automation, and the ones to leave alone. You get an honest answer on cost and timeline — and if AI isn’t the right tool, we say so.

A scoped build to get the first workflow live, then one monthly retainer to run it: monitoring, evaluation, model updates and improvements. No per-seat licences and no change-request billing. We give you numbers after the audit, once we know the scope.

Typically one to two weeks from the first conversation to kickoff. We start with one workflow, measured against how it runs today, and expand only when the numbers justify it.