Doc Wealth ×
Culture Memo Careers The Work Tax Team Bookkeeping Team Payroll Team Operations Team Marketing Team People Team View Roles
The Work Operations Team

Complexity
of the work

The systems behind the firm. The good part of the job.

{{ hlTop }} {{ hlBig }}

Doc Wealth runs on systems the operations team designs: entity setups, the automations that move work between the tax team and the software, the back and forth with vendors and clients, payments, and the daily admin that has to happen without anyone holding it together by hand. Very little of how we run is finished. You're handed something to design, not a process to keep alive.

One entity setup, anatomized

Dr. T.

36, hospitalist. Going 1099 next month and needs an S-corp stood up, mid-year, before her first locums check clears.

0 Moving parts in one setup
Composite client. Details changed.
  1. 01
    The intake The client fills the form. Half the fields need verifying before anything downstream can trust them.
  2. 02
    The state filing Every state has its own quirks, like the one that rejects a P.O. Box as a registered agent address, weeks later.
  3. 03
    The vendor queue Processing time you do not control, sitting inside a deadline you do. This month it is running twice as long.
  4. 04
    The election window The S-corp election has a clock on it. It starts the day the entity exists, whether or not the vendor hurried.
  5. 05
    The tax-team handoff The new entity has to land in the tax software, the payroll setup, and the calendar, correctly, without a human re-keying it.
  6. 06
    The payment rails Engagement, invoice, and payment setup, wired so the client never chases us and we never chase the client.
  7. 07
    The automation A scenario runs all of the above without a person touching it, until the edge case nobody met yet. Then you redesign it.
  8. They all depend on each other. Let the vendor slip in line 03 and the election in line 04 misses its window. The process will not flag it. You will.
You build the machine

Where the automation stops

Nobody here does the same manual task for years. If a step gets done the same way twice, the third time should be an automation, and you are the one who builds it. The job is noticing the step that shouldn't exist, saying so, and then redesigning it.

Genuinely intricate pipelines

Handoffs, not tickets

Operations here is the connective tissue: entities moving through vendors and states, work moving between the tax team and the software, money moving between clients and the firm, and automations moving all of it. Every handoff is a place where a client's outcome can quietly go wrong, and yours is the judgment that keeps it from happening.

Entities Automations Vendors Payments Handoffs
Ownership is the job

You own the outcome

The form didn't flag it, and nobody asked you to check. You flag it anyway, verify the rule, and fix it before it becomes a rejected filing and a frustrated client. “We followed the process” is never a complete answer here, and a process that stopped catching what matters gets fixed, not saluted.

You'll get better here, fast

Complex work compounds

A year of designing workflows for a firm that keeps doubling teaches you more than five years of running someone else's mature system. We review deeply, explain our reasoning, and expect you to push back when you disagree.
The surface area

Nothing here runs itself.
Everything here runs through you.

01

The automations

Client calls turn into task cards overnight. Calendars turn into morning prep notes. Applications get scored before a human reads them. Every one of those pipelines was designed by this team, and every one of them earns a redesign the day it stops fitting.

02

The entities

Every new S-corp and LLC moves through intake, vendor, state, election, and handoff, on a clock. Fifty states, each with its own quirks, and a tax deadline on the other end that doesn't care whose queue it sat in.

03

The money

Engagements, invoices, payment setup, and the follow-through, wired so a client never has to chase us and we never have to chase a client. When money moves wrong, it's a trust problem before it's an accounting problem.

04

The daily grind, deleted

The nitty-gritty admin that every firm has, we treat as a backlog to eliminate. The measure of a good month on this team is how much of last month's manual work no longer exists.

Where you sit

Between the tax team and the software. Between the vendor and the client. Between the plan and what actually happened.

Nobody sees more of the firm than operations. You'll learn more about physician taxation than you expected to, because you can't design around work you don't understand.

You'll hate it here if
  • You want a queue of tickets and nothing to redesign.
  • You'd rather route the hard call up than make it.
  • You measure the day by tasks closed.
You'll like it here if
  • You want to design the process, not just run it.
  • You'd rather be told your reasoning is wrong than told nothing.
  • You like being the person who fixed the step everyone complained about.

It's harder than the average operations job. It's also the reason people stay.

View Roles