AI enablement, automation and infrastructure
Systems small teams can still run after I hand them over.
I build AI, automation and infrastructure for small teams. I care about repeat work, clear handovers, and systems that still run after the project ends.
Available from December 2026 · BC, Canada · open to Vancouver, Calgary or remote
- 34containers running
- 3 LXC + 1 VMisolated hosts
- Aug 2024in production since
- 735automated checks
- 7interactive courses
- dailybackups, 7d/4w/3m kept
Who you would work with
Alexander G. Myers
I'm a research-oriented technologist from British Columbia. I start with the manuals, then build one system around the work your team already does.
I measure the work by whether the team still uses the system later, and whether someone else can maintain it after the project ends.
- Based
- BC, Canada · open to Vancouver, Calgary or remote
- Available
- Available from December 2026
- Focus
- AI enablement, automation and infrastructure
Case studies
Reconstructed client work and systems I run myself.
Client work is under NDA, so I rebuilt those cases from scratch for a fictional company using a similar methodology. The rest are systems I built and run myself.
How I rolled out AI to a small firm without losing control of client data
I wrote the rollout plan and built the vetting process, the risk tiers, the shared skills library and a deck generator for staff. I governed the rollout throughout.
How I turned recorded sessions into a self-serve course, with a check at every gate
I built a repeatable production line that turns source material into interactive H5P lessons and quizzes for the learning platform (LMS). The subject expert signs off at four points, and every build passes three quality checks before a learner sees it.
A homelab I run like production
I started with one media server. It is now a four-guest platform with VPN-only administration, monitoring, alerting and daily backups. Every number on this page comes from the system itself.
How I choose middleware without guessing
I turn a department's pain point into a shortlist with conditions. The sources are logged, dated and hashed.
A contact form that reaches my phone without exposing my servers
I built a workflow on my lab that fetches site enquiries, filters them and sends them to my phone and a log file. It needs no inbound webhook on the lab. I tested it; it goes live with the site.
How I measured search visibility when the search engines pushed back
I built a repeatable benchmark across three search engines. It turned a vague 'are we findable?' into a scored list of gaps and the page changes I recommended to close them.
Lab
Three demos you can use here.
Deck generator
Synthetic, seeded data goes in. A five-slide branded deck with KPIs, a pivot table and a chart comes out. It runs in your browser, and nothing is uploaded.
Sound, tuned by measurement
I made the sounds on this site and a music pipeline in code, then checked them with an open-source listening tool instead of leaving them to taste.
Working safely with client data
Four short activities for staff at Example XYZ Consulting. You inspect messages, limit vendor data sharing and handle a client file request.
How I work
Research first. Then build, check, and hand over.
- 01
Research
I read the manuals, forums and vendor docs before choosing anything. Most problems are already half-solved in public.
- 02
Specify
I write down the outcome, the constraints and what done looks like, so the build can be checked against them.
- 03
Build
I combine the right tools, open source first, into one working system instead of five half-tools.
- 04
Prove and hand over
I run automated checks and a review pass, then write documentation a successor can use without me.
Hiring, or have something that needs building?
I'm open to full-time roles in Vancouver, Calgary or remote, and to fixed-scope contract work through AGM Studios.