What you’re actually buying
You could build: Custom checkout templates, order bumps and a one-click upsell step after payment. Mechanically it is a flow of WooCommerce pages you control.
What you’d still be missing: One-click upsells mean charging a saved payment method after the order completes, which each gateway supports differently and some barely support at all. Plus the template library and keeping step templates working against every builder.
Is it worth building?
The prompt
Build a self-contained WordPress plugin that covers the core of CartFlows. I want a working first version I can install and test, not a scaffold. Requirements: - Multi-step flows with checkout, upsell and thank-you pages - Order bumps rendered and priced correctly at checkout - Post-purchase charges against the stored payment method, per gateway - Conversion tracking per step so the funnel can be read - A starting template library across the common page builders 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 a commercial plugin. 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?
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.