Team Operations

Summary

Asymmetric operates as a lean remote-first agency where staffing decisions are driven by revenue events — not performance cycles — and where operational gaps surface quickly when headcount drops. The November 2025 restructuring (triggered by a $102k invoice backlog) and the February 2026 account manager departure both exposed the same underlying fragility: the team has minimal redundancy in technical and account coverage roles. The Philippines-based staffing model is structurally sound but requires deliberate overlap management and localized HR policies. The most persistent operational risk is not headcount but accountability: task non-completion and uneven communication tool adoption have both created client-facing failures.

Current Understanding

Asymmetric's team operations reflect the constraints of a small agency trying to maintain client coverage across a distributed workforce while managing cash-flow-driven headcount changes. The structural decisions — Philippines-based specialists, consolidated account manager coverage, role shadowing for transitions — are coherent responses to those constraints, but they create specific failure modes that recur.

Staffing Model and Geographic Distribution

Asymmetric is remote-first with US-based account managers and coordinators operating on 8 AM–5 PM Central Time, and Philippines-based specialists required to maintain a 4-hour overlap from 8 AM–12 PM CST ^[1]. In practice, this means Philippines team members work 7 PM–4 AM Philippine Time — a significant schedule inversion that is a deliberate trade-off for cost and coverage. Roy Tolosa, hired as Social Media Specialist on March 4, 2026 at $775/month, is the clearest example of this model in action ^[2]. Philippines team members receive 7 paid Philippine holidays per year in lieu of US federal holidays, with the exception of Christmas Eve, Christmas Day, New Year's Eve, and New Year's Day, which are observed universally ^[3].

The Account Coordinator role carries a geographic constraint that sits in tension with the remote-first model: candidates are expected to be within reasonable driving distance of Madison, WI (Oconomowoc, roughly one hour, is cited as acceptable), and the role requires at least one in-person client visit per quarter ^[4]. This is the one role where physical proximity is operationally required, not just preferred.

Restructuring Triggers and Headcount Decisions

Both major restructuring events in the observation period were revenue-driven, not performance-cycle-driven. The November 2025 restructuring followed a $102k invoice backlog — $34k of it overdue — that forced Mark to personally fund payroll ^[5]. Chris was terminated for a combination of high cost, wrong time zone, and a client communication style described as polarizing. Anup's hours were cut as a direct cost reduction measure. Ben received a formal performance warning with explicit messaging that output pace needed to improve immediately.

The February 2026 restructuring was triggered by client losses that reduced capacity needs, leading to Ben San Fratello's departure around February 27, 2026 ^[6]. In both cases, the restructuring created coverage gaps that required immediate reallocation: after Chris's termination, Mark spent five hours personally resolving 502 errors on the Doodler of Farms site because no one else on the team had the technical depth to handle server-level debugging ^[5]. This is the clearest evidence that the team operates with near-zero technical redundancy.

Role Transitions and Onboarding

Role transitions follow a structured shadowing model rather than immediate full ownership. Ben (a different Ben from San Fratello) is being transitioned into account management starting with Citrus America through a shadowing approach, with Mark and Melissa remaining actively involved rather than handing off the account ^[7]. Sebastian is being assigned to Abdabakir specifically because his PPC and SEO background aligns with that client's needs — account assignments are being made on skill match, not just availability ^[7].

New hire onboarding is operationalized through ClickUp task checklists with explicit completion targets. Roy's onboarding had a target completion date of March 7, 2026 — three days after his start date — with tool access tracked by status (confirmed vs. pending) and dependencies on other team members noted ^[2]. One internal contradiction: Roy's HubSpot access appears as both confirmed and pending within the same onboarding document, suggesting the checklist was not fully reconciled before use.

Operational Infrastructure and Accountability

The communication protocol assigns distinct channels by purpose: email for client-facing decisions, ClickUp for project-specific work, Slack for quick internal communication, and Google IM for urgent leadership escalation ^[8]. In practice, Slack adoption was uneven as of October 2025, with some team members checking it once per day or less — a gap that creates real response latency for anything routed through that channel.

The accountability framework is explicit: leadership treats failure to complete an assigned task as job failure, not a process gap ^[9]. The American Extractions case illustrates the stakes — ads confirmed as not running remained offline for a week despite explicit direction to activate them, while the client had been requesting leads for weeks ^[9]. The software subscription audit, initiated February 20, 2026 and assigned to Isalia Ramirez, reflects the same pattern: operational problems are addressed through systematic audits once they surface, not proactive monitoring. The LastPass audit found 20 licenses purchased against 12 active users (8 unused seats) and a defunct egan@getfound address as the account contact — a security and lockout risk that had gone undetected ^[10].

These operational gaps connect directly to the restructuring pattern: when the team is under revenue pressure, the bandwidth for proactive infrastructure maintenance disappears, and problems accumulate until they force a reactive response.

What Works

Skill-matched account assignments. Assigning Sebastian to Abdabakir because his PPC and SEO background aligns with that client's needs is a more defensible allocation than pure availability-based assignment. It reduces the ramp time for the account manager and increases the likelihood of substantive client conversations from the start ^[7].

Shadowing-based role transitions. Rather than handing off accounts immediately after a restructuring, the shadowing model keeps experienced team members (Mark, Melissa) actively involved while the incoming manager (Ben) builds context. This reduces the risk of client relationship disruption during transitions, though it does create a temporary period of over-staffing on the account ^[7].

Philippines-based specialist model for defined-scope roles. The Social Media Specialist role maps cleanly onto the Philippines staffing model: the work is asynchronous-compatible, the 4-hour overlap window covers coordination needs, and the cost structure ($775/month for Roy) is materially lower than a US-based equivalent. The model works because the role has clear task boundaries and does not require real-time client interaction ^[11].

Batch-oriented content planning. Karly's social content for most clients is pre-planned through June, which allows Roy to work ahead on batches rather than scrambling at month-end. This is a structural advantage that reduces deadline pressure and enables quality review before publication ^[12].

Workload reallocation to address design team overload. When the design team was identified as overloaded during Sprint 10 planning, blog imagery work was reallocated to Gavin for placeholder insertion, with Jeff retaining final image selection. This freed design capacity without eliminating the quality gate ^[13].

Consolidated social media task ownership. Assigning both copy and graphics to a single Social Media Specialist (rather than splitting across roles) reduces handoff friction and clarifies accountability for the deliverable ^[14].

Localized holiday policy for international team members. Giving Philippines-based team members 7 Philippine holidays in lieu of US federal holidays is a straightforward equity adjustment that acknowledges the actual cultural context of those employees. The universal holidays (Christmas Eve/Day, New Year's Eve/Day) provide a shared anchor point ^[15].

ClickUp-based onboarding checklists with explicit completion targets. Structured onboarding with status-tracked tool access and a defined completion date (Roy's was March 7, three days post-start) creates accountability for the onboarding process itself, not just the new hire's performance ^[2].

What Doesn't Work

Reactive software subscription management. The LastPass situation — 8 unused seats, a defunct account contact email, and an upcoming renewal date — was not caught until a formal audit was initiated. Proactive subscription monitoring would have surfaced this months earlier. The audit itself was triggered by the problem, not by a standing process ^[10].

Assuming Slack as a real-time communication channel. The protocol designates Slack for quick internal communication, but as of October 2025, some team members were checking it once per day or less. Routing time-sensitive internal communication through a channel with inconsistent adoption creates response gaps that are invisible until they cause a problem ^[8].

Terminating technical specialists without coverage planning. Chris's termination created an immediate technical coverage gap that Mark had to fill personally — five hours on 502 errors for Doodler of Farms. The decision to terminate was financially justified, but the absence of a coverage plan for server-level debugging and complex integrations was a foreseeable gap that wasn't addressed before the departure ^[5].

One-pager proliferation as a response to performance gaps. At Agility Recovery, the organizational response to performance issues was to create training artifacts — 123+ one-pagers accumulated, creating content sprawl and version drift. Three training requests arrived in a single week, none of which were genuine training problems. This pattern treats documentation as a substitute for addressing root causes ^[16].

Feedback conversations in low-psychological-safety environments. Agility Recovery employees interpret direct feedback conversations as performance management actions rather than development opportunities. This is a client-side observation, but it's relevant context for any engagement involving Agility Recovery's internal team dynamics ^[16].

Onboarding checklists with unresolved status conflicts. Roy's onboarding checklist listed HubSpot access as both confirmed and pending within the same document. An unreconciled checklist creates ambiguity about what's actually complete and can leave new hires without access to tools they need ^[2].

Patterns Across Clients

Revenue events drive staffing decisions faster than performance cycles. Both the November 2025 and February 2026 restructurings were triggered by external revenue events (invoice backlog, client losses), not by planned performance reviews. This means headcount decisions happen under financial pressure rather than strategic planning conditions — which increases the likelihood of coverage gaps. Observed in both restructuring events ^[17].

Client-facing failures follow internal accountability gaps. The American Extractions ads case is the clearest example: a client requesting leads for weeks, ads confirmed offline, explicit direction given, and still a week of inaction. The task completion accountability framework was created in direct response to this pattern. The gap between "leadership directed it" and "it happened" is the operational risk ^[9].

Content pre-planning creates asymmetric workload distribution across accounts. For Crazy Lenny's and Doodla, Karly's content is pre-planned through June, enabling Roy to batch work efficiently. Scotland is the exception — content arrives only a few days before the month, requiring close-to-deadline execution. This means Roy's workload is not evenly distributed across accounts, and Scotland creates a recurring deadline crunch ^[12].

Account coordinator role standardization is ongoing, not complete. The role refinement initiated in late September 2025 was designed to standardize expectations between Carly and Sebastian. The fact that this was necessary suggests the role had been operating with informal, person-dependent expectations rather than documented standards ^[18].

Design team capacity is a recurring constraint. The Sprint 10 reallocation of blog imagery to Gavin was a direct response to design team overload. This suggests design capacity is consistently tight relative to demand, and that workload reallocation is the primary relief valve rather than headcount addition ^[13].

Remote culture maintenance requires deliberate investment. Monthly "Sip & Sinks" (rotating team-hosted virtual social events), personal photo sharing in shared channels, and quarterly in-person client visits for Account Coordinators are all intentional practices — not organic outcomes of remote work. Without these, the distributed team would have minimal social cohesion ^[4].

Agility Recovery's internal operations reflect a documentation-over-development culture. 123+ one-pagers, no dedicated trainer until Gus Donelson's hire, and employees who interpret feedback as performance management rather than development — these are consistent signals of an organization that has substituted artifact creation for genuine capability building. This context matters for how Asymmetric frames recommendations to that client ^[16].

Exceptions and Edge Cases

Universal holidays override the Philippines/US split. Christmas Eve, Christmas Day, New Year's Eve, and New Year's Day are observed by all team members regardless of location. This is the one exception to the rule that Philippines-based team members work on US holidays in exchange for their own national holidays ^[15].

Design team involvement in social media tasks is permitted for brand-specific work. The default is consolidated copy-and-graphics ownership under the Social Media Specialist. The exception: Andrzej, Michał, and Łukasz (the design team) may be added as consultants when Photoshop work, brand-specific assets, or template files are required. This is a consultant role, not co-ownership ^[14].

Scotland account requires near-deadline execution. The general model of batch-ahead social content planning breaks down for Scotland, where content typically arrives only a few days before the month. This account cannot be managed with the same lead time as Crazy Lenny's or Doodla, and Roy's workflow needs to account for that separately ^[12].

Blog imagery workflow has a two-stage ownership split. Gavin handles placeholder insertion; Jeff retains final image selection and does not delegate publication. This is a deliberate quality gate, not an oversight — Gavin does not have authority to finalize or publish posts ^[13].

Account Coordinator geographic requirement contradicts remote-first framing. The role requires proximity to Madison, WI for quarterly in-person client visits, which effectively makes it a regional hire despite the agency's remote-first identity. This is a functional constraint driven by client relationship requirements, not a policy inconsistency ^[4].

Evolution and Change

The observation period (September 2025–April 2026) captures a team in active structural flux. In September 2025, the Account Coordinator role was being standardized — a signal that the team had grown to a point where informal role definitions were creating gaps. By November 2025, the $102k invoice backlog forced an acute restructuring: one termination, one hours reduction, one performance warning, and a leadership-funded payroll. This was the most disruptive single event in the period.

Between November 2025 and February 2026, the team was in a stabilization phase: ClickUp launch was deferred to after January 1, 2026 pending Mark's sign-off, and the holiday period was managed with Melissa as the designated point of contact. The February 2026 account manager departure (Ben San Fratello) was a second restructuring event, smaller in scope but consequential for account coverage — the response was to double up remaining account managers on accounts rather than backfill.

The March 2026 Roy Tolosa hire represents the first net-new headcount addition in the period, and it's a specialist role (Social Media) rather than a generalist one. This suggests the agency is moving toward a model where specialist functions are staffed internationally at lower cost, while US-based headcount is reserved for client-facing account management.

The software subscription audit initiated in February 2026 signals a shift toward more proactive operational infrastructure management — though it was itself reactive in origin. If the tracker Isalia Ramirez was tasked with building becomes a standing process, it would represent a genuine operational maturation. Whether that happens is not yet visible in the evidence.

Gaps in Our Understanding

No visibility into account manager workload after doubling up. Following Ben San Fratello's departure, remaining account managers are covering more accounts. We have no data on whether this is sustainable or whether it's creating service quality degradation on specific accounts.

Roy's performance post-onboarding is unobserved. Roy joined March 4, 2026. The evidence covers his onboarding structure but not his output quality, client feedback, or whether the Scotland account's close-to-deadline content pattern is creating problems in practice.

Anup's expanded role is unresolved. Anup expressed interest in building Meta ads, which could free Sebastian's time. Whether this was acted on, and whether Anup has the skills to execute it, is not captured in any fragment.

No evidence on Didion or Vilas client operations. Both clients are mentioned in the client list but appear in no fragments. We cannot assess what account coverage or operational patterns apply to them.

The software subscription tracker's current state is unknown. Isalia Ramirez was tasked with building it on February 20, 2026. Whether it was completed, what it covers, and whether it's being maintained is not captured in the evidence.

No data on the ClickUp full launch outcome. The launch was deferred to after January 1, 2026 pending Mark's sign-off. Whether it launched, what the adoption looked like, and whether it resolved the time tracking and task management gaps is not visible in the fragments.

Open Questions

What is the right technical coverage model after Chris's departure? Mark spending five hours on 502 errors is not a scalable solution. Does the agency need a part-time technical contractor on retainer, or can Anup's skills be developed to cover basic server-level issues?

At what revenue level does the Philippines staffing model break down? The model works for defined-scope specialist roles. If the agency grows and needs more senior strategic capacity, the 4-hour overlap window and asynchronous-compatible work requirement may become limiting constraints.

Does the shadowing-based account transition model actually reduce client churn risk? The Citrus America transition is the test case. Whether clients notice or care about the transition, and whether the shadowing period is long enough to build genuine account manager context, is an empirical question the current evidence can't answer.

How does Slack adoption get fixed without mandating behavior? The protocol assigns Slack for quick internal communication, but adoption is uneven. Mandating check-in frequency is possible but creates resentment in a remote-first culture. What's the actual enforcement mechanism?

Is the Account Coordinator geographic requirement creating a talent pool constraint? Limiting candidates to within driving distance of Madison, WI significantly narrows the hiring pool. If the role is hard to fill, this constraint may need to be revisited against the actual frequency of in-person client visits.

What happens to the one-pager backlog at Agility Recovery? 123+ one-pagers with version drift is a content governance problem, not a training problem. Does Asymmetric have a role in helping Agility Recovery rationalize that library, or is it outside scope?

Related Topics

Sources

Synthesized from 20 Layer 2 articles, spanning 2025-09-30 to 2026-04-08.