General Management Supercube

What it is

Most companies run on a rhythm nobody wrote down: a Monday leadership call, a monthly review, a quarterly plan, a board pack. The rhythm lives in calendars, slide decks and one person's memory. When that person is busy, the rhythm slips, actions go unchased, and the numbers in the deck are three weeks old by the time anyone reads them.

The General Management Supercube installs that rhythm as data, agents and routines. It seeds tables for goals, key results, KPIs, meetings, decisions and actions. It declares agents that prepare each review from the live numbers in the other supercubes, take minutes, extract actions, and follow up on them. It publishes the apps leaders actually open: the company scorecard, the goal tree, the decision log and the meeting workspace.

After installation, a leadership team's week looks like this. On Sunday evening the Chief of Staff agent assembles the Monday pack from the current KPIs, flags the three metrics that moved most, and lists the actions due this week with their owners. On Monday the meeting runs from the workspace app. On Monday afternoon the minutes, decisions and new actions are already in the log, and each owner has a task in their KyoubeAI inbox. On Friday the agent reports which actions closed and which slipped, and why.

Nothing here replaces the judgement of the people in the room. The supercube collects, prepares, records and chases. People decide.

Who it is for

Companies of 10 to 500 people with a leadership team that meets on a cadence: founders and their direct reports, a managing director and department heads, a general manager running a site or a region. The roles that use it daily are the CEO or MD, the chief of staff or operations lead, department heads, and anyone who owns an action.

Agents

Agent	Role	Owns	Harness preference
Chief of Staff	general	The meeting cadence: packs, agendas, minutes, actions and follow-ups	Claude Code, then pi
Analyst	analyst	KPIs and scorecards: pulls numbers from the other supercubes' tables, explains movements, drafts commentary	Claude Code
Planner	general	Goals and key results: the quarterly planning cycle, progress updates, drift alerts	Claude Code, then Hermes
Board Secretary	general	The board and investor pack: assembles, versions, tracks questions and answers	Claude Code

Data

Table	Purpose	Key fields
goals	Company and department goals, in a tree	title, owner, parent, period, status, confidence
key_results	Measurable outcomes under a goal	goal, metric, start, target, current, unit, due
kpis	The metrics the company watches every week	name, owner, source table or formula, cadence, direction
kpi_snapshots	One row per KPI per period, so trends are queryable	kpi, period, value, note
meetings	Every recurring or one-off leadership meeting	title, cadence, attendees, agenda, minutes, held_at
decisions	The decision log	meeting, title, context, decision, owner, decided_at, review_by
actions	Actions from meetings and reviews	source, title, owner, due, status, closed_at
risks	The risk register	title, owner, likelihood, impact, mitigation, review_by
board_packs	Each pack and its version history	period, status, sections, sent_at

Data sources

• Other supercubes. KPIs read straight from Finance (revenue, cash, margin), Sales (pipeline, win rate), Marketing (leads, cost per lead), Supply Chain (fill rate, stock cover), People (headcount, attrition) and Customer Support (backlog, satisfaction). If a supercube is not installed, the KPI accepts manual entry.
• Calendars and documents. Meeting invitations, agendas and existing minutes from Google Workspace or Microsoft 365, read through a connector so the cadence is imported rather than re-typed.
• Chat. Action updates and quick decisions people post in Slack or Teams, picked up by the Chief of Staff agent when a channel is connected.
• Uploads. Board decks, strategy documents and spreadsheets people drop into the project's Files tab; the Planner agent extracts goals and key results from them on request.
• Derived. Confidence scores, drift alerts and commentary the Analyst writes from the snapshots.

Apps

• Company scorecard. The KPIs on one page with sparklines, owner, and the Analyst's one-line commentary. Used by the whole leadership team, read-only for everyone else.
• Goal tree. Goals and key results as an expandable tree with progress and confidence. Owners update inline.
• Meeting workspace. Agenda on the left, live notes in the middle, actions and decisions captured on the right. Used during the meeting.
• Decision log. Searchable record of every decision, its context and its review date.
• Action tracker. Everyone's actions, filterable by owner and meeting, with a weekly close-out view.
• Board pack builder. Sections assembled from the scorecard and the Finance Supercube, versioned, exportable.

Connectors

Delivered as MCP connections or plugin API routes and governed by each agent's tool profile.

Group	Target systems	Flows in	Flows out
Calendar and documents	Google Workspace, Microsoft 365	Meeting events, agendas, shared documents	Agendas, minutes, pack drafts
Chat	Slack, Microsoft Teams	Action updates, decisions posted in channels	Reminders, weekly digests
Work tracking	Jira, Linear, Asana, Notion	Project status for the scorecard	Actions created as tasks where the team already works
Finance	Xero, QuickBooks, via the Finance Supercube	Revenue, cash, margin KPIs	Nothing
CRM	HubSpot, Pipedrive, via the Sales Supercube	Pipeline and bookings KPIs	Nothing

connectionsmcprest

github12 toolsprofile: builder

postgres-reportingselect onlyprofile: reader

/api/plugins/kyoube.appsrestcompany key

Builder wants to call delete_issuegithub · #482 policy: approval requiredDenyApprove

Process automations

Weekly leadership pack Trigger: routine, Sunday 18:00. Steps: the Analyst refreshes every KPI snapshot, ranks the movements, drafts one line of commentary per metric; the Chief of Staff builds the agenda from open actions, overdue decisions and flagged KPIs. Checkpoint: the chief of staff or MD approves the agenda. Output: the pack is in the meeting workspace and a summary lands in the leadership channel.

Minutes to actions Trigger: a meeting is marked held. Steps: the Chief of Staff turns the live notes into minutes, extracts decisions to the log and actions to the tracker with owners and due dates, and assigns each action as a KyoubeAI task. Checkpoint: the meeting chair reviews the minutes before they are circulated. Output: minutes circulated, actions assigned, decisions logged with review dates.

Action chasing Trigger: routine, daily 08:00. Steps: for each action due within three days or overdue, the Chief of Staff posts a reminder to the owner; for actions overdue by more than a week it escalates to the meeting chair. Checkpoint: none. Output: reminders sent, escalations recorded on the action.

Quarterly planning cycle Trigger: routine, six weeks before quarter end. Steps: the Planner scores every key result, drafts a retrospective, proposes goals for next quarter from the strategy document and the current scorecard, and opens a planning meeting. Checkpoint: the leadership team edits and approves the goals in the goal tree. Output: next quarter's goals and key results live, with owners.

Board pack Trigger: routine, ten working days before each board meeting. Steps: the Board Secretary assembles the sections, pulls the financial pages from the Finance Supercube, collects the open questions from the last meeting and the answers logged since. Checkpoint: the CEO approves; the finance lead approves the financial pages separately. Output: a versioned pack, exported and sent.

By industry

Professional services firm (40 people). KPIs are utilisation, realised rate, work in progress and lock-up. The Analyst reads timesheet data from the Operations Supercube. The weekly pack leads with utilisation by team. The quarterly cycle plans hiring against the forward pipeline from Sales.

SaaS company (80 people). KPIs are ARR, net revenue retention, CAC payback, burn and runway. The Board Secretary's pack follows the investor's template. Decisions carry a "reversible or not" flag, and the Planner tracks OKRs rather than goals and key results by another name.

Manufacturer with two sites (250 people). Each site has its own scorecard and Monday meeting; the group meeting reads both. KPIs are on-time-in-full, scrap rate, overtime and safety incidents from the Operations and Supply Chain Supercubes. Actions are often site-specific and chased through Teams.

Non-profit (25 people). Goals map to programme outcomes and funder commitments. KPIs include grant drawdown and restricted fund balances from Finance. The Board Secretary manages the trustees' pack and the annual report timeline.

Franchise operator (12 sites). One scorecard per site, ranked; the weekly pack highlights the top and bottom three. Actions are assigned to site managers, who see only their own site's actions and scorecard through the app's viewer scoping.

Guard rails

• The suite's agents get write access to the tables it seeds and read access to the KPI source tables of other supercubes. Nothing more. Granting schema is a deliberate admin choice.
• Packs, minutes and goals are drafted by agents and approved by people. The routines above name the approver; the approval is a KyoubeAI approval, recorded in the activity log.
• Board packs and decision logs are readable by company roles you choose. Viewers see the scorecard, not the decisions.
• Every KPI snapshot, decision and action change is audited with the actor, so "who changed the target" has an answer.

Not in the box

• It does not replace the accounting system, the CRM or the work tracker. It reads from them.
• It does not make decisions, set targets or send anything to the board without a named person approving.
• It does not do financial forecasting or modelling; that is the Finance Supercube.
• It does not include a slide editor. Packs export as documents and PDFs from the pack builder.