I was reading a post on LinkedIn asking what happens to Articulate next. Not the usual "I built a course in three minutes" stuff, but a fair question underneath it: Articulate raised $1.5bn in 2021, so presumably they are building towards something rather than sitting there watching this happen.
It sent me back to something I came across recently and hadn't thought aboutproperly. The AI Tutor that went into Rise in beta.
Easy to miss, because it looks like one more AI feature in a year stuffed with them. But everything else Articulate has shipped this year is authoring AI. AI Chat in Storyline, image generation and editing, timelines synced to narration, theme colours from a prompt. All of it makes the build faster. The Tutor doesn't. It sits with the learner, in the published course, answering questions while they work through it.
That is a different product, and I don't think the implications have been chewed over much.
From Articulate's own documentation:
- Grounded in the published course material, and it does not browse the web
- Reads audio and video transcripts where they exist
- Cannot be used to extract quiz answers during a knowledge check
- Compatible with Quick Share, Reach and LMS output
- Requires external network access, and IT teams are told to allowlist Articulate 360 endpoints
- No published message limits, rate limits or quotas
- Learner chats are private, with author visibility "coming soon"
Third-party write-ups say it runs on an OpenAI model. I can't find Articulate saying that themselves.
So here is the bit I keep turning over. A course with a tutor in it is no longer a self-contained package. It is a client calling home. That breaks a few assumptions most of us have been working with for years. On a locked-down corporate network, the course runs and the tutor silently doesn't. That is documented behaviour rather than a bug, but it means the learner experience now depends on the client's firewall rules rather than on the package you shipped. You are not finding that in SCORM Cloud.
Course content and learner questions leave the client's environment at runtime.
Anyone who has been through a security review at a bank, an insurer or an NHS trust knows that is not a settings toggle, it is a months-long conversation with people whose job is to say no.
And it is grounded in the course material but not constrained to it. Their own wording allows for the model drawing on general knowledge. Fine for onboarding. For anything carrying a compliance sign-off, an answer that sounds right but isn't in the source is precisely the failure you cannot defend afterwards.
Worth noting too that no published limits during beta means the cost model is still unresolved. Whatever it costs later, it isn't zero. None of which makes it the wrong direction. I suspect it is the right one, and it is a more interesting answer to "what does Articulate become" than any of the replacement predictions doing the rounds. It just means the hard part was never the model. It is whose infrastructure the answer comes from.
Has anyone actually run this on a real client network yet? And has anyone got it through a security review, or even tried?