Custom LMS development: cost, break-even, and when to build

Custom LMS development pays for itself only when the licence bill it replaces is bigger than the cost of running your own system. On our price list an LMS platform starts at $40,000 and from 8 weeks. Against a $30,000 a year licence bill and $12,000 a year of running cost, that build pays back in 2.2 years. Against a published plan at a few thousand dollars a year for the same employee training, it never pays back on price at all.

That is the whole decision in two sentences, and most build-versus-buy articles skip it in favour of a feature comparison. This one is about the arithmetic: what an off-the-shelf platform actually charges for, what a build costs to make and to keep, how to compute your own break-even point, and the three things that usually make the answer wrong. If you want the basics first, our older post on what a learning management system does covers the product category itself.

What people mean by custom LMS development

Three different things, and they carry different bills. Naming which one you are pricing removes half the confusion in a build-versus-buy conversation.

• Subscribe to a hosted platform. You rent a shared product. Setup is days, the vendor runs it, and you pay per user or per active user for as long as you use it.
• Extend an open-source platform. Usually Moodle. The licence costs nothing, and you take on hosting, upgrades, and a plugin layer that has to survive every core release.
• Build your own. Your data model, your roles, your integrations, in a cloud account you own. This is what custom software development means here, and it is the only one of the three where the shape of the system follows the shape of your organisation rather than the reverse.

Most organisations that end up building have already run route one or route two for a year or two. That is a good order to do it in, because a year of real usage produces a requirements list nobody can write from an empty page.

What actually drives the cost of an off-the-shelf LMS

The metering model decides it. Two vendors can print similar per-user numbers and send very different bills, because they count different people. Before you compare features, find out whether you are paying for everyone in the directory, everyone who logged in this month, or everyone who logged in this year.

Two consequences follow. First, a quote for a platform that meters yearly active users will look worse than one that meters monthly active users at the same headline rate, and for seasonal training it usually is worse. Second, a free licence is not a free platform, which is why the Moodle row still costs money every year even though the software costs nothing.

The tier you land on is often decided by integrations rather than by headcount, and the plan table shows exactly where. TalentLMS lists single sign-on on Core, its cheapest paid plan, but greys out LTI 1.3 support there and switches it on from Grow. A thirty-person team that only needs single sign-on stays at $119 a month; the same team pays $229 the day it wants to plug in a tool over LTI. Price the plan your integrations put you on, then add the band your user count puts you in.

What a custom build costs, and what it costs to keep

Our own numbers, so you have a real starting figure rather than a range invented for an article. Our price list carries two entry points that touch this work: LMS platform development from $40,000 and from 8 weeks in the enterprise line, and education software from $30,000 and from 3 months in the industry line, where the price list scopes it to custom LMS, training and self-learning apps for schools and organisations. Which line your project sits in is settled in the analysis phase. Around them sit the smaller pieces most projects buy first.

• Analysis phase, $2,000 to $3,000, 1 to 2 weeks. The written plan the build estimate is calculated from: who the roles are, what each one has to be able to do, which systems the platform has to reach, and what that adds up to in budget and calendar time.
• Proof of concept, from $8,000, from 2 weeks. Worth buying when one thing in the plan is genuinely uncertain, such as a video pipeline or a synchronisation with a legacy HR database.
• Third-party API integration, from $3,000 each, from 1 week. Priced per connection because that is how the work arrives.
• Running it afterwards, and this is the line people forget. Two published shapes, and they are far apart. Hourly DevOps and support work is $50 an hour, so twenty hours a month comes to $12,000 a year. A managed technical support package starts at $5,000 a month, which is $60,000 a year, and enterprise support starts at $15,000 a month. Pick the shape you would actually buy before you run the calculation below, because it decides the answer more than the build price does.

What pushes the build above the $40,000 floor is not screens. It is the number of roles the system has to separate, the number of systems it has to reach at $3,000 or more per connection, whether existing course content has to be migrated rather than uploaded, and whether one part of the plan is uncertain enough to deserve an $8,000 proof of concept first. Count those four before you treat the floor as your budget.

The break-even calculation

One line of arithmetic decides most of this, and you can do it before you talk to anybody.

Years to break even = build cost divided by (annual licence bill minus annual running cost). If your running cost is equal to or higher than the licence bill, there is no break-even point and the build has to justify itself on something other than price.

Take the published $40,000 build and the cheaper of the two running shapes, twenty hours a month of hourly work at $50 an hour, which is $12,000 a year. Set that against a $30,000 a year licence bill. The difference is $18,000 a year, and $40,000 divided by $18,000 is 2.2 years. Anything past that point is money you keep.

Change the licence bill and keep the other two figures, and the picture moves fast. The table below is the same formula with the same $40,000 build and the same $12,000 a year of running cost.

Now run it against a published plan instead of an enterprise quote. TalentLMS Pro at its smallest user band with yearly billing is printed at $449 a month, which is $5,388 a year. Subtract $12,000 of running cost and the difference is negative, so the build never repays itself. That is a common outcome among the organisations who ask us this question.

Then swap the running shape and watch the answer flip. On a managed technical support package at $5,000 a month, the running cost is $60,000 a year, which is more than the $30,000 licence bill on its own. There is no break-even point at all, and the build would have to earn its keep on something other than price. This is why we ask which support model you want before we quote anything: it moves the result further than the build price does.

Have a renewal quote in front of you? Send us the annual figure and the user count and we will tell you whether a build can beat it.

Contact us

Where the arithmetic usually goes wrong

Three mistakes account for most of the decisions we have seen reversed a year later. All three sit in the inputs rather than in the formula.

You compared a sticker price with an active-user bill

A plan band and an active-user contract are not the same product. If you have 4,000 people in the directory and 600 of them log in during a given month, a monthly active user contract bills for 600 and a registered user contract bills for 4,000. Before you put a licence figure into the formula, ask the vendor which of the two you are being quoted, and ask what happens in the month a compliance deadline pushes everybody into the system at once.

You counted integrations as one line

Each connection is a build item and a maintenance item. An identity provider for single sign-on, an HR system that owns the org chart, a payment provider if you sell courses, a video service, a calendar. We price third-party integrations from $3,000 each precisely because that is the unit the work comes in, and the same is true on the buy side: an off-the-shelf platform with five connectors you have to configure and keep working is not the zero-effort option the demo suggested.

You assumed your content and records come with you

This is the expensive one, because it does not show up until you try to leave. Course content packaged as SCORM moves between platforms. Learner activity moves too, but only if you were already writing it into a learning record store of your own with xAPI while the vendor platform was running. That specification is now an IEEE standard, published as 9274.1.1-2023 and built on the earlier xAPI 1.0.3 specification, which is a decent sign it is worth designing around. External tools plug in over Learning Tools Interoperability, and 1EdTech, the body that publishes it, names LTI 1.3 as the current version. What does not travel is everything the vendor holds in its own tables.

“Decide where the learner records will live before you decide which platform holds them. If every completion exists only in the vendor database, the price of leaving climbs every month whether you leave or not. Send the same events to a store you control from the first week, and you can swap the platform underneath later without losing the history.”

Alexander Storozhevsky, Lead developer at Ronas IT

When we tell people to buy off the shelf

Whenever the training itself is standard, which is more often than the people asking us expect. If your training is course delivery, quizzes, certificates and reporting for a few hundred people, that is a solved product sold at a price no build can match. The same goes for a team that has nobody to own a system afterwards: software without an owner degrades, and a vendor subscription at least buys you somebody whose job it is to keep it running.

We would also point you at Moodle before quoting a build, if what you need is standard course structures and you have or can hire the operations capacity. A free licence plus hosting is a cheaper experiment than anything we can write, and it produces the requirements list you would otherwise pay us to guess at.

“If your whole training operation fits inside a plan that costs a few thousand dollars a year, we will say so, and we will say it before you pay us for an analysis phase. A build has to answer for itself on something the subscription cannot do. When the honest answer is that it cannot, the client keeps the money and we keep a relationship that is worth more than one project.”

Roman Surikov, CEO at Ronas IT

When building is the cheaper answer

In four situations, and only the first one is about price. The other three are about things a subscription cannot sell you at any tier.

1. The licence bill has outgrown the build. Run the formula with your own numbers. In the worked example above, $24,000 a year of licence spend repays the build in 3.3 years and $48,000 repays it in 1.1, and the case gets stronger every time the contract renews.
2. Learning is part of the product you sell. If customers or partners log in to learn, the learning platform is a customer-facing product with your billing, your branding and your onboarding in it. Vendor portals are built for the internal case and charge extra for the external one.
3. The process does not fit the vendor data model. Multi-employer training records, regulated competency frameworks, assessment signed off by two named people, certificates that expire on a schedule set by a regulator. If you are already planning a spreadsheet to sit beside the platform, the platform does not fit the process.
4. The integrations are the point. If the value is in what the learning data does after the course finishes, feeding a competency profile, a shift roster or an audit report, then the platform is a data source and you want to own its schema.

How we scope an LMS build before quoting

We start with an analysis phase, and the deliverable is a plan you own whether or not we build it. Our discovery phase for a tutoring platform is the closest published example, and it was analysis rather than delivery: the product had not been released, so the case shows placeholder branding and does not name the client. That engagement is published at $1,300 and two weeks, below the $2,000 to $3,000 the analysis phase line carries today. The work is the same shape on a corporate learning platform.

• Roles before screens. Three of them there, student, tutor and administrator, each with its needs written down and a journey map reviewed with the client. Changing a journey map costs an afternoon. Changing it during development costs a sprint.
• Features as user stories, then priorities. Every action each role can take, grouped into versions, so the first release carries the thing the product is actually for and nothing else.
• Business rules in writing. On that project the rules covered holding and charging money, refunds, cancellations, dispute resolution and participant safety. On a corporate platform the equivalent list is enrolment, mandatory training, expiry and who is allowed to see whose results.
• Integrations chosen, not built. We shortlisted Stripe Billing for payments and refunds, the Zoom SDK for lessons, the Google Calendar API for schedules and Intercom for support, so the team would spend its budget on the part nobody sells.
• A stack proposal with a reason. React on the front end, Laravel on the back end and Laravel Nova for the admin panel, chosen because we have component libraries for them and can move faster than a first build normally allows.

An estimate made before design is an estimate about an assumption, so ours arrives with its assumptions written down, which is what lets you argue with it later.

Who owns the system after launch

This decides your exit cost on the build side, exactly as the vendor schema decides it on the buy side. A project with us starts in the client cloud account rather than ours, and the infrastructure, the cluster and the repositories are all stood up from code we reuse across projects. Because both the account and the code belong to the client, another team can pick the system up as it stands. Our Google Cloud fast start page spells the same arrangement out in full, down to the infrastructure code living in your repository.

I ask about this at the first call, before anyone talks about features. A learning platform outlives the team that builds it, and the question that decides whether it stays cheap to own is who holds the account and the code five years from now.

What we run afterwards is deliberately small: two environments, automated releases and monitoring, with security patching and a regular look at what the infrastructure costs. Response times come out of the support agreement rather than a number published on a page. If you would rather not stay on a support package with us, our DevOps services and a dedicated development team are the two ways clients usually take it over.

What to do next

Five steps, in the order we would take them.

1. Write down your real annual licence bill. Not the list price. The renewal quote, including implementation services, extra connectors and the seats you added mid-term.
2. Find out what your vendor counts. Registered users, monthly active users or yearly active users. Then ask what a compliance month does to the invoice.
3. Ask for a sample export. Course packages, learner records, completion history. What comes back tells you your exit cost more honestly than the contract does.
4. List the integrations and count them. One line each. That list is the difference between a $40,000 build and a much larger one, on either side of the decision.
5. Run the formula with your own three numbers. Build cost, licence bill, running cost. If there is no break-even point, write down what the build would buy you that the subscription cannot, and decide on that instead.

Do those five and you will know the answer before anyone quotes you. If the arithmetic comes out close and you want a second opinion, send us the licence figure, the user count and the list of systems the platform has to talk to, and we will come back with a scope and a number rather than a brochure.

Sources for the figures above, all read in September 2026: our own pricing page, the published TalentLMS plans, the Docebo pricing page, and the Moodle licensing statement. All four change, so check the primary source before you commit a budget to it.

Send us your licence bill, your user count and the systems the platform has to connect to, and we will come back with a scope and a figure.

Get an estimate