WooCommerce Devs Aren’t Marketers, and That’s the Problem  🔗 **Source:** [WooCommerce Devs Aren’t Marketers, and That’s the Problem](https://www.businessbloomer.com/woocommerce-devs-arent-marketers-and-thats-the-problem/) > [!note]+ Document Notes > tags: [woocommerce, plugin-business, commitment-devices, developer-marketing, ai-commoditisation] > author: Rodolfo Melogli > source: Business Bloomer > reference: https://savetheplugin.com/ > date created: 2026-09-25 > > > [!info] Generated analysis — not the author's words. Sections below are machine-written > > from the captured source. Only text inside `> [!quote]` blocks is verbatim from the author. > > Do not quote or attribute any other line to the named author. > <!-- deep-read:sections start --> ## 🏷️ Title **"WooCommerce Devs Aren't Marketers, and That's the Problem"** — Rodolfo Melogli, Business Bloomer, September 2026. Roughly 690 words. An argument that AI has moved the bottleneck in the plugin business from building to selling, followed by the launch of a paid 30-day marketing sprint that the author is selling. Sprint begins Monday 5 October 2026. **Read it as two documents at once.** The diagnosis is genuine, experienced and largely correct. The prescription is a product the author sells, at $297 rising to $397. Both halves deserve to be taken seriously; neither should be read as if the other were absent. ## 🧭 Table of Contents 1. [References (in-page)](#-references-in-page) 2. [Summary](#-summary) 3. [Main Content](#-main-content) → [Notes](#️-notes) 4. [References](#-references) 5. [Paraphrase](#️-paraphrase) 6. [Newsletter](#-newsletter) 7. [Action Items](#-action-items) 8. [Hypotheses](#-hypotheses) 9. [Methodology](#-methodology) 10. [Questions](#-questions) 11. [Future Research](#-future-research) 12. [Implications](#-implications) 13. [Learning Styles Assessment](#-learning-styles-assessment) 14. [Accessibility Assessment](#-accessibility-assessment) 15. [DEIB Assessment](#-deib-assessment) 16. [Logical Validity](#-logical-validity) 17. [DARVO Analysis](#️-darvo-analysis) 18. [Conclusion](#-conclusion) 19. [Refactor Appendix](#-refactor-appendix) ## 🔗 References (in-page) The markup was enumerated before any sourcing claim was made. Seven link positions, one image. **Third-party (one):** 1. [stepbet.com](https://www.stepbet.com/) — the commitment-device app offered as the argument's only external evidence. This is the single link in the piece that points at something the author does not own or benefit from. **The product being sold (four positions, one destination):** 2–5. [savetheplugin.com](https://savetheplugin.com/) — linked at the product introduction, again on the screenshot image, and twice more in the closing paragraphs. **The author's own properties, as reward inventory (three):** 6. [wcwkly.com/sponsors](https://wcwkly.com/sponsors/) — newsletter sponsorships. 7. [businessbloomer.com/club](https://www.businessbloomer.com/club/) — the author's membership community. 8. [checkoutsummit.com](https://checkoutsummit.com/) — conference ticket. **Image (one):** a screenshot of the Save The Plugin website, hosted on businessbloomer.com and hyperlinked to the product. No alt text in the capture — the alt brackets are empty. **Sourcing assessment.** This piece is well-linked and almost entirely self-referential. Seven of eight link positions point to the product or to properties in the author's orbit; exactly one points outward, to StepBet, and that one carries the entire evidential weight of the central analogy. Calling the article "uncited" would be wrong — it links freely and places its links precisely. What it lacks is *independent* evidence: no research on commitment devices, no data on plugin marketing outcomes, no third-party source for the claim that free courses fail. The one external link is to a commercial product, not to a study. ## 📝 Summary **What happened.** Rodolfo Melogli argues that AI has collapsed the cost of building WooCommerce plugins, leaving marketing as the only remaining bottleneck — and that most developers fail at marketing not through incapacity but through absent motivation, because marketing has no deadlines, no error messages and nothing that visibly breaks when skipped. He reports that free advice and free courses have not fixed this, citing near-zero completion rates from his own giveaways. He then launches Save The Plugin: 20 marketing tasks over 30 days, five released each Monday, run personally in a private Slack, $297 for the first ten seats and $397 thereafter, with a sponsor-donated reward worth $400–$500 for anyone who completes all 20 tasks inside the window. Six seats remained at time of writing. The sprint starts Monday 5 October 2026. **Why it matters.** The diagnosis is the valuable part and it generalises past WooCommerce. When a bottleneck is removed — here, building — the constraint moves to whatever was previously hidden behind it, and the people who were selected for skill at the old bottleneck are rarely selected for skill at the new one. That is a structural claim about what AI does to any craft-based small business, and it is stated more clearly here than in most commentary that addresses it directly. **Stakeholders.** Premium WooCommerce plugin developers with existing paying customers, who are the explicitly named audience; the author, who sells the remedy; the sponsors donating reward inventory; and, more broadly, every solo maker in the WordPress economy facing the same shift. **Risks.** The author sells the solution to the problem he diagnoses, which does not make the diagnosis wrong but does mean no independent source confirms any part of it. The evidence base is one commercial analogy and one unquantified personal observation. The scarcity signals — six seats, price rising — are unverifiable by construction. And the commitment mechanism the article invokes to justify its design is not quite the mechanism the product implements; see **Logical Validity**. **Bottom line.** A sharp, honest, well-written piece of reasoning attached to a sales page, by someone who says plainly that he is also the customer. Take the diagnosis seriously. Evaluate the product on its own terms. ## 📖 Main Content **The core argument is a bottleneck-migration claim, and it is the best thing in the piece.** > [!quote] > AI has made shipping a WooCommerce plugin easier than it's ever been. Which means the part that was always the hard part, **actually getting people to buy it, is now the only part left standing**. That is the whole thesis in two sentences. Building was never the *hard* part in commercial terms — it was merely the *binding* part, the step that consumed the available time. Remove it and the previously-hidden constraint becomes visible. The author develops this properly rather than asserting it: *"Scaffolding, boilerplate, entire features that used to take a week now happen in minutes. Building used to be the bottleneck."* And then the inference: *"What's left exposed, now that building is cheap, is marketing."* **The second argument — that the obstacle is motivation, not capability — is more contestable and better supported.** The support is structural rather than anecdotal, which is what makes it good: > [!quote] > Building has deadlines, error messages, and a working feature at the end to prove you did something. Marketing has none of that built-in structure. Nothing breaks if you skip the blog post. Nothing crashes if you never send the outreach email. This is a genuinely useful observation. Software development supplies its own forcing function: the compiler objects, the test fails, the feature either works or does not. Marketing supplies none, so it is *always* safe to defer, and the safety of deferral is precisely what guarantees indefinite deferral. The author has the causal direction right, and he does not overreach — he explicitly allows that *"some genuinely are"* bad at marketing while maintaining that most are capable and simply do not get to it. **The commitment-device argument is where the reasoning gets thinner.** The gym analogy is asserted flatly — *"If you got free access to the gym, you still wouldn't work out. Free doesn't create commitment"* — and then supported by a single example, StepBet, described accurately: pay an entry fee, hit your step goals, get your stake back plus a share of what those who missed forfeited. The author's gloss is correct as a description of StepBet: *"Miss your own goals, and you lose your stake."* But the product he builds does not work that way, and the difference is not cosmetic. Under Save The Plugin, the $297 is spent either way; completion earns an *additional* reward worth $400–$500. The author states this plainly — *"Don't finish, and you keep everything you shipped and posted, you just don't get the reward!"* — so nothing is concealed. Economically the two designs rhyme: finish and you come out ahead, fail and you are down. But the *psychological* mechanism the article names as the active ingredient is loss of stake, and what ships is forgone gain. Those are the two sides of the loss-aversion literature, and the entire reason commitment devices use the first is that it is the stronger lever. The article cites the mechanism it does not implement. **The product structure is coherent and the numbers check out.** Twenty tasks, five each Monday, means four release dates — 5, 12, 19 and 26 October — with the final batch landing nine days before the 30-day window closes on 4 November. That leaves real time to finish the last five, which is sound design. The named tasks are concrete and recognisably the right ones: *"Auditing your product page. Running a flash sale. Reaching out to your own users."* Access to the author in a private Slack is the differentiator over the free courses he says failed. **The commercial framing is conventional and mildly aggressive.** A price ladder ($297 for the first ten, $397 after), a live scarcity count (*"six are left as I'm writing this"*), a named start date, and a tight audience qualifier: *"If you run a premium WooCommerce plugin with real paying customers."* That last one is the most honest sentence in the sales half — it actively excludes people for whom the product would not work, which most sales pages will not do. **The disclosure is real and lightly made.** *"I'm into it as well, because I NEED to get that marketing work done too!"* The author names himself as subject to the problem, and earlier includes himself in the diagnosis — *"Most WooCommerce developers (including me!)"*. That is not a formal conflict-of-interest statement, but it is not nothing, and it sets the register: this is a peer selling to peers, not an expert selling to novices. ### 🗒️ Notes - **The bottleneck-migration claim is the transferable idea** and it has nothing to do with WooCommerce. Any craft business where AI reduces production cost will find its constraint relocating to distribution, and the practitioners were selected for production skill. - **"Nothing breaks if you skip the blog post"** is the sharpest line in the article and the most useful diagnostic. The absence of a forcing function, not the absence of ability, explains the pattern. - **The cited mechanism and the shipped mechanism differ.** StepBet returns your stake; Save The Plugin does not, and adds a reward instead. Loss-framed versus gain-framed. Both create incentive; the literature the analogy gestures at says the first is stronger. Disclosed, not concealed. - **Reward value is face value, not cash.** Newsletter sponsorships, community membership and a conference ticket are sponsor-donated inventory whose marginal cost to the donor is low. "$400–$500" is list price, and the winner cannot convert it to cash. Neither dishonest nor equivalent to money. - **The dates are internally consistent.** 5 October 2026 is indeed a Monday; four Monday drops fit inside a 30-day window ending 4 November, leaving nine days after the final release. Checked rather than assumed. - **The economics of the first cohort are small.** Ten seats at $297 is $2,970 in launch revenue. This is not a scaled product; it reads as a genuine first cohort run personally, consistent with the private-Slack promise. - **Completion-rate claim is unquantified.** *"Close to zero"* for free courses, from the author's own experience. Plausible — it matches published MOOC completion figures — but no number, no denominator, no source. - **The audience qualifier does real work.** "Premium plugin with real paying customers" excludes free-plugin authors and pre-revenue builders, for whom several tasks (flash sale, reach out to your users, ask for a review) have no object. - **AI is treated as settled background, not as a thesis to defend.** "Entire features that used to take a week now happen in minutes" is asserted without evidence. For this audience in late 2026 that is probably a reasonable assumption about shared experience rather than a claim needing support. - **Capture is clean.** Full body, no truncation, no widget furniture. One image lost as information (a product screenshot, so little is lost). ## 📚 References **External, and the only one (linked):** - [StepBet](https://www.stepbet.com/) — the commitment-device app carrying the argument's entire evidential weight. A commercial product, not a study. Its existence demonstrates that people pay to enter such challenges; it does not by itself demonstrate efficacy, and no outcome data is offered here. **The product (linked, four positions):** - [Save The Plugin](https://savetheplugin.com/) — 20 tasks / 30 days / private Slack, $297 then $397, starting 5 October 2026. **Author-orbit properties offered as reward inventory (all linked):** - [WC Weekly sponsorships](https://wcwkly.com/sponsors/), [Business Bloomer Club](https://www.businessbloomer.com/club/), [Checkout Summit 2027](https://checkoutsummit.com/). **Not present and worth seeking independently:** - Any behavioural-economics literature on commitment contracts — the academic work on deposit contracts and goal commitment is substantial and would either strengthen or qualify the gym theory considerably. - Outcome data from StepBet or comparable services, as opposed to a description of the mechanism. - Any measurement of whether marketing sprints change plugin revenue, which is the claim that actually matters to a buyer. - Evidence for the AI-collapses-build-time premise, treated here as shared background. **Sourcing assessment.** Densely linked, precisely placed, and almost entirely self-referential. One outbound link, to a commercial analogy. The document is not uncited; it is un-evidenced, which is a different and more specific finding. ## 🗣️ Paraphrase *Restated in the analyst's words. None of the following is the author's phrasing.* **The opening claim.** Producing a WooCommerce extension has never required less effort, thanks to AI tooling. Consequently the difficulty that was always present but always deferred — persuading anyone to purchase — is now the sole remaining obstacle. **On who the audience is.** Developers in this market, the author included, are not generally incompetent at promotion. They simply never arrive at the moment of doing it: the video that stays on the list, the partnership email never sent, the testimonial never requested. **On the real diagnosis.** Lack of time, boredom, and not identifying as a salesperson are offered by developers as reasons. The author's position is that none of these is the actual cause, and that what is missing is motivation — which he proposes to supply financially. **On why free things fail.** Complimentary gym membership does not produce exercise, because nothing is at risk. A step-counting app demonstrates the alternative: entrants stake money, meet their targets, and recover their stake along with a portion of what the unsuccessful forfeited. Risk of loss converts intention into action. **On the structural asymmetry.** Writing software comes with its own enforcement — due dates, failures, a functioning result. Promotion carries none of these. Skipping it produces no visible consequence, so postponement is costless and therefore perpetual. The author reports observing this for more than ten years, and that the free material he has distributed goes almost entirely uncompleted. **On the offer.** A thirty-day programme of twenty promotional exercises, released in weekly groups of five, conducted personally by the author in a closed Slack workspace. Examples include reviewing one's product page, discounting temporarily, and contacting existing customers. **On the incentive.** Completing all twenty within the period earns a prize, donated by sponsors, with a stated value between four and five hundred dollars — in addition to whatever revenue the promotional work itself produces. Failing to complete costs the prize but not the work already done. **On availability and price.** The opening ten places cost $297, of which six remained when the piece was written; subsequently the price becomes $397. The author states he is participating himself because he too needs to do this work. The programme begins on Monday 5 October 2026, and is aimed at people already selling a paid extension to actual customers. ## 📰 Newsletter **The bottleneck moved and nobody sent a memo** Rodolfo Melogli has written the most quietly alarming sentence in the WordPress economy this month, and it is not the one he is selling against: > AI has made shipping a WooCommerce plugin easier than it's ever been. Which means the part that was always the hard part, **actually getting people to buy it, is now the only part left standing**. He is right, and the implications go well past WooCommerce. For twenty years the plugin business has had a natural moat made of effort. Building the thing was slow, so the people who could build the thing had a defensible position, and marketing could be deferred indefinitely because the queue of work in front of it never emptied. The queue has emptied. What is standing there, blinking, is a sales page nobody wrote. The diagnosis of *why* developers don't market is the best part, and it is not the usual scolding about mindset: > Building has deadlines, error messages, and a working feature at the end to prove you did something. Marketing has none of that built-in structure. Nothing breaks if you skip the blog post. That is exactly it. Code shouts when you get it wrong. A blog post you never wrote is silent forever. Every contributor who has watched a documentation task sit in a queue for three release cycles knows this shape — it is the same failure mode wearing a different hat, and it is why "someone should write that up" is the most reliably unfulfilled sentence in open source. The remedy on offer is [Save The Plugin](https://savetheplugin.com/): twenty marketing tasks over thirty days, five every Monday, run in a private Slack, $297 for the first ten seats, $397 after, with a sponsor-donated reward worth $400–$500 if you finish. Starts 5 October. Melogli is upfront that he is in it himself and that he sells it, which is more disclosure than most of the internet manages before breakfast. One thing worth noticing before you reach for a card. He justifies the design with [StepBet](https://www.stepbet.com/), where you stake money and **get it back** if you hit your goals — loss aversion, the strongest lever behavioural economics has. What he actually ships is the gain-framed cousin: your $297 is spent regardless, and finishing earns you a prize on top. He says so plainly, no concealment. But the mechanism he cites as the reason this works is not the mechanism in the box, and if you are buying specifically because "money on the line makes me do it," that is worth knowing. Also: the reward is sponsor-donated inventory — newsletter slots, community access, a conference ticket. Worth $400–$500 at list price, and worth exactly nothing at the supermarket. None of which is a reason not to do it. The deadline-plus-peer-group-plus-small-financial-sting combination is a real forcing function, and the free courses genuinely don't work — the completion rates on free anything are famously close to zero and always have been. If you ship a premium plugin and your last blog post is from 2024, the diagnosis in this article is about you, and you already knew that, which is rather the point. ## ✅ Action Items **Plugins / Themes** - The bottleneck-migration claim is directly relevant to the .org plugin economy. If building is cheap, submission volume rises and discovery pressure rises with it. Worth anticipating as a directory and review-queue question, not just a developer-business one. - The forcing-function insight suggests something practical: plugin authors respond to structured deadlines. Any programme wanting better plugin hygiene (accessibility passes, readme quality, security updates) should carry deadlines and visible consequences rather than documentation and encouragement. **Training** - "Free courses have near-zero completion" is a claim the Training team can test against its own data rather than accept. If Learn WordPress completion rates tell the same story, that is an argument for cohort-based, deadline-bearing formats over self-paced libraries — and the evidence would be first-party rather than anecdotal. - The structural point — that skipped work with no visible failure gets deferred indefinitely — applies to every self-paced learning path in the project. **Marketing** - Same insight, applied internally: marketing tasks without deadlines do not happen, in a volunteer project as much as in a solo business. Worth naming when scoping contributor work. **Documentation** - "Nothing breaks if you skip the blog post" is the documentation problem exactly. Docs tasks have no forcing function, which is why they sit. This article articulates the mechanism better than most internal discussions of it. **Community** - The peer-group-plus-deadline structure is replicable without money. A time-boxed cohort with public commitment and a named facilitator is most of the mechanism; the financial stake is one lever among several. **DevRel** - Worth citing the diagnosis when talking to plugin businesses about what AI changes. It is more useful and more specific than the general "AI changes everything" register. **OSPO** - Note the economic shift: if production cost collapses, the differentiator in the plugin economy becomes distribution, and distribution favours those with audiences. That has consolidation implications for an ecosystem that depends on many small independent vendors. **Core, Core Performance, Core AI, Core Program Team, Mobile, Playground, Support, Design, Photos, TV, Polyglots, Accessibility, Meta, CLI, Hosting, Tide, Openverse / FAIR / The WPOCC** - No action. A commercial marketing sprint for plugin vendors generates no work for these teams. ## 🧪 Hypotheses 1. **When AI lowers production cost in a craft market, the binding constraint moves to distribution, and incumbents underperform because they were selected for production skill.** *Testable:* survey WooCommerce plugin vendors on time allocated to building versus marketing in 2024 against 2026, and correlate the shift with revenue change. If the thesis holds, vendors who reallocated toward marketing outperform those who did not. 2. **Absence of a forcing function, not absence of ability, predicts marketing non-completion.** *Testable:* give two matched groups of developers the same marketing task list, one with deadlines and public check-ins, one without. Compare completion. The author's claim predicts a large gap. 3. **Loss-framed stakes outperform gain-framed rewards at equivalent value.** The article cites the first and implements the second. *Testable:* run two cohorts, one where the fee is refunded on completion, one where an equivalent-value prize is awarded, and compare completion rates. This is the cleanest experiment the product itself could run. 4. **Face-value rewards motivate less than cash of the same nominal value.** Sponsor-donated inventory cannot be converted. *Testable:* offer one cohort $400 in donated inventory and another $250 cash, and see which produces higher completion. 5. **Free-course completion rates in the WordPress ecosystem are near zero and cohort formats materially improve them.** *Testable:* directly measurable from Learn WordPress data, and the result would inform Training strategy regardless of what it shows. 6. **Scarcity signalling raises conversion but not completion.** "Six seats left" sells places; it does not make anyone finish twenty tasks. *Testable:* compare completion rates between buyers who converted during scarcity messaging and those who bought at the higher price without it. ## 📊 Methodology **The source's method.** Argument from experience plus one analogy. The claims rest on the author's decade of observing plugin businesses (*"I've watched this happen to good plugins for over a decade"*), his own completion data from free material he has distributed (unquantified, reported as "close to zero"), and the existence of StepBet as an example of a commitment device that people pay to join. There is no survey, no dataset, no citation to the behavioural-economics literature the gym theory implicitly depends on, and no outcome measurement of any prior cohort — because this is the first. For a short persuasive essay by a practitioner that is a normal and defensible method; it is not evidence in any stronger sense, and the piece does not pretend otherwise. **This analysis's method.** The captured body was read in full and its link positions enumerated and classified by destination before any sourcing claim was made — eight positions, of which one is genuinely third-party and seven point to the product or to the author's own properties. The stated schedule was checked rather than assumed: 5 October 2026 is a Monday, four Monday releases of five tasks fit within a 30-day window closing 4 November, and the final batch lands nine days before the deadline — all internally consistent. The incentive structure was compared against the analogy the article uses to justify it, which is how the loss-framed/gain-framed divergence surfaced; the article's own words establish both sides of that comparison, so it is a reading of the text rather than an inference about the author's intent. Reward value was assessed as face value of donated inventory rather than cash, which follows from the article's own description of the prizes. The first-cohort revenue figure ($2,970) is arithmetic on the stated price and seat count. **Limits.** No external source was consulted — not StepBet, not the product page, not the commitment-contract literature. No claim is made here about whether the sprint works, because no outcome data exists for a programme that has not yet started. The judgement that the diagnosis is sound rests on its internal coherence and its fit with widely observed patterns, not on independent verification. ## ❓ Questions - Why a reward rather than a refundable stake, when the article's own analogy is refund-based? Payment-processing friction, sponsor economics, or a deliberate choice? - What were the actual completion rates on the free courses — out of how many enrolled? - What happens to a participant who completes 18 of 20 tasks? All-or-nothing thresholds create a cliff at which effort collapses once the target becomes unreachable. - Who judges completion, and against what standard? "Audited your product page" admits of very different levels of effort. - Will outcome data be published — completion rate, and any revenue change participants report? That would convert the whole proposition from plausible to evidenced. - Does the mechanism work for free-plugin authors, or is the paying-customer prerequisite load-bearing? Several tasks presuppose an existing customer base. - Is the bottleneck-migration thesis true beyond WooCommerce — for themes, for SaaS, for agencies? - If building is now cheap, does marketing effort still convert at historical rates, or has the volume of competing plugins moved that too? ## 🔮 Future Research - **Measure the bottleneck shift directly.** Time-allocation survey of plugin vendors across 2024–2026 against revenue outcomes. The thesis is testable and nobody has tested it. - **Run the loss-versus-gain experiment.** Two cohorts, equivalent value, different framing. The product is an ideal vehicle and the result would be genuinely informative rather than merely commercial. - **Pull Learn WordPress completion data.** The free-courses-fail claim can be checked first-party, and the answer changes how the Training team should build. - **Read the commitment-contract literature properly.** Deposit contracts and goal-commitment research would either underwrite the gym theory or qualify it, and the article gestures at it without engaging. - **Study post-AI plugin submission volume.** If building is cheap, directory submissions should rise. That is measurable and has discovery-policy consequences. - **Follow up after 4 November 2026.** Completion rate and participant-reported outcomes would turn this from a hypothesis into a result. ## 💡 Implications **Practice.** The transferable move is free and requires nobody's product: attach a deadline, a peer group and a visible consequence to work that has no natural forcing function. The insight that marketing fails because nothing breaks — not because people are bad at it — redirects effort from self-improvement to structure, which is the more tractable target. **Policy.** For the plugin ecosystem, cheap production plus expensive distribution favours vendors who already hold audiences. That is a consolidation pressure on a marketplace whose health depends on many small independent vendors, and it is worth naming in any discussion of directory discovery or marketplace policy. **Security.** Not applicable to this source in the usual sense, with one adjacent note worth recording: if AI makes shipping plugins dramatically cheaper and the constraint moves to marketing rather than to quality, the volume of published code rises without a corresponding rise in review capacity. That is a supply-chain pressure on the ecosystem, and it follows from the article's own premise even though the article does not raise it. **Education.** The near-zero completion claim for free self-paced material, if it holds, is an argument for cohort-based, deadline-bearing, facilitated formats in WordPress training — which cost more to run and work better. The structural explanation offered here (no forcing function, no visible failure) is a better guide to course design than the usual appeals to learner motivation. **Funding.** A $297 price point with a $400–$500 donated-inventory reward is a small, personally-run first cohort, not a scaled business — ten seats is under $3,000. Worth noting that the reward economics depend on sponsors donating inventory at face value, which works at this scale and would not obviously survive scaling. ## 🧠 Learning Styles Assessment - **Visual.** Weak in the capture and probably weak in life. One image, a product screenshot, with no alt text. Nothing illustrates the argument — and the bottleneck-migration claim is the kind of idea a single diagram would fix permanently. - **Aural.** Not applicable to this source. No audio or video component. - **Verbal.** Very strong and the dominant mode. Short paragraphs, heavy use of bold to carry the argumentative spine, conversational register, rhetorical questions. Reads aloud well. - **Kinesthetic.** Strong by reference rather than in the text. The article advertises a programme that is entirely doing — twenty concrete tasks — and names several of them. The page itself offers nothing to do beyond buying. - **Logical.** Moderate. There is a clear causal chain (building cheap → marketing exposed → no forcing function → indefinite deferral → stakes needed) and it is easy to follow. What is absent is any number: no completion rate, no revenue figure, no outcome data. A logical learner can follow the reasoning and has nothing to check it against. - **Social.** Strong as a promise. A private Slack with direct access to the author is the central differentiator over free material, and the article knows it. - **Solitary.** Adequate for the reading; the product is explicitly not solitary, which is the point. - **Naturalistic.** Not applicable to this source. No environmental or natural-systems content. **Reading level.** Roughly US grade 8–9. Short sentences, conversational contractions, common vocabulary. The only specialist terms — WooCommerce, plugin, boilerplate, scaffolding, flash sale — are all audience-native. Deliberately and effectively easy to read. ## 📊 Accessibility Assessment Mapped to WCAG 2.2 AA, assessed against the captured artifact. 1. **Text alternatives (1.1.1 Non-text Content).** Fails. The single image — a screenshot of the product website, itself a link — has empty alt brackets in the capture. Because it is a linked image, this is a compound failure: a screen-reader user encounters a link with no accessible name at all. 2. **Time-based media (1.2.x).** Not applicable to this source. No audio or video in the article, though the text mentions a demo video as an example task. 3. **Adaptable / info and relationships (1.3.1).** Passes. Real headings throughout, semantic paragraphs, and bold used for emphasis that is genuinely semantic rather than decorative — the bolded phrases are the argument's load-bearing claims. 4. **Distinguishable (1.4.3 Contrast, 1.4.4 Resize Text).** Not determinable from the capture. No styling information survives markdown conversion. 5. **Navigable / link purpose (2.4.4).** Mixed. Text links are good — "StepBet," "savetheplugin.com," "newsletter sponsorships," "online community" all convey purpose out of context. The image link fails entirely, per (1). Additionally the product is linked four times in a short article, which is repetitive for anyone tabbing through. 6. **Readable (3.1.1 Language, 3.1.5 Reading Level).** Passes well. Grade 8–9, no unglossed jargon beyond audience-native terms, consistent terminology throughout. 7. **Robust / parsing and name-role-value (4.1.2).** Partially failing, on the same image-link issue as (1) and (5): a link whose only content is an image with no alt text has no accessible name, so its role is conveyed but its purpose is not. **Overall.** The prose is among the most accessible in this batch — short, plain, well structured, genuinely easy to read. The single failure is the unlabelled image link, and it is a one-line fix with real consequences for anyone using assistive technology. ## 🌍 DEIB Assessment **Cultural breadth.** Narrow and largely unmarked. English only, US dollars, US-centric business framing, and a gym metaphor that assumes paid gym membership is a familiar reference point. The audience — WooCommerce plugin vendors — is genuinely global, and nothing in the piece acknowledges that a $297 entry fee represents wildly different commitments in different economies. The author writes from Italy, so the monolingual dollar framing is a market choice rather than an unconscious default, which makes it more deliberate but no less narrowing. **Inclusive language.** Clean. No gendered pronouns anywhere — "developers," "they," "you" throughout. No idiom that would trip a non-native reader except the gym analogy, which is explained as it is used. The self-inclusion (*"including me!"*, *"I NEED to get that marketing work done too"*) is the notable choice: the author places himself inside the group being described rather than above it, which removes most of the condescension this genre usually carries. **Neurodiversity support.** Strong, and arguably the article's best accessibility feature. Very short paragraphs, one idea each. Bold marking the spine of the argument so it can be skimmed without losing the thread. Descriptive section headings. Concrete examples in place of abstraction. And the product itself is structured for exactly the executive-function difficulty the article describes — externally imposed deadlines, tasks broken into fives, a person to ask when stuck. The diagnosis ("marketing has no built-in structure, so it gets deferred indefinitely") will read to many neurodivergent people as a precise description of task initiation difficulty, though the article frames it as universal rather than naming it. **Representation.** One named individual, the author. No people depicted. Not applicable in the usual sense. Worth a neutral note that the framing assumes a solo operator with discretionary time and $297 — the plugin developer as independent small-business owner. Developers working under employment, in agencies, or in teams are outside the frame entirely, as are those for whom a 30-day sprint alongside existing obligations is not available. **Psychological safety.** Genuinely positive, with one commercial caveat. The article's central move is to relocate blame from character to structure: you are not lazy, you are not bad at this, the work simply lacks a forcing function. That is a kind reframe and an accurate one, and it lowers the cost of admitting the problem — which is the prerequisite for doing anything about it. The self-inclusion reinforces it. The caveat is that the reframe is also the sales mechanism: having removed the shame, the article supplies a paid remedy, and scarcity messaging ("six seats left") reintroduces pressure of a different kind. Both things are true at once, and neither cancels the other. ## ✅ Logical Validity **Strong reasoning.** The bottleneck-migration argument is well constructed: a premise about falling production cost, an inference about which constraint becomes binding, and a conclusion about who is poorly positioned for it. The motivation diagnosis is supported structurally rather than by assertion — building has deadlines and error messages, marketing has neither, therefore deferring marketing is costless and therefore perpetual — and that is a causal mechanism, not a character judgement. The author declines an available overreach: rather than claiming developers are bad at marketing, he explicitly allows that *"some genuinely are, but most are perfectly capable and just never get around to doing it,"* which is both more charitable and more likely true. He includes himself in the diagnosis and in the product. The audience qualifier at the end actively excludes people the product would not serve. And every commercial term — price, ladder, seat count, start date, what happens if you fail — is stated plainly rather than buried. **Fallacies.** *False dilemma — present, and load-bearing for the sale.* **Located** in: *"If your problem is 'I don't have the time' or 'Marketing is boring' or 'I'm not a salesperson', that's not your real problem. Your problem is motivation."* **Why it fails:** three candidate explanations are named and all three dismissed in favour of a fourth, with no argument for the substitution. For a developer supporting customers on a shipped product while doing client work, "I don't have the time" may be a literal and accurate description of a capacity constraint that no amount of motivation resolves — and a 30-day sprint would make it worse, not better. The rhetorical move is necessary for the pitch, because if time is the real constraint the product does not address it. **The fix:** "for many of us that's not the real problem" costs nothing, keeps the insight, and stops asserting something the author cannot know about the reader. *Weak analogy, with a mechanism mismatch — the most consequential finding here.* **Located** across the gym-theory section and the reward structure. The article establishes its principle with StepBet, correctly described: *"Miss your own goals, and you lose your stake."* The product then implements something structurally different — the fee is spent regardless, and completion earns an additional sponsor-donated prize, as the article states: *"Don't finish, and you keep everything you shipped and posted, you just don't get the reward!"* **Why it matters:** loss of a stake and forfeiture of a gain are the two sides of the loss-aversion literature, and the reason commitment devices are built around the first is that it is empirically the stronger lever. The article cites the mechanism it does not ship. **Why this is a fallacy and not a lie:** both facts are stated openly in the article itself; the failure is that the analogy is offered as justification for a design it does not describe. **The fix:** refund the fee on completion and fund the prize separately — or drop the StepBet framing and argue for reward-based motivation on its own terms. *Hasty generalisation from unquantified personal data.* **Located** in: *"Free advice hasn't fixed it. Free courses haven't fixed it. I've given away plenty of both, and the completion rate tells the story every time: close to zero."* **Why it is weak:** no enrolment figure, no completion figure, no comparison group, and the conclusion drawn — that free things fail *because* they are free — does not follow from low completion alone, since free offerings also attract browsers who never intended to finish. Selection differs, not just commitment. **Why it is nonetheless plausible:** published completion rates for free self-paced courses genuinely are very low, so the claim is likely true even though the evidence given does not establish it. **The fix:** publish the numbers, or cite someone who has. *Appeal to scarcity — present and unverifiable by construction.* **Located** in: *"The first 10 seats are $297, and six are left as I'm writing this... After that, the price goes to $397."* **Why it is a fallacy:** the seat count is a reason to buy now that has nothing to do with whether the programme suits you, and no reader can check it. **Mitigating:** the count is specific rather than vague, the price ladder is a normal launch mechanic, and "as I'm writing this" is an honest timestamp rather than a fake live counter. It remains an urgency appeal. *Undisclosed conflict — not present, and worth saying so.* The author sells the remedy to the problem he diagnoses, which is the structural shape of a conflict of interest. He does not formally disclose it, but he does not disguise it either: the article announces the product, names the price, and states that he is a participant himself. Readers know exactly what they are reading. This is noted here because its *absence* from the fallacy list is a judgement, not an oversight. **Tone of voice.** Warm, direct, peer-to-peer, lightly self-deprecating. Heavy bolding used as argumentative punctuation rather than decoration. Second person throughout, but inclusive second person — the author keeps putting himself inside the problem (*"including me!"*, *"I NEED to get that marketing work done too!"*). Exclamation marks and capitals give it an unpolished, written-in-one-sitting quality that reads as sincere rather than sloppy. The register is a practitioner talking to practitioners, and it is the right register for the argument; it is also, of course, extremely effective as sales copy, and those are not separable here. ## 🛡️ DARVO Analysis **Deny.** No denial pattern. No accusation exists in the material and the author denies nothing. The closest structural relative is the dismissal of the reader's stated reasons ("that's not your real problem"), which is a reframe rather than a denial — it substitutes an explanation rather than rejecting a charge. It is treated as a false dilemma in Logical Validity, which is the correct category. **Attack.** No attack. No competitor, alternative product, or individual is named or disparaged. Free courses and free advice are criticised as a *category* — *"Free advice hasn't fixed it. Free courses haven't fixed it"* — but the author immediately identifies himself as the supplier of the failed free material (*"I've given away plenty of both"*), which makes it self-criticism rather than an attack on others. Developers who fail to market are consistently described as capable rather than deficient. **Reverse victim and offender.** No reversal. There is no grievance, no injured party, no harm alleged, and no blame assigned in any direction. The article's rhetorical movement runs the opposite way from DARVO: it removes blame from the reader and relocates it onto an impersonal structural cause. **Assessment.** No DARVO pattern present. Retained per the template with this explanation. Worth recording the positive finding: in a persuasive sales document — a genre where casting a competitor or an alternative as the villain is the standard move — this article assigns fault to nobody at all, including the reader, and including the people who might otherwise be positioned as rivals. ## 🎯 Conclusion **Bottom line.** Two documents in one, and both are worth the time. The diagnosis is genuinely good: AI has collapsed the cost of building WooCommerce plugins, so the binding constraint has migrated to marketing, and the people holding these businesses were selected for skill at the old constraint rather than the new one. The explanation of *why* marketing gets deferred — that it has no deadlines, no error messages, and nothing that visibly breaks when skipped — is a structural account rather than a character judgement, and it is more useful than most of what is written on the subject. The prescription is a product the author sells: twenty tasks, thirty days, private Slack, $297 rising to $397, sponsor-donated reward worth $400–$500 on completion, starting 5 October 2026. The schedule checks out arithmetically and the design is sensible. Three things a buyer should weigh, all of them visible in the article itself. The dismissal of "I don't have the time" is a false dilemma that the sale requires, and for some readers time genuinely is the constraint. The reward is face value of donated inventory, not cash. And the commitment mechanism cited as justification — StepBet's refundable stake, loss-framed — is not the mechanism shipped, which is gain-framed and, by the literature the analogy points at, the weaker of the two. None of that makes it a bad offer. A deadline, a cohort, a facilitator and a small financial sting is a real forcing function, and the author is candid throughout, including about being his own customer. **Next steps.** Take the bottleneck-migration idea as the durable content and file it independently of the product; it applies well past WooCommerce. For the Training team, the free-course completion claim is checkable against first-party Learn WordPress data and would be worth checking. And if the sprint runs, its completion rate is the number that would turn all of this from plausible into known — worth looking for after 4 November 2026. ## 🔄 Refactor Appendix ### 📚 Literature Atoms #### [H1] Cheap building exposes marketing as the real constraint > [!quote] > AI has made shipping a WooCommerce plugin easier than it's ever been. Which means the part that was always the hard part, **actually getting people to buy it, is now the only part left standing**. **Context & use** - The thesis, and the part that generalises furthest beyond WooCommerce. - Building was never the hard part commercially — it was the *binding* part, consuming available time. Remove it and the hidden constraint becomes visible. - The people holding these businesses were selected for skill at the old constraint, not the new one. That is the uncomfortable corollary and the article does not state it outright. - Applies to any craft business where AI lowers production cost: themes, agencies, courses, writing. **Tags:** #ai-commoditisation #bottleneck-migration #plugin-business <!-- atomicity: 1 idea ✓ --> #### [H2] Marketing has no forcing function, so it defers forever > [!quote] > Building has deadlines, error messages, and a working feature at the end to prove you did something. Marketing has none of that built-in structure. Nothing breaks if you skip the blog post. Nothing crashes if you never send the outreach email. **Context & use** - The best diagnostic in the article: a structural explanation, not a character judgement. - The safety of deferral is precisely what guarantees indefinite deferral — the causal direction is right. - Applies identically to documentation, accessibility passes, and every open-source task whose omission is silent. "Someone should write that up" fails for this reason, not for lack of goodwill. - Redirects effort from self-improvement to structure, which is the more tractable target. **Tags:** #forcing-functions #task-initiation #developer-marketing <!-- atomicity: 1 idea ✓ --> #### [H3] The cited commitment mechanism is not the one shipped > [!quote] > **Miss your own goals, and you lose your stake**. The money is what turns "*I should probably do that*" into something you actually do. **Context & use** - Accurate as a description of StepBet, which returns the stake on success. - Save The Plugin does not refund: the $297 is spent either way and completion earns an additional sponsor-donated prize — the article states this plainly. - Loss of stake versus forfeiture of gain are the two sides of loss aversion; commitment devices use the first because it is the stronger lever. - Nothing is concealed. The defect is that the analogy is offered as justification for a design it does not describe. **Tags:** #commitment-devices #loss-aversion #incentive-design <!-- atomicity: 1 idea ✓ --> #### [H4] Free offerings complete at near zero > [!quote] > Free advice hasn't fixed it. Free courses haven't fixed it. I've given away plenty of both, and the completion rate tells the story every time: close to zero. **Nothing forces the work when there's nothing on the line**. **Context & use** - Unquantified and first-person: no enrolment figure, no completion figure, no comparison group. - Likely true anyway — published completion rates for free self-paced material are famously low — but the evidence given does not establish the stated cause. - The alternative explanation the article skips: free offerings attract browsers who never intended to finish. Selection differs, not only commitment. - Directly checkable against Learn WordPress data, which would make it first-party evidence instead of anecdote. **Tags:** #course-completion #free-vs-paid #training-design <!-- atomicity: 1 idea ✓ --> ### 🧠 Permanent Candidates #### [P1] removing-a-bottleneck-relocates-it-to-whatever-it-was-hiding **Claim.** Removing the binding constraint in a process does not make the process easy; it promotes the next constraint to binding. Where the old constraint also selected who entered the field, the incumbents are systematically unprepared for the new one — they were filtered for a skill that no longer discriminates. **Evidence pointer.** [H1] — AI collapses plugin build time, and the constraint moves to distribution, in a population that self-selected for enjoying building (*"Most WooCommerce plugin developers didn't get into this to… sell. They got into it to build things"*). **Scope & conditions.** Applies wherever a capability improvement removes a step that was previously rate-limiting. The selection corollary applies specifically where the removed constraint acted as a filter on entry — which is what makes this sharper than a generic observation about bottlenecks. Does not apply where the removed constraint was incidental rather than selective, or where the same skill governs both steps. **Links.** - Connects to [P1] output-shape-determines-whether-a-system-can-be-checked from the Jev analysis: both concern consequences that are fixed by an earlier structural choice and only become visible later. There, output shape decided whether evaluation was affordable; here, the old bottleneck decided who is in the room when it disappears. - Connects to [P1] a-saving-measured-where-you-were-looking-is-not-a-saving from the DocsBot reranking analysis — both are cases where attention stays on the place the change was made while the consequence lands somewhere else. - Practical application to the deep-read pipeline itself: generating analysis is now cheap, so the binding constraint has moved to routing and use. That is precisely the audit's finding, arrived at from a completely different direction — a WooCommerce marketing pitch. Worth noting that three documents in this corpus now converge on it. #### [P2] work-without-a-failure-signal-is-deferred-indefinitely-regardless-of-ability **Claim.** Tasks whose omission produces no visible failure get deferred perpetually, and the cause is the absence of a forcing function rather than any deficit of skill or will. Remedies aimed at the person — advice, courses, encouragement, discipline — fail predictably; remedies that supply external structure (deadline, cohort, visible consequence) work. **Evidence pointer.** [H2] — building carries deadlines, error messages and a working artifact; marketing carries none, so *"it's always safe to push marketing to next week, which is exactly why it gets pushed to next week, indefinitely."* [H4] supplies the corroborating negative: free advice and free courses, aimed at the person, completed at close to zero. **Scope & conditions.** Applies to any task whose omission is silent — documentation, accessibility remediation, test writing, dependency updates, marketing, follow-up. Does not apply where the person genuinely lacks capacity (the false dilemma in this article's own argument: for some readers time really is the constraint, and structure cannot manufacture hours). Strongest for solo operators with no external accountability; weakens inside teams, where colleagues supply some of the missing signal. **Links.** - This is the enforcement-over-instruction thesis of the knowledge-system audit, arriving from outside it and using none of its vocabulary. There: an instruction that asks for correctness does not survive contact with the work, and only a mechanism that runs does. Here: advice aimed at the person fails, and only structure that imposes a deadline works. Same claim, two domains, independently derived — which is the strongest kind of corroboration a principle like this can get. - Connects to [H3] in this document: having correctly diagnosed that a forcing function is required, the product then implements the weaker of the two available framings. Getting the diagnosis right does not guarantee getting the mechanism right. - Direct application to WordPress: documentation and accessibility tasks fail for exactly this reason, and the standard remedies (guidelines, encouragement, documentation about documentation) are person-aimed and therefore predicted to fail. ### ✏️ Fleeting Queue - Three documents in this corpus now converge on the same structure from unrelated directions — the knowledge-system audit, the Jev reranking evaluation, and a WooCommerce marketing pitch. When an idea keeps arriving unbidden from different fields it has earned a proper permanent note of its own, independent of any source. - The Learn WordPress completion-rate question is cheap to answer and would settle [H4] with first-party data. Worth asking the Training team. - The loss-versus-gain framing experiment is one the product could run on itself at no extra cost, and the answer would be genuinely useful to anyone designing a cohort programme. - If building is cheap, plugin directory submission volume should be rising. Is anyone measuring that, and what does it mean for review capacity? - Worth a note on all-or-nothing reward thresholds: what happens to a participant at 18 of 20 tasks, when the target becomes unreachable and effort collapses? - The unlabelled image link is a one-line accessibility fix on a page selling to developers. Mildly ironic; also genuinely worth reporting if there is any route to do so. ### → Things 3 - [ ] Ask the Training team for Learn WordPress course completion rates — it would test the free-courses-fail claim with first-party data and inform whether cohort formats are worth the extra cost. - [ ] Write the standalone permanent note for "work without a failure signal is deferred indefinitely" — three independent arrivals in this corpus is enough; it belongs as its own note, not as an observation attached to a source. <!-- deep-read:sections end --> 📄 **Full text:** [[Full Document Contents/Articles/WooCommerce Devs Aren’t Marketers, and That’s the Problem.md|WooCommerce Devs Aren’t Marketers, and That’s the Problem by Rodolfo Melogli]] ## Highlights - AI has made shipping a WooCommerce plugin easier than it’s ever been. ([View Highlight](https://read.readwise.io/read/01m3casb1bf8y93g0gf1dgtr59)) - Note: H1 — The thesis, and the part that generalises furthest. Building was never the hard part commercially; it was the BINDING part, consuming available time. Remove it and the hidden constraint becomes visible. The uncomfortable corollary the article doesn't state: the people holding these businesses were selected for skill at the old constraint, not the new one. - Tags: atom/literature/h1 - you pay an entry fee into a step-count challenge, hit your personal daily and weekly step goals through the challenge, and you get your stake back (plus a share of what everyone who missed their goals forfeited). ([View Highlight](https://read.readwise.io/read/01m3casgpknw8j57vea8558yfn)) - Note: H3 — Accurate as a description of StepBet: the stake is RETURNED on success. This is the loss-framed mechanism, the stronger lever in the loss-aversion literature, and it is the justification offered for the product's design. Compare against what ships (next highlight). - Tags: atom/literature/h3 - Building has deadlines, error messages, and a working feature at the end to prove you did something. Marketing has none of that built-in structure. Nothing breaks if you skip the blog post. Nothing crashes if you never send the outreach email. ([View Highlight](https://read.readwise.io/read/01m3casdt55x6eg16bb3wt6v8f)) - Note: H2 / Z1 — The best diagnostic here: a structural explanation, not a character judgement. The safety of deferral is precisely what guarantees indefinite deferral. Applies identically to documentation, accessibility passes, and every open-source task whose omission is silent — "someone should write that up" fails for this reason, not for lack of goodwill. Redirects effort from self-improvement to structure, which is the tractable target. - Tags: atom/literature/h2, atom/zettel/z1 - Free advice hasn’t fixed it. Free courses haven’t fixed it. I’ve given away plenty of both, and the completion rate tells the story every time: close to zero. ([View Highlight](https://read.readwise.io/read/01m3caspxwbs187jtdvr041192)) - Note: H4 — Fallacy (hasty generalisation from unquantified personal data): no enrolment figure, no completion figure, no comparison group. And the conclusion that free things fail BECAUSE they are free doesn't follow from low completion alone — free offerings also attract browsers who never intended to finish, so selection differs, not just commitment. Likely true anyway; the evidence given doesn't establish it. Directly checkable against Learn WordPress data, which would make it first-party evidence instead of anecdote. - Tags: atom/fleeting/f1, fallacy/hasty-generalization - Don’t finish, and you keep everything you shipped and posted, you just don’t get the reward! ([View Highlight](https://read.readwise.io/read/01m3cat255r5c13qmw0k4372nh)) - Note: Fallacy (weak analogy / mechanism mismatch) — the most consequential finding here. The $297 is spent either way; completion earns an ADDITIONAL sponsor-donated prize. That is gain-framed, not loss-framed like the StepBet analogy used to justify it. Loss of stake and forfeiture of gain are the two sides of loss aversion, and commitment devices use the first because it is empirically stronger. The article cites the mechanism it does not ship. Nothing is concealed — both facts are stated openly — but the analogy justifies a design it does not describe. Fix: refund the fee on completion and fund the prize separately, or argue for reward-based motivation on its own terms. Also note the prize is face value of donated inventory, not cash. - Tags: fallacy/weak-analogy - The first 10 seats are $297, and six are left as I’m writing this. ([View Highlight](https://read.readwise.io/read/01m3cast5gg10m04tdb7w16mt5)) - Note: Fallacy (appeal to scarcity), present and unverifiable by construction: the seat count is a reason to buy now that has nothing to do with whether the programme suits you, and no reader can check it. Mitigating — the count is specific rather than vague, the price ladder ($297 → $397) is a normal launch mechanic, and "as I'm writing this" is an honest timestamp rather than a fake live counter. Ten seats at $297 is $2,970, so this reads as a genuine small first cohort. - Tags: fallacy/appeal-to-scarcity