Account Assignment Model — 2-Person Per Account Structure

Overview

Asymmetric has moved to a structured 2-person-per-account model for client management. Each client account has two designated primary team members responsible for that relationship, replacing a looser arrangement where ownership was less explicit. Developers are also to be included in the assignment spreadsheet where they are heavily involved in day-to-day client work.

This model was discussed and clarified during the ^[1].

The Model

Primary Assignment

• 2 named team members are assigned to each client account as primary owners.
• A third person may be pulled in situationally, but the two primaries carry ongoing responsibility.

Developer Inclusion

• Developers (e.g., Raphael, Jeff) should be listed in the client assignment spreadsheet when they are heavily involved in an account — not just occasional contributors.
• The recommendation is to add them to the account manager column for those accounts, rather than a separate field, to keep them visible as active team members.

"What I would consider doing is adding Raphael to the account manager column on the ones that he's really heavily involved in." — Mark Hope

Spreadsheet Updates Required

Melissa Cusumano owns the client assignment spreadsheet and is responsible for the following updates:
- Add a Dev column to capture developer assignments
- Add Raphael to accounts where he is heavily involved (e.g., Scullin, Machine Resources)
- Add Jeff to Reynolds
- Remove Ben San Fratello from active assignments
- Reflect the 2-person model across all accounts

Known Account Assignments (as of 2026-02-26)

This table reflects discussion during the meeting and may not be fully reconciled with the spreadsheet. Treat the spreadsheet as the source of truth once updated.

Rationale

The 2-person model addresses several operational pain points:
- Coverage gaps when one team member is unavailable (travel, illness, departure)
- Knowledge silos where only one person understands a client relationship
- Developer visibility — it was noted that Mark frequently didn't know which developer to contact for a given account

Related Processes

• Client Brain is the single source of truth for client history, meeting notes, Slack threads, and sentiment tracking. Team members should consult it before client calls rather than relying solely on personal notes or Google Drive folders.
• Meeting prep should include having all relevant tabs open before a call begins — dashboards, ad accounts, analytics, etc.
• The assignment spreadsheet lives in the shared Google Drive and is maintained by Melissa Cusumano.

Action Items

• [ ] Melissa Cusumano — Add Dev column to client assignment spreadsheet; add Raphael (Scullin, Machine Resources); add Jeff (Reynolds); remove Ben; reflect 2-person model throughout
• [ ] Melissa Cusumano — Schedule Asymmetric website/ABM content call with Mark

Related Articles

• ^[2]
• ^[3]
• ^[4]
• ^[5]
• ^[6]