Why choose Moodle?

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.

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.

Yes. Audit-only engagements cover performance, security, plugins, accessibility, GDPR and a clear improvement plan, with no obligation to hire the implementation.

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.

By default yes. I can sign your standard NDA or supply a GDPR / LOPDGDD-compliant template.

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.

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.

Both. I build complete CRMs on Laravel when the sales process does not fit an off-the-shelf tool — your own funnel, versioned quotes, staged payments, invoicing and dashboards — and I also configure, automate and maintain market CRMs such as Zoho CRM. Before any code is written I tell you straight which of the two routes pays off for you.

Yes. Full administration: modules and fields, roles and fine-grained permissions, email templates, sales targets, automations and workflows (in Zoho CRM, with Deluge), integrations with your ERP, your Moodle or your payment gateway, and data migration with deduplication if you are coming from another system.

It depends on the real scope, which is why I never quote a number before your sales process has been mapped. What is fixed is the method: a short scope document you approve before any code is written, a fixed fee per functional block, and deliveries you can use from month one instead of waiting months for a big launch. No per-user licences: you pay for the build, not a fee that grows with your team.

You do. The code lives in your repository, the data on your server or the hosting you choose, and you get documentation and credentials so another team could take over if you ever decide to. No lock-in, no proprietary licences, no minimum term — exactly the same criterion I apply with Moodle.

Yes, if you want. I install and configure Moodle or your application on your server, in the cloud or in Docker, with HTTPS, automated backups, cron, queues and a sensible firewall. I can also just hand over the deployment documentation so your team or your provider sets it up. What I do not do is resell you hosting: you contract it directly and the credentials are yours.

Both. Some engagements are fixed-fee with a delivery date; others are a monthly block of hours covering version upgrades, security patches, incidents and small improvements. When I hand a project over I tell you straight whether it genuinely needs maintenance or whether it can sit quietly for a few months.

Yes. Moodle supports SCORM 1.2/2004, H5P (in core since 3.9) and xAPI out of the box, and I work with all three: importing existing packages, diagnosing content that fails to report grades or completion properly, building interactive content with H5P, and sending xAPI statements to an external LRS when you need analytics beyond Moodle.