Remote vs on-site is the wrong first question. The better question is: where does the operator need proximity to make better decisions, build trust, and see the real work?
A COO fixing warehouses, care delivery, stores, clinics, events, manufacturing, or field operations has a different proximity requirement from a Chief of Staff improving CEO cadence in a distributed SaaS company. A fractional COO can often work remotely if the mandate is clear. A founding operator joining a chaotic 15-person team may need more face time in the first month, even if the long-term role is hybrid.
Use this guide to decide the working model before you write the role, constrain the search, or reject strong operators because they are not nearby.
The quick decision table
| Situation | Best default | Why | |---|---|---| | Distributed digital company with written decision habits | Remote-first or hybrid | The operator can build cadence, reporting, and handoffs through the same systems the company already uses. | | Founder needs close CEO leverage and fast trust-building | Hybrid with intense onboarding | A Chief of Staff or first operator may need early context, then can move to a designed rhythm. | | Multi-site, field, care, logistics, manufacturing, or in-person delivery | On-site or regular travel | The operator needs to observe real work, not only dashboards and status updates. | | Fuzzy mandate and uncertain permanent role | Fractional or diagnostic, often remote/hybrid | Start with diagnosis before forcing a full-time local search. | | Office-based leadership team with informal decision-making | Hybrid or on-site until habits improve | A remote operator will struggle if the real decisions happen in rooms they cannot access. | | Strong candidate pool is mostly outside your city | Remote-first with defined in-person rituals | Talent quality usually matters more than location preference if the work is not physical. |
If you are still deciding which operator role you need, first compare Chief of Staff vs COO, COO vs Head of Operations, and fractional COO vs full-time COO.
Start with the work, not the office policy
Before choosing remote, hybrid, or on-site, write down the operator mandate.
Ask five questions:
- What decisions will this person own? CEO leverage, team cadence, customer delivery, people ops, finance ops, launch readiness, functional execution, or company-wide operating rhythm?
- Where does the real work happen? In tools, customer calls, warehouses, clinics, stores, leadership meetings, Slack, docs, dashboards, or informal office conversations?
- What do they need to observe directly? Team behaviour, customer handoffs, frontline workflows, manager quality, sales-to-delivery friction, planning habits, or founder bottlenecks?
- What will the founder stop doing? If the founder still owns every decision, location will not fix the role.
- What operating rhythm will make the hire effective? Weekly founder check-in, leadership review, async updates, quarterly planning, site visits, office days, or field days?
This keeps the location decision tied to the actual operating problem. It also stops the common mistake of writing “hybrid” when the company really means “available whenever the founder feels nervous.”
For a fuller pre-hiring brief, use the startup COO mandate template and COO job description guide.
When remote operators work best
Remote operators work well when the company already knows how to make work visible.
Remote can be the right default when:
- the team already works across several locations;
- decisions are documented instead of trapped in private chats;
- the operator will own cadence, reporting, planning, hiring process, or cross-functional follow-through;
- the business is software, marketplace, media, services, or another digital-first model;
- the company needs a specific operator pattern that is unlikely to exist locally;
- the founder is willing to share context deliberately rather than through office osmosis.
The biggest advantage is search quality. Great startup operators are scarce. If the role does not require physical presence, restricting the search to one city can turn a hard search into a much weaker one.
Remote hiring is especially useful for specific pattern matches: a marketplace operations leader, a B2B SaaS Chief of Staff, a fractional COO who has built planning cadence before, or a VP Operations with a particular customer-ops background.
Remote does not mean detached. It means the operating system has to be explicit.
When remote operators struggle
Remote operator hires usually fail for one of three reasons.
1. The company has no written operating system
If priorities, owners, metrics, and decisions live in people’s heads, a remote operator starts behind. They spend their first months asking for context that the office absorbs informally.
Warning signs:
- important decisions happen in private chats or ad hoc calls;
- teams do not write down owners or next steps;
- the CEO changes direction verbally and expects everyone to infer it;
- leadership meetings are busy but unresolved;
- dashboards are not trusted;
- new hires learn by osmosis.
A strong operator can improve these systems, but only if the founder is willing to change how the company communicates.
2. The founder wants leverage but not handoff
A remote operator cannot create founder leverage if the founder keeps every decision. The issue is not location; it is authority.
Before hiring remotely, be clear on:
- what the operator can decide without founder approval;
- what they can change in cadence, reporting, or handoffs;
- when they escalate;
- how the founder will back them publicly.
If those answers are missing, read how to evaluate an operations hire before expanding the search.
3. The role depends on reality the operator cannot see
Some operating problems need direct observation. A dashboard can show delay; it may not show why a warehouse shift, care workflow, onboarding call, retail team, or field process keeps failing.
In those cases, remote can still be part of the model, but it should not be the whole model. Build in site visits, ride-alongs, office days, or field time around the real constraint.
When on-site operators are worth it
On-site or regular in-person time is valuable when proximity changes the quality of diagnosis or trust.
On-site is often justified when:
- the company has warehouses, stores, clinics, events, manufacturing, logistics, or field operations;
- the operator must rebuild trust with teams that are sceptical of “process people”;
- the leadership team is office-based and still makes informal decisions;
- the company is in a turnaround, integration, launch, or major operating reset;
- the role includes people leadership over teams that work in person;
- the founder needs a very close execution partner during a high-change period.
The advantage is not “culture” in the abstract. It is specific: the operator can watch how work really moves, where handoffs break, who people go to for decisions, which meetings are theatre, and where customers or employees get stuck.
That context can compress learning. It is worth paying for when the operating problem is physical, interpersonal, or highly informal.
The hidden cost of insisting on on-site
On-site constraints narrow the market. That may be worth it, but founders should be honest about the tradeoff.
A useful test:
What specific part of this operator’s job becomes materially worse if they are not in the office most days?
Strong answers:
- “They need to observe our care-delivery workflow and manager handoffs.”
- “They will run a warehouse reset and vendor process.”
- “The leadership team is co-located and the first 60 days require daily trust-building.”
Weak answers:
- “Alignment.”
- “Energy.”
- “Culture.”
- “We just work better in person.”
Those may point to real concerns, but they are not yet a hiring requirement. Translate them into work: decisions, meetings, workflows, trust gaps, onboarding, customer experience, or operating cadence.
Hybrid is usually the most practical model
For many startups, hybrid is the best answer — if it is designed, not improvised.
Useful hybrid patterns:
| Pattern | When it works | |---|---| | First 2-4 weeks on-site, then remote-first | First operator, Chief of Staff, or COO needs context quickly but the long-term work is system/cadence-heavy. | | Two fixed office days per week | Leadership rituals, founder handoff, planning, and manager follow-up benefit from a shared rhythm. | | Monthly operating review in person | Distributed leadership team needs periodic deeper problem-solving. | | Quarterly planning/offsites | Remote-first company wants strategic alignment without daily office requirements. | | Site visits around incidents or launches | Physical operations need observation only during specific high-stakes windows. |
The mistake is writing “hybrid” without naming the rhythm. Strong operators want to know what in-person time is for.
Better job-description language:
- “Remote-first within UK/EU time zones, with quarterly planning sessions in London.”
- “First two weeks on-site with the founding team, then two in-person leadership days per month.”
- “Hybrid: Tuesdays and Thursdays in office for leadership cadence and team rituals; other days remote.”
- “Remote role with monthly site visits during the first 90 days while we rebuild the customer-delivery handoff.”
Vague location language filters out good operators. Clear operating cadence attracts them.
Role-by-role guidance
COO
A COO can be remote, hybrid, or on-site depending on the operating surface. Company-wide cadence, metrics, planning, and manager rhythm can work remotely in a distributed company. Physical operations, executive trust resets, and office-based leadership teams usually need more in-person time.
If the COO will own several functions and budget/people decisions, location is less important than authority and access. If they cannot influence the real decision system, they will fail from any location.
Chief of Staff
A Chief of Staff often benefits from early proximity to the CEO. The role depends on context, judgment, written follow-through, and founder trust.
Remote can work if the founder is disciplined about context sharing. Hybrid often works best: enough in-person time for trust and nuance, enough remote structure to force clear communication.
Head of Operations or VP Operations
These roles depend on the function. Revenue operations, business operations, internal systems, people operations, and customer operations can often be remote or hybrid. Fulfilment, logistics, field, care, events, or facilities-heavy work usually needs site exposure.
The key question is whether the operator must see the workflow or can manage it through systems and owners.
Fractional COO or fractional operator
Fractional operators are often remote-first because the mandate is bounded: diagnose, install cadence, fix a specific operating loop, prepare the permanent hire, or support a founder through a transition.
But the first phase may still need in-person time if the company is messy, physical, or low-trust. The best fractional scope names the rhythm upfront: days per month, leadership meetings, async update format, on-site moments, and handoff plan.
A practical location scorecard
Use this before you constrain the search.
Score each row from 1 to 5.
| Question | 1 means... | 5 means... | |---|---|---| | Physical workflow dependency | Work is fully digital | Work depends on sites, shifts, field teams, or physical delivery | | Informal decision risk | Decisions are documented | Real decisions happen in rooms/chats the operator may miss | | Founder-context intensity | Role can run from written mandate | Role needs daily CEO context and trust-building | | Team distribution | Team is already distributed | Team is mostly office/site-based | | Operating-system maturity | Cadence, metrics, and owners are clear | Company runs on memory, escalation, and improvisation | | Candidate-supply constraint | Strong local market | Strong candidates are likely outside your city |
How to interpret the pattern:
- High physical workflow + high office/site team: lean on-site or regular travel.
- High founder-context + low physical workflow: use hybrid onboarding, then remote cadence.
- Low physical workflow + distributed team: remote-first is usually viable.
- Low operating-system maturity: do not assume on-site fixes it; make the operating rhythm part of the mandate.
- High candidate-supply constraint: avoid unnecessary location filters unless proximity clearly changes the work.
What to decide before contacting candidates
Before you speak to operators, write a short location brief:
Role type:
Operating problem:
Where the work happens:
Decisions the operator owns:
Founder handoff:
Required in-person moments:
Remote/hybrid cadence:
First 30 days location expectation:
Travel or site requirements:
What location is not solving:
That last line matters. Do not use location to cover for a vague mandate, weak authority, or poor communication habits.
Turn the location decision into a stronger shortlist
Once the working model is clear, use it as a search filter and an interview topic.
Ask candidates:
- What operating work have you done successfully remotely?
- When have you needed to be in person to diagnose the real issue?
- How would you design your first 30 days if the role is remote-first?
- What cadence would you need from the founder?
- Which parts of this mandate would you refuse to do without site access or office time?
- How do you keep trust and accountability high without adding meeting tax?
Good operators will have a point of view. Be careful with candidates who are ideological either way: “remote always works” and “operators must always be in the room” are both too simplistic.
Use FindOperators profiles as diligence inputs, compare role pages through /browse, and ask operators to submit a profile with clear location, timezone, availability, and working-model preferences.
Sources and further reading
- First Round Review: Make Operations Your Secret Weapon — operations-leadership timing, operator archetypes, and why the role depends on the company’s real constraint.
- Sifted: How to hire a chief operating officer — founder-COO fit, trust, autonomy, and role design for startup COO hires.
- Sifted: How to define the type of COO you need — guidance on matching COO type to the founder/company gap rather than treating COO as one fixed job.
- Startup Jobs: remote COO listings — live-market evidence that COO/operator roles can be remote or hybrid, but the individual mandate still determines fit.
Bottom line
Remote vs on-site is not a philosophy question. It is an operating-design question.
Hire remote when the work is visible, written, and system-driven. Hire on-site or require regular travel when the work depends on physical observation, informal trust, or site-level reality. Use hybrid when the operator needs early context but not permanent proximity.
The best answer is usually: hire the strongest operator you can access, make the mandate specific, and use in-person time deliberately rather than nostalgically.