Acquisition desk

Buyer diligence workspace

Back to site
Extension buyer memo

Browser extension with subscription revenue

Browser extension with subscription revenue is a Extension asset with $1,850 monthly profit and a orange risk rating. The first-pass memo is not about upside; it is about whether the buyer has enough proof to avoid a bad purchase.

Orange riskAsk
68risk
Asking price$29,000
Monthly profit$1,850
Annual multiple1.3x
Age31 mo

Executive Summary

Browser extension with subscription revenue is a Extension asset with $1,850 monthly profit and a orange risk rating. The first-pass memo is not about upside; it is about whether the buyer has enough proof to avoid a bad purchase.

Decision: Ask for the evidence package first; the deal may be viable, but the current listing is not diligence-ready.

Deal Facts

Marketplace
Acquire-style listing
Traffic
Chrome Web Store discovery and direct installs
Customers
3.4k installs, 420 paying users
Age
31 months

Risk Score Breakdown

Revenue quality58/100

Revenue appears less concentrated, pending direct verification.

Traffic quality55/100

Traffic risk is present but does not overwhelm the deal by itself.

Evidence quality68/100

Listing claims need direct platform access before pricing makes sense.

Transfer complexity74/100

Extension transfer has account, vendor, or platform handoff risk.

Platform dependency80/100

A single platform can materially change revenue after purchase.

Retention / repeatability46/100

Retention concern is moderate relative to the asset type.

Red Flags

  • Core claims are not yet backed by direct, read-only source access.
  • Transfer path could break value if accounts, rights, or platform assets cannot move cleanly.
  • Revenue depends heavily on a platform whose rules the buyer does not control.
  • Missing proof: Chrome Web Store transfer steps.
  • Missing proof: Extension permission audit.

Missing Evidence

  • Chrome Web Store transfer steps
  • Extension permission audit
  • Refund and cancellation history
  • Code repo commit history
  • Security issue log

Seller Questions

  • Can you document Chrome Web Store transfer steps and required permissions?
  • Can you share payment cancellation history and active subscriber cohorts?
  • What permissions does the extension request, and why?
  • Can you provide code repo history and any security issue log?
  • What exactly happens during transfer, and which accounts cannot be transferred directly?
  • Can you explain any month where revenue or traffic moved more than 20%?

Verification Checklist

  • Review store listing transfer requirements
  • Audit permissions, code, and security posture
  • Verify subscription cohorts and churn
  • Confirm domain, repo, payment, and support handoff
  • Reconcile claimed profit against payment, analytics, and expense records
  • Document every asset, login, vendor, and account required for handoff