Questions, answered.

ModuleMinder is built specifically for freelance L&D professionals, content studios and small to mid-sized agencies who create and sell eLearning content to corporate clients.

If you invest time and expertise creating modules, programmes or courses and then deliver them to clients who run them on their own LMS, ModuleMinder was built for you. If you have ever wondered how many people are actually accessing your content, or whether your licence agreement is being honoured, you are exactly who we had in mind.

ModuleMinder was created by the team at Aprendido after years of experiencing this problem first-hand. We know what it feels like to deliver content you have worked hard to create and then lose all visibility once it leaves your hands. We built the solution we wished existed.

As one of our founders put it: had we used ModuleMinder during our years of content delivery, we would gladly have paid to protect the revenue that content represented.

Absolutely not, and this is important. ModuleMinder is not about assuming your clients are acting in bad faith. Most licence overruns happen organically: a successful training rollout, a department expansion, a new cohort of staff.

ModuleMinder simply gives you the data to have an informed commercial conversation at exactly the right moment, rather than finding out months later. We think of it as a kinder supplier-client relationship model, one where you are always in a position to support your client proactively rather than react awkwardly after the fact.

ModuleMinder's Enterprise and Unlimited plans, coming soon, are designed for larger content businesses managing significant module portfolios. Customers with very specific requirements around self-hosted deployment or custom data processing agreements are welcome to get in touch directly to discuss their needs.

When you register a module and issue a client a licence, ModuleMinder generates a unique snippet tied to that licence. You paste it into your module in your authoring tool before you export.

When a learner runs the module on the client’s LMS, the snippet makes a silent call to the ModuleMinder licence server. The server logs an anonymised usage event and checks the running count against your agreed licence limit. If limits are being approached or exceeded, you are notified automatically. Nothing about the learner experience changes.

Yes. ModuleMinder works with Articulate Storyline, Articulate Rise 360, Adobe Captivate, Lectora, iSpring and Camtasia, and with any other tool that lets you add custom JavaScript or HTML to your content before export.

You don’t need to. Rise 360 and Camtasia have no JavaScript trigger, so instead you upload the published zip once and ModuleMinder builds a licensed copy for each client on demand.

An uploaded zip is the only content we ever hold. It is yours to delete, and it goes when the module does. Any other tool can use the upload route too, if you prefer it to the snippet.

ModuleMinder is not tied to a single content standard. The snippet runs inside the published course itself, so it works with SCORM 1.2, SCORM 2004 and other formats that support embedded code. As eLearning standards continue to evolve, ModuleMinder evolves with them.

Content plays by default. This is a core design principle of the platform. If our server is unreachable for any reason (scheduled maintenance, unexpected downtime or anything else), your content runs normally and your learners are never blocked or disrupted because of an issue on our side.

We are committed to maximum uptime, but we have also made sure your clients and their learners are never affected if we fall short of that commitment.

This is a deliberate design decision. Hard blocking (cutting off learner access the moment a limit is hit) disrupts learners mid-course, puts your client in an embarrassing position and can seriously damage a relationship you have spent years building.

In our experience, licence overruns are rarely malicious. They usually reflect business growth on your client’s side, which is a commercial opportunity for you. ModuleMinder notifies you at the right moment so you can have a conversation, sell additional licences and strengthen the relationship.

Yes. While our default and recommended approach is soft enforcement through alerts, ModuleMinder offers a hard block option for creators who need it. You choose the enforcement approach that suits each client relationship.

Yes. You can set a specific expiry date, or a duration from first use, for example 12 months from the date the module is first accessed. ModuleMinder alerts you ahead of expiry, giving you time to have a renewal conversation before access ends.

Yes. You can combine both, for example 50 users for 12 months, whichever limit is reached first. ModuleMinder monitors both and alerts you when either threshold is approached or exceeded.

No problem. Set the licence to unlimited. ModuleMinder will not send any threshold alerts, but you still get full visibility of how your content is being used, with no restriction on learner access.

Two things. First, the module on your client’s LMS stops working: learners can no longer run that content. Second, its usage data enters a 30-day grace period during which it is kept but inaccessible. Restore the module within 30 days and your history comes back and the content resumes working. After 30 days, the data is permanently deleted.

Deleting a module should be a considered decision, particularly if the content is still in use. We recommend only deleting modules that have formally reached the end of their licence period, once the client has been told.

No. ModuleMinder captures only anonymised usage data. We record that a module was run, an anonymised session identifier and any scoring data generated. We never store names, email addresses or any other personally identifiable information about learners.

Yes. ModuleMinder is designed around data minimisation and privacy by design. We do not collect personal data and we do not share data with third parties. Full GDPR documentation is available on request, and organisations with specific compliance requirements, including public sector bodies, are welcome to contact us directly.

Because ModuleMinder only processes anonymised, non-personal data, the usual data controller obligations for personal data do not apply in the same way. We provide full documentation of our data architecture for any client, IT or legal team that needs to review it.

Some corporate LMS environments sit behind strict firewalls or Content Security Policies that restrict outbound connections. In those cases the client’s IT team will need to allow the ModuleMinder server address, which is a standard IT process. We provide a clean, documented URL and technical guidance to make it straightforward.

And as always: if the server cannot be reached, content plays by default.

Two plans are available today, Free and Pay per module. Four portfolio plans for larger catalogues are coming soon:

• Free: 1 active module, free forever, no credit card required
• Pay per module: £10 a month or £100 a year per module, reporting included
• Studio (coming soon): 30 active modules, £1,500 a year, reporting add-on £400 a year
• Agency (coming soon): 100 active modules, £3,500 a year, reporting add-on £1,500 a year
• Enterprise (coming soon): 300 active modules, £7,500 a year, reporting add-on £2,000 a year
• Unlimited (coming soon): unlimited active modules within fair use, £10,000 a year, reporting add-on £5,000 a year

Yes. Even if you only have one or two modules to protect, you get complete visibility of usage and scoring data as well as licence management, for £10 a month or £100 a year per module.

If you have sold a module to a client for £3,000, paying £100 a year to protect it, monitor its usage and receive independent performance data is just over 3% of the contract value.

For a studio with 30 modules representing £90,000 in annual content revenue, the Studio plan (coming soon) at £1,500 a year will be less than 2% of that revenue, for complete visibility and control across the whole portfolio.

The portfolio plans are coming soon. Once they launch: above 15 modules, Studio at £1,500 a year will be cheaper than paying £100 per module, with room for 30. Agency becomes better value at 35 modules, with capacity for 100. Above 100, Enterprise covers up to 300.

Until then, Pay per module covers any number of modules, with reporting included.

The reporting add-on comes with the portfolio plans, which are coming soon (Pay per module already includes reporting). When it launches, adding it mid-year will be charged pro rata for the remaining months, so your licence management and reporting fees renew on the same date. We will always confirm the amount before taking payment.

Yes. Upgrading is immediate and any additional fee is handled pro rata. Downgrading takes effect at your next renewal date.

Registering, generating your snippet and pasting it into a module takes around ten minutes. As we like to say: spend £10 and 10 minutes, and get protected content.

No. If you can paste text into your authoring tool, you can use ModuleMinder. ModuleMinder shows you exactly where the snippet goes in your tool, and handles everything after that. No development knowledge is required.

Start on the free plan. One module is protected forever, with no credit card and no trial period, so you can see your first module’s usage data before deciding anything else.