Founders ask Collective 54 this 5 times in our records, 2 of them in 2026. The scaling answer on this site covers how operations change as a firm grows; this page covers the specific choice between a hire, a vendor and building it yourself.
The operations essay starts from what founders feel. They know where they want to take the firm, but their days go to execution issues that will not stay solved, broken handoffs, missed commitments and decisions that have to be revisited because no one enforced them. They are serving, by default, as the operations manager of the firm. What they want is a number two who owns execution, enforces decisions, stabilizes operations and frees them for growth and strategy.
The essay is precise about what that role is not: a project manager, a meeting facilitator, a dashboard owner, a process optimizer or a junior COO. Those roles support execution. The operations role owns it. As an inference, that distinction answers part of the question already: a vendor that sells project management or process improvement is not filling this seat, however capable it is.
The essay describes the role breaking at every stage of a boutique, and each failure maps onto one of the options in the question.
Hiring early is unaffordable. Small firms desperately want an operations leader but cannot afford a truly capable one, so the founder absorbs the work. The essay calls that a failure of fit rather than ambition.
Hiring in the middle goes wrong. Mid-sized firms can afford the role but do not know what good looks like, how to scope it, or how to divide the work between founder, operations and team. They confuse senior project management with execution ownership, operational support with operational leadership, and process optimization with decision enforcement. The results are overqualified hires who outgrow the role, underpowered hires who cannot enforce decisions, and churn.
Vendors and fractional leaders work only partly. The essay says firms turned to fractional and outsourced operations leadership for the same reason they outsourced finance, and that this mirrors a sensible pattern. But without clear role design these arrangements fail for the same reasons internal hires do: unclear authority, insufficient scope, poor division of labor and lack of continuity. Fractional does not solve ambiguity.
And larger firms usually have someone in the seat who was hired to keep the firm running, not to own execution independently of the founder, so the firm stays founder-dependent and the exit stalls or discounts.
The essay explains why the comparison with finance only goes so far. Most boutiques outsource or hybridize finance long before they can staff a full-time finance leader, because finance needs rigor and cadence a founder cannot supply alone. Operations is similar but more urgent: finance shows up monthly or quarterly, operations shows up every day, and execution failures surface immediately. The overhead answer on this site places operations in the overhead block with finance, IT, HR and legal, which argues for keeping it lean; the essay closes by saying operations is not overhead but the foundation that makes everything else possible. As an inference, both hold: keep the cost lean, but do not treat the role as optional.
The essay summarizes the failure in one line: the traditional model was a people-first role in an environment that now requires role-first architecture. Firms tried to hire a person to absorb complexity without defining what must be owned, enforced and remembered.
That definition is the work no hire or vendor can do for you. The essay provides the specification as a capability map of eight areas: decision capture and memory, commitment enforcement, operating cadence, cross-functional visibility, drift detection and correction, an execution learning loop, protection of founder time, and leadership transferability. Alongside it sits authority: the essay says ownership requires the authority to enforce decisions, visibility across functions, memory of past commitments and continuity beyond individual projects.
As an inference, write those down before you interview anyone or sign any vendor, including what this person or provider may decide without you and what must be escalated. That document is what turns any of the three options from a gamble into a staffable role.
The essay splits the role in two. AI owns decision memory, commitment tracking, cadence enforcement, drift detection, cross-functional visibility and pattern recognition, the continuous governance no person can sustain. Humans own strategic interpretation, judgment under ambiguity, escalation and intervention, people leadership and final accountability. It says this is what finally makes the role staffable at every stage: early firms get execution ownership without full-time cost, mid-sized firms can define the role clearly and avoid hiring mistakes, and larger firms can institutionalize execution so leadership becomes transferable.
As an inference, building it yourself in this sense means installing that governance capability inside the firm, with the tooling bought rather than built, as the build or buy answer on this site advises for software the firm runs on.
As an inference from the stage descriptions in the essay:
In a smaller firm, the founder keeps the human part of the role for now, the governance runs on AI, and a fractional operations leader can help if their authority is written down. The aim is to stop the founder being the only record of what was decided.
In a mid-sized firm, hire or contract against the capability map, choosing the profile that matches the eight areas rather than a title, and give the person explicit decision rights. A fractional leader is reasonable if continuity and authority are spelled out.
In a larger firm, or one preparing to sell, the seat needs a leader who can own execution without the founder, because the essay names leadership transferability as the capability that determines whether the firm can exit.
Collective 54 names no fractional operations provider, sets no revenue or headcount level for an operations hire, and publishes no job description or compensation for the role. The published positions are execution ownership as a role rather than a trait, the stage-specific failures of hiring and fractional arrangements, role-first design, the eight-area capability map, the split between AI governance and human leadership, and transferability as the condition for exit.
If what you actually need is project coordination or process cleanup rather than execution ownership, a project manager or process consultant may be the right purchase; just do not expect it to free the founder.
If you already have an operations leader who is not working out, as an inference check the role design before replacing the person, because the essay traces these failures to unclear authority, scope and role design.
And if a partner is already acting as the number two informally, write the role around them before looking outside.
Design the role before choosing a hire, a vendor or a build. The operations essay says the operations role fails differently at each stage of a boutique: unaffordable when small, mis-hired in the middle, and unable to succeed the founder later, while fractional arrangements fail without role design because fractional does not solve ambiguity. Write down what the role owns using the eight-area capability map, and what authority it has. Let AI carry the continuous governance of decision memory, commitments, cadence and drift, with the tooling bought rather than built. Then staff the human part, judgment, escalation, people leadership and accountability, according to size: the founder plus fractional help when small, a defined hire or fractional leader with explicit decision rights in the middle, and a leader who can run execution without the founder before a sale.
As an inference, usually not yet. The operations essay says small firms need an operations leader but cannot afford a truly capable one, and that the traditional COO role was designed for scale boutiques do not have. It argues AI now gives early-stage firms execution ownership without full-time cost. Collective 54 sets no size threshold for the hire.
Only with clear role design. The operations essay says fractional and outsourced operations leadership mirrors what firms did with finance, but fails for the same reasons internal hires fail: unclear authority, insufficient scope, poor division of labor and lack of continuity. In its words, fractional does not solve ambiguity.
The operations essay lists eight capabilities: decision capture and memory, commitment enforcement, operating cadence, cross-functional visibility, drift detection, an execution learning loop, protecting founder time, and leadership transferability. It says the role is not a project manager, meeting facilitator, dashboard owner, process optimizer or junior COO.
The operations essay says mid-sized firms do not know what good looks like or how to divide work between founder, operations and team. They confuse senior project management with execution ownership and process optimization with decision enforcement, which produces overqualified hires who outgrow the role, underpowered hires who cannot enforce decisions, and churn.
Sources: Greg Alexander, The AI-Native Boutique Firm (Advantage Books, January 2027), specifically The AI Operations Manager for the founder as default operations manager, the critical number two, what the role is not, the stage-specific failures of the role in small, mid-sized and larger firms, the confusions behind mid-sized hiring mistakes, fractional and outsourced operations leadership mirroring finance but failing without role design, the comparison with finance and operations showing up every day, operations described as the foundation rather than overhead, people-first roles versus role-first architecture, the requirements of ownership, the eight-category capability map, the division between AI governance and human leadership, AI making the role staffable at every stage, and leadership transferability as the condition for exit. Related Collective 54 answers on this site: how do we scale our processes and operations as the firm grows; how should we structure our operating system, roles and accountability; should we build AI tools ourselves or find and buy existing software; should I hire full-time employees or use contractors and fractional talent. Note on scope: Collective 54 names no provider and sets no threshold, job description or compensation for the role. Reconciling operations as overhead with the essay calling it the foundation, reading project management and process vendors as not filling the seat, writing the role and its decision rights before hiring or contracting, building the capability with bought tooling, the size-based recommendations, and checking role design before replacing an existing leader are inferences used here to organize the source material rather than published Collective 54 positions.
Collective 54 is the private community for founders and executives of boutique professional services firms between $5M and $50M in revenue. Members work these answers against their own numbers.