Skip to content
Updated today

← Can you vibe-code it?

Can You Vibe-Code Easy Digital Downloads?

Not really Medium confidence

Real-world usage 38.5K+ live sites #54 by usage View plugin details →
Pro from $99/yr What it costs
A few weekends To get an MVP working
~12 h/yr To keep it alive, forever
34% Of it is just code

What you’re actually buying

34% code you could commission 66% somebody running something

You could build: A downloadable product type, a cart, a Stripe checkout and a signed expiring download link. The store works by the end of the weekend.

What you’d still be missing: Then the actual business arrives: software licensing with activation limits, recurring payments and their failure modes, EU VAT determined by customer location, refunds, and a gateway matrix. EDD's own add-on catalogue is the honest map of what you would end up rebuilding.

Integrations Compliance Maintenance Support

Is it worth building?

About 16 hours to get a working version (a few weekends), then roughly 12 hours a year keeping it alive. So year one is about 28 hours of your time — both figures assume you’re using an agent for the maintenance too, not just the build.

Against $99 a year for the licence. At $50/hour that’s $1,400 of your time in year one — so it pays off once you run it on about 15 sites, because the licence is per site and your build isn’t.

15 sites — break even +$1,570/yr $0 -$1,301/yr 1 15 30 sites you'd run it on (maintenance at $50/hr)
If your time is worth Year one Each year after Sites to break even
$25/hr $700 $300 8
$50/hr $1,400 $600 15
$100/hr $2,800 $1,200 29
$150/hr $4,200 $1,800 43

Year one only, and it assumes the 66% above is worth nothing to you. That is the assumption most likely to be wrong — read the “still missing” line again before you decide.

The prompt

A starting point, not a magic spell. Expect to iterate — and to be told what it skipped.

Starter prompt
Build a self-contained WordPress plugin that covers the core of Easy Digital Downloads. I want a working first version I can install and test, not a scaffold.

Requirements:
- Digital product type with variable pricing and secure expiring downloads
- Checkout with at least one gateway, plus refunds and receipts
- Recurring payments including retries and cancellation
- Software licence keys with activation limits and remote validation
- Tax handled for the jurisdictions you sell into, EU VAT included

Constraints:
- Plain PHP against the WordPress APIs. No build step, no framework, no Composer runtime dependencies.
- Follow WordPress coding standards. Prefix every global function, class and option.
- Escape on output, sanitise on input, nonce + capability check every write. Prepare every SQL query.
- Translation-ready with a single text domain.
- Uninstall routine that removes options and tables it created.
- Target the current WordPress and PHP 8.1+.

Deliver: the plugin files, a short README covering setup and limitations, and an explicit list of what you did NOT implement.

Context for scope: the paid product is Pro from $99/yr. Do not try to match it feature for feature — build the part I would actually use, and tell me where the gap is.

Don’t feel like building it?

Free or open-source, finished, and already doing the job.

0 people say they built this instead

Self-reported and unverified — one tap per person, roughly. Treat it as a mood ring, not a statistic.

Why this list exists

“Can I just vibe-code this?” has become a reasonable question to ask before renewing a licence. For most SaaS the answer is a straight yes or no. For WordPress plugins it usually isn’t, because a premium licence is rarely paying for source code alone.

Ask an agent for a security plugin and you’ll get a firewall and a file scanner in an afternoon. What you won’t get is the rule that shipped this morning for the vulnerability disclosed last night — that’s a research team, and it’s the entire reason the product works. Ask for a caching plugin and you’ll get page caching, minification and lazy-loading. What you won’t get is the eight years of exclusion rules that stop it breaking somebody’s checkout.

So instead of a verdict, every plugin above is split in two: the share an agent could plausibly build for you, and the share that only exists because a vendor is running something on an ongoing basis — a live data feed, servers doing the work, a legal review, or an integration matrix kept alive against other companies’ breaking changes.

How to read the score

The percentage is the answer to one question: what would you still be missing the day after the agent finished? A low score means the product really is mostly code, and building it yourself is a fair trade. A high score means you’d finish the build and still need to buy the thing that made it useful.

The baseline is one competent developer with a good agent and a couple of weekends — not a team, and not a year. Scores are editorial judgement rather than measurement, and they’re deliberately arguable. If you think a call is wrong, that’s the interesting conversation.

Ranking, prices and live-site counts come from the same daily data as the rest of the site — see the premium plugin ranking for how those are gathered.