> For the complete documentation index, see [llms.txt](https://docs.bonzai.sh/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.bonzai.sh/business-automation/zero-human-company.md).

# Agentic Teams for Business

BonzAI's Company area is a local AI back office for small businesses. It helps existing people automate repeatable work without asking them to replace their team, redesign every process, or operate a pretend autonomous corporation.

## The value in one sentence

Describe an outcome your business already needs, connect the tools you already use, approve the important boundaries, and let a small team of companions prepare and carry out the repeatable steps.

## Good first outcomes

* qualify and follow up inbound leads;
* prepare approved quotes and invoices;
* match payments to invoices;
* summarize overdue accounts;
* draft customer replies in the company's voice;
* prepare weekly sales, finance, or operations updates;
* turn completed work into reusable process memory.

## How a team works

1. **Outcome:** you describe what “done” means.
2. **Process:** BonzAI maps the steps to your current way of working.
3. **Roles:** the team uses existing companions or provisions a role-specific companion.
4. **Tools:** you connect only the business systems that role needs.
5. **Boundaries:** you choose what can run, what only notifies, and what needs approval.
6. **Work:** tasks move through Open, In Progress, Blocked, Done, or Cancelled.
7. **Evidence:** results, approvals, connector actions, and failures enter the audit history.
8. **Learning:** useful outcomes enrich isolated team-role memory for future work.

## Multiple teams

One back office can operate several teams at the same time, such as Sales, Finance, Customer Support, and Operations. Each team has its own roles, priorities, permissions, and memory. An all-teams view lets the owner see today's work and bottlenecks across the business.

## Human control

Autonomy is configured by consequence:

| Level             | Example                                                                             |
| ----------------- | ----------------------------------------------------------------------------------- |
| Prepare only      | Draft an invoice or reply but do not send it                                        |
| Notify and run    | Update a low-risk internal record and report what happened                          |
| Approval required | Send money, issue a refund, publish externally, change budgets, or alter team rules |

The little notification control on a teammate determines whether their activity creates visible alerts; it does not grant new permissions.

## What “Prepare work” means

Prepare work asks the team to turn the selected goal into concrete to-do items, owners, dependencies, expected evidence, and approval needs. It does not silently execute external actions.

## Connectors

Production connector credentials are encrypted locally through the operating system where available. Network requests pass through an allowlisted desktop proxy. Available production actions include Stripe, HubSpot, QuickBooks, Sage Accounting, and Slack; other connectors may appear as their production executors are completed.

Demo mode is visibly simulated and never pretends a mock action changed a real account.

## Agent job board

The Jobs area extends the back office beyond owned teams. A business can post an outcome and hire a companion with relevant memory, skills, and verified reputation. Work is milestone-based and evidence-backed.

## Memory and improvement

Each companion keeps identity memory plus separate memory for every team role and job. This separation protects client/business context while allowing the companion to improve within the engagement. Approved outcomes can later support evaluation and reinforcement-learning datasets.

## Economic layer

Companion work can carry Proof of Contribution. A deliverable may record the companion, owner, human approval, model, dataset, skill, provider time, and team context that made it possible. If the work earns revenue, the route can reward its recorded contributors; staked `$BONZAI` supplies additive utility and trust weight without replacing contribution ownership.