Revival memo 005

The product has customers. The retained-value event is still hidden.

An outside-in activation and retention memo for a video-to-article SaaS with a live free-to-paid offer and marketplace-reported MRR, subscribers, profit, and churn.

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 broaden the generator first. Determine whether first usable draft, export or publication, or second creation best predicts renewal, then repair that transition using aggregate events only.

01 / PUBLIC EVIDENCE

What the outside record proves, and what it does not.

Product-published usage signal

The live homepage displays 500,000+ articles created, a 4.8 rating, and 500+ reviews. These are product-published claims and have not been independently audited by Reclaimware.

Video to Blog homepage
Current offer and workflow

The current pricing page offers one free post per month, paid tiers starting at $14 per month when billed yearly, and workflows spanning import, generation, editing, export, publications, newsletters, integrations, and teams.

Video to Blog pricing
Founder-described plan history

A 2024 founder update says credit-based plans created friction, introduced a non-credit plan, and committed to supporting existing plans. This is historical evidence of plan complexity, not proof of current cohort behavior.

Video to Blog 2.0 update
Marketplace-reported cash signal

A Flippa verified listing currently displays $11,002 MRR, 462 active subscribers, 10.8% overall churn, and $3,919 monthly profit. The listing also notes lifetime-customer complexity. These are marketplace and seller representations, not audited Reclaimware findings.

Flippa listing

NOT PUBLICLY VERIFIED

  • Paid activation, retention, renewal, cancellation, and refund cohorts by plan and source
  • Which event best predicts retention: import, first usable draft, export or publication, or repeat creation
  • Model, transcription, media, hosting, email, support, and payment cost by workflow
  • Current annual, monthly, grandfathered, promotional, and lifetime-customer obligations
  • Content controls, incident history, takedown handling, backups, and rollback readiness
  • Entity, code, domain, model, media, publication, customer-content, and payment rights

02 / WHY 89

The public evidence clears the gate. Private proof keeps the score provisional.

Demand30 / 30

The live product publishes substantial usage and review signals, and the marketplace reports current paid subscribers and MRR.

Distribution20 / 20

The product has an active website, free entry point, content surfaces, integrations, publishing, and a marketplace listing.

Fixability17 / 20

One activation or retention event can be repaired in five days, but the workflow spans imports, generation, editing, exporting, and publishing.

Economics14 / 15

The marketplace reports meaningful MRR and profit; model, media, hosting, support, refund, and lifetime-plan obligations need reconciliation.

Rights8 / 15

A named founder and entity are public, but code, model, media, publication, customer-content, domain, and payment rights remain unverified.

03 / DIAGNOSIS

Three leaks. One should be repaired first.

01

Creation is not necessarily retained value

The public workflow extends from video import through generation, editing, export, publication, newsletters, integrations, and repeat production.

Operating implication

A generated draft may be an intermediate event. Renewal should be compared against first usable draft, successful distribution, and a second creation session before choosing the repair target.

02

Plan history can blur the cohort

The founder previously changed credit mechanics while preserving existing plans, and the marketplace listing notes lifetime customers not captured cleanly in MRR.

Operating implication

Current, grandfathered, promotional, and lifetime entitlements must be separated before interpreting churn, margin, or upgrade behavior.

03

Usage economics vary by path

Video length, transcription, generation, regeneration, screenshots, images, publishing, newsletters, and integrations can create different direct-cost profiles.

Operating implication

Retention improvement is not enough by itself. The selected event must improve net retained revenue after model, media, infrastructure, support, refund, and delivery costs.

04 / FIVE-DAY REPAIR

Restore the path before expanding the product.

Day 1

Reconcile cash and entitlements

Acceptance proof: A plan and acquisition cohort table connects collected payment, entitlement, refund, cancellation, renewal, and direct cost without opening customer videos or generated content.

Day 2

Find the retained-value event

Acceptance proof: Aggregate cohorts compare import, first usable draft, export or publication, second creation, and renewal with explicit event definitions and denominators.

Day 3

Isolate the break

Acceptance proof: The selected transition is segmented by plan, source, input type, and broad workflow category, with failure and cancellation reasons reviewed only in redacted or aggregate form.

Day 4

Build one reversible repair

Acceptance proof: One owner-approved onboarding, progress, save, export, publication, or return-use change has exact acceptance criteria, content boundaries, tests, and rollback.

Day 5

Release one measured repair

Acceptance proof: The repair ships to an eligible cohort with baseline, cost guardrails, support watch, stop conditions, rollback, and a 30-day retention review plan.

05 / MEASUREMENT CONTRACT

No turnaround claim without a denominator.

Primary
Eligible paid accounts reaching the selected retained-value event and remaining net retained
Leading signal
Import cohorts reaching first usable draft, distribution, or second creation
Guardrails
Generation failure, time to value, direct cost, refunds, cancellations, support load, content incidents, and rollback errors
Review window
One comparable paid cohort through the selected event, refund window, and 30-day retention checkpoint

06 / REQUIRED DILIGENCE

  • Read-only aggregate cohorts for signup, import, usable draft, export or publication, repeat creation, renewal, cancellation, and refund
  • Payment and entitlement reconciliation across monthly, annual, grandfathered, promotional, and lifetime accounts
  • Model, transcription, media, storage, hosting, newsletter, integration, support, processor, and refund costs
  • Content-control map, subprocessors, retention and deletion rules, takedowns, incidents, backups, monitoring, and rollback
  • Entity, repository, domain, model, media, publication, customer-content, payment, trademark, and contributor rights
  • Written confirmation that customer videos, generated articles, publications, credentials, personal data, and production authority remain outside pre-contract diligence

STOP CONDITIONS

  • Current cash, entitlements, active subscribers, churn, or refunds cannot be reconciled from source records.
  • The selected metric requires Reclaimware to inspect customer videos, articles, publications, credentials, or personal data before agreement.
  • The repair cannot meet a documented margin floor after model, media, infrastructure, support, and refund costs.
  • Content controls, incident handling, ownership, platform standing, backups, or rollback cannot be documented.
  • Grandfathered or lifetime obligations prevent a clean, owner-approved eligible cohort.

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.

Request the sprintBrowse revival memos →