There's a proposal on your desk. It says $180,000 for Year 1. 7% uplift Year 2. Per-seat fees scaling with headcount. Three-year term. "Unlimited modules" — though the implementation plan only schedules four in the first year.
Your CFO is going to ask you three questions before they sign that contract. This post is how to answer them honestly, and where the math actually lands.
Question 1: "What do we own at the end of the contract?"
If the answer involves "platform-specific format," "proprietary content blocks," or "data export available for a fee," what you own is approximately nothing. The content was authored in their tool. The personas live in their schema. The scoring rubrics are tied to their dashboard. If you cancel in Year 4, you start over.
If the answer is "you own a SCORM package," you can take it with you. SCORM is portable. Your existing LMS already consumes it. A different LMS in five years will also consume it. That's the asset.
This is the question that most often kills a SaaS deal once the CFO sees the answer in writing.
Question 2: "What's our cost per module, actually?"
Most enterprises ship two to four core modules per year, regardless of what the vendor's "unlimited modules" pitch implies. Your L&D team has finite SME bandwidth, finite stakeholder review cycles, and a finite number of priority topics from leadership each year. The vendor's pricing model assumes you'll ship twenty. You'll ship four.
The honest cost-per-module math at $180K Year 1 with four modules shipped:
- Per-module cost (Year 1): $45,000
- You do not own the modules
- You do not own the data
- You pay again in Year 2 and Year 3, whether you ship more modules or not
For comparison, a fixed-fee module build runs low-to-mid five figures per module, one-time, with you owning the artifact and the data on delivery. Four modules in a year lands between $80K and $160K total — and there is no Year 2 invoice unless you commission Year-2 modules.
Question 3: "What happens if this vendor gets acquired?"
The L&D SaaS market has had three major acquisitions in the last 18 months. The pattern is consistent: the acquiring company kills the lower-margin product lines, raises prices on the survivors, and tells customers they're "evolving to a stronger platform." Your contract is probably worded such that this is allowed.
If you own a SCORM package, an acquisition doesn't affect you. The package keeps running in your LMS. The LLM call keeps hitting your IT-approved provider. The dashboard keeps working because it reads data your LMS already collects.
If you don't own anything, your contract is a hostage situation waiting for a private-equity acquisition note.
When the SaaS proposal is actually the right call
To be fair: SaaS makes sense if you're shipping a new module every two weeks, you have a dedicated L&D engineering team of three or more, and you need analytics and authoring tools beyond what your LMS provides. That's a real shape of buyer — usually 1,000+ person sales orgs with mature enablement functions and a dedicated training-tech stack.
If that's you, buy the SaaS. The platform value exists. The recurring fee is paying for ongoing platform development you'll actually use.
When fixed-fee module delivery is the right call
Almost everyone else. Specifically:
- You ship 1-6 modules a year, not 20+
- Your LMS is already paid for, already integrated, and already passed security
- You want the artifact to outlive any single vendor relationship
- Your budget process prefers a one-time capital line over recurring subscription spend
- You don't have an L&D engineering team and don't plan to hire one
The most common objection — and the honest answer
"But what about updates? Content goes stale. SaaS keeps it fresh."
True: AI personas drift, scoring rubrics need recalibration, and source content evolves. The honest answer: most enterprise L&D content evolves on a yearly cadence, not a monthly one. Compliance requirements change at most twice a year. Product training evolves quarterly. Leadership-skill content barely changes at all.
When the module needs an update, treat it as a one-week refresh build — fixed-fee, scoped to the changes you want. Two refreshes a year across four modules is a known annual cost that's still well below a three-year SaaS contract at the same module count.
The portfolio play
The strongest pattern we see at customers who get this right:
- Buy a single fixed-fee module to validate the format with one team
- Run it for 90 days, measure behavior change with your existing LMS reports plus our optional insights dashboard
- If it works, commission two or three more across other teams
- At year two, reassess platform-vs-fixed-fee with real usage data, not vendor projections
This is structurally lower-risk than committing to a three-year SaaS contract before you've shipped a single module on the new approach.
What to do with the proposal on your desk
Before you sign it:
- Ask the vendor for the cancellation terms in writing. Specifically: what happens to your content and learner data if you cancel in Year 2?
- Ask for a fixed-fee single-module quote outside the platform. If they can't or won't quote it, you've learned what the unit economics actually look like.
- Run the build-vs-buy math at your real module-per-year cadence, not the vendor's projection.
If you want a second opinion on the proposal before you sign — or a fixed-fee quote on the first module so you have a comparable — the next step is a 15-minute discovery call: https://learningdevelopment.solutions
Learning Development Solutions is a service of Latchmere Consulting. We deliver fixed-fee AI-augmented training modules for L&D teams that ship 1-6 modules a year. No SaaS. No retainer. No lock-in.