A Firm Design Memo

The middle is a design choice, not a compromise.

You don't want to build a sweatshop, and you don't want clients to own you. The model that lives between those extremes has a name and a shape — and it requires deliberate construction, not drift.

For JO · Principal

Subject Service Tier Architecture

Frame The Leveraged Pod

01 / The Spectrum

Three firms. One is yours.

The volume firm and the boutique are not the only options — they're the two extremes most people accidentally drift toward when they don't design on purpose. The middle is a real model with its own mechanics.

Model A

The Volume Firm

"Production line for compliance"

PricingHourly / low fixed

Margin LeverHours billed

Principal RoleProduction manager

ScopeStandardized, narrow

Client Promise"Cheap & on time"

You despise hour tracking. This model lives or dies on it.

Model B — You

The Leveraged Pod

"High-touch delivery, low-touch principal"

PricingFixed annual / tier-based

Margin LeverPod capacity & tier mix

Principal RoleStrategy & escalation only

ScopeDefined by tier, not by client

Client Promise"Your pod knows you"

No hour timers. No principal-dependency. Scope discipline.

Model C

The Boutique

"Couture for the C-suite"

PricingPremium / project

Margin LeverPrincipal's hours

Principal RoleThe entire product

ScopeCustom per engagement

Client Promise"You'll always get me"

Clients own you. Your team can't yet carry it.

02 / Anatomy

Inside one pod.

A pod is a self-contained service unit that owns a book of clients end-to-end. The pod is what the client experiences. You sit outside it.

Principal

Strategy sessions (rationed by tier) · escalation availability (capped hours) · final sign-off · internal review · firm building. Not the default contact.

↓ escalates up · signs off down ↓

The relationship owner

Pod Lead

Manager-level. Owns every client relationship in the pod. Runs all scheduled client meetings, delivers advisory conversations, reviews complex work, decides what gets escalated. Clients trust this person, not you.

The technical engine

Senior Associate

Prepares complex returns, reviews staff work, drafts advisory deliverables, handles routine client questions in writing. The pod lead's backstop.

The throughput

Staff Associate

Return preparation, bookkeeping, document collection, TaxDome workflow execution. Client contact only for document chase — never for advisory.

Book of clients

30 – 50

depending on tier mix · concentrated by industry or complexity for leverage

03 / The Tier Ladder

Three tiers, one ladder.

Tiers signal expectation up front. The client buys access, not just deliverables. Anything outside the tier scope is a separate engagement with a separate fee — this is the scope discipline that ends the over-delivery problem.

Essentials

Compliance done well. Pod-delivered. No principal contact.

Annual fee range

$4 – 8K / year

→
Returns1040 + state(s) · or one simple entity return
→
PlanningYear-end projection · one annual check-in (pod lead, 30 min)
→
CommunicationEmail-only, 48-hour SLA, pod inbox
→
PrincipalNone. Sign-off only.
→
Out of scopeAdvisory questions = separate fee

Plus

Compliance + light planning. Pod-led with structured advisory.

Annual fee range

$10 – 20K / year

→
Returns1040 + state(s) + Sch C/E · or pass-through + owner 1040
→
PlanningMid-year + year-end projections · quarterly check-ins (pod lead)
→
AdvisoryOne scheduled session per year (pod lead delivers from playbook)
→
CommunicationEmail + scheduled calls, 24-48hr SLA
→
PrincipalSign-off + escalation only. No direct contact by default.

Premier —

Multi-entity, complex, advisory-active. Pod-led with bounded principal access.

Annual fee range

$25 – 60K+ / year

→
ReturnsMulti-entity · complex pass-through · multi-state
→
PlanningQuarterly projections · monthly or quarterly meetings (pod lead)
→
AdvisoryUp to 4 sessions / year · pod lead delivers
→
PrincipalOne annual strategy session · escalation capped at 2 hrs/month
→
SLA24-hour response · designated pod team

04 / Annual Rhythm

Who touches the client, when.

This is how you actually get out of the day-to-day. Every touchpoint is owned, scheduled, and bounded — not improvised.

Onboarding

Pod LeadConducts onboarding, document collection, engagement letter walkthrough, TaxDome setup

PrincipalPremier only — brief 30-min welcome call to set the relationship tone, then hands off

Quarterly Check-ins

Pod LeadAll quarterly meetings (Plus & Premier) · projections, planning, Q&A

— none —

Mid-year Planning

Senior + LeadSenior prepares projection, pod lead delivers it

PrincipalReviews Premier projections internally only — no client meeting

Annual Strategy

Pod LeadHosts for Plus · co-hosts for Premier

PrincipalPremier only — one session per year, scheduled in Q3

Return Filing

Staff + SeniorPreparation & review · pod lead handles all client questions

PrincipalFinal sign-off review only — no client contact unless flagged

Ad-hoc Questions

Pod LeadDefault owner. Within-scope = answered. Out-of-scope = scoped as new engagement.

— never default —

Escalation

Pod LeadIdentifies escalation, prepares brief, schedules with principal

PrincipalResponds within bounded hours/month — via pod lead, not direct to client

05 / Where You Live

What stays with you — and what doesn't.

The whole model collapses if the boundary is fuzzy. Write these down. Put them in engagement letters. Train pod leads to enforce them on your behalf.

The Principal does

Five categories · everything else delegates

Strategic firm directionGrowth, hiring, partnerships, service line evolution, infrastructure builds.
Premier annual strategy sessionOne per Premier client per year. Scheduled. Bounded. Prepared by pod lead.
Complex advisory escalationWhen pod lead flags genuinely complex matters. Capped at agreed monthly hours.
Final review & sign-offReturns and major deliverables. Internal — no client contact required.
Team developmentCoaching pod leads. Building playbooks. Making the team better so you don't have to do the work.

The Principal doesn't

Default refusals · pod owns these

Take routine client callsPod lead owns the relationship. "Can I just talk to JO?" is answered with "JO is reviewing — I'll relay the question."
Answer ad-hoc client emailsClient emails to principal get auto-routed to pod inbox. Pod lead responds, principal cc'd only on escalations.
Re-explain what the pod already coveredIf pod lead has answered, the answer stands. No second opinion as a default service.
Accept scope creep without engagementNew advisory ask = new engagement letter. Even for Premier. Especially for Premier.
Be the back-channelIf clients can WhatsApp/text you directly, the model is already broken. One inbox, one calendar, one pod lead.

06 / What This Solves

Your specific frustrations, mapped.

"I despise tracking hours and building that model."

→

Fixed annual fees by tier. Internal time-tracking only for capacity planning and utilization review — never for client billing. The hour timer never touches the client relationship.

"I don't want clients to own me."

→

Principal access is rationed by tier and capped in hours. Even your highest-paying client gets one annual session plus bounded escalation. The pod lead is the daily owner. Premium fees buy depth of service, not unlimited access to you.

"Clients have different expectations — the team over-delivers for clients who aren't paying enough."

→

Tiers signal expectation in the engagement letter. Essentials clients don't get advisory conversations — they get the answer "that's outside your engagement; here's what it would cost to add it." This is the conversation the pod lead has to be trained to run.

"My team isn't proficient enough in sophisticated client communication and advisory."

→

Pod lead is the development priority. Phase in advisory with you co-delivering until pod lead is solo-ready. Use playbooks — the RC Tool, the entity diagram builder, the EBITDA toolkit — as scaffolding for the conversation. Tools make the advisor; you don't have to be the advisor forever.

"I want to remove myself from day-to-day."

→

Your calendar is locked. Touchpoint map dictates when you appear. Principal time is reserved blocks: review, escalations, strategy, team development, firm building. Everything else is "ask your pod lead."

07 / Honest Phasing

You can't flip a switch.

The model is the destination. Getting there has stages, because the constraint you named — pod leads aren't yet advisory-grade — is real. Plan in three phases, not one launch.

Architect & Sort

Months 0 – 3

Write tier definitions & scope boundaries
Sort existing book into Essentials / Plus / Premier
Identify mismatches: who is under-paying for their expectation
Identify your pod lead candidates internally (or define the hire)
Build engagement letter templates per tier with explicit out-of-scope clauses
Lock principal calendar — create the blocks before clients fill them

Co-Deliver & Codify

Months 3 – 12

Reprice clients into tiers at renewal — some will leave; that's the design working
Pod lead joins every advisory conversation; you co-deliver
Each conversation produces a playbook entry · tool · or template
Pod lead practices "no, that's outside scope" with your backing
Route inbound emails through pod inbox — train clients to the new pattern
Decline new client work below Plus floor

Pod-Led, Principal-Light

Months 12 – 24

Pod lead solo-delivers Plus advisory · co-delivers Premier with you
You appear only at touchpoints defined in the map
Build the second pod · first pod lead becomes the template for the second
Premier annual sessions are your concentrated client time
Day-to-day is unmistakably the pod, not you
Your time shifts to strategy, infrastructure, and partnerships