WHY THIS WORK
Why this work matters to me
I have worked inside businesses where growth added complexity faster than the systems could keep up.
I have seen what happens when too much context sits with one person, onboarding remains manual, and teams rely on informal processes to keep work moving.
My background spans founder-led business, customer success, operations, workflow design, compliance and cross-functional delivery.
That is why I do not start with a template or a stack of SOPs.
I start by understanding how the business actually runs, where work gets stuck, and what keeps pulling the founder back in.
Good operations should make the business easier to run, not create more administration.
EXPERIENCE
Experience behind the work
The work is grounded in building and running real systems, not just advising on them.
Built and operated businesses
Experience owning and growing service businesses, with direct responsibility for how work is delivered day to day.
Customer lifecycle systems
Building onboarding and customer lifecycle workflows that give teams clear ownership, defined next steps and better visibility from first contact through ongoing delivery.
Cross-functional operations
Working across operations, customer success, product, legal and delivery where ownership and handoffs matter.
Practical
implementation
I turn operational problems into workable processes, documentation and lightweight systems that teams can actually use day to day.
WHERE I FIT
Practical operational work, between advice and implementation.
Understudy Systems sits between high-level advice and open-ended outsourced operations. I help diagnose a defined operational problem, map what is really happening, and turn that into a practical way forward. That may mean clarifying ownership, redesigning a handoff, simplifying onboarding, documenting a recurring workflow, or building the lightweight system needed to keep it visible.
Best fit
Who I work best with
The best fit is usually a founder-led business that has moved beyond the very early stage. You have customers, a team, recurring work, and enough operational complexity that informal ways of working are starting to break. You do not need polished processes before we start. In fact, the useful work usually begins where the documented process and the real process no longer match.
Real operational complexity
Founder in the day-to-day
THE POINT
The goal is to remove the work that should no longer depend on the founder. Your judgement, leadership and experience should still matter. But you should not have to be the reminder system, approval queue, knowledge base and escalation point for routine work.
