For readers with four minutes, the whole argument:

•  The structure around a principal is a design decision, not a maturity ladder. What an executive needs beside them is a function of how the organization around them is built. One support hire and eight can both be right.

•  Every support seat maps to one of five layers: Readiness, Leverage, Synthesis, Narrative, Continuity. Hire against layers, not titles. "We need a Chief of Staff" is a guess wearing a job title.

•  Offices fail at the seams, not the seats. Nearly every dysfunctional office has good people in it. The failure is unwritten scope: an EA drifting into Chief of Staff work, two EAs colliding over territory, two senior operators circling the same mandate.

•  The five configurations in this paper run from $130K to $6M+ a year, fully loaded. The right one depends on your constraint: complexity, coverage hours, decision throughput, or cognitive load. Adding a body to the wrong layer buys more of the wrong thing.

•  The three most expensive mistakes: letting your EA become a part-time Chief of Staff by accretion, running multiple EAs without sentence-level scope, and leaving a single point of failure unpriced until the resignation letter arrives.

The rest of this paper is the detail: what each configuration looks like, what it costs, how it breaks, and how to hire for it.

A note on the numbers. We work at the top of the market, and the figures in this paper reflect that. Compensation and budget ranges are drawn from the sectors where pay runs highest: large public companies, elite financial institutions, well-funded startups and scale-ups, and family offices, concentrated in high-cost-of-living markets such as California, New York, Texas, and Connecticut. Outside those environments, expect meaningful discounts. Inside them, expect these numbers to be real.

The problem nobody designs for

The structure around a principal is a design decision, and it is usually the least designed part of any organization. Most support structures are archaeology, not architecture: an EA hired in year two, a Chief of Staff added after a burnout scare, a second assistant when travel got heavy, a comms lead after a bad press cycle. Nobody asked what the office is for.

There is no correct headcount. Two CEOs of comparable companies can run radically different offices and both be right, because what an executive needs beside them is a function of how the organization around them is built: how senior and self-managing the executive team is, where leverage sits, how much inbound has to be synthesized, how much of the schedule is coverage. A principal whose direct reports absorb the coordination load needs a fraction of the office required by one who is the sole synthesizer of everything upstream. The question is never "how big should my office be." It is "which work needs to sit near me, and in whose hands."

The cost is invisible on a P&L. It looks like a principal triaging their own inbox on Sunday night. A $250,000 Chief of Staff managing a calendar. Two capable EAs quietly at war over ambiguous territory. Decisions queuing behind one overloaded gatekeeper. The best operator in the building leaving because the role they were sold isn't the role they got.

What follows: five configurations, with the strengths, failure modes, hiring realities, and budgets for each. Read it before your next support hire, not after.

Every support function around a principal maps to one of five layers. Configurations differ only in which layers they staff, how heavily, and who owns each one. Once you see the layers, you can diagnose any office in ten minutes.

1. Readiness. The who, what, where, and why. Calendar, travel, correspondence triage, meeting preparation, follow-up capture. Dismissed as "admin," it is the layer that decides whether a principal's day compounds or leaks. A principal fifteen minutes behind and under-briefed by 10am stays that way until midnight.
2. Leverage. The secondary responsibilities the principal owns but shouldn't personally execute: cross-functional projects, board preparation, operating cadence, follow-through on decisions made. Chief of Staff territory. Done well, it converts the principal's judgment into throughput without consuming their hours.
3. Synthesis. Compressing inbound information into decision-ready form: briefing packs, pre-reads, "here are the three options and here's what I'd do." Folded into other seats at small scale; a standalone analyst function at large scale.
4. Narrative. What the organization and the world hear from and about the principal. Absent by design in small offices; a structural necessity once the principal is the brand.
5. Continuity. The office's ability to survive its own turnover, and, at its most sophisticated, to export people. A rotational Chief of Staff program is a continuity mechanism in reverse: it pushes knowledge of how the principal thinks out into the business, inside a person.

Two rules follow, and they govern everything else in this paper.

Hire against layers, not titles. "We need a Chief of Staff" is not a requirement. The requirement is "our Readiness layer is saturated and Leverage work is being done by the principal at 11pm." Different diagnosis, sometimes a different hire.

Offices fail at the seams, not the seats. Almost every dysfunctional office we've been asked to fix had good people in it. The failure was in the boundaries between them. Scope is not bureaucracy. Scope is what lets serious people run hard in their own lane without checking their shoulder.

Principal + one Executive Assistant operating above their title

More common at the top of the market than people assume. One C-suite principal, one exceptional EA, nothing else. The EA owns Readiness completely and crosses into CoS-lite territory: discrete projects, ad-hoc requests, first filter on inbound, judgment calls made without escalating.

How work flows

Everything routes through one person. No handoff loss, because there are no handoffs. The model works where the principal's direct reports are genuinely senior and self-managing: the Leverage layer is distributed into the line, not centralized in an office.

How decisions get made

Fast, and by the principal. The EA shapes the queue: what arrives, in what order, with what framing. More decision influence than most org charts admit. But the deciding is undelegated.

Managing down

Near zero. One relationship, high trust, low process. Also the quiet dependency: the entire system is one person's calendar, one person's health, one person's decision to stay.

Strengths

Speed. Total context in one head. No internal politics. The cheapest configuration by an order of magnitude. When the EA is elite, principals call this the best support they've ever had, because there is nothing between them and execution.

Weaknesses and failure modes

Three, all structural. Ceiling: the model fails gradually, then suddenly, when complexity exceeds one person's bandwidth. The tell is project work crowding out Readiness: under-prepped meetings, slipping follow-ups. The EA is the last to admit it, because admitting it feels like failure. Key person risk: no redundancy. A resignation or a sick month takes the operating system down. Title drift without recognition: an EA doing CoS-lite work on an EA package will eventually be recruited by someone who names the job honestly. We know. We're often the ones calling.

Hiring reality

The hardest single hire in the support market. You are buying judgment, discretion, and project capability in a market that prices those as separate roles. The candidates who can do it are rare, know it, and are almost never actively looking. Pay for the job being done, not the title on the door. The strong end of the market clears $150,000-$250,000 total. At the largest public technology companies, where equity is a real part of EA packages, the most senior operators exceed $500,000 all-in: $250,000-$300,000 base, RSUs over four years, bonus on top. If that surprises you, price the alternative: a mediocre hire here taxes every hour of the most expensive person in your company.

Fully-loaded annual budget

$180,000-$350,000 in most markets; $400,000-$600,000 at the top of the public-company market.

Best fit

Principals with strong executive teams and distributed leverage. In practice this includes most rainmaker principals in financial services: investment banking, private equity, big law. Even heavy revenue generators typically run on one exceptional EA who speaks the language of the business, not a larger office. Wrong fit for principals who need a strategic thought partner or whose direct reports require active orchestration.

Founder + Founder's Associate or early Chief of Staff

The startup and scale-up version. A founder pairs with a Founder's Associate (CoS-lite, typically 2-6 years of experience, often ex-consulting or banking) or a full Chief of Staff. The defining condition is ambiguity: fundraising support, investor materials, hiring processes, operational fires, special projects, with a scope that reshapes itself monthly because the company does.

Readiness is often thin or absent here, and that is frequently right. Founders at this stage run their own calendars or use a virtual assistant at a fraction of the cost. What they lack isn't scheduling. It is a second pair of capable hands on problems that don't yet have an owner.

How work flows

The CoS is pointed at whatever is on fire. Work arrives as fragments: a half-formed idea in Slack at 11pm, a "look into this" after a board call. The core skill is converting fragments into finished outcomes without a spelled-out brief. Imposing heavy process here would destroy the model's value.

How decisions get made

By the founder, at speed, often mid-conversation. The CoS frames options upstream and makes the hundred small execution calls downstream. The best pairs develop a shorthand: the CoS predicts the founder's call with 90% accuracy and knows exactly which 10% to escalate.

Managing down

Low in process, high in access. The configuration runs on proximity: in the room, on the calls, reading the same inbox. A CoS kept at arm's length is an expensive project manager starved of context.

Strengths

Maximum flexibility per dollar. A genuine force multiplier during the years when the founder is the company. For the associate, the best business education money can't buy, which is why strong candidates take these roles below their market cash value.

Weaknesses and failure modes

The role has no natural shape; it holds the shape the founder's discipline gives it. Common failures: the CoS becomes a permanent taskrabbit and leaves within eighteen months; the founder delegates accountability without authority; the company scales and nobody redefines the role, which dies of scope starvation. Build in an expiry or evolution point from day one: eighteen to thirty months, then a functional seat or a graduated Head of OCEO role. Say it at the offer stage. The candidates you want will respect it; the ones who flinch were planning to squat in the ambiguity.

One more risk: signal distortion. A CoS who controls a founder's information flow becomes a filter on reality. If your CoS has never pushed back on you, you don't have a Chief of Staff. You have a mirror with a salary.

Hiring reality

Cash-negotiable, equity-real. Founder's Associates run $100,000-$200,000 base plus bonus and equity. Full Chiefs of Staff flex between $150,000-$250,000 base plus bonus and equity, with grants from roughly 0.1% to 1% by stage. The screen isn't intelligence; the applicant pool is absurdly credentialed. It is ambiguity tolerance, low ego, and execution stamina, three traits resumes cannot reveal. Test with a live, messy problem from your actual week, not a case study.

Fully-loaded annual budget

$130,000-$320,000 cash, plus equity, plus optionally $25,000-$50,000 for VA-tier readiness support.

Best fit

Seed through Series C; principals in build mode. Wrong fit for principals who need polish, process, and a stable readiness layer. That is a different animal, covered next.

Principal + a bench of EAs (two to five, depending on the principal's pattern of life) + Chief of Staff + Comms/PR support

The first institutional configuration, most at home in large public companies where the CEO's schedule is global and the exposure is extraordinary. An EA bench built for continuous coverage: two can cover a heavy domestic schedule with international overflow; five may be needed for constant global travel. The bench splits across time zones, domains (calendar and correspondence; travel and events; personal and family interface), or both. Around it: a Chief of Staff on secondary responsibilities and dedicated comms shaping the narrative.

Heavy on Readiness and Narrative, moderate on Leverage, and with no Continuity component at all. This is a machine for keeping one person operational across a brutal schedule. It develops nobody, exports nothing, and holds its institutional knowledge in the heads of whoever currently fills the seats.

How work flows

Readiness follows the sun or the domain split, with formal handovers between EAs. The quality of those handovers is the quality of the office. The principal should experience the bench as one continuous person. The moment they start thinking about which EA owns something, the configuration is leaking its core value.

How decisions get made

Still by the principal. This configuration adds coverage, not decision infrastructure, and that is its hidden limit: a CEO with a full bench and a comms team can be perfectly scheduled and still be the sole synthesizer of every strategic input. Coverage solves availability. It does nothing for cognitive load.

Managing down

Higher than principals expect. Four to six direct support relationships, inter-EA coordination to referee, comms alignment to maintain. Well-run versions appoint a lead EA with explicit seniority to absorb the coordination. Without one, the principal becomes the router between their own assistants: an expensive way to create administrative work.

Strengths

True 24-hour capability. Resilience through redundancy: a resignation in the bench is absorbable in a way Configurations One and Two cannot manage. Narrative competence, no longer optional at this exposure. For principals running 150+ travel days a year, nothing lighter works.

Weaknesses and failure modes

The multi-EA scope problem, in plain language: several capable EAs sharing a principal without precisely drawn territory produces crossover, then confusion, then quiet competition for the principal's favor, then resentment. We have been called into offices where two excellent assistants had stopped speaking to each other. The root cause is always the same: nobody wrote down who owned what. Scope each seat to the sentence level. Revisit whenever the principal's pattern of life changes. The seats don't defend their own boundaries; the design has to.

Second: the CoS as odd one out. In a Readiness-heavy office, the lone CoS drifts into becoming another super-EA, dragged into scheduling arbitration because they are senior and present, while the Leverage mandate starves. Protect the seat or lose the hire.

Third: gatekeeping optics. At this scale the office is the principal's interface with the organization. An office that is slow, political, or opaque costs the principal reputation, one frustrated senior executive at a time.

Hiring reality

The lead EA is the keystone hire: a management role wearing an EA title, compensated as such. Build the bench on complementary strengths, not identical profiles. For comms, one senior in-house operator plus agency support usually beats a premature internal team.

On compensation, where the market data most misleads: inside the largest public technology companies (Google, Meta, Microsoft, Amazon and peers), EA compensation at the CEO's office is a different market. Bases of $250,000-$300,000, RSUs over four years, bonuses taking total compensation past $500,000 for the most senior seats. Supporting bench EAs commonly clear $200,000-$350,000 all-in. Run several EAs at these levels, add a CoS and comms, and the office is a multi-million-dollar annual line. It is priced that way for a reason: the principal is among the most consequential executives in the world. The same configuration supporting a division president or non-CEO principal runs leaner in both headcount and per-seat pay.

Fully-loaded annual budget

$700,000-$1,200,000 supporting a non-CEO principal or private company CEO. $1,500,000-$3,000,000+ for a public mega-cap CEO's office.

Best fit

Globally scheduled CEOs of large public companies; heavy public exposure; constraint measured in hours of coverage. Wrong fit where the constraint is decision throughput. Adding another EA to a thinking problem buys more of the wrong thing.

Principal + primary EA + junior OCEO administrator + Head of OCEO Operations + rotational Chief of Staff + Comms/PR support

The configuration we would design from a blank sheet for the CEO of a serious institution, and the one almost nobody arrives at by accident, because it requires thinking in layers rather than hires.

Five seats, each mapped to a layer. A primary EA owns Readiness exclusively, scope protected from creep in both directions. A junior OCEO administrator absorbs the office's own admin load and serves as the office's shock absorber and succession bench; more on that below. A Head of OCEO Operations is the strategic right hand: a permanent senior operator who runs the office as a function, owns the operating cadence, and carries the principal's authority into the organization. A Chief of Staff on rotation, an 18-to-24-month tour for a high-potential leader pulled from the business, provides plug-in Leverage capacity while absorbing how the CEO thinks and decides, then rotates back out carrying that knowledge into a business unit. Comms/PR owns Narrative.

The rotation is the piece that makes this configuration categorically different. Every other structure in this paper consumes talent. This one manufactures it. Run for a decade, it seeds the leadership bench with executives who each spent two years inside the CEO's head. No leadership program replicates that.

How work flows

The Head of OCEO Operations is the routing layer, and that is the structural insight: the principal manages one senior relationship for everything that isn't Readiness or a live rotation project. Inbound hits the office, gets triaged, and reaches the principal synthesized and sequenced. Decisions leave with an owner, a deadline, and a follow-up mechanism that doesn't depend on the principal's memory. The EA lane runs parallel and independent.

How decisions get made

The first configuration with genuine decision infrastructure: an explicit cadence of what gets decided where, materiality thresholds the Head of Ops can act within, a synthesized decision queue rather than an ambush of asks. The principal spends their decision hours on genuinely contested, consequential calls, because everything else was resolved a layer down.

Managing down

Low, by design, and this is the headline benefit. A five-seat office in which the principal actively manages two relationships: primary EA and Head of Ops, with the rotational CoS a lighter third. A well-built Balanced Office feels smaller than a two-seat office while doing four times the work.

Strengths

Every layer staffed, no seat overloaded. The primary EA is structurally protected from CoS-drift because Leverage capacity visibly exists elsewhere. Succession depth in the admin seat. Talent manufacture through the rotation. An office that can absorb a departure in most seats without the principal's operating system going down.

Most seats. Not all.

Weaknesses and failure modes

Two load-bearing walls: the primary EA and the Head of OCEO Operations. Lose either without warning and the office degrades within weeks, because those two hold the accumulated context the structure runs on, and the principal is suddenly back in the routing business.

The mitigations are unglamorous. Retention economics for both seats: pay them as the infrastructure they are. Documented ways-of-working, not oral tradition. And, most underrated: hire the junior administrator as a genuine step-up candidate, not cheap hands. A junior admin deliberately selected for the capability to hold the primary EA's seat for a quarter converts a load-bearing wall into a managed risk. They won't replace an elite EA overnight, but they keep Readiness standing while a proper search runs: the difference between a stressful quarter and a structural failure. That changes the hiring spec. You are buying insurance and building a bench, and the candidate should know that is the job.

Second: the rotation demands loyalty and discipline, or it curdles. A rotational CoS holds extraordinary access: board dynamics, unfiltered assessments, the principal's real opinions. The wrong selection is a political liability; the right selection with the wrong contract is a flight risk, trained at enormous expense and then poached. Select for discretion as hard as for talent, structure the exit before the tour starts, and make the rotation prestigious enough that alumni advocate for it.

Third: Head of Ops versus rotational CoS boundary tension. Both senior, both in Leverage. The distinction that works: Head of Ops owns the standing machine; the CoS owns finite missions. Standing versus finite. Write it down.

Hiring reality

Sequence: primary EA, then Head of OCEO Operations, then the rest. The Head of Ops helps design and hire the remaining seats, because they will run them. The profile is rare: senior enough to carry the principal's authority, egoless enough to spend prime years making someone else effective, operational enough to run the office as a function. Ex-CoS operators five years on, former COOs of smaller businesses, senior operations leaders. Expect $250,000-$400,000 total, meaningfully more at large public companies once equity is included, and a search of a quarter or more. The rotational seat is filled from inside; the work there is selection discipline, not sourcing.

Fully-loaded annual budget

$900,000-$1,600,000 for most institutions; $1,500,000-$2,500,000+ at large public companies. Priced as a percentage of the value of one improved major decision per year, it rounds to zero.

Best fit

CEOs of substantial institutions, building for a decade rather than surviving a year, with the leadership depth to feed a rotation. Wrong fit for principals unwilling to invest in the design and first-year calibration. Bought off the shelf and left unmanaged, this is just Configuration Three with better titles.

Principal + EA bench (time zones and in-person travel) + multiple Chiefs of Staff with business-unit lines + analyst pool + comms + personal support

The maximal case: a public company CEO operating at global scale, traveling constantly, and traveling accompanied. The office stops being support and becomes an institution. Multiple EAs covering time zones and traveling with the principal. Multiple Chiefs of Staff, each with a line into a different business unit. An analyst pool synthesizing inbound into digestible packs, because raw volume exceeds any individual's capacity. Comms as a standing function. And where commercial and personal lives interweave, as at this level they almost always do, dedicated personal support: estate, family, philanthropy, security coordination.

How work flows

Compression upward, expansion downward. Information enters wide, gets synthesized by analysts, structured by the CoS layer, sequenced by the EA layer, and reaches the principal decision-ready. Decisions exit in reverse, unpacked by the relevant CoS into workstreams. At its best, a genuine command structure: the principal's attention allocated deliberately, like capital.

How decisions get made

At this scale the apparatus shapes decisions before the principal sees the question: what gets synthesized, what gets escalated, how options are framed. That is the power and the permanent danger. Every layer between the principal and the ground is a layer where reality gets smoothed. The principals who run this well fight for unmediated contact: skip-levels, direct reads of primary material, deliberately unfiltered channels, precisely because their office is so good at filtering.

Managing down

Deceptively high. The org chart says a handful of leads; the reality is a court, and courts have politics. Access becomes currency. Proximity on the plane becomes status. Parallel CoS mandates compete unless boundaries are actively maintained. The senior office lead spends real time on the office's internal dynamics, and that time is the maintenance cost of the machine.

Strengths

Nothing else supports this operating intensity. Global coverage, physical presence, synthesis at industrial scale, narrative management, continuity across a life where business and personal have fully merged. For the few who genuinely operate at this level, the alternative isn't a leaner office. It is incapacity.

Weaknesses and failure modes

Burnout is the defining occupational fact; travel-heavy seats churn fastest. Build redundancy and enforce recovery, or run a permanent recruitment treadmill. Insulation is the strategic risk: a principal who hasn't heard uncomfortable, unsynthesized truth in eighteen months is being managed by their own office. Shadow hierarchy is the organizational risk: when a business unit head learns the fastest route to a decision is through a particular CoS, the formal structure starts to atrophy. And cost discipline erodes quietly, because nobody inside the apparatus has an incentive to shrink it.

Hiring reality

You are not filling roles; you are casting an ensemble. Individual excellence matters less than fit within the machine: discretion above all, stamina, and the makeup to be near power without needing to be seen. Vetting matters as much as assessment. Plan for churn as part of the design: assume travel EA seats turn every two to three years and build handover infrastructure accordingly. A single miscast hire inside a machine this interdependent degrades every seat around it, which is why seat-by-seat transactional hiring fails here.

Fully-loaded annual budget

$2,500,000-$6,000,000+, unbounded above at public technology companies where every senior seat carries equity. At this scale the discipline isn't the total but the composition: is every seat mapped to a layer, or has the apparatus started growing seats because apparatuses do?

Best fit

The genuinely few. Our candid advice to most principals flirting with this: you probably want Configuration Four, run properly, plus a travel EA. Enter the apparatus reluctantly. It is far easier to build than to dismantle.

The comparison at a glance

Two views of the same landscape: which layers each configuration staffs, and what each costs to run. The table beneath them carries the management-load comparison, which no budget line captures.

Figure 3. Fully-loaded annual budgets (US, log scale). Lighter segments show the top of the public-company market, where equity forms a significant share of packages.

Configuration	Seats	Principal management load
1. The Lean Line	1	Minimal: one relationship, high trust
2. The Founder Pairing	1-2	Low process, high access
3. The Coverage Office	4-7	High without a lead EA to absorb coordination
4. The Balanced Office	5-6	Low, by design: two managed relationships
5. The Full Apparatus	8+	Deceptively high: a court, with politics

 

The seams: where every configuration actually fails

Five structures, one lesson. When these offices break, they break in the same places, and every one is a scoping failure, not a talent failure.

EA-to-CoS drift. The most common corruption in the market. An excellent EA gets handed project work, delivers, gets handed more, and the Readiness layer quietly degrades while everyone congratulates themselves on the EA's growth. If you want your EA to become a Chief of Staff: promote them, backfill Readiness, do it on purpose. Let it happen by accretion and you get both jobs done at 50%.

Multi-EA scope collision. Capable assistants sharing a principal without written territory produce the same sequence every time: crossover, confusion, competition, resentment. The assistants get blamed. The design was the problem.

Leverage-layer ambiguity. Any two senior operators in the same layer will grind against each other unless the boundary is explicit. Standing versus finite. Domains versus missions. Pick a principle and write it down.

Delegation without authority. A Chief of Staff sent to move executives who don't answer to them, without the principal's visible backing, fails publicly and then leaves. If you won't lend the office your authority, don't build one.

The unpriced single point of failure. Configurations One and Four each rest on one or two people whose sudden departure takes the operating system down. Manageable, through retention economics, documentation, and real succession seats, but only if acknowledged. Most principals discover it via a resignation letter.

Hiring in the wrong order. Readiness before Leverage, almost always. A Chief of Staff hired into a broken Readiness layer spends year one doing calendar triage: $250,000 for a calendar manager who is now updating their resume.

Transition signals: how to know you've outgrown your configuration

Configurations are not a maturity ladder; plenty of principals should stay in One or Three forever. But they have load limits, and the signals of breach are consistent:

•  Your EA's project work is crowding out your preparation. You are walking into meetings less briefed than a year ago. (One: the hybrid seat is saturated; split Readiness from Leverage)

•  You've become the router. Meaningful hours each week directing traffic between your own support staff. (Three to Four)

•  Decisions are queuing. Things you would have settled in a day now wait a week. Not for information. For you. (Any, toward real Leverage or Synthesis capacity)

•  Your CoS role has been "redefined" twice in a year without anyone deciding what it is for. (Two: redefine the role or execute the designed exit)

•  You are consuming raw inbound. Reading source material at volume because nothing reaches you synthesized. (Three to Four or Five)

•  Coverage gaps have consequences. A missed handover cost you something real: a commitment, a relationship, a deal detail. (One to Three or Four)

The wrong response is the reflexive one: add a body. The right response is to identify which layer is saturated and staff that, which sometimes means a different hire than the one you were about to make, and occasionally a redesign rather than a hire at all.

Six questions before your next support hire

1.   Which layer is actually saturated? Not "do I need a Chief of Staff." Which layer of work is being done badly, late, or by you at 11pm?

2.   What is the written scope of every current seat? If you can't produce it, you've found your first problem, and it isn't headcount.

3.   What happens if your most critical support hire resigns on Friday? If the honest answer is "chaos," your configuration has an unpriced risk.

4.   Is anyone in your office doing two layers at 50% instead of one at 100%? That is not versatility. That is drift.

5.   Does your structure develop anyone? If every seat is a terminus, you will pay for it in churn. The best operators go where the role goes somewhere.

6.   When did someone in your office last tell you that you were wrong? If you can't remember, the office isn't supporting you. It is insulating you.

The Blackbook view

Most firms in our market place Executive Assistants, or place Chiefs of Staff, and treat each search as a transaction: a seat, a spec, a shortlist. The seat gets filled. Whether the office works, whether the seams hold, whether the configuration matches the principal, is nobody's mandate.

It is ours. Blackbook Associates builds Office of the CEO functions for some of the largest companies in the United States: public technology companies valued in excess of $850 billion, where we design and staff multi-seat offices at the top of the compensation market; boutique financial services firms building lean two-person teams around a single rainmaking principal; family offices making one critical, discreet hire. Every search is assessed against the system it is entering, not just the spec it arrives with. Sometimes that means telling a client the hire they briefed us on is the wrong hire, and what the right one is. Our clients remember those conversations longer than the placements.

If you are building, restructuring, or quietly worried about the office around you or your principal, that conversation costs nothing.

Blackbook Associates | Retained search for the Office of the CEO

© 2026 Blackbook Associates. Compensation figures reflect the top of the US market as of 2026: large public companies, elite financial institutions, well-funded startups and scale-ups, and family offices in high-cost-of-living markets. Drawn from placement experience and current market data. At the largest public technology companies, equity forms a significant share of total compensation. Fully-loaded budgets include base, bonus, equity where applicable, benefits burden, and typical employer costs.