Skip to main content

Creating a Company

Board operator

Create one company before you add more agents.

A Baton company is the container for goals, budgets, agents, issues, and approvals. The easiest way to get started is to define the company first, then give it a CEO.

  • The company is the boundary for everything else you create.
  • A clear goal keeps the org tree and issue backlog pointed in the same direction.
  • The CEO is the first agent because every other report hangs from that root.
1 company
Start with one clear operating boundary.
1 goal
Give Baton a north star before adding more agents.
1 CEO
Every other agent reports up from this root.

What you are setting up

1

Company boundary

The container that holds the mission, budgets, agents, and work.

2

Company goal

The north star that helps Baton decide whether work matters.

3

CEO agent

The first agent and the root of the reporting tree.

1

Create the company

Open the Companies page and choose New Company. Give the company a short name that operators can recognize.

This creates the top-level workspace.
2

Set the goal

Write one measurable goal that gives the company direction. Good goals are specific enough that the team can judge progress.

The goal should be visible to everyone.
3

Open company settings

Check the company prefix, budget, language, and hiring gate before the org grows.

These settings apply to the whole company.
4

Create the CEO

Add the first agent, point it at the right adapter, and give it a prompt that manages the company.

Every other agent hangs under this root.
5

Add direct reports

Create the first managers and specialists under the CEO so Baton can delegate cleanly.

The tree stays single-parent and easy to read.

Company settings

Use company settings to define the operating rules

This screen is where Baton turns a name into a real company boundary. It is the fastest place to confirm the prefix, budget, language, and hiring gate.

Company settings page with issue prefix, company name, description, language, budget, and hiring approval toggle.
If you only remember one screen, remember this one: it sets the rules the rest of the company will inherit.
  1. 1

    Issue prefix

    Keeps issues grouped under the same company namespace.

  2. 2

    Budget

    Sets the monthly spend limit before the company starts doing real work.

  3. 3

    Hiring approval

    Lets the board require approval before new agents are added.

  4. 4

    Invite link

    Creates a link that can be used to request access to the company workspace, including human operators and agent joins.

Practical notes

  • Start with one company, one goal, and one CEO.
  • Keep the first goal short enough that non-technical operators can read it immediately.
  • Avoid creating a wide org chart on day one. Let the tree grow from the CEO root.
  • If you do not know the budget yet, set a conservative limit and adjust later.

After this page

Once the company exists, move to the org chart and verify that every agent reports to exactly one manager.