Skip to content
Updated yesterday

← Can you vibe-code it?

Can You Vibe-Code MemberPress?

Not really Medium confidence

Real-world usage 21.2K+ live sites #60 by usage View plugin details →
from $179/yr What it costs
A few weekends To get an MVP working
~14 h/yr To keep it alive, forever
36% Of it is just code

What you’re actually buying

36% code you could commission 64% somebody running something

You could build: Paywalled content rules, membership levels, a signup flow and a Stripe subscription behind them. The happy path is genuinely a couple of weekends.

What you’d still be missing: Everything that happens when the happy path fails: dunning and failed-payment retries, proration on upgrades, cancellations and refunds, EU VAT and US sales tax, plus the gateway and CRM matrix. This is somebody's recurring revenue, and the edge cases are where it leaks.

Integrations Compliance Maintenance Support

Is it worth building?

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

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

9 sites — break even +$1,722/yr $0 -$1,321/yr 1 9 18 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 $750 $350 5
$50/hr $1,500 $700 9
$100/hr $3,000 $1,400 17
$150/hr $4,500 $2,100 26

Year one only, and it assumes the 64% 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 MemberPress. I want a working first version I can install and test, not a scaffold.

Requirements:
- Membership levels with content-access rules by post, category and taxonomy
- Recurring billing with at least one gateway, including dunning and retries
- Upgrade/downgrade with proration and cancellation handling
- Tax handling for the jurisdictions you actually sell into
- Member account area: invoices, payment method, subscription state

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 from $179/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.