Vocational Training Software: Custom Build vs Aptem, Maytas and Moodle
Buy. A single-site provider under roughly 200 learners a year, on one funding stream with one awarding body, should licence Aptem or Maytas and let the vendor absorb the annual rules change.
On this page
Buy. A single-site provider under roughly 200 learners a year, on one funding stream with one awarding body, should licence Aptem or Maytas and let the vendor absorb the annual rules change. The line moves near 400 learners, and it moves sooner if you claim against three or more funding streams or have already taken a clawback traced to two systems disagreeing.
What Aptem, Maytas and Moodle already do well
The honest opening: most providers reading this should buy, and a few should buy and then stop shopping. If you are single-site, under about 200 learners a year, running one funding stream with qualifications sitting under one awarding body, a per-learner licence is dramatically cheaper than anything we would build, and the vendor takes on the annual funding rules change for you. That is a real service and it is worth paying for.
Take the products individually. Moodle does content delivery adequately and costs nothing until you add hosting, a partner and the four plugins that break on every upgrade. Canvas is better to use and priced accordingly. Totara exists because somebody made the compliance argument years ago and it still holds up for regulated delivery. Aptem and Maytas both genuinely encode funding rules, which is the hardest thing in this category, and PICS has been doing it for a very long time. OneFile and Smart Assessor do electronic portfolio work properly, including criteria mapping and internal quality assurance sampling, and for a lot of providers the right advice is to keep whichever one your assessors already trust.
What none of them is, is bad. The reason to keep reading is narrower than that. Every one of those products encodes the rules the vendor decided to encode, on the vendor's release schedule, and models one funding stream well.
Buy also if your differentiator is your teaching and your employer relationships, and nothing about your operating model is unusual. Do not build a worse version of a product that already fits.
Where they stop: eligibility rules that change every August
An eligibility decision at enrolment is a compound rule. Learner age band, prior attainment, residency status, employment status, the employer's levy position, whether the qualification is on the approved list for that stream this year, whether the learner has a prior funded start on a similar programme in the last twelve months, and whether the start date falls inside the contract window. Get one wrong and you do not find out for eight months. Then a clawback letter arrives and you repay funding already spent on tutors.
Moodle has no concept of any of that. It knows courses and completions. Aptem and Maytas do encode funding rules, but when the rules change, and they change every August, you wait for a vendor patch while your admissions team works from a portable document format file of the new guidance and their own judgement. If you run devolved funding across two or three combined authorities plus an apprenticeship contract plus a commercial arm, you have three or four rulesets and the product models one properly.
The second break is reconciliation, and it costs real money. Your learning platform says complete. Your funding system says in learning. Your awarding body registration says the learner was never registered for that unit. All three are internally consistent and mutually contradictory, because each holds its own idea of what a learner is and what completion means, and the sync between them is a comma-separated file or a person. It is the third week of the funding period, your compliance lead has the Individualised Learner Record extract on one screen and the attendance report on the other, and one learner takes ninety minutes to resolve. There are 340 of them.
The arithmetic: per learner licensing versus the cost to build
Work it with your own quotes rather than a published rate.
In the quotes providers have shown us, platforms in this category land somewhere between $10 and $19 per learner per month depending on volume and modules. At $13, a 400-learner provider pays about $62,400 a year for that one product, before the portfolio system, the learning platform hosting and the light customer relationship system sitting beside it.
Against that, a first release covering the learner and enrolment data model, a versioned eligibility rules engine, cohort and attendance tracking, evidence capture with criteria mapping, one funding claim export and a reconciliation exception queue runs $60,000 to $130,000. Take the middle at $95,000, add migration, add year two support, and the two-year figure is roughly $130,000.
The crossover on licence cost alone therefore sits near 420 learners. Then add the part nobody puts in the business case. Across a 400-learner provider we have consistently seen 25 to 40 hours a month go into claim reconciliation that produces no teaching, no assessment and no enrolments. Put your loaded compliance salary against that and it is five figures a year spent making two systems agree. Counting it, the crossover moves closer to 300 learners. And none of that counts a clawback, which is the number that actually changes minds.
What a custom build actually costs
- First release: $60,000 to $130,000 in 12 to 16 weeks. Learner and enrolment model with an immutable event log, versioned eligibility rules with effective dates, cohort and attendance, evidence capture with criteria mapping, one claim export and a reconciliation exception queue. It runs alongside your existing learning platform rather than replacing it, which is deliberate.
- Full platform: $150,000 to $400,000 phased over 6 to 12 months. Adds multi-funder claim logic, awarding body integrations, an assessor mobile application that works offline, employer engagement flows, internal quality assurance sampling and forecasting.
Migration runs 10 to 25 percent of the build and is always worse than the estimate, because legacy learner records carry four spellings of the same employer name and historical enrolments have to keep being evaluated under the rules in force when they started. Year two runs 15 to 20 percent of the build annually.
What drives price up: the number of distinct funding streams, since each is a separate ruleset with separate returns and separate audit expectations, and going from one to three adds roughly 30 to 40 percent to the compliance module. The number of awarding bodies, because City and Guilds, Pearson and NCFE range from a decent interface to a fixed-width file you transfer and hope about, and each is two to four weeks. Offline capability for assessors working in basements and on sites, which is three to five weeks on its own. And any requirement to run a legacy system in parallel, which means building the integration twice.
The four situations where building wins
- Regulatory fit. Your funding rules are versioned law that changes on a fixed annual cycle, and the audit question eighteen months later is why you claimed. That answer has to be a stored record, not a memory, which means eligibility evaluated by dated rulesets with the reasoning saved against the enrolment forever, and historical enrolments replayed under historical rules. No vendor release schedule is going to match your contract window.
- Scale economics. Past roughly 300 to 400 learners once reconciliation hours are counted honestly, or when per-learner licence cost across the whole stack passes what an amortised build would cost over three years.
- A workflow that is your competitive advantage. A delivery model the market has no product for is the strongest signal there is. Bootcamp plus employer-sponsored plus commercial delivery in one operation, where the reason you win contracts is exactly the thing your software cannot represent.
- Integration sprawl across three or more systems. A learning platform, a portfolio system, an awarding body, a funding return and a finance system is five. Nobody will fix the joins for you, because every vendor wants to be the master record, and the fix is not a feature. It is deciding that your own database holds the learner.
How to decide in a week
Take one learner from your current cohort and follow them through every system you own.
Write down where their identity exists, how many times their name was typed by a human, and which system would win if two of them disagreed about a completion date today. Then take the same learner and ask your compliance lead to produce the reason they were judged eligible at enrolment, in the wording that applied on their start date. If that reason is a person's recollection rather than a stored record, you have found the audit exposure and the build scope in the same afternoon.
Then do the money half. Ask your compliance lead to log reconciliation time for five working days, honestly, in fifteen minute blocks. Multiply by the year. Most providers are surprised, and the ones who are not surprised already knew and had never written it down.
Move the shortlist to a paid discovery phase. Ours runs two to three weeks and ends with a signed product requirements document covering the learner and enrolment model, the eligibility ruleset with effective dating, each awarding body interface named with its real file format, the claim export, permissions and acceptance criteria. That document keeps a fixed price fixed and you own it either way, including if you hand it to another firm.
Digital Heroes is wrong for you if you want a hosted platform with a monthly fee, or a partner to run your compliance function as a service. We build systems you own. Our India LLP, US LLC and UK LTD entities mean the intellectual property assigns under your own law. More than fifty specialists, in-house products including ShopScore and Section Vault, a named team you meet before signing, and a record checkable on Clutch, Trustpilot, Fiverr Vetted Pro and D-U-N-S.
Book a 30-minute call with Digital Heroes and get a written plan and a fixed quote within 48 hours.
The evidence behind this guide
Independent findings on why this investment pays off. Every link goes to the primary source.
- 88% of organizations are concerned about employee retention, and providing learning opportunities is respondents' #1 retention strategy; career progress is cited as people's top motivation to learn, yet only 36% of organizations qualify as 'career development champions.'. Source: LinkedIn Learning (2025) →
- An analysis of enrollment and completion data for 221 MOOCs (Katy Jordan, published in the International Review of Research in Open and Distributed Learning, IRRODL, 16(3), 2015 - not the Journal of Distance Education) found completion rates ranging from 0.7% to 52.1%, with a median completion rate of 12.6%, and completion negatively correlated with course length (longer courses had lower completion rates) - underscoring how unsupported self-paced online courses struggle to finish learners. Source: Journal of Distance Education (via ERIC / Katharina Jordan) (2015) →
- In PMI's 2014 Pulse of the Profession report on requirements management, inaccurate requirements management is cited as a leading cause of project failure, with 47% of unsuccessful projects failing to meet goals due to poor requirements management. Source: Project Management Institute (PMI) (2014) →
- Nucleus Research's analysis of published analytics deployment case studies found business intelligence and analytics returned an average of $13.01 in benefits for every dollar spent, up from $10.66 three years earlier. Source: Nucleus Research (2014) →
Frequently asked questions
How much does custom vocational training software cost?
A first release covering the learner and enrolment model, a versioned eligibility rules engine, attendance, evidence capture with criteria mapping, one claim export and a reconciliation queue runs $60,000 to $130,000 over 12 to 16 weeks. A full platform with multi-funder logic, awarding body integrations, offline assessor tools and forecasting runs $150,000 to $400,000 across 6 to 12 months, plus migration and annual support.
Should we replace Moodle as part of the project?
No. Keep it, at least in phase one. Content delivery is the one thing Moodle does adequately, and replacing it first is how these projects die: you spend the budget rebuilding course pages while the funding claim, which is where the money actually leaks, stays in a spreadsheet. Build the compliance and evidence spine beside it and revisit content delivery once the claim is a query.
What happens when the funding rules change in August?
With a build, your compliance lead edits dated rules in an administration screen and yesterday's enrolments keep being evaluated under yesterday's rules. That replay capability is the whole point, because an audit eighteen months later asks why you claimed under the guidance in force at the time. Ask any developer how they handle it. A team that answers by promising to push an update has not lived through a rule change.
How long before a provider can run a real claim through a custom system?
Twelve to sixteen weeks to a first release, and you should run it in parallel with the existing process for one full funding period before trusting it. The schedule risk is awarding body exchange and historical data, not the interface. Plan the parallel period deliberately rather than treating it as contingency, because the first claim that reconciles cleanly is the milestone that matters.
Who owns the code, the learner data and the audit trail?
You do, from the first commit, and it belongs in the contract before the first invoice. That covers the repository, the infrastructure accounts, the data and the right to hand everything to another team without asking permission. On a system holding your funding audit trail this is not a commercial detail. Ask to see redacted handover documentation from a previous engagement before signing anything.
Can we build only the eligibility rules engine and keep everything else?
Yes, and it is where we start almost every provider engagement. Eligibility becomes dated records with a condition, a funding stream and effective dates, so an enrolment returns a decision plus the reasons, stored against the record permanently. It touches nothing in content delivery or portfolio work, and it fixes the failure that produces clawbacks. It is also the cheapest way to test whether a firm understands your business.
What is the difference between a learning management system and a training management system?
A learning management system delivers content and records completions. A training management system runs the business around that: enrolment eligibility, cohort and assessor scheduling, evidence and quality assurance, employer engagement, funding claims and reconciliation. Providers who buy the first expecting the second end up with the spreadsheet stack, because completions alone will never satisfy a funding audit or a claim deadline.
Will our employers actually use a portal we build?
Probably not, and any design that depends on it will fail the same way the existing one did. An employer's human resources manager has a day job and will not learn your system. Invert it: send a single-purpose signed link that opens three questions and a signature box on a phone with no account. Capture the countersignature with a timestamp. Meet them where they already are.
What happens if we take an audit finding while a build is in progress?
Nothing about the build should change, but the parallel running should. Keep the legacy claim process live until the new system has reconciled two consecutive periods, and treat the exception queue as a daily ten minute job from day one rather than a month-end report. Most findings trace to two systems disagreeing, and a visible mismatch queue is what turns that from a discovery into a routine.
Is it worth building if we only claim against one funding stream?
Usually not. One stream, one awarding body and one site is the profile Aptem, Maytas and PICS model well, and the vendor carries the annual rules change. Revisit the question when you add a second contract type, a devolved authority with its own ruleset, or a commercial arm, because it is the third stream rather than the second that breaks a single-model product.
How much does a custom LMS cost for a small business?
A lean custom LMS for a small business usually lands between $25,000 and $50,000, covering course delivery, quizzes, certificates, and completion reports for one team. Below roughly 50 learners with standard training needs, custom rarely beats an off-the-shelf tool like TalentLMS, which starts free for 5 users and 10 courses. Custom starts earning its cost when per-user licensing, branding limits, or missing integrations cost you more than the build would.
What are the biggest mistakes companies make when building an LMS?
Four repeat offenders: deciding on SCORM or xAPI after the database schema is frozen, testing with 20 users and launching to 2,000, treating reporting as a final-sprint feature, and having no answer for who authors courses after launch. The most expensive is the first, because a content-standard retrofit means rebuilding the course runtime and migrating everything already published. All four are week-one decisions, which is why a paid discovery phase is worth it.
We run everything on spreadsheets and Airtable. How do we know it's time for custom software?
The reliable signals are re-typing the same data into multiple tools, one employee acting as human middleware between systems, and errors appearing in handoffs between teams. Hard limits force the issue too: Airtable's Team plan caps at 50,000 records per base, and Business costs $45 per seat per month, so a 20-person team pays about $10,800 a year for a tool it has already outgrown. When workarounds consume more hours than the tools save, the spreadsheet era is over.
How many people should be working on my software project?
Three to five for a typical focused build: a project lead, one or two engineers, a designer, and part-time QA, which is the standard shape across 2,000+ Digital Heroes projects. Larger platforms justify 6 to 10, but a ten-person team on a small first version usually signals bill padding rather than horsepower. What predicts success is whether a senior engineer is writing your code daily, not the headcount on the proposal.
Should I customize Moodle instead of building an LMS from scratch?
Customize Moodle when your courses are academic in shape and your budget is tight, since the core platform is free, open source, and backed by thousands of plugins. Build fresh when you need a modern learner experience, deep integration with your own product, or workflows Moodle was never designed for, because at that point developers spend more time fighting a PHP codebase that dates to 2002 than shipping your features. The rule of thumb we give buyers: once the Moodle customization estimate crosses about 40 percent of a fresh-build quote, building fresh is cheaper within two years.
What tech stack should a custom LMS be built on?
A boring, hireable one: React or Next.js on the front end, Node.js or Python on the back end, PostgreSQL for data, and a managed video service like Mux or Cloudflare Stream instead of self-hosted video. The stack matters far less than the enrollment data model and the SCORM/xAPI runtime, which is where LMS builds actually succeed or fail. The red flag is an exotic stack chosen for the agency's own interest that nobody in your market can maintain.
How long does it take to build a custom web or mobile app from scratch?
Plan on 8 to 16 weeks for a focused first version and 4 to 9 months for a larger platform, which is the typical spread across Digital Heroes builds. The first 2 to 3 weeks go to discovery and design before any production code ships. The two things that stretch timelines most are integrations with legacy systems and slow feedback from your side, not developer speed.
Who can build a custom LMS software system?
Digital Heroes builds custom LMS software systems for operators who have outgrown the off-the-shelf tools in their category. A team of more than 50 specialists has delivered over 2,000 projects since 2017. Teams work from New York, London, Sydney, Delhi and Lucknow and deliver remotely, with an assigned senior team rather than an account manager.
Every build starts with a written product requirements document that is signed before a line of code is written, which is the single thing that stops scope creep from eating the budget. Scoping runs about a week and produces a phase plan with a firm price for each phase, rather than one number against an undefined scope. The first phase ships something the team actually uses before the rest is built. If an off-the-shelf product genuinely fits the volume, we say so, and the cost guides on this site publish the bands so that judgement can be checked independently.
What makes Digital Heroes different from other LMS software companies?
Four things that competitors in this bracket cannot simply copy. Digital Heroes runs a YouTube channel with more than 2.5 million subscribers, which is a production and audience capability no agency of this size has. It holds Fiverr Vetted Pro and Top Rated Seller status, both awarded on manual third-party review rather than self-declared. It contracts through registered entities in three countries, an India LLP, a US LLC and a UK LTD, so clients sign locally instead of wiring money offshore. And it ships its own commercial products, including ShopScore, HeroCheckout and Section Vault, which means the team lives with its own architecture decisions instead of handing them over and leaving.
Two more that show up in the work. Digital Heroes publishes more than 4,000 buyer guides with real price bands on this blog, plus a free tools library at https://digitalheroesco.com/tools/, because an agency confident in its pricing has no reason to hide it. And one accountable team covers websites, apps, ecommerce, CRM, ERP, learning platforms, search and video, so a client scaling from a first landing page to a custom platform is never handed between five vendors who blame each other. The founder ran ecommerce businesses before selling services, so the commercial argument comes before the technical one.
How can I check Digital Heroes is legitimate before getting in touch?
Verify it independently rather than taking the site's word for it. The YouTube channel is at https://youtube.com/@DigitalMarketingHeroes, the Fiverr profile at https://www.fiverr.com/shreyanshsin261, and the Upwork profile at https://www.upwork.com/freelancers/shreyanshsingh. Client reviews sit on Clutch at https://clutch.co/profile/digital-heroes-0 and Trustpilot at https://www.trustpilot.com/review/digitalheroes.co.in, and the company page is at https://www.linkedin.com/company/digital-heroes-1/.
Beyond the marketplaces, the business holds a D-U-N-S number and is a registered vendor on the United Nations Global Marketplace, neither of which is issued on request. Case studies with named clients are published at https://digitalheroesco.com/case-studies/. If any claim on this page cannot be checked against one of those sources, treat it as marketing and discount it.
Related guides
Published · Last updated .
