Skip to content
Ashish Kumar AgnihotriOperating Partner

The remote model

Remote Fractional COO — How a Distributed Operating Partner Works

Remote operating leadership has a bad reputation it mostly earned: a standing video call, a monthly deck, no ownership, no artefacts. This page describes the version that works — cadence, scorecards, written decisions, real accountability — and is equally specific about where remote fails. It is the operating manual for how my own distributed engagements run, published so you can inspect it.

The prejudice against remote operating leadership rests on a real observation wrongly attributed. Companies that hired remote advisers and got nothing lasting did not fail because of distance; they failed because the engagement had no structure distance could expose. An on-site consultant can hide thin work behind presence — visible busyness, hallway rapport, being seen in the right meetings at the right moments. A remote operator has no such cover. Everything must exist in artefacts: a scorecard that updates on a known rhythm, a decision log anyone can inspect, documented workflows with named owners, outcomes measured against numbers agreed in advance. Distance does not weaken operating discipline. It audits it, weekly, in front of your whole leadership team.

My conviction here is not theoretical. For nineteen years I ran operations where distribution was the baseline condition — most recently as Senior Director, Business Excellence at Publicis Groupe, leading quality and delivery across global digital operations: 500+ clients, teams of more than 2,000 people, over USD 750 million in annual media spend, for brands including Disney, Samsung, Adobe and P&G, served from inside a global network. The account lead, the production hub, the quality layer and the client routinely sat on different continents. The results that survived that condition — 95% to 99% quality across 2,000+ campaigns, USD 20M+ protected by audit, billing compressed from two months to fifteen days across 75 entities — were produced by systems, not proximity.

This page is the model itself, stated plainly rather than sold: the weekly cadence and what happens inside it, hour by hour; what ownership means when the operator is not in the building, and where the line sits between owning and advising; the scorecard and the written artefacts that carry the engagement between reviews; the time-zone architecture that lets one practice, based in Gurgaon, serve the US East Coast, all of Europe, the Gulf, Singapore and Australia in their own working hours; and — because credibility requires it — the specific, recurring circumstances in which remote operating leadership fails and a resident operator is the honest recommendation instead.

In depth

What you need to know.

Distance punishes ambiguity — which was already your problem

Every operating failure I have ever unpicked reduces to ambiguity somewhere: who owns this step, what does “done” mean, which number is the real one, who decided what and when. Co-located companies survive their ambiguity longer because proximity keeps patching it — someone leans over a desk and asks. Distance removes the patch, which is why weak remote engagements collapse fast; the ambiguity was always there, now nothing hides it. This is also why a disciplined remote engagement often outperforms a co-located one: it is forced to fix the root condition. Every owner named. Every definition written. Every decision logged. One source of truth for every number that matters. Companies emerge from that discipline stronger for reasons that have nothing to do with where the operator sat.

The weekly operating cadence, hour by hour

The heartbeat of the engagement is one weekly operating review, held live in the client’s working hours, run to a fixed grammar. It opens on the scorecard — the handful of numbers leadership has agreed actually matter — with each owner speaking to their own line: on track, off track, why. Off-track items get decisions, not discussion for its own sake: a call is made in the room or explicitly assigned with a date, and either way it enters the decision log. New issues are triaged onto the scorecard or consciously parked. The review closes in under an hour because preparation happened asynchronously — my analysis and the updated scorecard land before the meeting, not during it. Between reviews: one-to-ones with process owners, escalations inside agreed windows, and the documentation that turns fixes into systems.

Ownership at distance: the line between owning and advising

The word that separates a fractional COO from a consultant is ownership, and it survives distance intact if it is defined honestly. Owning a process remotely means: the number attached to that process is mine to move and mine to answer for at the weekly review; the workflow design, the escalation rules and the quality gate are my decisions, made with the team but not delegated upward to the founder; when the process fails at 2am your time, the post-mortem lands on my desk, and the fix ships with my name on it. What ownership does not require is standing beside the team while they execute — at Publicis Groupe the teams executing my quality systems were thousands of people I would never meet, across continents, and the score still moved from 95% to 99%.

The scorecard: one source of truth or nothing

Remote operating leadership runs on a single artefact more than any other: the leadership scorecard, built on one source of truth. Not five dashboards that disagree; not a spreadsheet someone reconciles the night before the board meeting — one place where the ten or twelve numbers that describe the operating reality live, updated on a known rhythm, with an owner against each. Installing it is usually the first month’s work, and it is diagnostic in itself: every disagreement about whose number is right exposes a process seam nobody owned. Once it exists, distance becomes largely irrelevant to oversight — I can see what the leadership team sees, at the same moment, from Gurgaon or from your boardroom. The scorecard is also what I hand back: it remains, fully yours, when the engagement ends.

Written artefacts: the paper trail that replaces the hallway

Co-located companies run on an invisible infrastructure of hallway agreements — fast, warm, and completely unauditable. A distributed engagement replaces that hallway with paper, deliberately: a decision log recording what was decided, by whom, on what basis, so nothing relies on memory across time zones; documented workflows with named owners at every handoff; playbooks written as the work stabilises, so the operating model becomes teachable rather than resident in one head; and written escalation paths with clock-time commitments, so urgency has a protocol instead of a mood. Teams resist this for about six weeks, then discover the compounding return: onboarding accelerates, disputes about who-said-what disappear, and the operating model survives the departure of any individual — including, by design, me. The artefacts are the asset; the meetings are just where they get exercised.

The time-zone architecture of a global practice

Serving five regions from one desk in Gurgaon is an engineering problem, and India is unusually well-placed for it. The UAE sits ninety minutes behind me — effectively a shared day. Europe’s working day, three and a half to five and a half hours behind India, fills my afternoon and evening; London fits the same envelope. Singapore, two and a half hours ahead, and Australia’s east coast, four and a half to five and a half ahead, occupy my morning — their afternoons. The US East Coast morning lands in my evening, a window I hold deliberately for American clients. The result: every client’s weekly review runs live in their own business hours, and my non-overlap time produces the written work each region wakes up to. This architecture was my daily reality at network scale; the practice simply formalises it.

When remote fails: the honest list

Remote operating leadership fails in four specific, predictable circumstances, and pretending otherwise would cost us both. It fails when the work is physical — plants, warehouses, retail floors, kitchens — because the operating truth lives in the building and must be walked, not reported. It fails when the leadership team will not write things down: if every commitment made in a scorecard review dissolves by Thursday, the artefacts become fiction, and no cadence survives fictional artefacts. It fails when the founder wants a presence — a reassuring senior figure seen by staff and investors — rather than an operating system; that is a legitimate want, but it is a different purchase. And it fails when the company is too early: below roughly thirty people, there is no operating layer to install, only work to do. In each case, I say so at the diagnostic and stop.

What on-site time is for, and how to start

Remote-first is not remote-always. Travel, by arrangement, has three legitimate uses: the kickoff immersion, where mapping the operation and earning the leadership team’s trust genuinely benefit from a week in the building; the milestone moment — an operating-model rollout, an annual planning cycle, a board session — where symbolism and substance coincide; and the periodic recalibration visit on long engagements, particularly for near markets like the Gulf where flights are short. What travel must never become is the product. If presence is doing the persuading, the system is not. Starting is deliberately low-commitment either way: a conversation in your hours, then a fixed-fee diagnostic — two to four weeks, a written board-ready read, a plain recommendation — which doubles as a live trial of this entire model before you owe anyone a retainer.

Questions

Common questions.

Yes, and the proof standard should be biographical, not rhetorical. I spent nineteen years running operations where the team, the client and the quality layer sat on different continents — most recently leading Business Excellence across Publicis Groupe’s global network: 500+ clients, 2,000+ people, USD 750M+ in annual media spend, serving brands including Disney, Samsung, Adobe and P&G from inside that network. The measured results survived exactly the distance this page is about. Ask any remote operator the same question: not whether distance works, but what they have already made work across it.

By architecture rather than heroics. India’s clock position is the quiet advantage: the Gulf is ninety minutes away, Europe fills my afternoon and evening, Singapore and Australia occupy my morning, and the US East Coast morning lands in my evening — a window I hold for American clients. Every engagement’s weekly review therefore runs live in the client’s own business hours, without exception. The non-overlap hours are not dead time; they produce the analysis, scorecard updates and documentation each region wakes up to. No client shares my calendar; each one experiences the practice in their own day.

The structure is the honest answer. My engagements run as a fixed-fee diagnostic first — two to four weeks, priced separately, ending in a written recommendation — then a monthly retainer scaled to cadence and scope, never hourly. On levels: the most transparent published benchmarks are American, clustering experienced fractional COOs in the low-to-mid five figures per month; UK and European levels generally track below that; an India-cost-base practice prices materially below all of them for equivalent seniority. Remote is not a discount tier — the cadence and ownership are identical. The economics differ because the cost base does, not the product.

The one with verifiable distributed-scale evidence, because remote work strips away every substitute for it. Four filters: operations actually run across geographies — mine spanned 500+ clients and 2,000+ people across continents at Publicis Groupe; measured results that survived distance — 95% to 99% quality across 2,000+ campaigns, USD 20M+ protected by audit, billing from two months to fifteen days across 75 entities; a concrete ninety-day installation plan stated before signature; and artefacts — scorecard, decision log, playbooks — that remain when the engagement ends. Local candidates deserve the same filters. Distance just makes the gaps easier to see.

Yours, deliberately. The model is tool-agnostic because the discipline lives in the artefacts, not the software: a scorecard on a single source of truth, a decision log, documented workflows, written escalation paths. Those can live in whatever your team already uses — spreadsheets and shared documents included — and installing them in your existing stack is a feature, not a compromise, because the system must remain fully operable by your team after I leave. What I do not do is arrive with a proprietary platform your company becomes dependent on. Dependence is the failure mode this entire practice is designed against.

Ownership, cadence and consequences. A consultant analyses, recommends and departs; the risk of execution stays entirely with you. A fractional COO owns processes — the number attached to each owned process is mine to move and mine to answer for at every weekly review. A consultant’s deliverable is a document; mine is an installed operating system: scorecard running, decisions closing, quality measured, playbooks written, team trained to run it without me. The remoteness changes neither definition — it just makes the difference unmissable, because a remote consultant leaves nothing behind and a remote operating partner leaves everything behind.

Four cases, stated as plainly on this page as in my diagnostics. Physical operations — plants, warehouses, retail, hospitality — where the truth lives on a floor someone must walk. Leadership teams that will not commit decisions and definitions to writing, because every remote artefact then becomes fiction. Founders who, examined honestly, want a visible senior presence for staff and investors rather than an operating system — a legitimate need that a resident executive serves better. And companies below roughly thirty people, where the work is doing, not installing. If your situation is one of these, the diagnostic will say so, and the engagement will not proceed.

A conversation held in your working hours — the first small proof of the architecture — followed, where the problem warrants it, by the fixed-fee diagnostic: two to four weeks of structured leadership interviews, a review of your numbers and workflows, and a written, board-ready report on where the operating model strains, what that costs, and what to fix first. The diagnostic is deliberately a working trial of everything this page describes: the overlap scheduling, the written artefacts, the cadence. If the model suits you, you will feel it inside a month — and if it does not, the report says so and stands alone.

The next step

A short conversation settles most of this — and a fixed-fee diagnostic settles the rest.

Book a consultationThe diagnostic

Keep exploring

Fractional COO cost: India, USA & EuropeStructures, benchmarks and the value arithmetic.What is a fractional COO?The plain-language guide to the role.Hire a fractional COOThe buyer’s guide — process, questions, red flags.Fractional COO servicesScope, deliverables and the engagement itself.Fractional COO for USA companiesThe model applied to the US market.Fractional COO for European companiesThe model applied across CET.