Everyone agrees a great Chief of Staff is transformational. Nobody agrees on what makes one great. I've seen the role described as "EA with strategy," "mini-COO," "founder's shadow," and "chief problem solver." All true in certain contexts. None useful for deciding which archetype to actually hire.
There are four Chief of Staff archetypes. Most companies hire the wrong one.
The Strategist. Lives in frameworks and board decks. Owns quarterly planning. Strong in a mature organization where the question is resource allocation, not survival. Weak in chaos.
The Executor. Runs the operating system. Tracks decisions, manages cadence, follows up on every open loop. Indispensable in a scaled organization where the problem is coordination overhead. Struggles when the operating system doesn't exist yet and needs to be invented.
The Diplomat. The internal translator. Manages the relationship between founder and leadership team. Runs difficult conversations the founder shouldn't have to run. Critical in companies with founder-leadership tension. Limited leverage when the company is too small for real organizational politics.
The Builder. Creates functions that don't exist. Stands up the sales process from scratch. Builds the data room before the CFO is hired. Runs international expansion before the GM is on board. Does the thing until the company hires the person who will own it permanently. Runs on high ambiguity. Has little interest in maintaining what already works.
At a seed-stage company, any company where the fundamental problem is "building the plane while flying it," you want the Builder.
I know because I've been both the wrong and right archetype at different points. At US Mobile, the company needed someone to build structure where none existed. I spent six months creating the operating cadence, reporting infrastructure, and early GTM architecture. Builder work. The company grew from $20M to $150M partly because we scaled ops fast enough to support product growth.
At Retailo, the role required more Diplomat and Executor skills: managing board relationships, running fundraising, coordinating across international teams. But even there, the highest-leverage work was Builder: standing up Riyadh operations, building investor reporting, creating the international expansion framework before we had the team to run it.
The mistake most companies make is hiring a Strategist or Executor when they need a Builder. Strategists are impressive in interviews. They have polished answers to "how would you think about market positioning." They're less useful when the CRM isn't set up, the sales team has no pipeline process, and the board deck is due in two weeks with nobody owning it.
Executors are safe hires. They keep things running. But in a company still defining what it is, keeping things running is not the constraint. Building the right things is.
Builders are harder to evaluate because they work best in environments too chaotic to demonstrate output clearly. You can't point to a dashboard a Builder maintained. You can point to a function that didn't exist six months ago and now runs smoothly enough that someone was hired to own it full-time. That's the measure: what did they create, and is it still standing without them?
There is a version of the CoS role that is fundamentally administrative: calendar management, meeting prep, catching things that fall through cracks. That role has value. It does not change company outcomes. The CoS who changes outcomes sees the organizational problem two steps ahead, builds the system to address it, and moves on before anyone noticed the problem existed.
Most companies figure out which CoS they need after a costly mismatch. The better approach: be honest about where the company is. Do you need someone to think more clearly, or someone to build the machine that turns thinking into output? Almost every early-stage company needs the second. Hire the Builder.