Nico
- Twilio
- Slack or Microsoft Teams
- Salesforce
- Google Calendar
Answers the phone after hours as your receptionist, holds a real conversation, decides whether it is urgent, and writes the call up for the morning.
How Nico worksAgents
AI agents for small business, each focused on one job: calls, email, invoices, listing graphics or website management. See what each one does and how it fits your systems.
The roster
Choose the job you want off your plate. Each card links to the agent’s workflow, scope and current status. If your job is not on this list, describe it and we will tell you whether an agent can take it.
Answers as your receptionist, holds a real conversation, then writes up the call and hands it to your team with a recording.
Live on real calls
Asks in Slack whether you want a campaign, researches every prospect, writes each email itself, follows up three times and flags the replies worth your time.
In production
Connects Salesforce, QuickBooks and BILL to prepare invoices, check payments and draft follow-ups. Your team approves the booking and every send in Slack.
In production
Takes listing requests from a form, fits your uploaded photo to the brokerage’s template and returns an editable flyer in Slack. You approve every one.
Live brokerage pilot
Keeps website checks, content corrections and small improvements in one queue. You review a preview and approve each change before it goes live.
Proposed website care
What they touch
Answers the phone after hours as your receptionist, holds a real conversation, decides whether it is urgent, and writes the call up for the morning.
How Nico worksAsks in Slack whether you want a campaign, builds the list from your CRM, researches each company, writes every email individually, follows up three times, then reads the replies and hands you the ones worth your time.
How Beep Beep worksWatches for a closed deal, creates the purchase order and invoice after approval, confirms the downstream copy matches, and prepares the payment link and email. It checks payment status before drafting follow-ups. A person approves every send.
How the finance agent manages receivablesFills the brokerage’s listing templates with supplied details, fits one uploaded property photo and returns an editable flyer in Slack for human approval.
How Gable worksBrings scheduled website checks and small improvements into a Slack workflow, with a preview for your review before publication. Initial scope covers an existing, supported Next.js site on Vercel with code in GitHub.
How Milo worksThe one you actually need
Most conversations start with a job that is not on this page. Someone is re-keying orders out of a supplier portal, or reconciling two systems that disagree every Monday, or reading the same category of email forty times a week and filing it. That is the work an agent is for, and it is almost never identical between two companies.
The build looks the same regardless of the job: we watch the work, scope one agent, write down what it will never do, build it against your accounts, and run it. What changes is the job itself. Tell us the one that eats your week and we will tell you whether it is a fit, including when the answer is no.
How they're built
An agent that does one thing well is easier to trust, test and switch off than a platform that does everything badly.
The call becomes a card in Slack. The closed deal becomes an invoice in QuickBooks. Nothing lands in a dashboard you have to go and check.
Customer-facing and financial actions wait for a click until you say otherwise. Every action is logged with what the agent saw and why it acted.
Hosting, monitoring, model updates, and a person on our side reading the logs. A flat monthly fee, cancel any time.
Software that uses a language model to read something that arrives (a call, an email, a document, a record), decides what to do, and does it in your systems. A chatbot answers questions. An agent finishes a job.
They are built around the systems small teams already use: Salesforce, QuickBooks, BILL, Slack and Google Workspace. Gable, for example, handles listing graphics in a live brokerage pilot.
One agent. Start with the job that hurts most. Add another when the first one has earned it.
It's caught at the approval step, and the log shows exactly what it read and why it acted. We fix the rule, add a test, and the fix ships to every customer running that agent.
That is the usual case. These agents are examples of the pattern, not a menu. If the work arrives somewhere predictable, the rules mostly fit on a page, and a mistake is cheap to catch with an approval step, it is probably a fit. Describe the job and we will tell you either way.
We do. Hosting, monitoring, model updates when providers change them, and a person on our side reading the logs. It is a flat monthly fee you can cancel. You can also take the code and run it yourself, but most people would rather not own that.
It depends almost entirely on how clean the access to your systems is. A documented API with credentials ready is a very different job from an on-premise system with none. We scope it after looking at your actual setup rather than quoting a number first.
Only where it helps. The email agent writes unsubscribes back to the CRM that the finance agent also reads, so nobody gets chased after asking to be left alone. Beyond that they stay separate on purpose — one job each is what makes them testable.
Tell us which job. We'll tell you what it would take to run it for you.