Publishers · Learning platforms · Brands · Local business
I build editorial CMS architecture for newsrooms, LearnDash platforms for schools and training departments, and the WordPress infrastructure that holds it all together. If your team is adding AI tools, I can build the governance layer around that too — but that’s a separate conversation.
The editorial workflow depends on one person who has been there since the beginning. The LMS is held together by integrations nobody fully understands. The AI usage has no audit trail and no cost attribution. The site has not been touched in eighteen months because nobody is confident they will not break something important.
The problem is almost always the same: the digital systems were built faster than the operating layer around them. I’ve seen it at media organizations, school boards, government teams — the pattern doesn’t change.
The work I do is stabilize what’s fragile, get your team out of the manual workarounds they’ve built up around broken systems, and build in the kind of audit trail that finance and legal can actually read.
Publishers · Primary service area
Your publishing platform is the infrastructure your editorial team depends on. When it is fragile, their work is fragile. I design systems around how you actually publish — not what was easiest to install.
Publishing infrastructure →
Learning
Your LMS is the qualification layer your whole team runs on. I build and fix LMS architecture, SIS integrations, and the curriculum that runs inside it.
Learning platform services →
Brands
Technical SEO, WordPress infrastructure, and AI operations for national brands and enterprise teams where the stack is complex enough that you need someone who’s built at this scale before.
Brand and enterprise services →
Local
A website that works, built by someone who also builds for national organizations. Fast, practical, no overengineering.
Local business websites →
AI operations
AIOS is the AI operations layer I built and run for my own consulting work. It routes tasks across Claude, local models, and GitHub Copilot by cost and capability. It logs every work event with billing attribution. It maintains a library of 50+ specialized agent personas. Every client implementation is an adapted version of this architecture — tested against real production conditions before it touches their organization.
What that means for your organization: when your CFO asks what AI cost last quarter, you can answer. When compliance asks for the audit trail, it exists. When a new team member joins, the routing rules and agent library hand off cleanly.
Direct access to the person who built it. No account manager, no junior handoff, no re-explaining the same context twice. Every engagement runs through one senior — me.
Role-specific agents, full billing attribution, CFO-readable audit logs. Deployed inside your existing WordPress or LMS stack — no new vendor contracts, no new SaaS subscriptions.
Documentation, clean architecture, and code the next developer can actually read. Work that doesn’t create a new single point of failure — the person who built it.
Most of the people who contact me aren’t certain. That’s fine — that’s what the 20 minutes is for. I’ll tell you whether this is a fit, and who to call if it isn’t.
In 2011–2012, when Postmedia moved its network of major Canadian daily newspapers onto WordPress, I was part of the team that built the platform — starting with the National Post as the flagship, then cascading to papers including the Calgary Herald, Montreal Gazette, Ottawa Citizen, Vancouver Sun, and seven more. This is the architecture behind…
A gallery with no digital presence. A cinema running membership sales through a new e-commerce channel. A consignment shop with a loyal following but a site that didn’t reflect the room. Three engagements, one junior practitioner executing, one senior advisor at the quality gate. Here is what that split produced.
Fourteen hours on my own site, $30,800–$61,847 of senior WordPress delivery on the work log, and a 64% measurement gap the file itself surfaced before I did. The case study for AIOS, the internal system that produced both numbers.
Book a 20-minute call — I’ll tell you honestly which service area fits, or whether I’m not the right person for it. Or send me the brief in writing if that’s easier. Both land with me directly.