Custom Moodle plugins
I build Moodle plugins from scratch — local, block, activity, enrolment, repository, course format, theme and report — following the official coding style and publishable to moodle.org on request.
Always start with a short spec doc: use case, edge cases, visual mock, data model, privacy-provider + hook decisions. You approve before any code is written.
Built on a separate branch with PHPUnit tests and Behat where it makes sense. Keeps compatibility with the two latest LTS branches; supported versions explicitly declared.
Delivery: source code, README, CHANGELOG, install plan, screenshots, manual test plan, maintenance policy.
Published plugins so far: local_ioe (Moodle ↔ Zoho CRM), block_course_recommender (tag-based recommendations).
Tell me what plugin you need. Fixed-fee proposals start at €500.
Frequently asked questions
How much does a custom Moodle plugin cost? ＋
Custom plugins start at €500. The final price depends on scope: number of screens, external API integrations, automated test requirements and the maintenance policy you want. You get a fixed-fee proposal within 24 hours of a brief or discovery call.
Do you work with Moodle 4 and Moodle 5? ＋
Yes. I keep plugins compatible with both branches and plan migrations from 3.x to 4.x and from 4.x to 5.x. Audit-only migration reports are available if you just need the report.
Can you audit my Moodle and only deliver the report? ＋
Yes. Audit-only engagements cover performance, security, plugins, accessibility, GDPR and a clear improvement plan, with no obligation to hire the implementation.
Do you work with clients outside Spain? ＋
Yes. I invoice in EUR and USD, sign international contracts and work CET / GMT hours. I have shipped projects with clients in Colombia, Mexico, the United States and across the EU.
Will you sign an NDA? ＋
By default yes. I can sign your standard NDA or supply a GDPR / LOPDGDD-compliant template.
Do you publish my plugin on moodle.org? ＋
Only if you authorise it and the scope is generic (not specific to your organisation). When we do, it is explicit in the contract and you keep all brand and configuration rights.
How do you handle WCAG accessibility? ＋
Every new plugin ships with a WCAG 2.1 level AA checklist covered: contrast, keyboard navigation, visible focus, alt text, HTML semantics, screen-reader compatibility and prefers-reduced-motion support.