Hiring a Moodle developer in 2026: rates, red flags, what to ask
There is no clean market rate for Moodle developers. What the numbers that exist say, where to find people, the red flags in a quote and ten questions to ask before you pay.
Most Moodle sites need a developer at some point. Usually for a small job: a report the core can’t produce, a plugin that broke on upgrade, an integration with the student system. And most site owners hire one so rarely that they don’t know what a fair price is, what good work looks like, or how to tell before paying.
This is the guide we would want if we were on the other side of the table. We sell Moodle development, so read it with that in mind. Everything checkable is linked.
What does a Moodle developer cost?
Short answer: nobody publishes a reliable number, because the market is too small.
The best public data on contract rates in the UK is ITJobsWatch, which tracks rates quoted in job adverts. In the six months to 4 November 2026 it found two contract adverts for “Moodle Developer” in the whole UK, and not one with a daily rate, so it couldn’t calculate a median. In the same period of 2024 there were eight adverts, and the seven with rates had a median of £365 a day.1 For comparison, the median for all UK IT contracts in the last six months was £525 a day.1
Elsewhere the numbers are just as thin:
| Source | What it says | How much to trust it |
|---|---|---|
| ITJobsWatch, UK, 2024 | £365 a day median, Moodle Developer contracts | 7 data points |
| ITJobsWatch, UK, 2026 | £525 a day median, all IT contracts | Large sample, not Moodle |
| Flexiple, India, August 2026 | About $8 an hour for a mid-level Moodle developer | Modelled from salaries, not real invoices2 |
| Upwork, 2026 | $10 to $25 an hour for beginners, any skill | General guide, no Moodle figure3 |
So the honest range runs from under $10 an hour to over $70, and the hourly rate tells you little on its own. A developer at $15 an hour who needs 80 hours and leaves no tests costs more than one at $60 who needs 15. What you want to compare is the total price for a written scope, and what you get at the end of it.
Where do you find one?
- Moodle Partners. Certified by Moodle HQ, usually also hosting and support companies. Good for large projects and long contracts. Slower and more expensive for a single plugin.
- The Moodle Marketplace. Look at who maintains plugins close to what you need. A developer whose code is public and reviewed is easier to judge than any CV. (The Marketplace replaced the old plugins directory this year; what changed.)
- Freelance platforms. Upwork, Freelancer, Malt. Lots of choice, very uneven quality, and you do all the checking.
- Moodle forums and Moodle Academy. Developers who answer hard questions in the developer forum usually know the code.
- Fixed-price shops, like us. You get a price for a scope rather than a rate. More on that trade-off below.
Red flags in a quote
These are the patterns we see when clients bring us a half-finished project.
- No written scope. “We’ll build the plugin” is not a scope. If the quote doesn’t list what the plugin does, which Moodle versions it supports and what “done” means, you will argue about it later.
- Core changes. Any plan that edits Moodle’s own files, instead of a plugin, makes every future upgrade painful. Moodle can do almost everything through plugins, hooks and events. Ask the question directly.
- No tests. Moodle has PHPUnit and Behat built in, and
moodle-plugin-ciruns the same checks the Marketplace uses. A developer who doesn’t use them is guessing that the code works. More in testing Moodle plugins in the AI era. - No privacy provider. Every plugin needs one, even if it stores nothing, and the Marketplace blocks plugins without it. It is also how Moodle handles GDPR requests.
- You don’t get the repository. Moodle plugins are GPL. You should get the full Git history, not a zip.
- “We support all versions.” Nobody tests on every Moodle version. A good answer names them, for example 4.5 to 5.1, and says what happens when 5.2 comes out.
- Hourly with no cap. Fine for open-ended support, risky for a defined job.
Ten questions to ask before you pay
- Which Moodle and PHP versions will you test on?
- Will any of this change Moodle core? (The answer should be no.)
- Which Moodle APIs will it use? (Events, hooks, the web service layer, the task API. A specific answer means they have thought about it.)
- What tests will be included, and do they run in CI?
- Does it pass
moodle-plugin-ciwith no errors? - Who owns the code, and do I get the Git repository?
- What happens if it breaks on the next Moodle upgrade?
- How long do you fix bugs for free after delivery?
- Can I see a plugin you have published or open sourced?
- Is the price fixed, and what would make it change?
Question 9 matters most. Code is the only CV that doesn’t lie. Ours is Autoflow, an open source workflow plugin with every test report public.
Fixed price or hourly?
Hourly works when you can’t define the work in advance: ongoing support, investigating a slow site, a long project where the plan will change. You carry the risk that it takes longer.
Fixed price works when the job can be written down: a plugin, an integration, an upgrade of known code. The developer carries the risk, so they will spend time on the scope before quoting. That is a good thing. If a developer won’t give a fixed price for a well-defined plugin, they either don’t understand it yet or don’t trust their own estimate.
Either way, ask for a small paid first step if the job is large: a written specification, or one feature finished and tested. It costs little and tells you more than any interview.
What about AI?
In 2026, most developers use AI tools, and you should expect it. It makes routine Moodle code much faster to write. It doesn’t make it correct. The questions above are the same whether the code was typed by a person or an agent, and tests matter more, not less. We wrote up how AI changes Moodle development in detail.
What AI has changed is price. A plugin that took two weeks in 2022 can take two or three days now, if the person driving the tools knows Moodle. If a quote looks like it was priced in 2022, ask why.
The short version
Don’t compare rates. Compare a written scope, a fixed total, tests, the repository and a public example of the developer’s work. If you want to see what that looks like for your job, describe it here and get a fixed price in a few minutes.
Sources
-
ITJobsWatch, Moodle Developer contracts, UK, six months to 4 November 2026 and the same periods in 2025 and 2024. ↑ ↑
-
Flexiple, Moodle developer salaries and rates, updated August 2026. Modelled from 329 Indian salary records. ↑
-
Upwork, Upwork hourly rates by skill and experience, 2026. ↑
Need a Moodle plugin built or rescued?
Tell the scoping assistant what you need. You get a fixed price and a timeline in a few minutes, and an engineer reviews it within one business day.
Get a fixed quote