You Built an LMS With AI. Who Fixes It at 9pm?

Words by
Kaine Shutler

TL;DR
Key takeaways
AI coding tools can produce a working LMS quickly, but the build is the small part. Security, accessibility, records, integrations and upkeep continue for as long as the platform runs.
A home-built LMS holds learner records and often payment details, so a breach is expensive: IBM puts the average at $4.99 million globally and $11.5 million in the US.
Owning your LMS doesn't mean building it from scratch. A specialist can build a custom LMS from components they've already tested, and you still own the code.
AI coding tools have made a new idea sound reasonable: build your own LMS over a weekend. A recent Forbes Council piece, written by the chief learning officer of an LMS vendor, says you can - and argues you probably shouldn't (Forbes).
He has a point. If you run a training business, the question isn't whether you can build an LMS with AI. It's whether you want to run one.
What AI genuinely makes possible
The demo is real. Describe your courses, quizzes and a learner dashboard, and today's AI tools will produce working code in hours.
For a prototype, a pilot or an internal tool with a few dozen users, that can be enough. A quick build is also a cheap way to find out what you actually need before you spend serious money.
What the weekend build leaves out
A learning platform for paying learners is a service you run, every day. The weekend version usually skips the parts that matter once customers depend on it:
Security. You're holding learner records, assessment results and often payment details. IBM's 2026 report puts the average breach at $4.99 million globally and $11.5 million in the US (eSecurity Planet). Someone has to patch, monitor and test it.
Accessibility. Corporate and public-sector buyers often ask for accessibility conformance before they sign. Keeping it up is ongoing work.
Records you can stand behind. Completion history, certificates and CE or compliance evidence need audit trails that survive every update.
Integrations. SSO, CRM and payment providers change their APIs, and each change becomes your problem.
Scale. A build that works for 50 learners can struggle at 5,000, usually on your busiest day.
Upkeep. Every bug, feature request and dependency update is yours for as long as the platform exists.
None of this shows in a demo.
When building it yourself makes sense
Sometimes it does. If the platform is your product and you have engineers who will own it long term, building in-house can be the right call. Prototyping with AI to test an idea is sensible too.
The risky case is a training business with no engineering team, where the person who built it ends up fixing every problem.
Research on AI projects points the same way. MIT's NANDA study of enterprise generative AI found that tools bought from specialist vendors or built with partners succeeded about two-thirds of the time, while internal builds succeeded a third as often (Fortune).
The third option: own it without starting from zero
The Forbes piece frames this as build versus buy. There's a third option: a custom LMS you own, built by a team that has done it before.
That's how we work. We start from components we've already built and tested on real platforms, then design and build the parts specific to your business. You get the source code and your data. We run it, with security, testing and updates handled, for as long as you want - or you take it in-house.
To compare the cost of a SaaS LMS with owning a custom one over 10 years, use our cost calculator.
Want to talk it through? Book a call with our founder to work out whether to build, buy or own.
Questions to answer before you build
Who fixes it at 9pm when learners can't log in?
Who keeps it secure, and how will you prove that to a customer's security team?
Can it produce the records your customers or regulators ask for?
What happens when your SSO, CRM or payment provider changes its API?
Will it hold up on your busiest day?
If the person who built it leaves, can someone else run it?
If you have good answers, build it. If you don't, that's your answer too.
FAQ
Can you build an LMS with AI?
Yes. AI coding tools can produce a working LMS prototype quickly. Running it for paying learners - security, accessibility, records, integrations and upkeep - is the larger, ongoing job.
How much does it cost to build your own LMS?
The first build can be cheap. The running costs aren't: hosting, security, testing, accessibility and someone to maintain it for as long as it runs.
Should I build or buy an LMS?
Buy a SaaS LMS if you need something standard quickly. Build in-house if the platform is your product and you have engineers to own it. A custom LMS from a specialist sits between the two: you own the code, and the specialist builds and maintains it.
What does an LMS need beyond courses and quizzes?
Secure accounts, completion and certificate records with audit trails, accessibility, integrations such as SSO, CRM and payments, reporting, and the capacity to handle peak load.
Who owns the code if an agency builds my LMS?
It depends on the contract. Check that you get the source code, your data, and the right to host or maintain the platform elsewhere.

Kaine Shutler is the founder and managing director of Plume, a studio specialising in custom learning technology. With 14 years of experience, Kaine has established expertise in Learning Management Systems, UI/UX design, and scalability, working with clients including Google and training businesses across multiple sectors.
You Built an LMS With AI. Who Fixes It at 9pm?

Words by
Kaine Shutler

TL;DR
Key takeaways
AI coding tools can produce a working LMS quickly, but the build is the small part. Security, accessibility, records, integrations and upkeep continue for as long as the platform runs.
A home-built LMS holds learner records and often payment details, so a breach is expensive: IBM puts the average at $4.99 million globally and $11.5 million in the US.
Owning your LMS doesn't mean building it from scratch. A specialist can build a custom LMS from components they've already tested, and you still own the code.
AI coding tools have made a new idea sound reasonable: build your own LMS over a weekend. A recent Forbes Council piece, written by the chief learning officer of an LMS vendor, says you can - and argues you probably shouldn't (Forbes).
He has a point. If you run a training business, the question isn't whether you can build an LMS with AI. It's whether you want to run one.
What AI genuinely makes possible
The demo is real. Describe your courses, quizzes and a learner dashboard, and today's AI tools will produce working code in hours.
For a prototype, a pilot or an internal tool with a few dozen users, that can be enough. A quick build is also a cheap way to find out what you actually need before you spend serious money.
What the weekend build leaves out
A learning platform for paying learners is a service you run, every day. The weekend version usually skips the parts that matter once customers depend on it:
Security. You're holding learner records, assessment results and often payment details. IBM's 2026 report puts the average breach at $4.99 million globally and $11.5 million in the US (eSecurity Planet). Someone has to patch, monitor and test it.
Accessibility. Corporate and public-sector buyers often ask for accessibility conformance before they sign. Keeping it up is ongoing work.
Records you can stand behind. Completion history, certificates and CE or compliance evidence need audit trails that survive every update.
Integrations. SSO, CRM and payment providers change their APIs, and each change becomes your problem.
Scale. A build that works for 50 learners can struggle at 5,000, usually on your busiest day.
Upkeep. Every bug, feature request and dependency update is yours for as long as the platform exists.
None of this shows in a demo.
When building it yourself makes sense
Sometimes it does. If the platform is your product and you have engineers who will own it long term, building in-house can be the right call. Prototyping with AI to test an idea is sensible too.
The risky case is a training business with no engineering team, where the person who built it ends up fixing every problem.
Research on AI projects points the same way. MIT's NANDA study of enterprise generative AI found that tools bought from specialist vendors or built with partners succeeded about two-thirds of the time, while internal builds succeeded a third as often (Fortune).
The third option: own it without starting from zero
The Forbes piece frames this as build versus buy. There's a third option: a custom LMS you own, built by a team that has done it before.
That's how we work. We start from components we've already built and tested on real platforms, then design and build the parts specific to your business. You get the source code and your data. We run it, with security, testing and updates handled, for as long as you want - or you take it in-house.
To compare the cost of a SaaS LMS with owning a custom one over 10 years, use our cost calculator.
Want to talk it through? Book a call with our founder to work out whether to build, buy or own.
Questions to answer before you build
Who fixes it at 9pm when learners can't log in?
Who keeps it secure, and how will you prove that to a customer's security team?
Can it produce the records your customers or regulators ask for?
What happens when your SSO, CRM or payment provider changes its API?
Will it hold up on your busiest day?
If the person who built it leaves, can someone else run it?
If you have good answers, build it. If you don't, that's your answer too.
FAQ
Can you build an LMS with AI?
Yes. AI coding tools can produce a working LMS prototype quickly. Running it for paying learners - security, accessibility, records, integrations and upkeep - is the larger, ongoing job.
How much does it cost to build your own LMS?
The first build can be cheap. The running costs aren't: hosting, security, testing, accessibility and someone to maintain it for as long as it runs.
Should I build or buy an LMS?
Buy a SaaS LMS if you need something standard quickly. Build in-house if the platform is your product and you have engineers to own it. A custom LMS from a specialist sits between the two: you own the code, and the specialist builds and maintains it.
What does an LMS need beyond courses and quizzes?
Secure accounts, completion and certificate records with audit trails, accessibility, integrations such as SSO, CRM and payments, reporting, and the capacity to handle peak load.
Who owns the code if an agency builds my LMS?
It depends on the contract. Check that you get the source code, your data, and the right to host or maintain the platform elsewhere.

Kaine Shutler is the founder and managing director of Plume, a UK-based agency specialising in custom learning technology. With 14 years of experience, Kaine has established expertise in Learning Management Systems, UI/UX design, and scalability, working with clients including Google and training businesses across multiple sectors.
You Built an LMS With AI. Who Fixes It at 9pm?

Words by
Kaine Shutler

TL;DR
Key takeaways
AI coding tools can produce a working LMS quickly, but the build is the small part. Security, accessibility, records, integrations and upkeep continue for as long as the platform runs.
A home-built LMS holds learner records and often payment details, so a breach is expensive: IBM puts the average at $4.99 million globally and $11.5 million in the US.
Owning your LMS doesn't mean building it from scratch. A specialist can build a custom LMS from components they've already tested, and you still own the code.
AI coding tools have made a new idea sound reasonable: build your own LMS over a weekend. A recent Forbes Council piece, written by the chief learning officer of an LMS vendor, says you can - and argues you probably shouldn't (Forbes).
He has a point. If you run a training business, the question isn't whether you can build an LMS with AI. It's whether you want to run one.
What AI genuinely makes possible
The demo is real. Describe your courses, quizzes and a learner dashboard, and today's AI tools will produce working code in hours.
For a prototype, a pilot or an internal tool with a few dozen users, that can be enough. A quick build is also a cheap way to find out what you actually need before you spend serious money.
What the weekend build leaves out
A learning platform for paying learners is a service you run, every day. The weekend version usually skips the parts that matter once customers depend on it:
Security. You're holding learner records, assessment results and often payment details. IBM's 2026 report puts the average breach at $4.99 million globally and $11.5 million in the US (eSecurity Planet). Someone has to patch, monitor and test it.
Accessibility. Corporate and public-sector buyers often ask for accessibility conformance before they sign. Keeping it up is ongoing work.
Records you can stand behind. Completion history, certificates and CE or compliance evidence need audit trails that survive every update.
Integrations. SSO, CRM and payment providers change their APIs, and each change becomes your problem.
Scale. A build that works for 50 learners can struggle at 5,000, usually on your busiest day.
Upkeep. Every bug, feature request and dependency update is yours for as long as the platform exists.
None of this shows in a demo.
When building it yourself makes sense
Sometimes it does. If the platform is your product and you have engineers who will own it long term, building in-house can be the right call. Prototyping with AI to test an idea is sensible too.
The risky case is a training business with no engineering team, where the person who built it ends up fixing every problem.
Research on AI projects points the same way. MIT's NANDA study of enterprise generative AI found that tools bought from specialist vendors or built with partners succeeded about two-thirds of the time, while internal builds succeeded a third as often (Fortune).
The third option: own it without starting from zero
The Forbes piece frames this as build versus buy. There's a third option: a custom LMS you own, built by a team that has done it before.
That's how we work. We start from components we've already built and tested on real platforms, then design and build the parts specific to your business. You get the source code and your data. We run it, with security, testing and updates handled, for as long as you want - or you take it in-house.
To compare the cost of a SaaS LMS with owning a custom one over 10 years, use our cost calculator.
Want to talk it through? Book a call with our founder to work out whether to build, buy or own.
Questions to answer before you build
Who fixes it at 9pm when learners can't log in?
Who keeps it secure, and how will you prove that to a customer's security team?
Can it produce the records your customers or regulators ask for?
What happens when your SSO, CRM or payment provider changes its API?
Will it hold up on your busiest day?
If the person who built it leaves, can someone else run it?
If you have good answers, build it. If you don't, that's your answer too.
FAQ
Can you build an LMS with AI?
Yes. AI coding tools can produce a working LMS prototype quickly. Running it for paying learners - security, accessibility, records, integrations and upkeep - is the larger, ongoing job.
How much does it cost to build your own LMS?
The first build can be cheap. The running costs aren't: hosting, security, testing, accessibility and someone to maintain it for as long as it runs.
Should I build or buy an LMS?
Buy a SaaS LMS if you need something standard quickly. Build in-house if the platform is your product and you have engineers to own it. A custom LMS from a specialist sits between the two: you own the code, and the specialist builds and maintains it.
What does an LMS need beyond courses and quizzes?
Secure accounts, completion and certificate records with audit trails, accessibility, integrations such as SSO, CRM and payments, reporting, and the capacity to handle peak load.
Who owns the code if an agency builds my LMS?
It depends on the contract. Check that you get the source code, your data, and the right to host or maintain the platform elsewhere.

Kaine Shutler is the founder and managing director of Plume, a UK-based agency specialising in custom learning technology. With 14 years of experience, Kaine has established expertise in Learning Management Systems, UI/UX design, and scalability, working with clients including Google and training businesses across multiple sectors.
Plan your next learning platform with our founder
About Plume
As the leading custom learning platform provider serving training businesses in the US, UK and Europe, we help businesses design, build and grow pioneering learning tech that unlocks limitless growth potential.

Plan your next learning platform with our founder
About Plume
As the leading custom learning platform provider serving training businesses in the US, UK and Europe, we help businesses design, build and grow pioneering learning tech that unlocks limitless growth potential.

Plan your next learning platform with our founder
About Plume
As the leading custom learning platform provider serving training businesses in the US, UK and Europe, we help businesses design, build and grow pioneering learning tech that unlocks limitless growth potential.



