Cabinet for a company with departments.

The full leadership team, a meeting rhythm for every level, people who join with a role, and a record of who changed what. The same weekly loop as for a small business, with more seats at the table.

The full team: six leaders

A larger company gets all six. They read up on your company before they speak, so their answers are about your customers and your numbers, not generic advice.

  • Chief of Staff

    Runs the meetings and keeps everyone on track

  • CEO

    Sets direction and decides what matters most

  • CFO

    Watches your money: prices, costs, and cash

  • CMO

    Brings in customers: marketing, ads, and reviews

  • CTO

    Looks after your website and tech

  • Skeptic

    Asks the hard questions before you commit

The Skeptic joins a meeting when the room agrees too fast, and argues the strongest case against. The Skeptic doesn't vote, so a plan still has to win on its merits.

Setting up as a larger company turns on all six. The Trial, Team, and Pro plans include all six leaders; Owner includes the chief of staff, CEO, and CFO.

When there's hands-on work, make a hire: the website and tech engineer, an ads expert, an SEO manager, a content marketer, a social media manager, or an online store manager. Each works only with the access you give it and inside the same rules, and you can remove one at any time. Every plan includes every hire.

Every kind of meeting

Seven kinds, each starting from your numbers. You choose which ones run and when.

  • Morning update

    What changed, what needs a decision from you, and what the team is working on.

  • Daily check-in

    A short update from each leader you pick: what moved, what is blocked, and what happens today. Nothing is written down as a decision.

  • Weekly meeting

    Goes over the week and decides what's next. Every task gets a name and a date.

  • Ideas session

    The team suggests ideas, argues about them, and ranks them using your numbers.

  • Follow-up on a decision

    On a decision's check-back date, looks at how it turned out, including whether the one who disagreed had a point.

  • Weekly look-back

    A look back over the week, by default on Friday afternoon.

  • Quarterly planning

    On the first Monday of each quarter: which three to seven priorities the company will finish by the end of it, who owns each, and how you'll know.

Times are set in Settings, and you can add your own scheduled meetings. Team and Pro run every kind; the Owner plan leaves out the ideas session, the weekly look-back, and the daily check-in.

One team inside a larger company

Each team that wants Cabinet gets its own, with its own people, tools, files, and spending limit.

  • Owner

    Approves everything and manages the account. A few decisions are an owner's alone: changing the spending limit or the company settings, changing a team member's instructions, making a hire, turning ads on, raising how much code the team may change by itself, and cancelling engineering work.

  • Admin

    Invites people, changes settings, connects tools, and approves ordinary changes. Can give someone the viewer, member, or admin role.

  • Member

    Talks with the team in the chat and asks questions.

  • Viewer

    Can read what the team is doing and has decided, and can't change anything.

People join by invitation and sign in with an emailed link, Google, or Slack. There is no per-person price.

Approvals can be decided in Slack, Google Chat, or the dashboard. An approval nobody decides expires after 7 days. A rejection can carry a reason, and the team member who asked sees it.

The audit log lists settings changes and approvals with who made them, and admins and owners can search it. Every decision also records who was in charge and who disagreed.

Where your team talks

Cabinet works in Slack, in Google Chat, and on the web. Each team chooses where its team channels live in Settings; the chat in the web dashboard is always there, so a team without Slack or Google Chat is not left out.

Anything that needs a person's OK arrives with Approve and Reject buttons wherever the team talks.

Your own AI keys, and where the work runs

Every paid plan includes AI use each month, and the trial includes a small amount once. Add your own Anthropic, OpenAI, Google, or xAI keys on any plan and calls made with them use none of what's included. Your keys are stored encrypted, for your team alone.

The website and tech engineer, Nightshift, works through a GitHub App in the repositories you choose and opens pull requests. It runs on Cabinet; on the Pro plan it can run on your own servers.

How much code it may change without you depends on the plan. Trial and Owner: code changes wait for your OK. Team: low-risk code changes go in after a review. Pro: you choose which code changes go in on their own.

A week at a larger company

Examples, not real data: the numbers it watches, the decision it writes down, and how an earlier one went, at a firm or agency, a software company, a manufacturer, and a nonprofit. These examples keep the six-member cast.

See a week at a company like yours

1 · The numbers it watches

  • Revenue and margin by month
  • Cash on hand and what customers owe
  • New customers and where they came from
  • The one number you watch most

2 · This week’s agenda

  • Which number matters most this quarter?
  • Raise prices, or cut what costs the most?
  • What should we stop doing?

3 · The decision it writes down

Stop the work that does not move [YOUR NUMBER]

In charge
CEO
Check back
In 90 days
We’ll know it didn’t work if
[YOUR NUMBER] is flat after a quarter
Disagreed
Skeptic: some of that work keeps current customers happy.

Approve, change, or say no. The team checks back on the date it set.

4 · Asked between meetings

“Can we afford another hire before the busy season?”

CFO: Yes, if the two largest overdue invoices are paid this month. Without them, cash covers three months, not five.

5 · Making sure it happens

  • Chief of staffChecks in with whoever has each task midweek and puts anything late on the next brief.
  • A hireBuilds an ad campaign for what sells best. It starts paused and runs only after you approve.

6 · How an earlier decision went

Ask every new customer for a review

Good call

Reviews tripled in 60 days, and the Skeptic's worry about annoying customers did not come true.

Where the numbers come from: Tell the team in a meeting or a chat, or paste the report you already keep. It records each figure with its source and date, and reads the tools you connect.

Give it your website. Come back to a plan.

Questions: hello@agntwrk.com