I build the systems I run
Most operations people inherit a process and keep it alive. Most developers build a tool and hand it over. I sit in the overlap — close enough to the work to know what actually breaks, and technical enough to fix it properly.
How I got here
I started in customer operations at Amazon, moved into administrative management at a digital forensics firm, then into construction project coordination. Different industries, the same recurring discovery: the thing slowing the business down was almost never a lack of talent. It was that nobody had written the process down.
So I started writing them down. Then I started noticing which documented steps a computer should be doing instead — and, eventually, building those.
The training was already there. I hold a Computer Programming NC IV and was named Programmer of the Year in 2017, which felt like an irrelevant detail through most of the administrative years. It stopped being irrelevant the moment a spreadsheet stopped coping and the honest answer was “this should be an application.”
The most recent chapter is legal operations — client coordination and executive support at an intellectual property firm, where the same pattern applies: intake, onboarding, matter administration and compliance, held together by documentation and improved with automation where automation genuinely earns its place.
The part I care about is handover. A system that only works while I'm running it isn't a system — it's a dependency. Everything on this site was built to be given away.
Roles
Supporting the principal attorney while owning client experience, executive operations and legal administrative workflow. I'm the coordination point between attorneys, clients, vendors and outside providers — which in practice means making sure matters keep moving and leadership stays on the work only they can do.
Client intake and onboarding end to end: engagement letters, retainers, payments and documentation, plus the follow-up tracking that stops matters stalling. Matter administration across Clio Grow and Clio Manage. Standardised procedures for trademarks, patents, business matters and litigation support. AI-assisted workflows for inbox review, reporting, research and drafting. Business development support covering networking, referral tracking, prospect research and LinkedIn content.
Built the agency's client reporting platform and its companion intake portal, plus a sales onboarding portal for new starters. Replaced a manual monthly reporting cycle with software that collects the numbers, drafts the narrative, renders the PDF and sends it.
Planning, organising and executing residential construction projects. Coordinated contractors, vendors and internal teams; tracked progress and maintained documentation. Standardised estimating and allowance setup in Buildertrend and organised compliance documentation so nothing lapsed unnoticed.
Escalation-tier support across phone, email and chat. Where I learned that most recurring problems are process problems wearing a customer's clothes.
Administrative management for the customer service department — reporting, records and budget management.
Education
- Computer Programming NC IVInfotech College of Arts and Sciences
- Programmer of the Year, 20171st Honorable Mention