The Chief of Staff's AI Toolkit: 6 Steps to Run a Tighter Ship with Half the Overhead

The most fundamental information problem in any growing company is the gap between what's happening in each function and what the leadership team collectively knows. Here's the structural fix.

Yesterday: Each department sends a weekly update in whatever format feels natural to that department head. Some are narrative emails. Some are bulleted lists. Some are slide decks. The CoS compiles them into a synthesized brief by hand: 4 to 6 hours of work every week that is purely mechanical aggregation with no analytical value-add.

Today: Each functional lead submits a structured weekly input using a standardized template: key metrics (mandatory), decisions needed (mandatory), risks flagged (mandatory), notable wins (optional), next week priorities (optional). Peripheral ingests all functional inputs simultaneously, cross-references them for dependencies and compounding risks, and generates a single prioritized executive brief. The CoS reviews and calibrates the output rather than constructing it from scratch adding the organizational context and judgment that only they can provide.

Tomorrow: Peripheral learns which functional signals matter most to the CEO over time, automatically adjusting the emphasis and priority ranking of the weekly executive brief without any reconfiguration from the CoS.

Tools: Notion  ·  Airtable  ·  Peripheral Metrics + Insights

The quarterly OKR review is theoretically one of the most valuable management rituals in a growth-stage company. In practice, it's one of the most dreaded. Here's how to make it the former.

Yesterday: Someone compiles OKR status by pulling data from half a dozen source systems, translating quantitative data into a coherent picture, and formatting it into a presentation that shows which OKRs are on track. This compilation work consumes the better part of a day every week during the OKR reporting period, and it's pure aggregation, requiring zero judgment.

Today: Key results are connected to source systems: revenue KRs pull from Salesforce, product KRs pull from Jira, people KRs pull from Lattice. Peripheral computes current performance against targets automatically and generates the weekly status view. The CoS's role shifts from building the status report to interpreting it: which OKRs are at risk, why, and what intervention would most improve the trajectory.

Tomorrow: Peripheral monitors OKR progress continuously throughout the quarter, proactively flagging at-risk key results the moment the trajectory makes the target unlikely, rather than waiting for the weekly status cycle to surface the problem.

Tools: Salesforce  ·  Jira  ·  Lattice  ·  Peripheral Metrics

Meetings in most organizations are underprepared, under-facilitated, and under-documented. The CoS is responsible for fixing all three. Here's the system that does it.

Yesterday: Meeting preparation is inconsistent: some get a pre-read, most don't. Note-taking is fragmented: the person assigned writes what they catch, missing the context of the decisions. Follow-through is informal: action items are verbally assigned, remembered with varying reliability, and completed with varying accountability.

Today: Pre-meeting: Peripheral generates a structured brief from past meeting notes, CRM context, and company data, available to all participants 24 hours before. During: AI note-takers (Granola or Fireflies) capture decisions, commitments, and unresolved questions, with the transcript summary auto-forwarded to the relevant Peripheral workspace. Post-meeting: Peripheral extracts action items and routes them to owners via the project management system with due dates and context. Every meeting brief is automatically enriched by what was committed to in the previous one.

Tomorrow: Peripheral generates pre-meeting briefs automatically for every scheduled leadership meeting, pulls outstanding action items from prior sessions, and flags any unresolved commitments that need to be addressed before the conversation begins.

Tools: Fireflies.ai  ·  Granola  ·  Notion  ·  Peripheral Insights

The quarterly board cycle is one of the most predictable recurring events in a growth-stage company. It's also, for most, a chaotic last-minute scramble. Predictable + chaotic = a process problem, not a workload problem.

Yesterday: Board prep starts 2 weeks before the meeting when the CoS sends a reminder. Department heads submit inputs 3 days before the deadline. The CFO finishes the financial package the day before. The CEO stays up finalizing the deck the night before. Every quarter, the same scramble.

Today: The 8-week board cycle: 8 weeks before: templates and timeline distributed to all department heads. 6 weeks before: first drafts due. 4 weeks before: CFO financial package first draft. 3 weeks before: CEO editorial pass. 2 weeks before: Peripheral generates the intelligence brief: board questions anticipated, key metrics narrative drafted, and strategic talking points surfaced from the quarter's accumulated data. 1 week before: deck finalized. Day before: CEO and CFO run final preparation from the Peripheral brief. Predictable, professional, and calm.

Tomorrow: Peripheral manages the board cycle timeline autonomously, sending structured input requests to department heads at the right intervals, tracking submission status in real time, and alerting the CoS only when a deadline is at risk rather than requiring manual follow-up throughout the cycle.

Tools: Notion  ·  Google Slides  ·  Peripheral Fortress + Insights

The most dangerous risks in a growing company don't appear in any single functional report. They live in the seams between functions. The CoS is the only person positioned to see them. Here's the system that makes it systematic.

Yesterday: Cross-functional risks are identified anecdotally when two department heads happen to mention related issues in the same all-hands, or when the CEO notices a pattern across separate conversations. By the time the pattern is visible, the risk has often compounded into a problem that's harder to address.

Today: Weekly functional briefings are ingested into Peripheral, which cross-references inputs across all functions simultaneously for dependencies and compounding risks. When a sales pipeline softness and a product delay appear in the same update period (or when a burn rate overrun and a planned hiring spree coincide) Peripheral surfaces these connections automatically. The CoS makes the judgment call: coincidence or compounding risk requiring leadership escalation.

Tomorrow: Peripheral monitors cross-functional dependencies continuously, surfacing compounding risks the moment two or more functional signals align rather than waiting for the weekly briefing synthesis to identify the connection.

Tools: Peripheral Projects + cross-Space queries  ·  Slack (async signals)  ·  Linear / Jira

A new executive needs 6 to 12 months to become fully effective. Most of that timeline is context-building that could be delivered in 6 weeks with the right infrastructure.

Yesterday: New executives build context through conversations, reading whatever documentation they can find, and learning by doing which means learning by making some decisions with incomplete information. The first 6 months are productive but slower and riskier than they need to be. The organizational knowledge that would help them isn't accessible. It's in people's heads.

Today: Build a structured onboarding context package for each new executive hire using Peripheral Fortress as the source: the most important strategic documents, board presentations, customer insights, functional history, and open decisions organised by topic and annotated with organizational context. The context package is a live Peripheral workspace the new executive can query directly: rather than reading through hundreds of documents, they ask questions and receive synthesised answers drawn from the full body of the company's institutional knowledge.

Tomorrow: Peripheral serves as the company's permanent institutional memory layer, continuously enriching the knowledge base as new decisions are made and new context is accumulated, so that every future onboarding package is more complete than the last one.

Tools: Loom · Notion · Peripheral Fortress