SaaS product research tool
SaaS product research tool is a SaaS asset with $2,297 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.
Executive Summary
SaaS product research tool is a SaaS asset with $2,297 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
- Flippa-style listing
- Traffic
- 8.6k monthly visits, mostly organic and direct
- Customers
- 75 active subscribers
- Age
- 28 months
Risk Score Breakdown
Revenue appears less concentrated, pending direct verification.
Traffic risk is present but does not overwhelm the deal by itself.
Listing claims need direct platform access before pricing makes sense.
Transfer looks manageable if account ownership and vendor access are documented.
Platform exposure exists but does not dominate the whole memo.
Retention or repeatability needs cohort-level proof.
Red Flags
- Core claims are not yet backed by direct, read-only source access.
- Retention needs cohort proof; headline MRR is not enough.
- Missing proof: Read-only Stripe or Paddle access.
- Missing proof: Cohort retention report.
Missing Evidence
- Read-only Stripe or Paddle access
- Cohort retention report
- Support ticket volume
- Code repository history
- Customer concentration by MRR
Seller Questions
- Can you provide read-only payment processor access for the last 12 months?
- What caused the latest churn spikes, and which customer segments churn fastest?
- What percentage of MRR comes from the top 10 customers?
- Can you share support tickets, bug backlog, and code repository activity?
- 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
- Verify MRR in payment processor
- Review churn and cohort retention
- Inspect support queue and product backlog
- Confirm domain, code, account, and dependency transfer
- Reconcile claimed profit against payment, analytics, and expense records
- Document every asset, login, vendor, and account required for handoff