Your implementation pod

A named four-person pod, on every workspace

No round-robin tickets. No tier 1 / tier 2 escalation maze. From day one you have a solution architect, a finance ops lead, a security partner, and a customer DRI — published in your workspace, with tenure, on-call rotation, and direct lines.

Pod size

4

Named, photographed, reachable

Median tenure

8.4 yrs

In domain, not at ADmetric

First response (SEV-1)

≤ 15 min

Pod DRI on bridge ≤ 30 min

Max workspaces / pod

6 – 12

Capacity enforced, not aspirational

Roles on your pod

Solution architect

Owns the deployment plan, integration design, and acceptance tests. Sits in your weekly stand-up for the first eight weeks; after go-live moves to monthly business review.

Median experience
7.4 yrs in ad ops / fintech
On-call coverage
Business hours in your timezone
Capacity ratio
Max 6 workspaces per architect

Finance operations lead

Owns budget policy translation, pacing windows, reconciliation rules, and the chart-of-accounts mapping. Pair-programs your first month-end close with your controller.

Median experience
9.1 yrs as FP&A / treasury
On-call coverage
Business hours, close week always covered
Capacity ratio
Max 8 workspaces per lead

Security partner

Owns SSO, SCIM, KMS keys, role design, and the security questionnaire. Runs the first tabletop with your CISO within 30 days.

Median experience
11 yrs in security engineering
On-call coverage
24/7 for SEV-1 and SEV-2
Capacity ratio
Max 12 workspaces per partner

Customer DRI

Single named point of contact, end to end. Owns escalations, schedules QBRs, hosts office hours, and signs your annual integrity letter.

Median experience
6.2 yrs in enterprise SaaS
On-call coverage
On bridge during SEV-1 within 30 min
Capacity ratio
Max 10 workspaces per DRI

Why a named pod, not a queue

  • Continuity beats volume. The same four people in week 1 are the same four in year 4.
  • Escalation paths are pre-named, with backups, published on /decision-rights.
  • Workspace capacity is hard-capped. If a pod is full, we hire — we do not stack new customers on tired engineers.
  • Pod composition changes only with 30 days written notice and an introduction from the outgoing member.