Operations Manager & AI Systems Builder
I run operations — and I build the software that runs them. Nine years across legal, construction, marketing and customer operations, with a habit of turning the messy, undocumented parts of a business into systems somebody else can follow.
Eight projects across four organisations. Some are software, some are process, some are both — the useful ones usually are.
A seventeen-step onboarding chain from first enquiry to open matter — documented, delegable, and wired across Clio, DocuSign, LawPay and Dropbox. New enquiries stop falling through the gaps because nobody has to remember what happens next.
Protected blocks, prep buffers, team availability and deadlines as fixtures — so the week is a budget rather than a queue, and the work only the attorney can do gets time.
Twenty-four articles in eight months on AI and intellectual property — written, reviewed, illustrated and published to a cadence that survived the busy months.
A multi-tenant dashboard that collects weekly numbers from every account, writes the monthly narrative, renders the PDF and emails it — replacing a manual reporting cycle.
A mobile-first promo page for a gym under new ownership. One serverless backend, two hosts, both confirmation emails, and the print collateral to match.
Estimates, allowances and compliance documentation brought into one predictable shape, so a project coordinator could hand the job over without a phone call.
Sequential training modules with assessments, so a new starter ramps on a defined path instead of shadowing whoever happens to be free.
The original of the pair. A prospect picks a class, the team gets an email formatted for their CRM, and the front desk works from a written playbook.
Owning the day-to-day so leadership doesn't have to. Scheduling, inbox triage, client coordination, vendor management, and the follow-up that stops work stalling between people.
When the spreadsheet stops coping, I build the thing that replaces it — authenticated, deployed, and simple enough that the team adopts it without a training session.
Turning what one person knows into something the whole team can run. Written down, sequenced, and owned — the difference between a business that scales and one that depends on you.
The outward-facing half. Editorial programmes that hold their cadence, landing pages that convert, and the unglamorous collateral a campaign needs before it can actually run.
Applied where it removes real work, not where it demos well. Inbox triage, drafting, research, summarisation and reporting — built as reusable workflows the team can rely on.
Five sectors, one throughline: I arrive somewhere the process lives in somebody's head, and I leave it written down and running. Full background →
Thank you so much for getting this put together. This is perfect.
Looks good … I'll keep looking through it. But looks really good!
Whether that's owning operations day to day or building the system that finally makes them predictable — tell me what's breaking and I'll tell you how I'd fix it.
