WordPress.org displays 10,000+ active installations, 34 reviews, a 4.5 rating, and version 2.3.8 updated three days before this review.
WordPress.org plugin directory ↗Revival memo 004
The free plugin has distribution. The paid bridge needs a denominator.
An outside-in conversion memo for a maintained affiliate plugin with 10,000+ active installations, a current paid offer, and marketplace-reported recurring revenue.
Outside-in review using public evidence checked August 22, 2026. Reclaimware has not audited, operated, contacted, or received private access to this product. Seller and founder statements are labeled and are not treated as verified current metrics.
OPERATOR VERDICT
Do not add another block first. Join free activation to Pro intent, purchase, refund, and renewal, then repair the strongest measurable paid workflow.
01 / PUBLIC EVIDENCE
What the outside record proves, and what it does not.
The public product pages place click analytics and basic broken-link checking in Free. Pro adds capabilities including scheduled link scans, email reports, product-data integrations, geotargeting, and premium blocks.
AffiliateX product site ↗The product site displays annual prices of $55, $135, and $343 and lifetime prices of $159, $479, and $879 across one, three, and ten-site licenses. It also advertises a 14-day refund period.
AffiliateX pricing ↗A Flippa verified listing reports $2,445 in monthly profit, a 100% profit margin, and a reduced $90,000 asking price. These are marketplace and seller representations, not audited Reclaimware findings.
Flippa listing ↗NOT PUBLICLY VERIFIED
- Install, activation, and retention cohorts by plugin and WordPress version
- Free activation to Pro intent, purchase, refund, and renewal conversion
- Revenue by annual, lifetime, site-count, promotion, and acquisition cohort
- Processor, email, support, product-data, and Zero API costs
- Current patched-version coverage, platform standing, and unresolved support load
- Publisher, code, Pro asset, domain, customer-record, and contributor rights
02 / WHY 88
The public evidence clears the gate. Private proof keeps the score provisional.
Demand29 / 30
WordPress.org shows 10,000+ active installations, current reviews, and an actively maintained release.
Distribution20 / 20
The free plugin, product site, documentation, and marketplace listing provide multiple current acquisition surfaces.
Fixability13 / 20
One activation-to-paid cohort can be repaired in five days, but editor, marketplace, and version coverage increase test scope.
Economics15 / 15
The marketplace reports recurring revenue and high margin; processor, support, email, and Zero API costs still need source review.
Rights11 / 15
The public listing identifies contributors and a seller, but code, Pro assets, customer records, domains, and contributor assignments remain unverified.
03 / DIAGNOSIS
Three leaks. One should be repaired first.
Distribution does not reveal the paid bridge
The public directory proves a large installation base, while public pricing proves a paid offer. Neither source shows how many sites reach first value or which activated behavior precedes a Pro purchase.
Operating implicationThe first repair is a cohort join, not a redesign. Every conversion claim needs installs, activated sites, eligible Pro impressions, purchases, refunds, and renewals in the denominator.
Pro contains several different reasons to buy
The paid offer spans automation, alerts, product-data access, geotargeting, additional networks, and premium presentation blocks.
Operating implicationOne workflow should be selected from observed intent. Showing every premium capability at once can hide whether the paying job is automation, data access, risk prevention, or design leverage.
Reliability is part of conversion
AffiliateX depends on WordPress editors and external product or affiliate ecosystems, and the public directory shows active release and support surfaces.
Operating implicationA paid-boundary test is not valid unless it controls for editor, plugin, WordPress, API, and patched-version coverage. A compatibility failure must not be mislabeled as pricing resistance.
04 / FIVE-DAY REPAIR
Restore the path before expanding the product.
Reconcile the install-to-cash path
Acceptance proof: A source-backed funnel from plugin install and activation through first published block, repeat use, Pro intent, checkout, collected payment, refund, and renewal.
Find the strongest paid workflow
Acceptance proof: Activated cohorts are grouped by automation, alerts, product-data, network, geotargeting, and premium-block intent without inspecting site or customer content.
Separate friction from compatibility
Acceptance proof: The selected cohort is segmented by plugin, WordPress, editor, and patched-version coverage so broken activation is not treated as an offer problem.
Build one reversible paid bridge
Acceptance proof: One owner-approved prompt or onboarding change connects demonstrated free value to the selected Pro workflow with exact pricing, refund terms, event definitions, and rollback.
Release one measured repair
Acceptance proof: The repair ships to an eligible cohort with baseline, test coverage, support watch, stop conditions, rollback, and a 30-day renewal review plan.
05 / MEASUREMENT CONTRACT
No turnaround claim without a denominator.
- Primary
- Eligible activated sites becoming net retained Pro customers
- Leading signal
- Activated sites reaching the selected Pro workflow and purchase intent
- Guardrails
- Activation failure, compatibility errors, refunds, support load, renewals, platform standing, and product-data incidents
- Review window
- One comparable eligible cohort through purchase, refund, and renewal or a documented 30-day proxy
06 / REQUIRED DILIGENCE
- Read-only aggregate cohorts for installs, activated sites, first published block, repeat use, Pro intent, checkout, payment, refund, and renewal
- Revenue and refund records by annual, lifetime, site-count, promotion, and acquisition cohort
- Processor, email, support, Zero API, product-data, and marketplace costs
- Compatibility matrix, incident history, support backlog, security advisories, and patched-version coverage
- WordPress publisher, repository, Pro code, domains, licenses, customer records, trademarks, and contributor assignments
- Written confirmation that no site content, affiliate credentials, payment data, or production authority enters pre-contract diligence
STOP CONDITIONS
- Current revenue or the install-to-paid path cannot be reconciled from source records.
- Publisher, Pro code, customer-record, domain, or contributor rights cannot be documented.
- The selected workflow depends on unresolved security, product-data, marketplace, or platform-policy risk.
- The experiment requires site content, affiliate credentials, payment data, or production access before a signed agreement.
- Compatibility failures prevent a clean eligible cohort or safe rollback.
FOUNDER'S NEXT MOVE
Five days to prove the repair.
Revenue Rescue scopes one measurable leak, ships one bounded repair, and leaves a 30-day operating plan. Applying is free. The first two completed sprint agreements are priced at $2,500. No result is guaranteed.