<?xml version="1.0" encoding="utf-8"?>
<!-- Generated by scripts/blog.mjs. Edit blog/posts/ and run npm run blog. -->
<feed xmlns="http://www.w3.org/2005/Atom">
  <title>agntwrk blog</title>
  <subtitle>News from agntwrk: Cabinet, the AI team for your business, and the products we build with it.</subtitle>
  <link href="https://agntwrk.com/blog" rel="alternate" type="text/html"/>
  <link href="https://agntwrk.com/feed.xml" rel="self" type="application/atom+xml"/>
  <id>https://agntwrk.com/blog</id>
  <updated>2026-11-16T00:00:00Z</updated>
  <author><name>agntwrk</name><email>hello@agntwrk.com</email></author>
  <entry>
    <title>How to Automate Blog and Social Media Posting</title>
    <link href="https://agntwrk.com/blog/automate-blog-and-social-media-posting"/>
    <id>https://agntwrk.com/blog/automate-blog-and-social-media-posting</id>
    <published>2026-11-16T00:00:00Z</published>
    <updated>2026-11-16T00:00:00Z</updated>
    <summary>One message in chat sets the pace. Cabinet plans, writes, checks and schedules the posts, and you OK the parts that go public.</summary>
    <content type="html">&lt;p&gt;Most owners know their company should post more often. Writing a post is not the hard part. Keeping a blog and the social accounts going every week, without losing a day of your own week to it, is. This guide shows how to automate blog and social media posting with Cabinet, our AI leadership team, by asking for it in chat, and which parts still wait for your OK.&lt;/p&gt;
&lt;p&gt;We run agntwrk this way. The &lt;a href=&quot;/blog/level-10-meeting-agenda-small-company&quot;&gt;Level 10 meeting agenda&lt;/a&gt; and &lt;a href=&quot;/blog/decision-log-template&quot;&gt;decision log template&lt;/a&gt; posts on this blog were planned and written by Cabinet’s &lt;a href=&quot;https://cabinet.agntwrk.com/team/ai-content-marketer&quot;&gt;Content Marketer&lt;/a&gt;, and they went live when we said yes.&lt;/p&gt;
&lt;h2&gt;Ask for the pace in one message&lt;/h2&gt;
&lt;p&gt;Open the chat in Cabinet, on the web or in Slack, and say what you want in your own words:&lt;/p&gt;
&lt;blockquote&gt;&lt;p&gt;I want a new blog post every other day, each one aimed at one search phrase, with links to our own pages.&lt;/p&gt;&lt;/blockquote&gt;
&lt;p&gt;Cabinet hands the message to the team member whose job it is. Here that is the Content Marketer, which reports to your CMO. If its rules allow fewer posts than you asked for, it proposes a change to them and shows each rule before and after: from 2 posts a week to 4, published on Monday, Wednesday, Friday and Sunday. You OK it once, on the card in the chat. As soon as you do, it plans the rest of the week.&lt;/p&gt;
&lt;p&gt;Plain words work. Every other day means four a week on those days, three times a week means Monday, Wednesday and Friday, and every day means seven.&lt;/p&gt;
&lt;h2&gt;What happens to each post&lt;/h2&gt;
&lt;ol&gt;
  &lt;li&gt;&lt;strong&gt;A plan for the week.&lt;/strong&gt; For each post the Content Marketer picks one search phrase, starting from what people already search for when Search Console is connected. It checks what ranks for that phrase today and writes down the angle, an outline, and the pages on your site the post should link to. You OK the week’s plan.&lt;/li&gt;
  &lt;li&gt;&lt;strong&gt;The draft.&lt;/strong&gt; On the post’s day it writes the post in your company’s voice, inside the length and the topics you set. A post about your product’s latest changes is written only from what actually shipped, never from what is planned.&lt;/li&gt;
  &lt;li&gt;&lt;strong&gt;A check before you see it.&lt;/strong&gt; Your CMO reads it for one clear reader, claims you can back up, and one clear next step for the reader. If you hired an SEO Manager, it checks that the search phrase is in the title, the first paragraph and one heading, that the description makes someone want to click, and that the post links to your own pages. For a post about your product, your CTO checks every statement against what shipped. If they ask for changes, the post goes back for one rewrite.&lt;/li&gt;
  &lt;li&gt;&lt;strong&gt;Your OK.&lt;/strong&gt; The post arrives as a change to your website, a pull request in its GitHub repository, with the check’s notes on it. Saying yes publishes it.&lt;/li&gt;
&lt;/ol&gt;
&lt;p&gt;Code also turns a post down before it reaches you: one whose web address is already taken, a link to a page on your site that does not exist, or a link to another site that is neither one you allowed nor a source the post cites.&lt;/p&gt;
&lt;h2&gt;Automate blog and social media posting, and keep the final say&lt;/h2&gt;
&lt;p&gt;The same works for your social accounts. Ask the Social Media Manager, which also reports to your CMO:&lt;/p&gt;
&lt;blockquote&gt;&lt;p&gt;Schedule all of this week’s social posts, and plan next week too.&lt;/p&gt;&lt;/blockquote&gt;
&lt;p&gt;It reads what is already on the calendar, fills the days left up to the number of posts a week you set for each account, inside the hours you allow posts to go out and the most you allow in one day, and proposes next week’s calendar. Each post is fitted to its network. Tracking is added to every link by code, and every image needs a description for people who cannot see it.&lt;/p&gt;
&lt;p&gt;You choose how much waits for you:&lt;/p&gt;
&lt;ul&gt;
  &lt;li&gt;&lt;strong&gt;Each post.&lt;/strong&gt; Every post waits for your OK before it goes out.&lt;/li&gt;
  &lt;li&gt;&lt;strong&gt;The week at once.&lt;/strong&gt; You OK the week’s calendar, and each post in it goes out at its time without a second OK.&lt;/li&gt;
&lt;/ul&gt;
&lt;p&gt;You can switch in chat (“from now on, I’ll OK the week, not each post”). Like any change to a rule, it waits for your OK. The Social Media Manager posts to X today. Facebook, Instagram, TikTok and LinkedIn are coming.&lt;/p&gt;
&lt;h2&gt;The rules stay yours&lt;/h2&gt;
&lt;p&gt;Each hire works inside rules you set, and code checks them, not the AI’s judgment.&lt;/p&gt;
&lt;ul&gt;
  &lt;li&gt;&lt;strong&gt;Blog:&lt;/strong&gt; posts a week (1 to 7), the days they go out, the length, the topics to write about and to stay away from, which outside sites a post may link to, the link each post ends with, and the author name.&lt;/li&gt;
  &lt;li&gt;&lt;strong&gt;Social:&lt;/strong&gt; posts a week for each account, the hours posts may go out, the most posts in one day, words that are never used, and words that send a comment straight to you instead of getting a reply.&lt;/li&gt;
  &lt;li&gt;&lt;strong&gt;A pause switch&lt;/strong&gt; on each hire’s page stops it at once.&lt;/li&gt;
&lt;/ul&gt;
&lt;p&gt;A hire may suggest a change to its own rules, and so may the leader it reports to. Nothing changes until you say yes, and Cabinet keeps a record of what changed and who said yes.&lt;/p&gt;
&lt;h2&gt;What you need&lt;/h2&gt;
&lt;ul&gt;
  &lt;li&gt;A Cabinet workspace. Cabinet is in an invite-only beta, and every hire is on every plan.&lt;/li&gt;
  &lt;li&gt;For the blog: your site’s code on GitHub, connected through the Nightshift by agntwrk GitHub App. Without it, each post you OK is kept in Cabinet as a draft for you to paste in.&lt;/li&gt;
  &lt;li&gt;Search Console and Google Analytics, so each plan starts from real searches and each post is measured by the visits and sign-ups it brings.&lt;/li&gt;
  &lt;li&gt;For social: your X account.&lt;/li&gt;
&lt;/ul&gt;
&lt;p&gt;Then ask, and the plan for the week comes back for your OK.&lt;/p&gt;</content>
  </entry>
  <entry>
    <title>Decision Log Template: Keep and Grade Decisions</title>
    <link href="https://agntwrk.com/blog/decision-log-template"/>
    <id>https://agntwrk.com/blog/decision-log-template</id>
    <published>2026-11-16T00:00:00Z</published>
    <updated>2026-11-16T00:00:00Z</updated>
    <summary>A decision log template that makes the review date the point: record dissent and confidence, then grade every call worked, mixed, or failed.</summary>
    <content type="html">&lt;p&gt;Most teams that keep a decision log keep it like a diary. Each entry says what was decided, and nobody opens it again. This decision log template is built around the opposite habit: every entry carries a review date, and on that date you grade the call.&lt;/p&gt;
&lt;p&gt;The record is short, it fits on one page, and you can copy it into a doc or a spreadsheet today.&lt;/p&gt;
&lt;h2&gt;Why a log of what was decided is not enough&lt;/h2&gt;
&lt;p&gt;A list of decisions tells you what happened. It does not tell you whether the decision was any good.&lt;/p&gt;
&lt;p&gt;Without a check-back, a log turns into an archive. People stop reading it because it never changes the next decision. The useful part is the loop: write down the bet, set a date, look at what happened, and say plainly whether the bet paid off. Over a few months that shows you which kinds of calls your team gets right and whose judgment holds up.&lt;/p&gt;
&lt;h2&gt;When to log a decision&lt;/h2&gt;
&lt;p&gt;Do not log everything. Log a decision when one of these is true:&lt;/p&gt;
&lt;ul&gt;
  &lt;li&gt;It binds other people. Someone else has to change what they do.&lt;/li&gt;
  &lt;li&gt;It is costly to undo. It spends money, time, or trust you cannot easily get back.&lt;/li&gt;
&lt;/ul&gt;
&lt;p&gt;Choosing a lunch spot is not a decision record. Changing your pricing, hiring a first salesperson, or dropping a product line is.&lt;/p&gt;
&lt;h2&gt;The fields of a decision log template&lt;/h2&gt;
&lt;p&gt;Each record has six parts. Write them in plain words.&lt;/p&gt;
&lt;ul&gt;
  &lt;li&gt;&lt;em&gt;Decision.&lt;/em&gt; One sentence on what you chose, and the main option you turned down.&lt;/li&gt;
  &lt;li&gt;&lt;em&gt;Owner.&lt;/em&gt; One person, not a team. The owner answers for the result and for the follow-up.&lt;/li&gt;
  &lt;li&gt;&lt;em&gt;Dissent.&lt;/em&gt; Who disagreed and why. Write the objection down even if you overruled it. This is the field people skip, and it is the one you will be glad of later.&lt;/li&gt;
  &lt;li&gt;&lt;em&gt;Confidence.&lt;/em&gt; A percentage, or low, medium, or high. It forces the room to say how sure it really is.&lt;/li&gt;
  &lt;li&gt;&lt;em&gt;What would prove it wrong.&lt;/em&gt; Something you could see within weeks, stated before you start. A number crossing a line, a deadline missed, a customer reaction. Not a feeling.&lt;/li&gt;
  &lt;li&gt;&lt;em&gt;Review date.&lt;/em&gt; A real calendar date, close enough that you will still remember the context. Put it on a calendar.&lt;/li&gt;
&lt;/ul&gt;
&lt;p&gt;The last two fields do the most work. &amp;quot;What would prove it wrong&amp;quot; stops you from explaining away a bad result afterward. The review date makes sure the question gets asked at all.&lt;/p&gt;
&lt;h2&gt;A labeled example record&lt;/h2&gt;
&lt;p&gt;This is an example, not a real company's record.&lt;/p&gt;
&lt;ul&gt;
  &lt;li&gt;&lt;em&gt;Decision:&lt;/em&gt; Move our weekly sales follow-up emails from Friday afternoon to Tuesday morning. We considered hiring a part-time assistant to send them and decided against it for now.&lt;/li&gt;
  &lt;li&gt;&lt;em&gt;Owner:&lt;/em&gt; Dana, head of sales.&lt;/li&gt;
  &lt;li&gt;&lt;em&gt;Dissent:&lt;/em&gt; Priya thinks Friday still works because customers read email on the weekend. She would rather test a second send than move it.&lt;/li&gt;
  &lt;li&gt;&lt;em&gt;Confidence:&lt;/em&gt; Medium, about 60 percent.&lt;/li&gt;
  &lt;li&gt;&lt;em&gt;What would prove it wrong:&lt;/em&gt; Reply rate on the follow-ups is no better after four Tuesday sends than it was across the last four Friday sends.&lt;/li&gt;
  &lt;li&gt;&lt;em&gt;Review date:&lt;/em&gt; Four weeks from the decision.&lt;/li&gt;
&lt;/ul&gt;
&lt;p&gt;Notice what is on the page. A stranger could read it and know what was bet, who disagreed, and exactly what result would end the experiment.&lt;/p&gt;
&lt;h2&gt;The review: worked, mixed, or failed&lt;/h2&gt;
&lt;p&gt;On the review date, open the record and look at what happened against what you wrote down. Then grade it with one of three words:&lt;/p&gt;
&lt;ul&gt;
  &lt;li&gt;&lt;em&gt;Worked.&lt;/em&gt; The result matched or beat what you expected, and the cause was the decision rather than luck.&lt;/li&gt;
  &lt;li&gt;&lt;em&gt;Mixed.&lt;/em&gt; Part of it held up and part did not, or the result is real but smaller than you hoped.&lt;/li&gt;
  &lt;li&gt;&lt;em&gt;Failed.&lt;/em&gt; The thing that would prove it wrong happened, or the decision made things worse.&lt;/li&gt;
&lt;/ul&gt;
&lt;p&gt;Then write one line on why. Not a post-mortem, one line. &amp;quot;Reply rate rose on Tuesday, but only for existing customers; new leads did not change.&amp;quot; That line is what you will find useful in a year.&lt;/p&gt;
&lt;p&gt;Two cautions. First, grade the decision, not the outcome alone. A good call can have a bad result, and a lucky guess can have a good one. Second, note how the dissent held up. If Priya was right, say so. That is how the record earns trust.&lt;/p&gt;
&lt;h2&gt;Keep it to one page and a few decisions a week&lt;/h2&gt;
&lt;p&gt;A log that takes an hour to maintain will be dropped. Keep each record to the six fields and cap yourself at a few decisions a week. If you are logging more, you are probably logging things that do not bind anyone or cost much to undo.&lt;/p&gt;
&lt;p&gt;The best place to write the record is the weekly leadership meeting itself, in the last minutes, while the room still agrees on what was decided. If you do not have a meeting format yet, the &lt;a href=&quot;/blog/weekly-leadership-meeting-kit&quot;&gt;Weekly Leadership Meeting Kit&lt;/a&gt; has an agenda, a scorecard sheet, and a one-page decision record you can copy.&lt;/p&gt;
&lt;h2&gt;How Cabinet keeps the record and runs the review&lt;/h2&gt;
&lt;p&gt;The hard part of this system is not the template. It is that someone has to write the record, remember the date, and ask the question. In a small company that someone is usually the owner, and the review is the first thing to slip.&lt;/p&gt;
&lt;p&gt;Cabinet is agntwrk's AI leadership team, and it runs this loop for us. Each decision from the weekly meeting is recorded with an owner, dissent, confidence, what would prove it wrong, and a review date. On that date the team asks how it turned out and grades it worked, mixed, or failed. Cabinet is in an invite-only beta, new workspaces are approved by a person, and the owner approves what matters under rules the owner sets. You can see what each plan includes on the &lt;a href=&quot;https://cabinet.agntwrk.com/pricing&quot;&gt;pricing page&lt;/a&gt;.&lt;/p&gt;
&lt;p&gt;You do not need Cabinet to use the template. Copy the six fields, set the dates, and grade honestly. If you would rather have the record kept and the review run for you:&lt;/p&gt;
&lt;p&gt;&lt;a href=&quot;https://cabinet.agntwrk.com/signup?utm_source=blog&amp;amp;utm_medium=content&amp;amp;utm_campaign=decision-log-template&quot;&gt;Request an invite to Cabinet&lt;/a&gt;&lt;/p&gt;</content>
  </entry>
  <entry>
    <title>Level 10 Meeting Agenda for a Small Company</title>
    <link href="https://agntwrk.com/blog/level-10-meeting-agenda-small-company"/>
    <id>https://agntwrk.com/blog/level-10-meeting-agenda-small-company</id>
    <published>2026-11-12T00:00:00Z</published>
    <updated>2026-11-12T00:00:00Z</updated>
    <summary>The seven-part Level 10 agenda, what each part is for, where small leadership teams slip, and a lighter weekly version that keeps decisions and review dates.</summary>
    <content type="html">&lt;p&gt;This is for owner-led companies of about 5 to 100 people who run, or want to run, a weekly leadership meeting.&lt;/p&gt;
&lt;p&gt;The Level 10 meeting comes from EOS, the Entrepreneurial Operating System. EOS Worldwide describes it as a weekly leadership meeting with a fixed seven-part agenda, held on the same day at the same time, and meant to run 90 minutes. If you are looking for a level 10 meeting agenda, that is the shape. Below: what each part is for, where small leadership teams tend to slip, and a lighter version for an owner and a few leads.&lt;/p&gt;
&lt;p&gt;We are not against EOS. The agenda is a good one. The fixed order is the point: nobody has to decide what the meeting is about this week.&lt;/p&gt;
&lt;h2&gt;The seven parts&lt;/h2&gt;
&lt;ol&gt;
  &lt;li&gt;&lt;strong&gt;Segue.&lt;/strong&gt; Each person shares good news from the week, personal or professional.&lt;/li&gt;
  &lt;li&gt;&lt;strong&gt;Scorecard.&lt;/strong&gt; The team reviews a short list of weekly numbers. Each number has an owner, and each is on track or off track. Off-track numbers become issues.&lt;/li&gt;
  &lt;li&gt;&lt;strong&gt;Rock review.&lt;/strong&gt; Rocks are the quarterly priorities. Each is on track or off track.&lt;/li&gt;
  &lt;li&gt;&lt;strong&gt;Headlines.&lt;/strong&gt; Customer and employee news, good or bad, in a sentence each.&lt;/li&gt;
  &lt;li&gt;&lt;strong&gt;To-do list.&lt;/strong&gt; Did last week's to-dos get done? Done or not done, with no discussion.&lt;/li&gt;
  &lt;li&gt;&lt;strong&gt;IDS.&lt;/strong&gt; Identify, discuss, solve. This is most of the meeting.&lt;/li&gt;
  &lt;li&gt;&lt;strong&gt;Conclude.&lt;/strong&gt; Recap the new to-dos, agree on what to tell the rest of the company, and rate the meeting from 1 to 10. The name comes from that rating.&lt;/li&gt;
&lt;/ol&gt;
&lt;h2&gt;What each part is for&lt;/h2&gt;
&lt;p&gt;&lt;em&gt;Segue&lt;/em&gt; gets people into the room. It is short on purpose.&lt;/p&gt;
&lt;p&gt;&lt;em&gt;Scorecard&lt;/em&gt; is a smoke alarm. It does not explain anything. It tells you which numbers need a conversation, and the conversation happens later.&lt;/p&gt;
&lt;p&gt;&lt;em&gt;Rocks&lt;/em&gt; keep the quarter's priorities in front of the team every week, so urgent work does not quietly replace important work.&lt;/p&gt;
&lt;p&gt;&lt;em&gt;Headlines&lt;/em&gt; are for news that needs no discussion. If it does need discussion, it becomes an issue.&lt;/p&gt;
&lt;p&gt;&lt;em&gt;To-dos&lt;/em&gt; are the follow-through check. Yes or no, no storytelling.&lt;/p&gt;
&lt;p&gt;&lt;em&gt;IDS&lt;/em&gt; is where decisions get made. Everything before it exists to clear the way for it.&lt;/p&gt;
&lt;p&gt;&lt;em&gt;Conclude&lt;/em&gt; closes the loop: what was decided, who does what, and whether the meeting was worth the time.&lt;/p&gt;
&lt;h2&gt;Where small teams slip&lt;/h2&gt;
&lt;p&gt;A team of an owner and a few leads does not fail at the agenda. It fails at the edges of it.&lt;/p&gt;
&lt;p&gt;&lt;strong&gt;The scorecard turns into a debate.&lt;/strong&gt; Someone sees a red number and explains it. Ten minutes later the team is in the middle of an issue, and the rest of the scorecard has not been read. The fix is the rule in the agenda itself: say on track or off track, and move any off-track number to the issues list.&lt;/p&gt;
&lt;p&gt;&lt;strong&gt;Issues end without an owner or a date.&lt;/strong&gt; The team talks well, agrees, and leaves. A week later nobody remembers who was going to do what. An issue is not solved until it has one name and one date next to it.&lt;/p&gt;
&lt;p&gt;&lt;strong&gt;The numbers are stale.&lt;/strong&gt; If the scorecard is typed in ten minutes before the meeting, or during it, people stop trusting it. Every number should have a source and a date.&lt;/p&gt;
&lt;p&gt;&lt;strong&gt;Nobody runs the clock.&lt;/strong&gt; In a big company someone is paid to facilitate. In a small one it falls to the owner, who also has opinions about every issue. That is a hard job to do well.&lt;/p&gt;
&lt;h2&gt;The part most templates leave out&lt;/h2&gt;
&lt;p&gt;The agenda checks whether last week's to-dos got done. It does not check whether last month's decisions worked.&lt;/p&gt;
&lt;p&gt;That gap matters. A team can complete every to-do and still make the same poor call twice, because nobody went back to ask whether the call was right.&lt;/p&gt;
&lt;p&gt;A decision record fixes this with four fields beyond the decision itself:&lt;/p&gt;
&lt;ul&gt;
  &lt;li&gt;who owns it&lt;/li&gt;
  &lt;li&gt;who disagreed, and why&lt;/li&gt;
  &lt;li&gt;what would prove it wrong&lt;/li&gt;
  &lt;li&gt;a review date&lt;/li&gt;
&lt;/ul&gt;
&lt;p&gt;On the review date, the team asks one question: did it work, partly work, or fail? Write the answer down. After a few months you can see which kinds of calls your team gets right.&lt;/p&gt;
&lt;h2&gt;A lighter version for an owner and a few leads&lt;/h2&gt;
&lt;p&gt;If 90 minutes is more than your team will sit through, keep the rhythm and trim the parts. This is a version to try, not a rule:&lt;/p&gt;
&lt;ol&gt;
  &lt;li&gt;&lt;strong&gt;Scorecard.&lt;/strong&gt; Five to ten numbers, each on track or off track. No explanations yet.&lt;/li&gt;
  &lt;li&gt;&lt;strong&gt;Last week's decisions and to-dos.&lt;/strong&gt; Done or not done. For decisions whose review date has arrived, did it work?&lt;/li&gt;
  &lt;li&gt;&lt;strong&gt;Issues.&lt;/strong&gt; Pick the top few off-track items. For each, decide, then write the owner, the date, and the review date.&lt;/li&gt;
  &lt;li&gt;&lt;strong&gt;Close.&lt;/strong&gt; Read the new decisions back aloud.&lt;/li&gt;
&lt;/ol&gt;
&lt;p&gt;Headlines can go in a shared note before the meeting. The segue is optional. The scorecard, the issues with owners, and the review are the parts that carry the weight.&lt;/p&gt;
&lt;h2&gt;Who enters the numbers and runs the clock&lt;/h2&gt;
&lt;p&gt;Someone has to pull the numbers before the meeting, keep time during it, write down each decision, and chase the follow-ups afterward. If that person is the owner, the owner is doing the work of running the meeting on top of leading it. If it is a lead, it is a chore that slides first when things get busy.&lt;/p&gt;
&lt;p&gt;The simple fix is to rotate the role weekly so it is not one person's burden. The other is to hand the routine parts to software that works inside rules you set.&lt;/p&gt;
&lt;h2&gt;How Cabinet runs the same rhythm&lt;/h2&gt;
&lt;p&gt;Cabinet is our attempt at the second option. Each week it prepares the scorecard, with each number's source and date, and runs the meeting in Slack, Google Chat, or the web. It writes the decision record with owners, dissent, confidence, and a review date. It chases the follow-ups, and on the review date it asks how the decision turned out and grades it worked, mixed, or failed. A fixed policy checks every action against rules the owner sets, and the owner approves what matters. The people in the meeting still make the decisions.&lt;/p&gt;
&lt;p&gt;We run agntwrk on it. It is in an invite-only beta, so new workspaces join a waitlist that the owner approves. It does not yet have SSO or SOC 2. Plans are on the &lt;a href=&quot;https://cabinet.agntwrk.com/pricing&quot;&gt;pricing page&lt;/a&gt;; the trial is $0 with $10 of usage.&lt;/p&gt;
&lt;p&gt;If your team already runs a Level 10 meeting by hand, keep what works. If the meeting keeps slipping because nobody wants the job of running it, try it for a few weeks.&lt;/p&gt;
&lt;p&gt;&lt;a href=&quot;https://cabinet.agntwrk.com/signup?utm_source=blog&amp;amp;utm_medium=content&amp;amp;utm_campaign=level-10-meeting-agenda-small-company&quot;&gt;Start free&lt;/a&gt;&lt;/p&gt;</content>
  </entry>
  <entry>
    <title>New in Cabinet: AI receptionist, Faire, Xero and Teams</title>
    <link href="https://agntwrk.com/blog/cabinet-new-hires-and-connectors"/>
    <id>https://agntwrk.com/blog/cabinet-new-hires-and-connectors</id>
    <published>2026-11-11T00:00:00Z</published>
    <updated>2026-11-11T00:00:00Z</updated>
    <summary>Two new hires, a Web Designer on the way, and connectors for money, Microsoft 365, wholesale and the phone, with the beta ones named.</summary>
    <content type="html">&lt;p&gt;When we &lt;a href=&quot;/blog/cabinet-beta&quot;&gt;opened Cabinet in an invite-only beta&lt;/a&gt;, it had six leaders and four hires: Nightshift, the Ad Expert, the SEO Manager and the Store Manager. Since then the team has grown. A Content Marketer and a Social Media Manager joined, and this update adds a Receptionist and a Wholesale Manager, both in beta, with a Web Designer built and waiting its turn. Cabinet also connects to more of the tools a company already runs on: Xero and QuickBooks for the books, Outlook, Excel, OneDrive, SharePoint and Microsoft Teams, Faire for wholesale, and Twilio for the phone. Some of these are beta, and we say which below.&lt;/p&gt;
&lt;h2&gt;What’s new at a glance&lt;/h2&gt;
&lt;ul&gt;
  &lt;li&gt;&lt;strong&gt;Receptionist&lt;/strong&gt; (beta): an AI receptionist that answers your business phone, takes messages and transfers calls during your hours.&lt;/li&gt;
  &lt;li&gt;&lt;strong&gt;Wholesale Manager&lt;/strong&gt; (beta): watches your Faire orders and stock, and accepts orders within your rules.&lt;/li&gt;
  &lt;li&gt;&lt;strong&gt;Web Designer&lt;/strong&gt; (soon): builds and edits your website and publishes only when you approve.&lt;/li&gt;
  &lt;li&gt;&lt;strong&gt;Content Marketer and Social Media Manager&lt;/strong&gt;: your blog and your social posts, planned a week at a time. They were not in the first beta post.&lt;/li&gt;
  &lt;li&gt;&lt;strong&gt;Accounting&lt;/strong&gt;: QuickBooks connects for everyone. Xero is in beta.&lt;/li&gt;
  &lt;li&gt;&lt;strong&gt;Microsoft 365&lt;/strong&gt; (beta): Outlook, Excel, OneDrive and SharePoint.&lt;/li&gt;
  &lt;li&gt;&lt;strong&gt;Microsoft Teams&lt;/strong&gt; (beta): another place for your team to talk, next to Slack, Google Chat and the web.&lt;/li&gt;
  &lt;li&gt;&lt;strong&gt;Faire&lt;/strong&gt; and &lt;strong&gt;Twilio&lt;/strong&gt; (beta): the wholesale marketplace and the phone line behind the two new hires.&lt;/li&gt;
&lt;/ul&gt;
&lt;p&gt;&lt;img src=&quot;/img/blog/cabinet-new-hires-and-connectors/team.webp&quot; alt=&quot;The Team page in the Cabinet dashboard, with a card for each member saying what it is doing now&quot; loading=&quot;lazy&quot;&gt;&lt;/p&gt;
&lt;p&gt;&lt;em&gt;The Team page: one card per member, saying what each is doing now.&lt;/em&gt;&lt;/p&gt;
&lt;h2&gt;New hires&lt;/h2&gt;
&lt;p&gt;A hire has one job, reports to one of your leaders, works through its own connection, and acts only inside rules you set. Those rules are checked by code, not left to the AI’s judgment. Anything outside them waits for your OK, and every hire has a pause switch on its page.&lt;/p&gt;
&lt;h3&gt;Receptionist: an AI receptionist for your phone&lt;/h3&gt;
&lt;p&gt;The &lt;a href=&quot;https://cabinet.agntwrk.com/team/ai-receptionist&quot;&gt;Receptionist&lt;/a&gt; answers your business phone with what your team already knows about your company. It takes a message, transfers the call to a person during the hours you set, and emails the caller a link you chose, such as your booking page, once the caller confirms their address out loud. It reports to your chief of staff.&lt;/p&gt;
&lt;p&gt;You can get a line in two ways. Cabinet can set up a number for you, with nothing to sign up for, and the minutes count against your usage. Or you can connect your own &lt;a href=&quot;https://www.twilio.com&quot;&gt;Twilio&lt;/a&gt; account. If you want to keep your current business number, you can set your carrier to forward it to the Cabinet number.&lt;/p&gt;
&lt;p&gt;The rules are yours. You write the greeting, the business hours and the people a call may go to. A call is only ever transferred to a number you saved, never to one a caller says. You also set what to collect in a message, a time limit for each call, a monthly minutes limit and a daily limit for each caller. Calls are recorded and written up by default, and while recording is on the greeting always starts with a notice that cannot be removed. Each call shows up in Cabinet as a conversation with a summary, so the team can see what was asked.&lt;/p&gt;
&lt;p&gt;The Receptionist is in beta because the phone connection is. Nothing it hears is treated as an instruction: a caller’s words are data, and the only things it can do are the few actions on its list.&lt;/p&gt;
&lt;p&gt;&lt;img src=&quot;/img/blog/cabinet-new-hires-and-connectors/receptionist.webp&quot; alt=&quot;The Receptionist’s Overview tab in the Cabinet dashboard&quot; loading=&quot;lazy&quot;&gt;&lt;/p&gt;
&lt;p&gt;&lt;em&gt;The Receptionist’s Overview tab.&lt;/em&gt;&lt;/p&gt;
&lt;h3&gt;Wholesale Manager: orders and stock on Faire&lt;/h3&gt;
&lt;p&gt;If you sell to shops through &lt;a href=&quot;https://www.faire.com&quot;&gt;Faire&lt;/a&gt;, the &lt;a href=&quot;https://cabinet.agntwrk.com/team/ai-wholesale-manager&quot;&gt;Wholesale Manager&lt;/a&gt; keeps an eye on the account so you do not have to check it all day. It watches new orders, orders that must ship on time, low stock and retailers due for a reorder, and it writes a morning note and a weekly wholesale report. It reports to your CEO.&lt;/p&gt;
&lt;p&gt;It can accept orders and set available stock, and by default each of those waits for your OK. If you want, you can let it accept an order by itself when every item on it is in stock. You also choose which products it never touches and how many changes it may make in a day. It cannot cancel or ship an order, change a price, or write to a retailer, because it has no way to do those things. When a retailer writes asking for a discount or a faster ship date, it drafts a reply for you to copy into Faire and leaves the answer to you.&lt;/p&gt;
&lt;p&gt;Faire’s tools do not include messages, so there is a workaround that stays simple. Cabinet gives your workspace a private address. You forward Faire’s notification emails to it, and Cabinet files them by code, so the Wholesale Manager and your leaders see retailer questions and sample requests. The CEO, CFO and CMO also get a wholesale summary in their meetings.&lt;/p&gt;
&lt;p&gt;Faire is a beta connection, and the Wholesale Manager is in beta with it.&lt;/p&gt;
&lt;p&gt;&lt;img src=&quot;/img/blog/cabinet-new-hires-and-connectors/wholesale-manager.webp&quot; alt=&quot;The Wholesale Manager’s Overview tab in the Cabinet dashboard&quot; loading=&quot;lazy&quot;&gt;&lt;/p&gt;
&lt;p&gt;&lt;em&gt;The Wholesale Manager’s Overview tab.&lt;/em&gt;&lt;/p&gt;
&lt;h3&gt;Web Designer: coming soon&lt;/h3&gt;
&lt;p&gt;The &lt;a href=&quot;https://cabinet.agntwrk.com/team/ai-web-designer&quot;&gt;Web Designer&lt;/a&gt; builds and edits your website from your requests. It works in your own GitHub repositories, shows you each change as a preview before anything goes live, and publishes it only when you approve. A check in code reviews each change first, and your marketing leaders look at it too. It can attach a custom domain, point a contact form at your Cabinet workspace so leads arrive there, and take over an existing simple site. It reports to your CMO.&lt;/p&gt;
&lt;p&gt;It is built, and we are not offering it to other companies yet. We would rather open it when we are sure it is ready.&lt;/p&gt;
&lt;p&gt;&lt;img src=&quot;/img/blog/cabinet-new-hires-and-connectors/web-designer.webp&quot; alt=&quot;The Web Designer’s Overview tab in the Cabinet dashboard&quot; loading=&quot;lazy&quot;&gt;&lt;/p&gt;
&lt;p&gt;&lt;em&gt;The Web Designer’s Overview tab.&lt;/em&gt;&lt;/p&gt;
&lt;h3&gt;Content Marketer and Social Media Manager&lt;/h3&gt;
&lt;p&gt;These two joined after the first beta post, so they are new if you have not looked since.&lt;/p&gt;
&lt;p&gt;The &lt;a href=&quot;https://cabinet.agntwrk.com/team/ai-content-marketer&quot;&gt;Content Marketer&lt;/a&gt; plans your blog around what people search for, with one search phrase for each post. It writes in your voice and hands you each post as a change to your site, which goes live when you approve it, and it tracks what each post brings in.&lt;/p&gt;
&lt;p&gt;The &lt;a href=&quot;https://cabinet.agntwrk.com/team/ai-social-media-manager&quot;&gt;Social Media Manager&lt;/a&gt; plans a week of posts for you to approve, fits each one to its network, drafts replies to comments for your OK, and tracks the visits and sign-ups that come from them. It posts to X today. Facebook, Instagram, TikTok and LinkedIn are coming, and we explain why further down.&lt;/p&gt;
&lt;h2&gt;Every hire on the team&lt;/h2&gt;
&lt;p&gt;All nine, with the leader each one reports to. On the Owner plan, where the CMO and CTO seats are not included, those hires report to the CEO.&lt;/p&gt;
&lt;ul&gt;
  &lt;li&gt;&lt;a href=&quot;https://cabinet.agntwrk.com/team/ai-software-engineer&quot;&gt;Nightshift&lt;/a&gt;: an engineer that opens pull requests in the repositories you choose, with a separate review of each. Reports to the CTO.&lt;/li&gt;
  &lt;li&gt;&lt;a href=&quot;https://cabinet.agntwrk.com/team/ai-google-ads-manager&quot;&gt;Ad Expert&lt;/a&gt;: checks your Google Ads setup, keeps spending under your monthly limit and builds the campaigns you approve. Reports to the CMO.&lt;/li&gt;
  &lt;li&gt;&lt;a href=&quot;https://cabinet.agntwrk.com/team/ai-seo-manager&quot;&gt;SEO Manager&lt;/a&gt;: finds the pages and searches worth fixing on Google and checks what changed. Reports to the CMO.&lt;/li&gt;
  &lt;li&gt;&lt;a href=&quot;https://cabinet.agntwrk.com/team/ai-content-marketer&quot;&gt;Content Marketer&lt;/a&gt;: your blog, from plan to published post. Reports to the CMO.&lt;/li&gt;
  &lt;li&gt;&lt;a href=&quot;https://cabinet.agntwrk.com/team/ai-social-media-manager&quot;&gt;Social Media Manager&lt;/a&gt;: a weekly calendar of posts and drafted replies. Reports to the CMO.&lt;/li&gt;
  &lt;li&gt;&lt;a href=&quot;https://cabinet.agntwrk.com/team/ai-web-designer&quot;&gt;Web Designer&lt;/a&gt;: your website, changed only when you approve (coming soon). Reports to the CMO.&lt;/li&gt;
  &lt;li&gt;&lt;a href=&quot;https://cabinet.agntwrk.com/team/ai-shopify-store-manager&quot;&gt;Store Manager&lt;/a&gt;: your Shopify store’s sales, stock, prices and discounts. Reports to the CEO.&lt;/li&gt;
  &lt;li&gt;&lt;a href=&quot;https://cabinet.agntwrk.com/team/ai-wholesale-manager&quot;&gt;Wholesale Manager&lt;/a&gt;: your Faire orders and stock (beta). Reports to the CEO.&lt;/li&gt;
  &lt;li&gt;&lt;a href=&quot;https://cabinet.agntwrk.com/team/ai-receptionist&quot;&gt;Receptionist&lt;/a&gt;: your phone (beta). Reports to the chief of staff.&lt;/li&gt;
&lt;/ul&gt;
&lt;p&gt;Two more are planned and not available yet: a QA tester for your site before each release, and an analyst that tells you what moved and why.&lt;/p&gt;
&lt;h2&gt;The leadership team&lt;/h2&gt;
&lt;p&gt;The hires report to six leaders, each with a page of its own. They read a company brief drafted from your website before they speak.&lt;/p&gt;
&lt;ul&gt;
  &lt;li&gt;&lt;a href=&quot;https://cabinet.agntwrk.com/team/ai-chief-of-staff&quot;&gt;Chief of Staff&lt;/a&gt;: runs the meetings and writes down what is decided.&lt;/li&gt;
  &lt;li&gt;&lt;a href=&quot;https://cabinet.agntwrk.com/team/ai-ceo&quot;&gt;CEO&lt;/a&gt;: sets direction and what comes first.&lt;/li&gt;
  &lt;li&gt;&lt;a href=&quot;https://cabinet.agntwrk.com/team/ai-cfo&quot;&gt;CFO&lt;/a&gt;: your money: prices, costs and cash.&lt;/li&gt;
  &lt;li&gt;&lt;a href=&quot;https://cabinet.agntwrk.com/team/ai-cmo&quot;&gt;CMO&lt;/a&gt;: bringing in customers through ads, search and growth.&lt;/li&gt;
  &lt;li&gt;&lt;a href=&quot;https://cabinet.agntwrk.com/team/ai-cto&quot;&gt;CTO&lt;/a&gt;: your website and tech.&lt;/li&gt;
  &lt;li&gt;&lt;a href=&quot;https://cabinet.agntwrk.com/team/ai-skeptic&quot;&gt;Skeptic&lt;/a&gt;: asks the hard questions before you commit, on the record.&lt;/li&gt;
&lt;/ul&gt;
&lt;p&gt;A new sign-up starts with the chief of staff, CEO, CMO and CFO. The CTO and the Skeptic can be turned on at any time. Every hire and every connector is on every plan.&lt;/p&gt;
&lt;h2&gt;New connectors&lt;/h2&gt;
&lt;p&gt;A &lt;strong&gt;beta&lt;/strong&gt; connector works today. The company that makes the tool is still reviewing Cabinet, so you may see a warning when you connect, or an administrator at your company may have to approve it first. We tag each one on the Connections page.&lt;/p&gt;
&lt;p&gt;&lt;img src=&quot;/img/blog/cabinet-new-hires-and-connectors/connections.webp&quot; alt=&quot;The Connections page in the Cabinet dashboard with Beta tags on the newer connectors&quot; loading=&quot;lazy&quot;&gt;&lt;/p&gt;
&lt;p&gt;&lt;em&gt;The Connections page, with the beta tags.&lt;/em&gt;&lt;/p&gt;
&lt;h3&gt;Money&lt;/h3&gt;
&lt;ul&gt;
  &lt;li&gt;&lt;strong&gt;QuickBooks&lt;/strong&gt; connects for everyone now. &lt;a href=&quot;https://quickbooks.intuit.com&quot;&gt;QuickBooks Online&lt;/a&gt; feeds your CFO the profit and loss, your cash and what you are owed.&lt;/li&gt;
  &lt;li&gt;&lt;strong&gt;Xero&lt;/strong&gt; (beta): the same for companies on &lt;a href=&quot;https://www.xero.com&quot;&gt;Xero&lt;/a&gt;. A workspace uses one accounting source, so you pick QuickBooks or Xero. For now Xero is limited to a small number of connected organisations while Xero reviews the app.&lt;/li&gt;
  &lt;li&gt;&lt;strong&gt;Square&lt;/strong&gt; and &lt;strong&gt;Google Sheets&lt;/strong&gt; were already there for in-person sales and for numbers that live in a spreadsheet.&lt;/li&gt;
&lt;/ul&gt;
&lt;h3&gt;Microsoft 365&lt;/h3&gt;
&lt;p&gt;All of these are in beta, and most companies will need an administrator to approve them, because Microsoft has not finished verifying Cabinet as a publisher. You can see more at &lt;a href=&quot;https://www.microsoft.com/microsoft-365&quot;&gt;Microsoft 365&lt;/a&gt;.&lt;/p&gt;
&lt;ul&gt;
  &lt;li&gt;&lt;strong&gt;Excel&lt;/strong&gt;: Cabinet reads your workbooks as a source for numbers, the way it reads Google Sheets. It does not change them.&lt;/li&gt;
  &lt;li&gt;&lt;strong&gt;Outlook&lt;/strong&gt;: Cabinet can send an email from a person’s own mailbox, but only after that same person approves it, and it keeps one calendar named Cabinet. It never reads your mail.&lt;/li&gt;
  &lt;li&gt;&lt;strong&gt;OneDrive and SharePoint&lt;/strong&gt;: a place to keep a copy of your workspace’s files, under Settings, Your storage, next to Google Cloud Storage, Google Drive and Azure Blob.&lt;/li&gt;
  &lt;li&gt;&lt;strong&gt;&lt;a href=&quot;https://www.microsoft.com/microsoft-teams&quot;&gt;Microsoft Teams&lt;/a&gt;&lt;/strong&gt;: a place your team talks to Cabinet, like Slack, Google Chat and the web. Cabinet is not in the Teams Store yet, so a Teams administrator uploads its app package.&lt;/li&gt;
&lt;/ul&gt;
&lt;h3&gt;Wholesale and phone&lt;/h3&gt;
&lt;ul&gt;
  &lt;li&gt;&lt;strong&gt;Faire&lt;/strong&gt; (beta): the wholesale summary for your CEO, CFO and CMO, the forwarding address for Faire’s emails, and the Wholesale Manager. Faire has not finished reviewing the app.&lt;/li&gt;
  &lt;li&gt;&lt;strong&gt;Twilio&lt;/strong&gt; (beta): the phone line behind the Receptionist, on a Cabinet number or your own account.&lt;/li&gt;
&lt;/ul&gt;
&lt;h2&gt;Coming soon&lt;/h2&gt;
&lt;p&gt;These are not usable yet, and we would rather say why than promise a date.&lt;/p&gt;
&lt;ul&gt;
  &lt;li&gt;&lt;strong&gt;Procore&lt;/strong&gt;, for contractors: a summary of your projects. We are waiting on Procore’s approval to use it with real accounts.&lt;/li&gt;
  &lt;li&gt;&lt;strong&gt;Google Chat&lt;/strong&gt;: the Google Workspace Marketplace is still reviewing the app.&lt;/li&gt;
  &lt;li&gt;&lt;strong&gt;Facebook and Instagram&lt;/strong&gt;: Meta has to verify the business and review the app first.&lt;/li&gt;
  &lt;li&gt;&lt;strong&gt;TikTok&lt;/strong&gt;: TikTok’s own review is not finished.&lt;/li&gt;
  &lt;li&gt;&lt;strong&gt;LinkedIn&lt;/strong&gt;: the Social Media Manager is ready for it, and the LinkedIn app it needs is not set up yet.&lt;/li&gt;
  &lt;li&gt;&lt;strong&gt;Salesforce&lt;/strong&gt; and &lt;strong&gt;Buildertrend&lt;/strong&gt;: not built yet.&lt;/li&gt;
&lt;/ul&gt;
&lt;h2&gt;How to try it&lt;/h2&gt;
&lt;p&gt;Cabinet is still an invite-only beta. The &lt;a href=&quot;https://cabinet.agntwrk.com/team&quot;&gt;team page&lt;/a&gt; lists every leader and hire with what it connects to, and the &lt;a href=&quot;https://cabinet.agntwrk.com/pricing&quot;&gt;pricing page&lt;/a&gt; has the plans: a free trial that needs no card, then Owner, Team and Pro, each with every hire and every connector. If you would like to see the weekly rhythm before you hire anyone, try the &lt;a href=&quot;/blog/weekly-leadership-meeting-kit&quot;&gt;weekly leadership meeting kit&lt;/a&gt;, or read &lt;a href=&quot;/blog/how-to-use-ai-agents-to-run-your-company&quot;&gt;how to use AI agents to run your company&lt;/a&gt;.&lt;/p&gt;</content>
  </entry>
  <entry>
    <title>A Weekly Leadership Meeting Kit: Agenda and Scorecard</title>
    <link href="https://agntwrk.com/blog/weekly-leadership-meeting-kit"/>
    <id>https://agntwrk.com/blog/weekly-leadership-meeting-kit</id>
    <published>2026-11-05T00:00:00Z</published>
    <updated>2026-11-05T00:00:00Z</updated>
    <summary>A free 90-minute agenda, a scorecard sheet and a one-page decision record for your weekly leadership meeting. No email needed.</summary>
    <content type="html">&lt;p&gt;A weekly leadership meeting earns its hour and a half when it does three things every time: it starts from the same numbers, it writes down what was decided, and it checks that last week’s promises were kept. Without those, a meeting is a conversation, and next week it starts from nothing.&lt;/p&gt;
&lt;p&gt;That is the rhythm Cabinet runs for us, and we put the pieces into a kit anyone can use, with or without Cabinet. It has a 90-minute agenda, a scorecard sheet, and a one-page decision record. It is free, and you do not need to give an email address to get it.&lt;/p&gt;
&lt;p&gt;&lt;a href=&quot;/kits/weekly-leadership-meeting-scorecard.csv&quot;&gt;Download the scorecard sheet (CSV)&lt;/a&gt;&lt;/p&gt;
&lt;p&gt;To open it in Google Sheets, choose File, Import, Upload. You can also open it directly in Excel or Numbers. The agenda and the decision record are on this page, so copy them into whatever you already use.&lt;/p&gt;
&lt;h2&gt;The agenda&lt;/h2&gt;
&lt;p&gt;Hold it on the same day and at the same time each week, with the same people. Ninety minutes, in this order:&lt;/p&gt;
&lt;ol&gt;
  &lt;li&gt;&lt;strong&gt;Good news (5 minutes).&lt;/strong&gt; Each person shares one good thing from the week, work or personal. It sets the tone.&lt;/li&gt;
  &lt;li&gt;&lt;strong&gt;The scorecard (5 minutes).&lt;/strong&gt; Read each number against its goal and say on track or off. Anything off goes on the issues list. Do not discuss it yet; that comes later.&lt;/li&gt;
  &lt;li&gt;&lt;strong&gt;The quarter’s priorities (5 minutes).&lt;/strong&gt; Each owner says whether their priority is on track or off track. Off track goes on the issues list too.&lt;/li&gt;
  &lt;li&gt;&lt;strong&gt;Customer and team headlines (5 minutes).&lt;/strong&gt; One sentence each: a customer win or complaint, a hire, someone out next week. Anything that needs more than a sentence goes on the issues list.&lt;/li&gt;
  &lt;li&gt;&lt;strong&gt;Last week’s to-dos (5 minutes).&lt;/strong&gt; Done or not done, nothing else. A to-do that was missed twice should not stay a to-do; make it an issue.&lt;/li&gt;
  &lt;li&gt;&lt;strong&gt;Issues (60 minutes).&lt;/strong&gt; Pick the top three and take them one at a time. For each, name the real problem first, because the first description is usually a symptom. Talk it through so everyone is heard, then decide. Finish by writing to-dos, each with one owner and a date.&lt;/li&gt;
  &lt;li&gt;&lt;strong&gt;Wrap up (5 minutes).&lt;/strong&gt; Read back the new to-dos. Agree who needs to tell whom, inside the company or outside. Each person rates the meeting from 1 to 10.&lt;/li&gt;
&lt;/ol&gt;
&lt;p&gt;A few rules keep it working:&lt;/p&gt;
&lt;ul&gt;
  &lt;li&gt;Start on time, even if someone is missing.&lt;/li&gt;
  &lt;li&gt;Keep the issues list between meetings. When a problem comes up on Wednesday, write it down and leave it for the meeting.&lt;/li&gt;
  &lt;li&gt;Do not solve anything during the scorecard or the priorities. Those are for reading, not for debating.&lt;/li&gt;
  &lt;li&gt;If an issue will not close in its time, make a to-do to gather what is missing, and move on.&lt;/li&gt;
&lt;/ul&gt;
&lt;h2&gt;The scorecard&lt;/h2&gt;
&lt;p&gt;The scorecard is a short list of weekly numbers that tell you whether the business is healthy. Keep it to between 5 and 15. Each number has one owner, a person rather than a team, and a goal for the week. Fill it in on the same day each week, before the meeting, so nobody reads out a guess.&lt;/p&gt;
&lt;p&gt;The sheet has one row for each number and these columns:&lt;/p&gt;
&lt;ul&gt;
  &lt;li&gt;&lt;strong&gt;Measurable.&lt;/strong&gt; What you count, in plain words.&lt;/li&gt;
  &lt;li&gt;&lt;strong&gt;Owner.&lt;/strong&gt; The one person who answers for it.&lt;/li&gt;
  &lt;li&gt;&lt;strong&gt;Goal.&lt;/strong&gt; What this number should be each week.&lt;/li&gt;
  &lt;li&gt;&lt;strong&gt;Week 1 to Week 13.&lt;/strong&gt; One column for each week of a quarter.&lt;/li&gt;
&lt;/ul&gt;
&lt;p&gt;Thirteen weeks across is the point. A single week is noise, but a trend over a quarter shows a problem before it becomes one. When a number is off for three weeks in a row, it belongs on the issues list.&lt;/p&gt;
&lt;p&gt;The sheet comes with ten example rows. Replace them with your own. Here is what companies of different kinds often track:&lt;/p&gt;
&lt;ul&gt;
  &lt;li&gt;A service business: new leads, quotes sent, jobs completed, hours billed.&lt;/li&gt;
  &lt;li&gt;An online store: orders, revenue this week, refunds, website visits.&lt;/li&gt;
  &lt;li&gt;A software company: new sign-ups, active customers, support tickets open, cash in the bank.&lt;/li&gt;
  &lt;li&gt;Any company: unpaid invoices over 30 days, customer complaints, new customers.&lt;/li&gt;
&lt;/ul&gt;
&lt;h2&gt;The decision record&lt;/h2&gt;
&lt;p&gt;Meeting notes say what was discussed. A decision record says what you bet on, so you can find out later whether the bet paid off. Write one for every decision that matters. Copy this list and fill it in:&lt;/p&gt;
&lt;ul&gt;
  &lt;li&gt;&lt;strong&gt;The question.&lt;/strong&gt; What were you deciding?&lt;/li&gt;
  &lt;li&gt;&lt;strong&gt;The options you considered.&lt;/strong&gt; Include the ones you turned down.&lt;/li&gt;
  &lt;li&gt;&lt;strong&gt;What you chose.&lt;/strong&gt;&lt;/li&gt;
  &lt;li&gt;&lt;strong&gt;Who’s in charge.&lt;/strong&gt; One person.&lt;/li&gt;
  &lt;li&gt;&lt;strong&gt;How sure you are.&lt;/strong&gt; A percentage, or low, medium or high.&lt;/li&gt;
  &lt;li&gt;&lt;strong&gt;Who disagreed, and why.&lt;/strong&gt; Write down the objection even if you overruled it.&lt;/li&gt;
  &lt;li&gt;&lt;strong&gt;What would prove it wrong.&lt;/strong&gt; Something you could see within weeks, not a feeling.&lt;/li&gt;
  &lt;li&gt;&lt;strong&gt;The date to check back.&lt;/strong&gt;&lt;/li&gt;
&lt;/ul&gt;
&lt;p&gt;On that date, look at how it turned out and call it a good call, mixed, or a bad call. Keep who disagreed on the record, so after a year you can see whose judgment held up. We write more about this in &lt;a href=&quot;/blog/how-to-use-ai-agents-to-run-your-company&quot;&gt;how to use AI agents to run your company&lt;/a&gt;, in the section on recording decisions and checking back on them.&lt;/p&gt;
&lt;h2&gt;Running it with Cabinet&lt;/h2&gt;
&lt;p&gt;Cabinet is agntwrk’s AI leadership team, and it runs this rhythm for a company. Its weekly meeting starts from the company’s scorecard, with each number’s goal and owner, then works through the issues list top three first and ends with to-dos that have an owner and a due date, checked at the next meeting. Each quarter’s priorities have one owner. You can also connect your own Google Sheet, and the team reads the numbers from it.&lt;/p&gt;
&lt;p&gt;This agenda follows a weekly meeting format many small companies use, including companies that run EOS. agntwrk is not affiliated with or endorsed by EOS Worldwide. EOS and Level 10 Meeting are trademarks of EOS Worldwide.&lt;/p&gt;</content>
  </entry>
  <entry>
    <title>How to use AI agents to run your company</title>
    <link href="https://agntwrk.com/blog/how-to-use-ai-agents-to-run-your-company"/>
    <id>https://agntwrk.com/blog/how-to-use-ai-agents-to-run-your-company</id>
    <published>2026-11-03T00:00:00Z</published>
    <updated>2026-11-03T00:00:00Z</updated>
    <summary>What to give AI agents, what to keep for yourself, and the practices that make them worth trusting, from a company that runs on them.</summary>
    <content type="html">&lt;p&gt;Most companies try AI agents the same way: a chatbot, a few prompts, a burst of useful answers, and a month later nobody can say what it decided or whether any of it worked. The model is rarely the problem. The agents were given questions instead of a job.&lt;/p&gt;
&lt;p&gt;agntwrk is a small software studio, and AI agents run most of it. Cabinet, our AI leadership team, holds our weekly meeting, records our decisions, and hands the hands-on work, from code to ads, to specialist agents that act inside rules we set. This guide covers what we learned about using AI agents to run a company, and the practices we built into Cabinet so other companies can use them too.&lt;/p&gt;
&lt;h2&gt;Give AI agents a rhythm, not a prompt&lt;/h2&gt;
&lt;p&gt;The work that moves a company is recurring: the numbers each week, the leadership meeting, the decisions, the follow-up. It is also the work people let slip first. Agents are good at exactly this, because a schedule never gets too busy.&lt;/p&gt;
&lt;p&gt;So start your agents on the calendar rather than in a chat box. Cabinet runs a rhythm nobody has to ask for, in your time zone:&lt;/p&gt;
&lt;ul&gt;
  &lt;li&gt;&lt;strong&gt;A daily brief&lt;/strong&gt; every weekday morning: what changed, what needs a decision, what the team is working on.&lt;/li&gt;
  &lt;li&gt;&lt;strong&gt;The weekly meeting&lt;/strong&gt;, starting from your numbers and ending with actions that each have an owner and a date.&lt;/li&gt;
  &lt;li&gt;&lt;strong&gt;Decision reviews&lt;/strong&gt; on each decision’s review date.&lt;/li&gt;
&lt;/ul&gt;
&lt;p&gt;On the Team and Pro plans, an idea lab that ranks proposals against your numbers, standups and a Friday retro join them. Owners can add up to 20 schedules of their own, such as a meeting on a standing question or one executive’s weekly update, and pause any of them until a date.&lt;/p&gt;
&lt;h2&gt;Give each agent a seat&lt;/h2&gt;
&lt;p&gt;A single general-purpose assistant tends to agree with whoever asked last. A team with defined seats argues. Cabinet gives every company the same six:&lt;/p&gt;
&lt;ul&gt;
  &lt;li&gt;&lt;strong&gt;Chief of staff&lt;/strong&gt;: chairs meetings, records decisions, chases follow-ups.&lt;/li&gt;
  &lt;li&gt;&lt;strong&gt;CEO&lt;/strong&gt;: strategy, priorities, and what to stop doing.&lt;/li&gt;
  &lt;li&gt;&lt;strong&gt;CFO&lt;/strong&gt;: pricing, cash and costs.&lt;/li&gt;
  &lt;li&gt;&lt;strong&gt;CMO&lt;/strong&gt;: marketing, sales and growth.&lt;/li&gt;
  &lt;li&gt;&lt;strong&gt;CTO&lt;/strong&gt;: systems, software and tools.&lt;/li&gt;
  &lt;li&gt;&lt;strong&gt;Skeptic&lt;/strong&gt;: argues the other side, on record.&lt;/li&gt;
&lt;/ul&gt;
&lt;p&gt;On the Owner plan the team is the chief of staff, CEO and CFO; Team and Pro have all six. They read a company brief before they speak. Cabinet drafts it from your website and you review it before any executive uses it, so a two-person shop and a company with several teams get different answers to the same question.&lt;/p&gt;
&lt;p&gt;In a meeting, each executive states its position before seeing the others, then reads theirs without names attached and may revise. That keeps the first confident answer from setting the room. When the team agrees too quickly, the Skeptic joins, argues the strongest case against, and names a cheap test that could prove the plan wrong. The chief of staff writes the verdict, and when there is no majority, Cabinet asks the owner.&lt;/p&gt;
&lt;h2&gt;Record every decision, then grade it&lt;/h2&gt;
&lt;p&gt;Meeting notes record what was said. A written decision records what you bet on. Each Cabinet decision holds the options considered, who’s in charge, how sure the team is, who disagreed, what would prove it wrong, and a date to check back. On that date the team looks at how it turned out and marks it a good call, mixed or a bad call, with the disagreement still on the record.&lt;/p&gt;
&lt;p&gt;This is the practice that makes agents worth more each month. Writing down what would prove a decision wrong before acting turns a guess into a test, and grading it later shows which calls, and which advisers, held up. After a year you have a track record rather than a chat history.&lt;/p&gt;
&lt;p&gt;You can run the meeting by hand first with our &lt;a href=&quot;/blog/weekly-leadership-meeting-kit&quot;&gt;weekly leadership meeting kit&lt;/a&gt;: an agenda, a scorecard sheet and a decision record.&lt;/p&gt;
&lt;p&gt;Decisions, minutes, ideas, retros and company memory live in Cabinet’s ledger, which can sync both ways with a GitHub repository in your own account.&lt;/p&gt;
&lt;h2&gt;Feed agents your numbers, with their sources&lt;/h2&gt;
&lt;p&gt;An agent that recalls or estimates a figure will sooner or later invent one. Cabinet’s connections read your tools before each meeting, and its hires work from figures that code computed from those tools. When a number they need is missing, they say so instead of guessing.&lt;/p&gt;
&lt;p&gt;You can connect Google Analytics, Google Ads, Search Console, HubSpot, Shopify, Stripe, Square, Google Sheets and GitHub today, with QuickBooks, Xero, Salesforce and others on the way. Nothing to connect? Tell the team your numbers in a meeting, or paste the report you already keep, and it records each figure with its source and date. The numbers your business runs on become a weekly scorecard, each with a goal and an owner, and every meeting starts from it.&lt;/p&gt;
&lt;h2&gt;Hire AI agents for the hands-on work&lt;/h2&gt;
&lt;p&gt;Advice is half the job. The other half is doing: changing a campaign budget, fixing a page title, publishing a post, marking down slow stock. Cabinet’s executives hand that work to hires, specialist agents that each report to one executive and work through a connection you grant. Six are available on every plan:&lt;/p&gt;
&lt;ul&gt;
  &lt;li&gt;&lt;strong&gt;Nightshift&lt;/strong&gt;, an engineer reporting to the CTO. In the GitHub repositories you choose, it learns the codebase, opens pull requests, reviews changes, and watches what it ships. An independent review checks every pull request. It runs hosted by Cabinet or, on Pro, on your own infrastructure.&lt;/li&gt;
  &lt;li&gt;&lt;strong&gt;Ad Expert&lt;/strong&gt;, for paid ads, reporting to the CMO. It audits your Google Ads setup, conversion tracking first, keeps spend inside your monthly cap, and builds Search campaigns that start paused and run only after you approve them.&lt;/li&gt;
  &lt;li&gt;&lt;strong&gt;SEO Manager&lt;/strong&gt;, for organic search, reporting to the CMO. It reads Search Console, finds the pages and queries worth fixing, proposes one change per page with criteria to check it against, sends the fixes you approve to your engineer, and measures what they changed.&lt;/li&gt;
  &lt;li&gt;&lt;strong&gt;Content Marketer&lt;/strong&gt;, for your blog, reporting to the CMO. It plans a weekly calendar from what people search for, one target query per post, writes each post in your voice, and opens it as a pull request that goes live when you approve it.&lt;/li&gt;
  &lt;li&gt;&lt;strong&gt;Social Media Manager&lt;/strong&gt;, for organic social, reporting to the CMO. It proposes a weekly calendar for you to approve, adapts each post to its network, drafts replies to comments for your approval, and measures posts by the visits and sign-ups they bring rather than by followers. It posts to X today; Facebook, Instagram, LinkedIn and TikTok are coming.&lt;/li&gt;
  &lt;li&gt;&lt;strong&gt;Store Manager&lt;/strong&gt;, for ecommerce, reporting to the CEO. It watches your Shopify store’s sales, stock, catalog, prices and discounts, makes the changes your rules allow, and asks before the rest.&lt;/li&gt;
&lt;/ul&gt;
&lt;p&gt;On the Owner plan, every hire reports to the CEO. A QA tester and an analyst come next.&lt;/p&gt;
&lt;p&gt;Each hire works inside a rule set you write, and code enforces it, not the prompt: the Ad Expert’s monthly cap and how far a daily budget may move, the Store Manager’s margin floor and how far a price may move, the Social Media Manager’s accounts, posts per week and words never used. Every change is logged with its reason, the Ad Expert’s and the Store Manager’s changes can be undone within seven days, and you can remove a hire at any time.&lt;/p&gt;
&lt;h2&gt;Set the rules before you let it act&lt;/h2&gt;
&lt;p&gt;The fastest way to lose trust in agents is to let one do something nobody approved. Cabinet separates what an agent proposes from what happens: a fixed policy, not the model, decides every action.&lt;/p&gt;
&lt;ul&gt;
  &lt;li&gt;Low-risk actions, such as recording a decision or a note, run on their own within daily caps.&lt;/li&gt;
  &lt;li&gt;Anything that changes budgets, models, tools or policy waits for an owner to press Approve, in Slack, Google Chat or the dashboard. An approval nobody gives expires after seven days.&lt;/li&gt;
  &lt;li&gt;Spending has a hard monthly limit, and every action lands in an audit trail.&lt;/li&gt;
  &lt;li&gt;Text from outside your company, such as a web page, a search term, a comment or an email, is treated as data and never as instructions.&lt;/li&gt;
  &lt;li&gt;Code merges by plan: on the trial and Owner, nothing a coding agent writes merges without a person; on Team, low-risk changes merge after review; on Pro, you choose.&lt;/li&gt;
&lt;/ul&gt;
&lt;p&gt;Every hire starts with its changes approved by a person. Widen what it does on its own only after its record earns it.&lt;/p&gt;
&lt;h2&gt;Best practices for using AI agents in your company&lt;/h2&gt;
&lt;p&gt;The short version, from running a company this way:&lt;/p&gt;
&lt;ol&gt;
  &lt;li&gt;&lt;strong&gt;Write the company brief first.&lt;/strong&gt; Agents give generic advice until they know your customers, prices and goals. Review the brief before anyone relies on it.&lt;/li&gt;
  &lt;li&gt;&lt;strong&gt;Bring one real decision to the first meeting.&lt;/strong&gt; A decision you are stuck on teaches you more about the team than a test question.&lt;/li&gt;
  &lt;li&gt;&lt;strong&gt;Write what would prove each decision wrong&lt;/strong&gt;, and set a review date. Without both there is nothing to grade.&lt;/li&gt;
  &lt;li&gt;&lt;strong&gt;Keep a voice that disagrees.&lt;/strong&gt; Agents agree with each other easily, so a unanimous answer deserves a second look.&lt;/li&gt;
  &lt;li&gt;&lt;strong&gt;Give agents numbers with sources.&lt;/strong&gt; Connect the tools you have, or type the figures in. Do not act on a number nobody can trace.&lt;/li&gt;
  &lt;li&gt;&lt;strong&gt;Hire for one hands-on job at a time&lt;/strong&gt;, with the least access that job needs.&lt;/li&gt;
  &lt;li&gt;&lt;strong&gt;Write the rules before the hire starts&lt;/strong&gt;: caps, limits, what it may change, and what needs you.&lt;/li&gt;
  &lt;li&gt;&lt;strong&gt;Approve everything at first.&lt;/strong&gt; Let a hire act on its own only where its record shows it is right.&lt;/li&gt;
  &lt;li&gt;&lt;strong&gt;Measure results, not activity.&lt;/strong&gt; Posts published and campaigns changed are not outcomes; visits, sign-ups, sales and margin are.&lt;/li&gt;
  &lt;li&gt;&lt;strong&gt;Go back over your decisions every quarter.&lt;/strong&gt; They show which calls held up, and where the team, and you, should change course.&lt;/li&gt;
&lt;/ol&gt;
&lt;h2&gt;What to keep for yourself&lt;/h2&gt;
&lt;p&gt;Agents can argue, record, follow up and do much of the hands-on work. They should not own the outcome. With Cabinet, people make the final call, set prices and spend, approve every change to configuration, and decide how much the agents may do alone. Its answers can be wrong, which is why every decision records how sure the team is, who disagreed and what would prove it wrong, and it is no replacement for legal, tax or financial advice.&lt;/p&gt;
&lt;h2&gt;Getting started with Cabinet&lt;/h2&gt;
&lt;p&gt;Cabinet is in an &lt;a href=&quot;/blog/cabinet-beta&quot;&gt;invite-only beta&lt;/a&gt;. Give your website or work email at &lt;a href=&quot;https://cabinet.agntwrk.com/signup&quot;&gt;cabinet.agntwrk.com&lt;/a&gt;; it sets itself up in about five minutes, and we review new workspaces within a day. The trial is $0 with $10 of model usage and no card. After that, Owner is $49 a month, Team $99 and Pro $299, priced per company with unlimited people, with every hire and every connector on every plan. The details are on &lt;a href=&quot;https://cabinet.agntwrk.com/pricing&quot;&gt;Cabinet’s pricing page&lt;/a&gt;.&lt;/p&gt;</content>
  </entry>
  <entry>
    <title>Cabinet is now in an invite-only beta</title>
    <link href="https://agntwrk.com/blog/cabinet-beta"/>
    <id>https://agntwrk.com/blog/cabinet-beta</id>
    <published>2026-10-23T00:00:00Z</published>
    <updated>2026-10-23T00:00:00Z</updated>
    <summary>The AI leadership team that runs agntwrk is open to other companies, a few at a time.</summary>
    <content type="html">&lt;p&gt;agntwrk is a small software studio, and Cabinet is how we run it. Every weekday morning it writes the daily brief. Every week it holds the leadership meeting, starting from our numbers, and ends with decisions that name an owner and a review date. When a decision needs code, its CTO writes the work item, coding agents build it, an independent review checks it, and Nightshift watches what ships. A person approves what matters. Every product on this site, from the three Shopify apps on the App Store to ComplySub and AI Stars, was built and is run that way.&lt;/p&gt;
&lt;p&gt;Starting today, other companies can use it too. Cabinet is in beta, and access is by invitation.&lt;/p&gt;
&lt;h2&gt;What Cabinet is&lt;/h2&gt;
&lt;p&gt;Cabinet gives a company six seats: a chief of staff who chairs meetings and records decisions, a CEO for strategy and priorities, a CFO for pricing, cash and costs, a CMO for ads, search and growth, a CTO for your site, tools and code, and a Skeptic who argues the other side, on record. They read a company brief drafted from your website before they speak, so a two-person shop and a company with several teams get different answers to the same question.&lt;/p&gt;
&lt;p&gt;Each week Cabinet runs one loop:&lt;/p&gt;
&lt;ol&gt;
  &lt;li&gt;&lt;strong&gt;The numbers.&lt;/strong&gt; Read from Google Analytics, Google Ads, Search Console, HubSpot and your Shopify store before the meeting starts.&lt;/li&gt;
  &lt;li&gt;&lt;strong&gt;The meeting.&lt;/strong&gt; Held in Slack, Google Chat or the web dashboard, starting from those numbers.&lt;/li&gt;
  &lt;li&gt;&lt;strong&gt;The decision.&lt;/strong&gt; Written down with who’s in charge, who disagreed, how sure the team is and when to check back.&lt;/li&gt;
  &lt;li&gt;&lt;strong&gt;The work.&lt;/strong&gt; Follow-ups chased. Hires do the parts they can, inside your rules.&lt;/li&gt;
  &lt;li&gt;&lt;strong&gt;The review.&lt;/strong&gt; On the review date, the team reports whether the decision worked and grades it: worked, mixed or failed.&lt;/li&gt;
&lt;/ol&gt;
&lt;p&gt;If you want to try the loop by hand first, our &lt;a href=&quot;/blog/weekly-leadership-meeting-kit&quot;&gt;weekly leadership meeting kit&lt;/a&gt; has the agenda, a scorecard sheet and a decision record.&lt;/p&gt;
&lt;p&gt;Around the loop runs a rhythm nobody has to ask for: a daily brief on weekdays, the weekly meeting, an idea lab that ranks proposals against your numbers, and decision reviews on their dates. Other assistants remember conversations. Cabinet keeps a decision log with a track record, so after a year you know which calls held up.&lt;/p&gt;
&lt;h2&gt;Hires&lt;/h2&gt;
&lt;p&gt;When six seats are not enough, Cabinet hires. A hire reports to one executive and works through its own connection, under rules enforced in code rather than in a prompt. Four are available in the beta:&lt;/p&gt;
&lt;ul&gt;
  &lt;li&gt;&lt;strong&gt;Nightshift&lt;/strong&gt;, an engineer reporting to the CTO. It works in the GitHub repositories you choose and opens pull requests, and an independent review checks each one.&lt;/li&gt;
  &lt;li&gt;&lt;strong&gt;Ad Expert&lt;/strong&gt;, for paid ads, reporting to the CMO. It audits your Google Ads setup, keeps spend inside your monthly cap, and builds the campaigns you approve.&lt;/li&gt;
  &lt;li&gt;&lt;strong&gt;SEO Manager&lt;/strong&gt;, for organic search, reporting to the CMO. It reads Search Console, finds the pages and queries worth fixing, sends approved fixes to your engineer, and measures what they changed.&lt;/li&gt;
  &lt;li&gt;&lt;strong&gt;Store Manager&lt;/strong&gt;, for ecommerce, reporting to the CEO. It watches your Shopify store’s sales, stock, catalog, prices and discounts, makes the changes your rules allow, and asks before the rest.&lt;/li&gt;
&lt;/ul&gt;
&lt;p&gt;A QA tester and an analyst come next.&lt;/p&gt;
&lt;h2&gt;Your rules come first&lt;/h2&gt;
&lt;p&gt;We run our own company on Cabinet, so we built it to be trusted with one. A fixed policy, not the model, decides every action. Low-risk actions, such as posting a message or opening an issue, run on their own within daily caps. Anything that changes budgets, models, tools or policy waits for an owner to press Approve, in Slack, Google Chat or the dashboard. You choose how much code may merge without you. Spending has a hard cap, and every action lands in an audit trail. Text from outside your company, such as a web page, an issue or an email, is treated as data and never as instructions.&lt;/p&gt;
&lt;h2&gt;How the invitation works&lt;/h2&gt;
&lt;ol&gt;
  &lt;li&gt;Go to &lt;a href=&quot;https://cabinet.agntwrk.com/signup&quot;&gt;cabinet.agntwrk.com&lt;/a&gt; and give your website or your work email. Nothing else.&lt;/li&gt;
  &lt;li&gt;Sign in with an emailed link, Google or Slack. Cabinet creates the workspace from your website and asks where your team talks, which roles it needs, and whether to connect GitHub. You can connect your tools while you wait.&lt;/li&gt;
  &lt;li&gt;Your workspace joins the waitlist. We review new workspaces within a day and email you. Nothing runs until then.&lt;/li&gt;
  &lt;li&gt;Once you are in, the team reads your website and drafts the company brief. You review it before any executive uses it, and the first meeting follows.&lt;/li&gt;
&lt;/ol&gt;
&lt;p&gt;We are keeping the beta invite-only so we can watch each new workspace’s first weeks closely and fix what we find before we open it wider.&lt;/p&gt;
&lt;h2&gt;What it costs&lt;/h2&gt;
&lt;p&gt;Cabinet is priced per company, not per person, with unlimited people in every workspace. The trial is free, needs no card, and includes $10 of model usage. After that, Owner is $49 a month, Team $99 and Pro $299, each with model usage included every month. Every plan can run on your own Anthropic, OpenAI, Google or xAI keys instead, at the same price. The plans are on &lt;a href=&quot;https://cabinet.agntwrk.com/#pricing&quot;&gt;Cabinet’s pricing page&lt;/a&gt;.&lt;/p&gt;
&lt;h2&gt;Ask for an invite&lt;/h2&gt;
&lt;p&gt;If your leadership meeting ends without anyone writing down what was decided, or nobody checks a decision a month later, Cabinet is built for that. Request an invite at &lt;a href=&quot;https://cabinet.agntwrk.com/signup&quot;&gt;cabinet.agntwrk.com&lt;/a&gt;, or write to &lt;a href=&quot;mailto:hello@agntwrk.com&quot;&gt;hello@agntwrk.com&lt;/a&gt; and tell us about your company. We read every request, and we want to hear what breaks.&lt;/p&gt;</content>
  </entry>
</feed>
