The founder reported a fivefold user increase after a post reached 100,000 views. Several users had exhausted all five free calls, every observed cap-hit use involved YouTube, and none had converted to a paid plan.
Founder post on Reddit ↗Revival memo 003
Users reach the limit. The payment path does not match the moment.
An outside-in conversion memo for a skill-generation product whose founder reported users exhausting free calls with public YouTube videos and zero paid conversions.
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
Keep private content and cryptocurrency out of the experiment. At the public-YouTube cap, test one clear human payment choice and measure whether episodic users prefer a small pack or the existing subscription.
01 / PUBLIC EVIDENCE
What the outside record proves, and what it does not.
The founder said Loreto deliberately does not store source URLs or content. That statement has not been independently audited, but the proposed sprint can preserve it by using aggregate events and public source categories only.
Founder post on Reddit ↗The public MCP repository describes skill generation from YouTube videos, articles, PDFs, and images. It currently documents two free human calls per month, a $29 plan for 100 calls, and a separate $0.75 USDC x402 path. The newer founder post describes five free calls, so the live plan needs reconciliation.
Loreto MCP repository ↗The package metadata asserts an MIT license. That declaration is useful diligence evidence, but it is not a substitute for the actual license text or confirmation that every relevant asset is covered.
Loreto package metadata ↗GitHub repository metadata currently reports no detected license, and the expected root LICENSE file is absent. That does not prove a rights defect, but it prevents operating or acquisition diligence from being considered complete.
GitHub repository metadata ↗NOT PUBLICLY VERIFIED
- Current registered, activated, cap-hit, paid, refunded, and retained user counts
- Which free allowance is live and how pricing differs by surface
- Completion, failure, and repeat-use rates by public source category
- Model, parsing, storage, support, processor, and refund costs per successful skill
- Entity, domain, service code, content-processing, contributor, and license rights
- Whether current privacy behavior matches the founder's no-storage statement
02 / WHY 81
The public evidence clears the gate. Private proof keeps the score provisional.
Demand25 / 30
Users reportedly exhaust the free allowance, but current account and retention counts are unknown.
Distribution15 / 20
A viral founder post and public MCP repository create visible reach; owned acquisition cohorts need verification.
Fixability20 / 20
The cap-hit event supports one bounded packaging and checkout experiment.
Economics13 / 15
The founder identified token cost as a constraint; actual model, parsing, storage, and support costs need reconciliation.
Rights8 / 15
A public owner and package exist, but service ownership, source rights, and repository licensing are incomplete.
03 / DIAGNOSIS
Three leaks. One should be repaired first.
The product reaches observable value
Multiple users reportedly completed enough calls to exhaust the free allowance rather than abandoning before first value.
Operating implicationThe immediate question is not whether the core workflow can be used. It is whether the next transaction matches the frequency and purpose of that use.
A subscription may not fit episodic learning
The observed cap-hit behavior centered on turning YouTube videos into skills, and the founder publicly considered packs after feedback about repeat frequency.
Operating implicationA small one-time pack is a testable alternative to a subscription. It should be presented beside the current plan, not assumed to replace it.
Privacy creates an instrumentation constraint
Not storing URLs or content limits use-case visibility, which is a deliberate privacy choice rather than permission to collect more content.
Operating implicationMeasure source category, completion, cap hit, offer choice, checkout, payment, and repeat use without recording the source itself.
04 / FIVE-DAY REPAIR
Restore the path before expanding the product.
Reconcile the live funnel
Acceptance proof: A reproducible baseline from public-YouTube call start through completion, allowance exhaustion, plan view, checkout, payment, refund, and repeat generation.
Define one cap-hit choice
Acceptance proof: A written comparison between the current subscription and one small pack, including unit cost, margin floor, entitlement, expiration, and refund treatment.
Instrument without source content
Acceptance proof: Aggregate events capture public source category, successful generation, cap hit, offer selection, checkout, and payment without retaining URLs or content.
Build the reversible offer
Acceptance proof: The cap-hit surface explains pack and subscription outcomes, exact price, limits, cancellation or expiration, and privacy boundary with a tested rollback path.
Release one measured experiment
Acceptance proof: The owner-approved public-YouTube and human-payment test ships with event definitions, cost guardrails, rollback, and a 30-day review plan.
05 / MEASUREMENT CONTRACT
No turnaround claim without a denominator.
- Primary
- Cap-hit public-YouTube users becoming net retained human-plan or pack customers
- Leading signal
- Cap-hit users selecting an offer and reaching checkout
- Guardrails
- Generation completion, model cost, refund rate, repeat use, support load, privacy incidents, and content complaints
- Review window
- One comparable cap-hit cohort through payment, refund, and 30-day repeat use
06 / REQUIRED DILIGENCE
- Read-only aggregate events for public-YouTube starts, completions, failures, cap hits, offer choices, checkouts, payments, refunds, and repeat use
- Current plan, entitlement, price, discount, processor, cancellation, and refund records
- Per-call model, parsing, storage, observability, support, and processor costs
- Data map, subprocessors, retention, deletion, incident history, and proof of the no-storage behavior
- Entity, domain, service repository, contributor, package, source-content, and license ownership
- Written exclusion of uploads, private content, customer content, and x402 from the sprint
STOP CONDITIONS
- Current cap-hit and zero-paid behavior cannot be reproduced from source records.
- The proposed test requires storing a source URL, source content, private upload, or customer content.
- A viable offer cannot clear the documented model and transaction cost floor.
- The human payment path cannot be isolated from x402 or another unreviewed cryptocurrency path.
- Ownership, source-content rights, or repository licensing cannot be documented before agreement.
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.