Small Agency Remote Operations: A Case Study in Distributed Service Work

Most remote work writing focuses on product teams. Service businesses — agencies, consultancies, firms that sell their work as discrete projects — face a different and harder problem. Their work is produced for a client who is paying attention to every milestone, often on a timeline set by the client rather than the team. Moving that work remote is not just a matter of changing where people sit. It changes how the work itself is structured.

This case study looks at a 12-person creative agency that moved fully remote over 18 months. The agency, which we will call Northbound, does brand and digital work for mid-sized B2B clients. Before the move, they worked out of a single office. After the move, they spanned four time zones across two continents. The story of how they got there is more useful than the outcome, because the failures are the parts most agencies repeat.

The starting point: why service work is harder to remote

A product team owns its roadmap. An agency owns someone else's roadmap, on someone else's timeline, with someone else reviewing the work at every milestone. That difference shapes everything. In an office, the client-facing rhythm is implicit: the client emails the account lead, the account lead walks over to the designer, the designer shows the work, the account lead walks back and replies. Remote work removes the walking-over step, which sounds trivial until you realize it was carrying half the context.

Northbound's first attempt at remote work was, in the founder's words, “the office, but on Zoom.” They kept the same meetings, the same review cycles, the same default to synchronous communication. Within six weeks, two things broke. The designers in the inconvenient time zones started missing reviews because the reviews were scheduled at their dinner time. And the account leads started forwarding client emails directly to designers with no context, because the walk-over conversation no longer happened.

The pattern is common. The lesson is that an agency cannot remote its way around an office workflow. The workflow itself has to change.

The three systems that did the heavy lifting

Once Northbound accepted that the workflow had to change, they built three systems that carried most of the weight. Each one replaced something the office used to do implicitly.

The three systems

1

Async review systemReplaced the walk-up review with a written review document. Designers post work for review at a predictable time; reviewers leave structured written feedback within a window; live review is reserved for creative direction that genuinely needs discussion.

↓

2

Client-facing information flowReplaced the implicit client context with a deliberate upward flow: a weekly client update, proactive flags when scope or timeline shifts, and a shared project view the client can check without asking.

↓

3

Onboarding as context transferReplaced the osmosis of office learning with a written onboarding system: a project wiki, a documented review process, and a buddy system that pairs new hires with a senior for the first month.

The systems are not novel. What made them work was that Northbound treated them as the work, not as overhead. The async review was not a temporary pandemic measure; it was how reviews happened from then on. The client update was not an extra task; it was part of the account lead's job, scheduled into the week.

System one: async reviews replaced walk-up reviews

The biggest single change was killing the walk-up review. In the office, a designer could turn their monitor toward a creative director and get feedback in two minutes. Remotely, the equivalent was a video call, and video calls do not scale across time zones. The first failure was scheduling reviews at times that worked for the creative director but not for the designers in other time zones.

The fix was a written review system with a predictable cadence:

• Designers post work for review by 10am in the creative director's time zone. The post includes the goal of the work, the constraints, and the specific questions the designer has.
• The creative director leaves written feedback by end of day. Structured: what is working, what is not, what to change next. No vague “make it pop.”
• Live review is reserved for creative direction. Decisions about direction, tone, or major pivots happen in a 30-minute call, not in writing. Everything else is async.

The system took three weeks to feel normal. The creative director initially hated it, because written feedback felt slower than talking. By week four, the team realized the written record meant feedback was no longer forgotten, misremembered, or inconsistently applied across designers. The slowness was a feature.

System two: the client-facing information flow

The second failure was the one most agencies miss. In an office, the client feels informed because they can walk in, or because the account lead can give them a quick verbal update. Remotely, the client only knows what they are explicitly told. Northbound lost a client in month three of the transition because the client felt out of the loop, even though the work was on track.

The fix was a deliberate client-facing information flow that mirrored the internal one:

• A weekly client update. Same structure as the internal status update: what moved, what is next, what risks or decisions need client input. Sent Friday morning, client time zone.
• Proactive flags when something changes. Scope shifts, timeline shifts, anything that changes the agreed plan. Sent the day the change is visible, not buried in the weekly update.
• A shared project view. The client can see the current state of the project without asking. Status, milestones, open questions. Not a live dashboard that updates every minute — a stable view that reflects reality.

The shared project view was the most contentious internally. The account team worried it would replace them. It did the opposite: it removed the status-update meetings, which freed the account team to do the actual relationship work that no dashboard can do.

System three: onboarding as context transfer

The third system was the one Northbound wished they had built first. In the office, new hires learned by osmosis: they overheard reviews, watched how the account team talked to clients, picked up the unwritten conventions of the work. Remotely, none of that happens. A new hire knows exactly what they are told and nothing more.

The onboarding system Northbound eventually built had three parts:

• A project wiki. Every active project has a page: the goal, the client, the constraints, the current state, the open questions. New hires read the wiki for their first week instead of being thrown into work.
• A documented review process. The async review system is written down, with examples. New hires know what a good review post looks like before they post one.
• A buddy system. Each new hire is paired with a senior team member for the first month. The buddy's job is to answer the questions that are too small to feel worth asking in a team channel.

The buddy system mattered more than the wiki. The wiki carried the explicit knowledge. The buddy carried the implicit knowledge — the “we usually do it this way,” the “this client hates surprises,” the “don't bother the creative director before noon.” Without the buddy, the wiki was a manual that no one read.

The failure that almost killed the transition

In month four, Northbound nearly lost a second client, and this time it was not a communication problem. It was a handoff problem. A designer in one time zone handed work to a developer in another, with a task list but no context. The developer rebuilt a section from scratch because they did not understand why the designer had made certain choices. The client saw the rebuild in a review and asked why the work had changed. The account lead could not answer.

The fix was a handoff document that carried three things: the current state, the reasoning behind the key decisions, and the open questions the next person was empowered to decide. It took five minutes to write and would have saved a week of rework. The agency added handoff documents to the review process, and the same failure never happened again.

What the numbers looked like one year in

A year after the transition, Northbound tracked a few metrics to see whether the move had actually worked. The numbers are specific to them, but the direction is likely generalizable to similar agencies.

• Client retention held. The two clients lost during the transition were replaced, and the agency retained its longest-standing clients. The client-facing flow was working.
• Review cycle time dropped by a third. Async reviews were faster than walk-up reviews, because the creative director could batch feedback instead of being interrupted. This was unexpected.
• Hiring cost fell. Access to a wider talent pool meant the agency filled roles faster and at lower recruiting cost. The savings on office space were real but secondary.
• Late-night calls dropped to near zero. The on-call rotation and the async default meant the founders were no longer woken up for non-urgent issues. This was the metric they cared most about.

The number that mattered most was not on the list: no one quit. The transition had been hard, and two people had considered leaving in month four. A year in, the team was stable, the work was shipping on time, and the founders were sleeping through the night.

Frequently asked questions