To vet a LearnDash developer, ask for work on a live LearnDash site with paying students, check that they build on a staging copy with version control, and start with a small paid project before the big one. Walk away from anyone who edits LearnDash's plugin files, works on your live site, or won't put code ownership in writing. Cost depends on scope and how the work is billed, so compare quotes by what each one delivers. The hourly rate tells you little.
We do LearnDash development: gamification, custom reporting dashboards and multi-instructor setups built for clients. If you have already decided to hire a LearnDash developer, that page covers what we take on. This guide is for the step before: telling a good developer from a convincing one, whoever you end up choosing.
What to ask a LearnDash developer, and what a good answer sounds like
Ask for proof of live LearnDash work, a staging workflow, a written test plan and code ownership in writing, using the eight questions below in the first conversation. The polish of the answer matters less than the specifics. Someone who has built on LearnDash names real features and the ways they fail. Someone who hasn't talks in generalities.
| Question | A good answer sounds like | A weak answer sounds like |
|---|---|---|
| Which live LearnDash sites with paying students have you built or maintained, and can I talk to one of those clients? | Describes the sites (size, what they built, what broke), offers a reference, and explains what is under NDA. | Shows demo sites, mockups or courses that never launched. |
| How would you build this using LearnDash's own hooks or REST API? | Names the events they would hook into, such as enrollment, course completion or quiz submission. LearnDash documents learndash_course_completed, for example. | “There's a plugin for that,” for every request. |
| Where do you build and test before anything touches the live site? | A staging copy with a recent copy of your data, and changes deployed from version control. | Edits on the live site “at night, when it's quiet.” |
| How will you test enrollment, completion, quizzes, groups and payments? | A written checklist, test accounts for each user role, and a real small purchase through your payment gateway. | “I'll click around and make sure it works.” |
| What happens when many members are logged in at once? | Asks for your busiest hour, mentions load testing, and knows logged-in pages can't be cached like public ones. | “That's a hosting issue.” |
| What does our LearnDash plan already include? | Checks LearnDash's current plan features and what is already installed on your site before proposing custom work. Also asks whether your renewal falls under the Nexcess plugin stack change that starts November 16, 2026, which can change what the plan includes (see LearnDash pricing). | Quotes a custom build without checking whether your license already covers it. |
| Who owns the code, and who can reach the repository after we finish? | You do, stated in the contract, with the repository in your account or handed over at the end. | Vague, or “the code stays on my server.” |
| What happens when LearnDash or WordPress updates next quarter? | A plan: update on staging first, run the regression tests, say who does it and whether it is a separate paid line. | “It should be fine,” or “that's after the project.” |
If your community layer runs on BuddyBoss, add a ninth question about how they handle the BuddyBoss and LearnDash integration, because an update can break either plugin or the connection between them.
Red flags that are specific to LearnDash
A developer who edits LearnDash's plugin files, or does any of the other five things below, should stop the process until it is fixed.
- They edit LearnDash's plugin files, or a bundled copy of them. The next plugin update overwrites the change, and you find out when a course breaks. Custom work belongs in a separate plugin or a child theme, using hooks and filters.
- They work directly on your live site. Orders, enrollments and course progress are written all day. A mistake on production reaches paying students.
- “There's a plugin for that” is the answer to everything. Every extra plugin is one more thing that can conflict at update time.
- They haven't tested a payment from start to finish. Enrollment on payment depends on the gateway sending a confirmation to your site. Ask how they verified it end to end, ideally with a real small purchase.
- Their references are designs, demos or courses that never launched, not live sites with paying students.
- They won't put scope, price and code ownership in writing. A developer who is vague on paper will be vague when something breaks.
Run a paid test project before the real one
A conversation can't show you how someone communicates when something goes wrong, so give them a small piece of real work first.
- Pick one small, real task: a reporting tweak, an enrollment rule, a bug that has been annoying you. A few hours of work, not weeks.
- Write the acceptance test before they start: what you will click, and what you should see.
- Pay for it at their normal rate. Unpaid trials mostly filter for people with free time.
- Require delivery on a staging copy, with the code in version control.
- Review how they worked as well as what they delivered. Did they ask questions you hadn't thought of? Did the test pass the first time? Did they tell you plainly what they didn't finish?
- Scope the larger project using what you learned, including how long things took against what they estimated.
Where to look for a LearnDash developer today
Don't count on an official directory, and check every claim yourself. LearnDash's old experts page, learndash.com/experts, redirects to the LearnDash product page on Liquid Web as of October 2026. An archived copy from November 2025 shows the directory page was live then. We can't tell you what happened to the program, so ask LearnDash for its current status.
Check the wording, too. LearnDash's Community Expert program rules say Community Experts are prohibited from representing themselves as LearnDash employees or “official partners” unless specified in a separate agreement. If a pitch says “official LearnDash expert,” ask what that means and for the evidence. That applies to us as much as anyone.
| Where | What it is | What to watch |
|---|---|---|
| Upwork | An open freelancer marketplace. Upwork's LearnDash page says rates vary with expertise, location and market conditions. | Quality ranges widely, so run every question above on each candidate. |
| Codeable | A WordPress marketplace that describes its experts as pre-vetted. | Pre-vetted is the marketplace's own description, so put the LearnDash questions to each candidate. |
| LearnExus | A talent marketplace that describes its talent as instructional designers, e-learning developers and LMS architects. | It isn't a LearnDash directory. Confirm they build on WordPress and LearnDash specifically. |
| A specialist agency | A team with several people behind the work. | Ask who does the work, and whether the person you meet is the person you get. |
| Referrals from similar sites | Owners of LearnDash sites like yours who have worked with someone. | A referral is only as good as the site behind it, so run the same questions. |
What a LearnDash developer costs and how to read the quote
We found no reliable published price range for LearnDash work, and the reason is plain: the work runs from small fixes to long builds. Budget by how the quote is built, and treat any single “average cost” figure with suspicion.
Codeable does publish its model. As of October 2026, its pricing page says its recommended rates range USD $80 to $120 per hour, lists a 17.5% fixed service fee, and says you deposit the project cost into escrow before the work starts. Those are Codeable's numbers for Codeable's process, not a market rate. Upwork's LearnDash page gives no rate guidance. It says rates vary with expertise, location and market conditions, and that an experienced specialist may charge more but work faster and deliver a higher-quality product. Take that last point seriously: a low hourly rate can cost more once the rework starts.
The engagement type changes what you should look for in the quote:
| Engagement | When it fits | How to read the quote | Red flag |
|---|---|---|---|
| Fixed price per deliverable | A defined feature, such as a reporting dashboard or an enrollment rule | Look for scope, exclusions, acceptance tests and a change-request process. | A single lump sum with no list of what is included. |
| Hourly | Investigation, bug fixing, work you can't scope yet | Ask for an estimate range, a weekly cap and a report of hours against tasks. | No cap and no breakdown. |
| Monthly retainer | Updates, regression tests and ongoing small changes | Ask what the hours cover, whether unused hours expire, and who is on the other end. | Hours that disappear into “maintenance” without a list. |
| Employee | Steady, daily LearnDash work | Ask how you cover a vacation, a departure and a skill gap. | A single person who is the only one who knows the setup. |
Whatever the model, a good quote lists the deliverables, what is not included, how each piece will be tested, that the work is delivered on staging first, who owns the code, and what happens after launch. If any of those are missing, ask for them before you compare prices.
Three costs that are easy to miss: the time it takes to test properly, the license and add-on renewals the build depends on, and the ongoing update work after launch. Nexcess says individual plugin subscriptions, LearnDash included, are being retired as licenses renew, and subscriptions it is converting move into its plugin stack at renewals from November 16, 2026 (unlimited-site and lifetime licenses are exempt; your renewal notice confirms yours), so budget from your renewal notice (details). Ask for all three up front.
After launch: who owns it and who updates it
Budget for maintaining custom LearnDash work after launch. Settle four things before you sign:
- Ownership: the code is yours, in the contract, and you have access to the repository.
- Documentation: a short written description of what was customized and why, so a different developer can pick it up.
- Updates: who runs LearnDash and WordPress updates, on staging first, with the checkout and enrollment tests rerun. Both products keep releasing updates, and custom code has to survive them.
- Continuity: what happens if your developer leaves, and how fast someone else can take over.
What we see on real sites
A feature that works in a demo can still fail on a live site for ordinary reasons. When enrollment breaks, a good developer starts with the cheap checks. They look for two caching layers fighting each other. They check that the payment gateway's confirmation reaches your site, for example with Stripe's webhook test button. They switch on a troubleshooting mode that disables plugins for their session only, turn back on just the ones checkout needs, then make a real small purchase to see it end to end. If a candidate's first move is to rewrite code, ask why.
Two client projects show why some of these checks are on the list.
- On enrollment automation for Realtime Voice Training, 71 enrollments in one month were processed automatically. Each one used to take 15 to 20 minutes by hand. Question 4, the test plan, exists to protect an enrollment path like that.
- On a client project for Head for Change, a pre-launch audit cut the plugins from 27 to 18 in 13 developer hours. The write-up is in our plugin audit case study. It is why “there's a plugin for that” is on the red-flag list.
A scorecard for the candidate in front of you
The scorecard turns everything above into a number you can compare between candidates. Tick only what they have shown or put in writing. Items carry 1 to 3 points, 20 in total.
Evidence of experience (points in brackets):
- Work on a live LearnDash site with paying students, and a reference you could call (3)
- Builds and tests on a staging copy, and explained how changes reach your live site (2)
- Uses version control, and agreed in writing that you own the code and can reach the repository (2)
- Named the LearnDash hooks, filters or REST API they would use for your feature (2)
- Gave a written test plan covering enrollment, completion, quizzes, groups, payments and user roles (2)
- Has a plan for LearnDash and WordPress updates after launch, including regression tests and who runs them (2)
- Load tests, or asked how many members are logged in at your busiest hour (2)
- Checked what your LearnDash plan already includes before quoting custom work (2)
- Scoped in writing: deliverables, exclusions, acceptance tests and how change requests work (2)
- Agreed to a small paid test project before the full build (1)
Red flags, any one of which pauses the process until it is resolved in writing: editing LearnDash plugin files, working on the live site, “there's a plugin for that” for everything, no end-to-end payment test, only demo sites to show, and refusing to put scope, price and ownership in writing.
How to read the score: 16 to 20 is strong evidence, and you can move to a paid test project if no red flag is open. 11 to 15 is promising with gaps, so close the gaps first. 10 or below means you don't have enough evidence yet, and no money should move.
LearnDash developer vetting scorecard
Tick what this candidate has actually shown you or put in writing, not what they said they could do. Nothing you tick leaves this page.
Frequently asked questions
How do I know a LearnDash developer is actually experienced?
Ask for a live LearnDash site with paying students and a reference you can call, then ask how they would build your feature with LearnDash's hooks or REST API. Experienced developers answer with specifics, including what went wrong on past projects.
Should I pay for a test project?
Yes. A few hours of paid work on something real shows how they communicate, test and document, and it costs far less than finding out on the full build.
Is a "LearnDash expert" badge or listing proof of quality?
No. LearnDash's Community Expert rules bar experts from calling themselves official partners without a separate agreement, and the public experts page now redirects to the product page. Treat any "expert" label as a claim to check.
Should I hire a freelancer or an agency?
A freelancer is usually simpler and has one person accountable. An agency gives you continuity if that person is sick or leaves. What decides it is whether you can survive losing the one person who knows your setup.
Next step
If you are ready to hire a LearnDash developer, tell us about your project and we'll give you a straight answer. If you aren't ready for that, our free membership site audit is an outside-in first look; it can't see logins, billing or anything behind the paywall.