The short version
My work blends software engineering and operations engineering. Vertical of the T: production code, schemas, services, APIs, observability. Horizontal: CRM migrations, multi-location workflows, AI agents, internal tooling.
Formaum is a one-person studio. Clients are multi-location operations across Canada, the US, and the UK that have outgrown their stack. I audit, architect, build, deploy, and optimise the next one.
How I got here
Two industries trained the operations discipline.
Film and TV. Production management on $100M-plus budgets: Skyfall, Avengers, Game of Thrones. Sprints, definition of done, fifteen vendors converging on a single shot. The schedule is the product. (IMDB →)
Gaming. EA Sports FIFA, a $7B global franchise. Annual release cycles, multi-region rollouts, zero tolerance for sloppy systems.
Both industries hid the same role: a human moving data between five disconnected tools. I built the system that replaced it. Now I build them for other operations.
Who I work with
Operations leaders at multi-location businesses with real revenue and real drag. Education, franchises, professional services, real estate, gaming, entertainment. The filter is operational complexity, not vertical.
Recent work:
- 5-location preschool franchise. 10 tools consolidated to 1. $1.8M recoverable revenue identified.
- Global education brand, 100K-plus students. Multi-language sales agent. $96K/month revenue leak closed.
- Angel investor, 12 portfolio companies. Custom business intelligence platform. $18K MRR.
- Executive coach, $500K/year close rate. Call intelligence system. 12 hours saved per week.
- VFX studio. 4 platforms unified. AI onboarding agent. New-hire ramp cut from 2 weeks to 3 days.
If your operations run on people doing integration work by hand, the cost is leaked pipeline, mis-routed leads, and stale data compounding monthly. (See the work →)
How I work
Production methodology. Sprints. Definition of done before anything ships. The single-location Operations Overhaul runs 6 weeks: audit, architect, build, deploy, optimise. Multi-location migrations run 3 to 6 months depending on size, complexity, and team. Exact scope is set after the audit. Most engagements continue with ongoing optimisation post-delivery.
One brain from discovery to production. The person on the discovery call writes the migration scripts. No handoff layer. One mis-mapped field can corrupt 309,000 contact records overnight. Rollback only works if the snapshots, branch isolation, and revert path were engineered before deploy day. Without that infrastructure, the change ships and the new database state is the record.
Operations running on integrated AI infrastructure compound their advantage quarter over quarter. The structural gap to legacy stacks widens monthly. Operators who consolidated 18 months ago now ship faster on every customer touchpoint than their direct competitors do.
The way I work: a CLAUDE.md per client engagement, written before any code runs, naming the failure modes and the revert path. The first audit pass usually happens live in Chrome DevTools because the network traffic tells you what the docs do not.
The thread: Same standard every client. Audit. Architect. Build. Deploy. Optimise. The shape is repeatable. The build is bespoke.
The tech I run
Claude for the AI layer. Claude Code for the build layer. Trigger.dev and n8n for orchestration. Supabase, PostgreSQL, BigQuery for data. GoHighLevel, HubSpot, Salesforce, Monday for CRM. Twilio, Vapi, ElevenLabs for voice. Next.js, FastAPI, Python for custom apps.
Tools change. The methodology doesn't.
Outside the work
Based in Canada. I read, garden, and design operations for the AI layer. Most ideas come from watching teams do manual work a system should already handle.
Tell me what you're running and what's not working.
One call. You leave with a sequenced fix list and a clear read on whether I'm the right hire.
Book a discovery call