Before you sign
How to Hire a WordPress Plugin Developer: Questions to Ask, Answers to Trust, and Who Keeps the Code
The quote arrived by email, friendly and confident. Then the developer stopped answering, and the half-built plugin now sits on a laptop you will never see. This page is for choosing the next one, and it applies to us as much as anyone.
November 13, 2026 · 10 min read
one developer asked good questions, then sent a number with no written scope
The short answer
To hire a WordPress plugin developer, ask how they scope the job, how they price it, which WordPress coding and security practices they follow, how they test, and where the code will live. Get a fixed price for a written scope and a signed agreement that states who owns the code, because commissioned software is not automatically a work made for hire. Have your attorney review it.
On this page
- The quote that vanished, and the four lines it never had
- Ten questions for the first call, and the answers worth hearing
- Red flags that send a bill later
- Who holds the code, the repository and the keys
- A hiring process that fits on one page
- What an owner can check without reading a line of PHP
- Where DataCram fits, and when to hire someone else
The quote that vanished, and the four lines it never had
Picture the usual version. A freelancer quotes a plugin in two friendly paragraphs, takes a deposit, sends one screenshot, and goes quiet. When you finally ask for what exists so far, there is nothing to ask for: no repository, no staging site, no files in your name. The plugin was always going to be delivered at the end, in one piece, by someone you can no longer reach.
Look back at that quote and four things are missing. It had no written scope, so nobody could say what done meant. It named no place where the code would live while it was built. It said nothing about whose accounts the plugin would use. And it never mentioned who would own the result. Every question on this page exists to put those four lines in writing before money changes hands, whoever you hire.
Ten questions for the first call, and the answers worth hearing
| Ask | A good answer sounds like | A worrying answer sounds like |
|---|---|---|
| What will the plugin do, in your words? | Your job restated, plus questions about edge cases and what happens when a system is down | "No problem, easy" before a single question |
| How do you price it? | One fixed figure for a written scope | An open-ended hourly rate with no ceiling, or a price before hearing the job |
| Will you change WordPress core or another plugin's files? | No. The work goes in a separate plugin that uses hooks | "Just a small edit to the core files" |
| How do you handle form input and permissions? | Validation, sanitizing, escaping, nonces and capability checks, named without prompting | "WordPress takes care of security" |
| Theme or plugin? | A plugin, so it survives a theme change | "I'll drop it in functions.php" |
| How will you test it? | On a staging copy with my theme, plugins and versions | On the live site, late at night, when traffic is low |
| Where does the code live during the build? | In a repository I can see | On the developer's own computer until delivery |
| Whose accounts hold the API keys? | Mine, in my company's name | The developer's, "to keep things simple" |
| Who owns the code when it is done? | Whatever the signed agreement says, so let's put it in writing | "You paid for it, so it's yours" |
| What happens after launch? | A named maintenance arrangement with a written price | "It won't need anything" |
The third row is not a matter of style. WordPress.org's Plugin Developer Handbook, read November 11, 2026, calls it the "cardinal rule" and explains why: "WordPress overwrites core files with each update." The fifth row has its own page, plugins versus functions.php. The ninth row is where most owners are surprised, so it gets a section of its own below.
Red flags that send a bill later
Most bad hires announce themselves early, politely, in phrases that sound like reassurance. Listen for these:
- Asking for your main admin password by text or email, instead of a login of their own that you can switch off afterward.
- A promise that the plugin will be "100% secure" or will "never break." No honest developer can promise either, and WordPress's own security guidance lists among its first principles "Never assume anything."
- A "lifetime license" to the developer's own product as the solution, from a business with no visible history.
- Hosting the finished plugin only on the developer's server, where you have no access.
- A price, a deposit request and a start date before any question about how your business works.
- No business name, address or way to reach anyone but one person's phone.

One flag deserves context. A developer who works alone is not a problem in itself; plenty of good plugins have one author. The problem is a plugin that only one person can find, read or deploy. The questions about the repository and the accounts solve that, whoever writes the code. If the plugin you already have is failing and its author has gone, a fixed-price plugin repair is often the first step.
Who holds the code, the repository and the keys
Start with the legal part, because it surprises people. Under Circular 30, the U.S. Copyright Office's guide to works made for hire (revised 08/2024), only two routes exist. An employee makes the work as part of the job, or an outside creator makes a commissioned work of a type on the circular's list of nine, under a signed agreement that expressly calls it a work made for hire. A plugin is code, and code is absent from that list. Miss any requirement, the circular warns, and "it is not a work made for hire."
Ownership can still change hands, but only on paper. Section 204(a) of the Copyright Act, 17 U.S.C. 204, requires "an instrument of conveyance, or a note or memorandum of the transfer," signed by the rights holder "or such owner's duly authorized agent." We read that, without offering legal advice, to mean a freelancer's plugin becomes yours through a signed assignment, and paying the bill does not do it alone. The Copyright Office says it "cannot provide legal advice about the status of a work." Your attorney can.
The license is a different question from ownership. WordPress.org's license page states its view that plugins "inherit the GPL license," a position it holds while conceding a "legal grey area" over what counts as a derivative work. Leave that one to your attorney too. The practical questions are simpler: the code should sit in a repository your company can reach, and every account the plugin uses, from the CRM to the texting service, should be in your company's name with keys you control.
A hiring process that fits on one page
- 1
Write the job in one paragraph
What should happen, for whom, and what happens now instead. Add the systems involved and the plugins that touch the same job. This paragraph is the start of the scope.
- 2
Talk to two or three developers
Use the ten questions. Notice who asks you questions back. A developer who asks about edge cases now will not discover them on your invoice later.
- 3
Compare written scopes, not prices
A low price for a vague scope is not cheaper. Line the scopes up and see which one says what the plugin will and will not do. Our plugin pricing page explains what moves a fair price.
- 4
Check one sample of their work
You need not read code to ask how a past plugin was organized, how it was tested, and whether another developer has maintained it since.
- 5
Sign after your attorney reads it
Scope, price, ownership of the code, the repository and the accounts, all in one signed agreement. Then the work can start.
If, halfway through this process, every developer tells you the job needs half a dozen plugins glued together, take that seriously. The site may need rebuilding more than it needs another plugin. The free should I leave WordPress check and our page on replacing WordPress help you decide before you hire for the wrong project.
What an owner can check without reading a line of PHP
You can verify a surprising amount yourself. WordPress publishes the rules, and several of them leave visible traces in the dashboard or the plugin folder.
A proper header
The header requirements page lists fields such as Plugin Name, Version, Requires PHP and License. A plugin that shows a clear name, version and license on the Plugins screen was put together with care.
A clean exit
WordPress's uninstall guidance says the uninstall step removes options and tables. Ask the developer what deleting the plugin leaves behind. "Nothing" is the right answer.
A unique prefix
The handbook says global code should carry a prefix of four letters at minimum, and it recommends five. Ask what the plugin's prefix is. A developer who follows the handbook knows instantly.
Conflict testing you can watch
WordPress.org's Health Check & Troubleshooting plugin offers a clean session "only for your user." Its page, read November 11, 2026, warns it "hasn't been tested with the latest 3 major releases of WordPress," so try it on a staging copy.
For a broken site rather than a new hire, the WordPress repair hub and our walkthrough of a theme and plugin conflict walk through the usual causes. Security practices in more depth are on plugin security, and keeping the finished plugin current is on plugin maintenance.
Where DataCram fits, and when to hire someone else
We are one of the developers you could call, so hold us to every question above. DataCram has built websites since 1999 from San Antonio, Texas, and our clients across the country meet us by phone or video and follow the work on a shared project page; about DataCram has the rest. A custom plugin build starts at $575 as of November 2026, and the price for yours, set by its complexity, arrives as one written figure before anything is built. API connections, through our API integrations work, go live the same day.
Hire someone else, or no one, when a supported plugin on the market covers the job; our custom versus off-the-shelf page explains how to tell. After launch, hosting and maintenance runs from $55 a month. The custom WordPress plugins hub maps every page in this section, and the work page shows projects we have published. Or call (210) 346-0848 and ask us the ten questions directly.
Questions owners ask about custom WordPress plugins
Ask how they will scope and price the job, whether they will edit WordPress core or other plugins, how they handle form input and permissions, where they will test, where the code will live during the build, whose accounts will hold the API keys, who will own the code, and what happens after launch. Listen for whether they ask you questions back.
Not automatically, whatever the invoice says. Software is missing from the nine kinds of commissioned work that Circular 30, from the U.S. Copyright Office, says can be made for hire, and a copyright transfer needs a signed writing under federal law. So the answer lives in your agreement. Check that it names the owner of the code, and ask your own lawyer to read it first; we cannot give legal advice.
Give them their own login with only the access the job needs, never your main admin password, and remove it when the work ends. Most building and testing belongs on a staging copy, not the live site. Accounts the plugin uses, such as the CRM or texting service, should stay in your company's name.
Not in itself. Hourly work can be fair for small, open-ended tasks. For a defined plugin, ask for a fixed price for a written scope, or at least a written ceiling. An hourly rate with no scope and no limit leaves all the risk with you, and it rewards the slow parts of the job.
The plugin itself, with a header stating its name, version and license; the code in a repository your company can reach; a plain-language note on what it does and every setting it adds; and a list of the accounts it depends on, in your name. Who owns the code should already be settled in the signed agreement.
Check that it shows a clear name, version and license on the Plugins screen, ask what its unique prefix is, and ask what deleting it leaves behind in the database. Test it on a staging copy alongside your other plugins. A developer who follows WordPress's handbook can answer each of these questions immediately.
Keep reading
- Ownership, in writingWho Owns Custom WordPress Plugin Code: Copyright, Work for Hire and the GPL, in Plain EnglishWho owns a custom WordPress plugin: what the Copyright Office says about work for hire, the signed transfer the law requires, and WordPress.org's GPL view.
- The offer, step by stepCustom WordPress Plugin Development Services, From the First Question to the HandoverWordPress plugin development services: discovery, a fixed written estimate, handbook-standard code, testing on a staging copy and a clear handover.
- The money questionWhat a Custom WordPress Plugin Costs, and What the Plugins on the Shelf Charge InsteadCustom WordPress plugin cost: from $575 with a fixed estimate, what moves the price, and published Gravity Forms, WPForms and Bookly prices beside it.
- Connections, built inWordPress API Integration Plugins That Put Each Lead in Your CRM the Minute It ArrivesA custom plugin that sends WordPress forms and orders to your CRM, field software, email or texting through their APIs. Live the same day, from $575.
- WooCommerce, extendedCustom WooCommerce Extensions for the Store Rule Your Staff Still Enforces by HandCustom WooCommerce extensions for pricing rules, shipping limits and checkout fields, built HPOS-compatible on WooCommerce's own APIs. From $575.
- Blocks, made to fitCustom Gutenberg Blocks Your Editors Can Fill In and Cannot Knock Out of LineCustom WordPress blocks built on block.json, as the Block Editor Handbook describes: fields your team fills in, a design they cannot break. From $575.
- Everything in Custom WordPress PluginsSee the section
From the Insights desk
- Own the Building: Why a Custom Next.js Site Beats WordPress and WebflowWordPress and Webflow both rent you a website — you may decorate, you may not renovate. A custom Next.js build hands you the keys: complete customizability, a CMS shaped to your business instead of a builder's data model, and a site you actually own.
- Did AI Kill WordPress? A Data-Driven Analysis of Traffic, Plugins, and Market Share DeclineWordPress is not dead, but the platform is under structural pressure from AI, new site builders, and changing search behavior. A data-driven look at the signals.
Ask us the ten questions
Send the job in a paragraph and the plugins installed today. Someone at DataCram answers with answers to every question on this page, then a fixed written estimate, or a plain note that you should buy a plugin instead.
Which of these sounds like you? (pick any)
Rather talk now? Call (210) 346-0848.