LTI Integration for Educational Publishers: What It Costs and When You Need It

If you sell content to schools, colleges, or universities, you've heard the question before: "Does it work with Canvas?" "We need it in Moodle." "Can it integrate with Blackboard?"

The honest answer for most publishers is: not yet, and that's costing you deals.

LTI is the standard that lets your content live inside the learning management systems institutions already use. Without it, you're asking students to leave their LMS, log into a separate platform, and remember another set of credentials. With it, you become a click-through experience that feels like part of their course.

Here's what LTI actually is, when it makes sense for your business, and what you should expect to spend.

What LTI Is, In Plain English

LTI stands for Learning Tools Interoperability. It's a protocol, a set of agreed rules that learning management systems and content providers use to talk to each other.

Think of it like Apple Pay. Your bank doesn't need a special agreement with every store that accepts Apple Pay. There's a standard, and as long as everyone follows it, the experience just works.

LTI is the same idea for educational content. A student clicks a link in their Canvas course, lands on your platform already authenticated, completes an exercise, and their grade flows back into the Canvas gradebook. The institution doesn't need a custom integration. You don't need a separate deal with each LMS vendor.

That's the value. Single sign-on, seamless content delivery, and grades flowing back where teachers expect to see them.

When You Actually Need LTI

LTI isn't free, and it isn't always necessary. Here's when it's a clear yes.

You're selling to institutions
Universities, K-12 districts, and further education colleges almost always require LTI in their procurement process. Not having it can disqualify you from the bid before anyone reads your pitch.
Teachers need to assign your content
If the typical use case is a teacher saying "this week's homework is on our platform," you need to be one click away from inside their LMS. Anything else loses students at the doorway.
Grades need to reach the gradebook
Teachers don't want to copy scores between systems. If grade reporting matters to your customers, LTI is the path of least resistance.
You're competing with platforms that already have it
If your competitors integrate cleanly with Canvas and you don't, you're already behind on every institutional sale.

When You Probably Don't Need It

You sell direct to consumers
If parents, students, or self-paced learners are buying directly, LTI adds complexity for no benefit.
Your content is corporate training
Corporate L&D usually runs on different standards (SCORM, xAPI). LTI is a higher education and K-12 protocol primarily.
You're early-stage and proving the product
Don't build LTI before you've validated the content itself. Institutional sales cycles are long. You can add LTI later, once the content is selling.

LTI 1.1 vs LTI 1.3: Which Version Do You Need?

There are two versions of LTI in active use, and you'll likely need to support both.

LTI 1.1 is the older standard. It's simpler and still widely deployed, and many institutions haven't migrated yet. If you only support LTI 1.3, you'll lose deals with schools that haven't upgraded.
LTI 1.3 (sometimes called "LTI Advantage") is the modern standard. It's more secure, supports better privacy controls, and is where the industry is heading. New institutional deployments use this.

The practical answer: if you're building from scratch in 2026, build LTI 1.3 first and add 1.1 support if your sales pipeline demands it. If you're working with established institutional customers, you'll likely need both from day one.

This is a conversation worth having with your sales team before development starts. Their target customer list determines which versions you actually need.

How LTI Integrates With Drupal

If your content platform is built on Drupal, you have two realistic approaches.

Option 1: Use a Drupal Module

There's a community-maintained module that handles the LTI protocol within Drupal itself. Your content lives in Drupal, students arrive via LTI launches, and Drupal authenticates them.

This makes sense if:

Your platform is a relatively standard Drupal site
You don't have complex multi-tenancy or custom workflows
You want the lowest upfront cost

The trade-off: module support has been inconsistent over the years, and LTI 1.3 support varies. Have someone qualified review current module status before committing.

Realistic cost: £5,000 - £15,000 for setup, configuration, and basic testing.

Option 2: Custom Drupal Implementation

For more complex requirements such as multi-tenancy, custom grade workflows, or integration with existing user systems, you build LTI handling into Drupal directly using established libraries.

This makes sense if:

You serve multiple institutions and need data isolation between them
Your assessment logic is non-standard
You need fine control over how launches and grade passback work

Realistic cost: £15,000 - £50,000 depending on complexity.

What Goes Wrong With LTI

Five things tend to bite publishers in the first year of an LTI rollout. Plan for them.

Different LMS platforms behave differently
Canvas, Moodle, Blackboard, and Brightspace all claim LTI compliance, and they all have quirks. Code that works perfectly in Canvas testing can fail silently in Moodle. You need to test against real platforms, not just specifications.
Some institutions don't share student email addresses
Privacy policies vary. If your user accounts depend on email, you'll need a fallback identifier strategy from day one.
Grade passback fails sometimes
The LMS might be down. The teacher might have moved the assignment. Your platform has to handle these failures gracefully, and never block the student's experience because grades couldn't be reported in real time.
Iframe and cookie restrictions break sessions
Modern browsers are increasingly aggressive about third-party cookies. If your content is loaded inside an LMS iframe (most launches are), session handling needs careful design. This catches teams who haven't dealt with it before.
Key rotation is awkward later
Each LMS connection has shared secrets that occasionally need to be updated. If you don't plan for rotation, you'll either have downtime during updates or you'll never update them, which is a security risk.

None of these are fatal. They're just things experienced LTI implementers know to design for.

Realistic Timeline

If you're starting from scratch:

Discovery and architecture: 2-3 weeks
Initial implementation: 4-6 weeks for a single LMS
Multi-LMS testing and refinement: 4-6 weeks
Pilot with a real institutional customer: 4-8 weeks

Total: 4-6 months from kick-off to a stable production rollout, longer if you need both LTI 1.1 and 1.3 from launch.

If your sales team is already pitching LTI to prospects, start the build before you sign the contract. You don't want to be 12 weeks into discovery with an institutional customer waiting on you.

Making the Decision

Ask yourself these four questions:

Is institutional sales actually our market?
If yes, LTI is a checkbox you must tick. If no, deprioritise it.
Are we losing deals because we don't have it?
Talk to your sales team. If procurement teams are filtering you out, the cost of LTI is less than the cost of those lost deals.
Do we need both LTI 1.1 and 1.3?
Look at your top 10 institutional prospects. What versions are their LMS platforms running? This determines your scope.
Do we want LTI as a feature, or as part of a broader platform modernisation?
If you're already considering headless architecture, modern frontend, or multi-channel content delivery, building LTI into that work is more efficient than retrofitting later.

Getting Started

Here's what I'd recommend if LTI is on your roadmap.

Get a real assessment of your sales pipeline
Have your sales team list every institutional opportunity in the last 12 months where LTI came up. That's your real demand signal.
Inventory the LMS platforms your prospects use
This determines whether you need 1.1, 1.3, or both, and which platforms you must test against.
Get architectural advice before you commit to an approach
The two options above have very different long-term cost profiles. The cheapest upfront isn't always the cheapest over five years, especially if you're scaling to multiple institutional customers.
Plan for a pilot, not a big-bang launch
The right first deployment is one institutional customer who's a good partner: willing to give feedback, tolerant of the inevitable early bugs. That's worth more than a polished launch with no real-world testing.

A Final Word

LTI looks straightforward on paper but is genuinely fiddly in practice. The protocol itself is well-documented. The hard parts are the things the documentation doesn't mention: how each LMS interprets the spec slightly differently, how to handle edge cases gracefully, how to design grade passback that survives the messy reality of real classrooms.

For most publishers, LTI is no longer a nice-to-have. It's the price of admission to institutional sales. The question isn't whether to do it, but how to do it without spending more than you need to or building something that fails in production.

Get the architecture right early, plan for the gotchas, and treat the first deployment as a learning exercise rather than a launch. You'll save yourself a lot of pain.