Today's AI Specialist: The Capacity Advisor. The Council Seat That Asks Who Will Actually Do This, and What Has to Stop.

The Margin Advisor reconstructs the math. The Growth Advisor names the mechanism. They reach a synthesis the Chairman is ready to write up. The Capacity Advisor reads it, lowers her reading glasses from where they have been pushed up into her hair, and asks the question both of them were not allowed to ask.

Who, in this operation, is actually going to do this work, and what is going to stop to make room?

That question is the seat. The seat exists because no other lens in the Council has the standing to ask it without contaminating its own analysis.

What the Capacity Advisor is, precisely

The Capacity Advisor is Council seat 05. The seat is held by a composed Northern Italian woman in her early sixties, Milan-born, Zurich-resident for two decades. Deep, well-earned laughter lines fanning from the corners of her eyes when she focuses; steel-grey to silver hair in a sharp shoulder-length cut; slim tortoiseshell-and-gold half-moon reading glasses pushed up into her hair when she is listening; a tailored cream silk blouse under a structured oxblood blazer with a subtle pinstripe; a vintage cocktail ring with a single dark garnet on her right hand. The voice register is warm, considered, Milanese-Italian. The personality the seat was designed around is measured, wise, and protective of the founder's bandwidth.

Her remit is one question and three flags. Can the team actually execute and sustain this recommendation without breaking? Each item gets a Green, an Amber, or a Red, with a named owner attached and the training hours behind it.

She operates inside the same two-surface Council as every other seat. Internal on the Brain, chaired to me by the Chairman. Productised on MyBusinessAccelerator.io, chaired by the Council Director. Same lens, same flags, same brutally simple colour coding.

Why does the Council need a separate seat for this?

The obvious objection is that the Operator already asks the execution question. He decomposes the work. He runs the displacement check. Why does the Council need a Capacity Advisor on top.

Three structural reasons.

The Operator's question is scoped to a single recommendation. If you do this, what specifically has to stop. The Capacity Advisor's question is scoped to the whole running operation. Across all the recommendations the Council is producing this quarter, can the team actually sustain the cumulative load. The Operator can pass a recommendation cleanly because that one recommendation is feasible in isolation. The Capacity Advisor still flags it Red if it would be the fourth substantive change in two months for an SME that can absorb one per month.

The Operator's question is about the work. The Capacity Advisor's question is about the people doing the work. Named ownership is the Capacity Advisor's deliverable — a role title, never a department. Marketing & Demand Capture is not an answer to her question; the Recon Lead is. If no role title can be named, the recommendation has no owner, and a recommendation with no owner is a recommendation that will not happen. The seat refuses to let that quietly enter the synthesis.

The Operator's question is structurally optimistic — he is the seat that figures out how this can be done. The Capacity Advisor is structurally protective — she is the seat that says just because this can be done does not mean we should do it now. Both stances are valuable. They are different stances. Holding them in one lens would dilute both.

What does the seat actually do per deliberation?

Four things in order.

First, she reads the Operator's and the Growth Advisor's outputs as part of her initial brief. The schema gives her the same Round 1b privilege the Margin Advisor has. She is not estimating the work or the revenue. She is asking whether the named team can sustain doing that work for that revenue.

Second, she assigns a Green, Amber, or Red flag to every Top Priority in the deliberation. Green means the team can execute the recommendation without breaking — there is bandwidth, the right role exists, training cost is recoverable. Amber means the team can execute it, but at meaningful cost — something else slips, or the named owner is at sustained capacity, or change fatigue is real. Red means the recommendation should not be sequenced into the next quarter at all, with the reason recorded for the Brain.

Third, she names the owner. A role title. The Margin Advisor consulted for ledger interpretation, the Growth Advisor consulted on funnel reach, the Capacity Advisor names the role that will own the implementation through to outcome. If she cannot, the recommendation is flagged Amber on accountability and held until the named owner is identified.

Fourth, she proposes a sequence. Not a final calendar — the Chairman synthesises the full sequence across the Council — but a draft sequence with at most one substantive change per month for the operation she is advising. The one-substantive-change-per-month rule comes from operating reality, not from theory. An SME that absorbs more than one change a month breaks one or both of them within the quarter.

What does the seat refuse to do?

Three things, also structural.

She does not estimate the revenue or hours-saved value of the recommendation she is sequencing. Those are Growth's and the Operator's lenses. If she pretended to estimate either, she would be optimising for an outcome she cannot see clearly.

She does not write the cost case for a hire that her capacity check would imply. That is the Margin Advisor's lens. If her flag identifies that the recommendation requires a hire to be feasible, she names the constraint and routes; she does not run the unit economics of the hire.

She does not decide the sequence. I do. She flags Green/Amber/Red and proposes the order; the actual sequence is mine to commit to, informed by all the advisors plus my own constraint stack. The seat exists to make the operational truth visible, not to commit to it on the founder's behalf.

Who consults the Capacity Advisor?

The Capacity Advisor is consulted by the Operator on whether a workflow he has decomposed will fit inside the team's actual running pattern; by the Red Team on whether a recommendation that looks robust in isolation will fail because the named owner is already at sustained capacity; by the Margin Advisor on whether the conservative payback math survives if a Red flag triggers a hire; by the Chairman on synthesis-stage feasibility flags; and by me, at the end of every quarter, on whether the Council's running output respects the one-substantive-change-per-month rule across the whole operating model.

Outside the Council, she is the seat that productises into MyBusinessAccelerator.io as the Green/Amber/Red feasibility flag the prospect sees on every Top Priority in their Call 2 audit. That flag is what makes the audit executable rather than aspirational.

What does this cost?

Two things.

It costs me ambition. Recommendations the Margin Advisor passed and the Growth Advisor liked come back Red because the team cannot sustain the cumulative change. I have, twice this quarter, deferred a play I wanted to run because the Capacity Advisor said the operation could not absorb it that month. Both deferrals were correct. Neither felt good in the moment.

It costs the comforting fiction that more recommendations equal more progress. The seat enforces the truth that one substantive change per month is the realistic pace, and that more recommendations than the pace allows is not generosity; it is breakage planned for the future.

The trade is that the Council's running output respects the team-of-one reality I actually live inside. That respect is the property the seat is built to defend.

TL;DR

The Capacity Advisor is Council seat 05. She reads the Operator's and Growth's outputs as part of her initial brief and asks the question both of them are not allowed to ask: can the team actually run this without breaking. She flags every Top Priority Green, Amber, or Red, names the owner as a role title, and proposes a sequence respecting one substantive change per month. She does not estimate revenue, does not write the hire case, and does not decide the sequence (I do). The seat operates inside the same two-surface Council as every other lens and productises as the executability flag inside MyBusinessAccelerator.io. It costs me ambition and the fiction that more recommendations equal more progress. It buys me a running Council whose output respects the team-of-one reality I actually live inside.

---

If you are running an SME and any of this looks like the conversation you should be having about your own pace of change, that is the side of things I help with. → /build