Seller asking price
$620,000
As stated in the fictional listing
Fictional data onlyTry the file intake
MNSeller data room · MN-042
MetricNest
Organic visibility monitoring for independent ecommerce brands
Seller-stated MRR
$18,420
Active customers stated
286
Seller asking price
$620,000
Data snapshot
June 30, 2026
This fictional buyer-side review organizes seller claims and evidence gaps. It is not a valuation, investment recommendation, or prediction of performance.
Open the full workpaper →Analyst readout · next step
Request native revenue and traffic sources before relying on the seller’s headline metrics.
The seller-reported revenue trend is positive, but the supplied package does not yet support an independent revenue tie-out. Traffic exposure is concentrated in organic search and two landing pages; retention and operating workload remain unverified. The next useful step is to obtain native, transaction-level source exports before relying on headline metrics.
Seller request pack
6 evidence requests selected · 5 priority questions
Price / stated monthly MRR
33.7×
Asking price ÷ $18,420 stated MRR
12× stated MRR
$221,040
Mechanical annualization; not audited revenue
Price / annualized stated MRR
2.80×
Arithmetic only; not a valuation or market benchmark
Revenue Integrity
Tie-out required
Reported MRR rises to $18,420, while the partial bank sample still has a $560 item to explain. Payout counts are not a dollar-based revenue reconciliation.
Billing detail and complete processor-to-bank bridge not provided
Traffic Durability
Concentrated
The seller summary attributes 71% of sessions to organic search; two landing pages represent 46% of organic visits, with a reported 18% quarter-over-quarter decline.
Seller summary only; native analytics and Search Console access absent
Data Confidence
Partial evidence
A first-pass review is possible, but key claims cannot yet be reproduced from source systems or customer-level records.
Cohort export, invoice detail, and native traffic sources missing
Seller-reported MRR trend
Billing summary provided by the seller · USD · not independently reconciled
$15.2KSeller-reported MRR · USD$18.4K
JanFebMarAprMayJun
Latest month: 5.1% increase versus May.
Six-month change: 21.2% from $15,200 to $18,420.
Both changes are calculated from the seller-provided monthly series. They describe the submitted figures, not verified collections, customer retention, or a forward forecast.
Evidence register
What is in the sample data room and what it can support
Billing exportMonthly MRR trend through June 2026; seller reports $18,420 for June.Summary received
Limit: No invoice-level rows, customer identifiers, refund ledger, or plan-change detail.
Processor and bankAbout 91% of expected payout rows were identified by count; $560 remains unassigned.Partial sample
Limit: No complete period, gross-to-net bridge, fee detail, or dollar coverage percentage.
Web analytics71% organic session share and landing-page concentration were reported.Seller summary
Limit: No native GA4 export, event definitions, conversion mapping, or consent context.
Search performanceTwo pages account for 46% of organic visits; organic traffic is reported down 18% QoQ.Seller summary
Limit: No Search Console page/query history or branded-versus-non-branded split.
Customer retention286 active customers and 3.4% monthly logo churn are seller-reported figures.Not provided
Limit: No cohort export, denominator, cancellation event definition, or revenue retention view.
Owner workload and handoffA questionnaire says the founder handles first-line support and editorial production.Not substantiated
Limit: No time log, recurring task inventory, runbooks, or access/dependency register.
A seller-provided export is a lead for verification. It is not independent confirmation of the source system or the underlying transaction.
Documented diligence issues
Findings, evidence & tests
Priorities describe sequencing for this fictional review, not a prediction of loss or a recommendation to transact.
01Reported MRR is not yet reconciled to cash settlementRevenue · Seller billing export and partial bank samplePriority 1
Evidence observed
- The seller billing export reports $18,420 MRR as of June 30, 2026.
- The supplied bank sample identifies about 91% of expected payout rows by count; the sample period and expected-row denominator are not documented.
- $560 remains unassigned. The file does not show whether it reflects processor fees, refunds, timing, reserves, or a different issue.
- The reported 91% is a row-count match, not 91% of revenue dollars. It cannot be used as a cash-coverage percentage.
Source quality: Seller-supplied summary plus incomplete bank evidence; no independent source access.
Analyst interpretation
There is not yet a supportable bridge from customer billings to processor payouts and bank deposits. A count-based match can conceal large or systematically missing dollar items.
Open uncertainty
Gross versus net MRR, taxes, annual plans, discounts, failed payments, refunds, chargebacks, reserves, fees, and payout timing have not been defined or independently checked.
Recommended test procedure
- 1Obtain 12 months of invoice and subscription rows with stable customer IDs, invoice status, currency, plan, billing interval, discounts, credits, and timestamps.
- 2Obtain processor balance transactions, payout batches, fee schedules, refunds, disputes, reserves, and complete matching bank statement lines for the same dates.
- 3Build a month-by-month bridge: gross billings → credits/refunds → processor fees and adjustments → net payout → bank deposit; retain IDs that link each stage.
- 4Reperform the June MRR calculation from active paid subscriptions and separately list timing items, annual-plan treatment, failed collections, and one-time charges.
Evidence to close this issue
A reviewer can reproduce the June MRR from source rows, trace payout batches to bank lines, and see every remaining variance itemized with supporting documentation and an agreed scope.
02Organic acquisition is concentrated and the reported trend is weakeningTraffic · Seller analytics summary and landing-page exportPriority 1
Evidence observed
- Organic search is reported as 71% of sessions.
- Two landing pages are reported to generate 46% of organic visits.
- The shared summary reports an 18% quarter-over-quarter decline in organic traffic.
Source quality: Summary supplied by the seller; native GA4 and Search Console data not delivered.
Analyst interpretation
A channel-level share and a small number of high-volume entry pages can create exposure if those pages lose rankings or conversion efficiency. Session volume alone does not establish trial starts, paid conversions, or revenue contribution.
Open uncertainty
The comparison window, seasonality, branded traffic, bot filtering, attribution rules, event quality, and page-to-paid-customer conversion are unknown. The reported decline has not been reproduced in a native source.
Recommended test procedure
- 1Request 16 months of read-only GA4 data by month, channel, landing page, country, device, and defined funnel event; include property time zone and consent configuration.
- 2Request 16 months of Search Console page and query exports with clicks, impressions, CTR, average position, device, and country.
- 3Separate branded from non-branded demand and reconcile GA4 organic sessions to Search Console clicks, noting the expected measurement differences.
- 4For the top landing pages, compare sessions → qualified signup → paid conversion by month and identify content, ranking, or product changes that coincide with movement.
Evidence to close this issue
Native, date-aligned exports reproduce the channel and page shares, explain the quarter-over-quarter movement, and show which pages and query groups contribute to qualified signups and paid customers.
03Retention claims cannot be reproduced from customer-level dataRetention · Seller overview; customer cohort export absentPriority 1
Evidence observed
- The seller reports 286 active customers as of June 30, 2026.
- The seller reports 3.4% monthly logo churn, but has not defined the starting population or event rules.
- The data room contains no monthly customer cohort, cancellation, failed-payment, pause, or refund detail.
Source quality: 286 active customers and 3.4% monthly logo churn are stated figures without supporting rows.
Analyst interpretation
The current package does not support a re-performance of logo churn, gross revenue retention, or net revenue retention. A single churn percentage is not comparable without a fixed definition and cohort basis.
Open uncertainty
The observation window, new-customer treatment, involuntary churn, reactivations, pauses, downgrades, annual renewals, and revenue denominator are unknown. No annualized churn or lifetime-value inference should be drawn from the stated rate.
Recommended test procedure
- 1Request a pseudonymous customer/subscription export with start, paid-through, cancellation, reactivation, pause, plan-change, invoice, and refund dates.
- 2Agree written definitions for active customer, logo churn, gross revenue retention, and net revenue retention before calculating them.
- 3Rebuild monthly starting cohorts and reconcile opening customers + new customers − churned customers ± reactivations to ending customers.
- 4Recalculate gross and net revenue retention separately, documenting treatment of expansion, contraction, refunds, and annual billing.
Evidence to close this issue
The 286 active-customer count and stated churn can be reproduced from dated source rows, with definitions, cohort movement, and revenue-retention calculations visible for review.
04Founder-dependent work and transfer requirements are not sizedOperations · Seller questionnaire; operating records absentPriority 2
Evidence observed
- The seller says they handle first-line support and editorial production.
- No monthly hours by activity, operating calendar, or support-volume history was supplied.
- No runbook, privileged-access inventory, backup/restore evidence, or transition plan is in the sample data room.
Source quality: Narrative response only; no recurring-work log or system ownership map.
Analyst interpretation
The questionnaire identifies workstreams that may need to transfer, but does not establish how much work they require or whether critical systems can be operated without the founder.
Open uncertainty
Support volume, release practices, contractor involvement, infrastructure ownership, incident history, recovery objectives, and post-close availability are unverified.
Recommended test procedure
- 1Request a 90-day support ticket sample and a 4-week time log split across support, engineering, content, billing, and administration.
- 2Map systems, domains, cloud accounts, repositories, payment/analytics ownership, third-party dependencies, recovery contacts, and administrator access.
- 3Ask the seller to demonstrate the deployment, backup restore, customer escalation, and content-publishing workflows using a written runbook.
- 4Document the proposed transition period, hours, named owner, handoff artifacts, and any work that remains dependent on the seller.
Evidence to close this issue
A buyer can name an owner and documented procedure for each recurring task and critical account, with transfer steps and post-close support explicitly agreed.
Prioritized evidence requests
Select the items to include in the copy-ready seller pack.
- P1
12-month invoice, subscription, refund, credit, and plan-change export
Why it matters: Reperform reported MRR and distinguish recurring subscription revenue from timing items and one-time amounts.
Minimum usable deliverable: CSV with stable pseudonymous customer IDs, invoice/subscription IDs, timestamps, status, currency, gross amount, discount, tax, credit/refund, and plan interval.
- P1
Processor balance transactions, payout batches, fee detail, and matching bank lines
Why it matters: Explain the $560 variance and convert the payout-row match into a complete dollar-based settlement bridge.
Minimum usable deliverable: Same 12-month period; transaction and payout IDs retained; complete statement pages; every unmatched or adjusted item annotated.
- P1
16-month read-only GA4 landing-page and funnel export
Why it matters: Reproduce channel mix and determine whether concentrated sessions create qualified trials and paid customers.
Minimum usable deliverable: Monthly source/medium and landing-page rows with sessions, defined signup/trial/paid events, country, device, property time zone, and event definitions.
- P1
16-month Search Console page and query history
Why it matters: Validate the reported organic decline, top-page concentration, branded demand, and query-level exposure.
Minimum usable deliverable: Native monthly page/query export with clicks, impressions, CTR, average position, device, and country, including property and export dates.
- P1
Pseudonymous subscription lifecycle and customer cohort export
Why it matters: Recalculate active customers, logo churn, gross revenue retention, and net revenue retention using agreed definitions.
Minimum usable deliverable: Customer/subscription ID, start/end/paid-through dates, plan and amount history, pause/reactivation, failed payments, cancellations, refunds, and renewal events.
- P2
Recurring task log, critical-system map, runbooks, and transition proposal
Why it matters: Size owner dependency and establish who can operate the product, support customers, and recover critical systems after handoff.
Minimum usable deliverable: Named system owners, admin-access transfer steps, recurring hours, support sample, tested recovery procedure, runbook links, and seller availability by week.
Priority seller questions
Each question is paired with its diligence purpose and the evidence to request.
01Can you walk us from June billed subscriptions to each processor payout and bank deposit?
Why ask: The current 91% match is measured by payout-row count, while the file still carries a $560 item and does not show dollar coverage.
Follow-up: Which billing period and expected-payout denominator were used? How are fees, refunds, reserves, failed payments, annual plans, and settlement timing treated?
Request: Invoice-level export, processor balance transactions and payout IDs, fee/refund ledger, and complete corresponding bank lines for 12 months.
02What is included in the $18,420 June MRR calculation?
Why ask: A headline MRR figure is not reproducible until active-subscription, discount, annual-plan, failed-payment, tax, and one-time-revenue rules are explicit.
Follow-up: Please show the calculation at customer/subscription level and identify any manual adjustments or excluded accounts.
Request: June 30 subscription snapshot, plan/price history, invoice statuses, and the written MRR definition used in the listing.
03Can you reproduce the 71% organic share, 46% top-two-page share, and 18% quarterly decline from native exports?
Why ask: Those three claims describe different views of exposure; the summary does not establish conversion contribution or source-system integrity.
Follow-up: What are the exact comparison dates, branded versus non-branded splits, page-level conversions, event definitions, and any tracking changes?
Request: 16 months of GA4 landing-page/channel funnel exports and Search Console page/query exports with property settings and export timestamps.
04How is the stated 3.4% monthly logo churn calculated?
Why ask: The result changes materially depending on starting population, cancellations, pauses, failed payments, reactivations, and annual renewals.
Follow-up: Please define the numerator, denominator, event date, observation window, and treatment of involuntary churn and returning customers.
Request: Pseudonymous subscription lifecycle rows and the seller's monthly churn workbook or query logic.
05Which recurring tasks and critical systems still depend on you personally?
Why ask: The questionnaire names support and editorial work but does not size hours, access, process knowledge, or recovery dependencies.
Follow-up: What would stop operating for one week if you were unavailable, and what handoff or training would remove that dependency?
Request: Recent support sample, four-week work log, system/access map, deployment and recovery runbooks, and proposed transition calendar.
Suggested workplan
Verification sequence & expected workpapers
Indicative review effort assumes complete, usable exports and read-only access. It excludes seller response time and follow-up exceptions.
Workstream 01
Rebuild the revenue-to-cash bridge
Objective: Establish whether the seller's June MRR can be reproduced and whether billed amounts settle to the bank as represented.
- 1.Normalize invoice, subscription, processor, payout, and bank rows to a shared period and stable IDs.
- 2.Recompute active recurring billings under a written MRR definition; exclude one-time items and list exceptions separately.
- 3.Bridge gross billings to net settlements and bank deposits; investigate unmatched counts and dollar variances separately.
Effort: 60–120 minutes after complete exports are received
Workpaper: A monthly tie-out workbook with source links, definition notes, variance categories, and a list of unresolved rows.
Depends on: Invoice/subscription export, processor ledger and payout detail, fee/refund data, and complete matching bank statements.
Workstream 02
Reproduce organic demand and page concentration
Objective: Validate the seller's traffic claims and connect channel/page movement to signup and paid conversion events.
- 1.Rebuild the monthly channel mix and top landing-page shares from native exports.
- 2.Compare like-for-like periods, brand versus non-brand queries, device/country segments, and any tracking changes.
- 3.Trace the top landing pages through qualified signup, trial, and paid conversion; document where source systems cannot be reconciled.
Effort: 60–90 minutes with read-only source access
Workpaper: A 16-month channel/page trend table, concentration view, conversion contribution summary, and exceptions log.
Depends on: GA4 landing-page/event export, Search Console page/query export, and written event definitions.
Workstream 03
Recalculate customer retention
Objective: Test the seller's active-customer count and churn claim using consistent monthly cohorts and event rules.
- 1.Agree the definitions for active, churned, reactivated, paused, and paid-through before calculation.
- 2.Reconcile opening customers, additions, churn, and reactivations to monthly ending customers.
- 3.Calculate logo churn, gross revenue retention, and net revenue retention as separate measures with stated denominators.
Effort: 45–90 minutes after the lifecycle export is received
Workpaper: A cohort table with formulas, customer-count movement, revenue retention, and definition notes.
Depends on: Pseudonymous subscription lifecycle rows, invoice amounts, plan changes, cancellations, pauses, and refunds.
Workstream 04
Map operating continuity and handoff
Objective: Identify work, accounts, and recovery knowledge that must transfer for a buyer to operate the service.
- 1.Inventory recurring tasks, time spent, current owner, deadline, and operating consequence if missed.
- 2.Map administrator access and third-party dependencies without collecting credentials in this demo.
- 3.Review deployment, incident, backup-restore, support-escalation, and content workflows; list undocumented steps.
Effort: 60–90 minutes plus seller walkthroughs
Workpaper: A transfer register with task/system owner, handoff artifact, open dependency, and proposed transition owner.
Depends on: Seller work log, system map, runbooks, support sample, and a defined seller transition window.
Full diligence workpaper
Keep the evidence, limitations, and next tests together.
The sample report expands each issue into a source note, verification procedure, buyer question, and workpaper output.
Scenario figures, seller claims, and data-room items are fictional. No source-system integrations are active. Arithmetic is descriptive only and is not financial, legal, tax, or investment advice. Share feedback on this sample review.