How did we put an AI employee inside WhatsApp? Lessons from building Gus

The problem we set out to solve

Owners of trades and service businesses spend their evenings on admin: quotes, invoices, receipts, the diary and social posts. They do not want another app to learn. They already run their business from their phone, and most of their conversations happen in WhatsApp.

Decision 1: put the AI in the channel people already use

Instead of asking owners to log in to new software, Gus lives in WhatsApp. An owner sends a message or a photo and gets a draft back in the same chat. The dashboard exists for the things a chat is bad at: reviewing documents, photos, visits and connected apps in one place. The same principle drives our enterprise work: the agent goes to the systems and channels people already use, not the other way round.

Decision 2: drafts first, a person approves

Gus prepares quotes and invoices as drafts the owner checks. Expenses are logged from a text or a receipt photo, and invoice drafts are reviewed in Gus and in Xero. Paid actions, such as an ad budget, need the owner's approval and the relevant connected accounts. This is the same human-in-the-loop pattern BLDR applies to enterprise agents: the AI does the work, a person signs off, and the action is recorded.

Decision 3: connect to the system of record

An assistant that only chats creates more copy and paste. Gus connects to Google Calendar for the diary, Xero for invoices and bills, and Facebook, Instagram and Meta Ads for marketing. With Xero connected, Gus can create draft invoices, show invoice and bill status, and compare invoiced revenue with tracked costs by project. Xero is optional, so an owner can start in Gus and connect it later, and disconnect it at any time.

Decision 4: make the first win fast

Setup is three steps: tell Gus about the business, area and contact details; activate WhatsApp and link apps; then request a first draft, check it and choose what happens next. The first useful output arrives in the first session, not after a project.

What this means if you are ready to start

The same four decisions apply to an enterprise rollout. Start with one workflow that has a clear owner and a measurable outcome. Deliver it in the channel people already work in, whether that is WhatsApp, Microsoft Teams, email or an ERP screen. Connect it to the system of record so it removes work instead of moving it. And keep a person approving every action that carries risk, with a log of what happened. For enterprises, we do this on BLDR, deployed where you decide, so the agents, approvals and logs stay under your control.

Questions people also ask

Liked this answer? The AI Glittch sends one like it every week to 3,500+ readers.Subscribe →