About this guide

A calm, plain-language AI reference, written for whoever needs it, at whatever depth they need it.

Who writes this

I'm Jamie Owen, a Microsoft 365 and AI specialist. My day job is IT: rolling out Copilot, securing it, writing the governance around it, and training the staff who end up with it on their ribbon. I've worked with AI tools for the past five years, since they first became available to the public, and the other assistants this site covers are part of that work too. These pages are written from inside real deployments, where the guidance has to survive contact with actual users. Certifications and the rest of the paper trail are on LinkedIn.

Why it exists

Nothing on this site is for sale or sponsored, and no page carries adverts or affiliate links. Separately, I take paid Microsoft 365 and AI automation work through OWENLABs, my consultancy. This site is a personal project: five years of accumulated answers, collected into one place, because I think access to this kind of information should be free. The reader comes first throughout. Start at "what is a large language model?" and follow the links until you reach "run an open-source model locally", without ever hitting a dead end. AI tools are part of how I keep it current, which felt worth being upfront about: here's the full reasoning.

How content is sourced and dated

Every page carries the date it was last updated. Anything that moves quickly, like model versions, pricing or security guidance, is flagged fast-moving and names the source to check for the current position. AI tools change monthly, so treat dated specifics as a snapshot and verify anything you're about to rely on. What changed and when is listed on the changelog.

What the site records

Visits are counted with Cloudflare Web Analytics, from the company that hosts the site. It sets no cookies and stores nothing in your browser, and what reaches me is totals, such as which pages get read and where visitors came from. That is enough to show which pages earn their place. There are no other trackers here, and no adverts to aim at you.

Suggest a correction

Found something out of date or wrong? Corrections are welcome, and they're the fastest way to make this more useful. Open an issue on GitHub and I'll fix it. Factual errors also get a public entry on the corrections page, stating what the page said and what it says now. Small fixes are as valued as big ones.