How to Buy an Online Tool or Web App

Online tools and web apps, browser extensions, productivity utilities, API services, calculators, and micro-SaaS products, can generate strong, recurring revenue with low overhead once established. The key advantage is scalability: a subscription-based tool with low churn and automated billing generates income with minimal ongoing effort. This guide covers every step, from evaluating user engagement metrics and auditing the codebase to assessing platform risk and completing the technical transfer. See also: general website buying guide, the website valuation guide, and the due diligence guide.

1. 1

   Define your tool and app investment criteria

   Before searching, establish your acquisition criteria: revenue model preference (subscription MRR, one-time license, usage-based, or freemium with paid tier), target monthly revenue range, acceptable owner time commitment, niche or problem domain, and whether you want a business that requires active development or one that runs on stable, largely maintenance-free infrastructure. Buyers with a development background can take on tools with technical debt or active feature roadmaps; non-technical buyers should target mature, stable tools with simple codebases, comprehensive documentation, and minimal ongoing update requirements. Decide upfront whether you can maintain the codebase yourself or will need to hire or retain a developer, this shapes both the type of tool to target and the price you should pay.

2. 2

   Understand how online tools and web apps generate revenue

   Online tools earn through four primary models: (1) Subscription MRR, users pay a monthly or annual fee for continued access. This is the most valuable revenue model because it is predictable and compounds with user growth. Monthly churn under 2% is healthy. (2) One-time license, users pay a fixed price for lifetime access. Revenue is unpredictable and requires constant new user acquisition; tools relying solely on one-time payments trade at lower multiples. (3) Usage-based pricing, customers pay per API call, data processed, or active user. Revenue can expand rapidly with customer growth but is harder to forecast and can drop sharply if a heavy user churns. (4) Freemium, basic access is free with premium features available for a subscription. A large free tier builds distribution but requires careful analysis of free-to-paid conversion rates (typically 2-5% of free users convert) and the infrastructure cost of supporting non-paying users.

3. 3

   Find online tools and web apps for sale

   Browse active tool and app listings on Buy Sites Direct, where owners sell directly with no broker or commission fees. Each listing shows the asking price, monthly revenue, owner time commitment, and a full business description. Focus on listings that disclose active user counts, monthly churn, revenue model, and infrastructure costs. Listings with subscription MRR, a growing active user base, and disclosed tech stack documentation are typically lower-risk acquisitions. Be cautious of tools where revenue is concentrated in a few high-paying accounts (revenue concentration risk), tools with heavy third-party API dependencies (platform risk), or listings where the seller cannot provide a month-by-month revenue breakdown for the trailing 12 months.

4. 4

   Evaluate MRR, churn, and user engagement metrics

   For subscription tools, the five most important acquisition metrics are: (1) Monthly Recurring Revenue (MRR), the sum of all active subscription revenue billed monthly. Verify against payment processor reports (Stripe, Paddle, Gumroad). (2) Monthly churn rate, the percentage of MRR lost each month to cancellations or downgrades. Under 2% monthly churn (roughly 22% annually) is acceptable; above 5% monthly churn signals product-market fit problems that cannot be fixed by the acquisition itself. (3) Activation rate, the percentage of new signups who reach the core value action within their first session. Under 15% suggests a broken onboarding experience with significant room for improvement. (4) Net Revenue Retention (NRR), whether existing customers are expanding, stable, or contracting their spending over time. Above 100% NRR means the existing customer base grows revenue without new acquisition. (5) Active user count trend, are monthly active users growing, flat, or declining over the past 6-12 months?

5. 5

   Audit the technical infrastructure and platform risk

   Online tools and web apps carry technical risks that do not exist in content sites or eCommerce stores. Before closing, assess: (1) Tech stack and codebase health, what language, framework, and hosting environment does the tool run on? Is the codebase documented? Are dependencies up to date, or are there known security vulnerabilities? Request a developer review before closing, or retain a freelance developer to audit the code. (2) API dependencies, does the tool's core functionality rely on a third-party API (OpenAI, Google Maps, Stripe, Twilio)? If so, verify API pricing, rate limits, and terms of service for commercial use. A price increase on a critical API can compress margins significantly. (3) Platform risk, is the tool distributed through a marketplace (Chrome Web Store, Shopify App Store, Apple App Store)? If so, review store policy compliance, current rating and reviews, and any recent policy changes that could affect the listing. (4) Infrastructure and hosting costs, what are the monthly hosting, database, CDN, and compute costs? Verify that gross margin after these costs is sustainable at the current user base.

6. 6

   Verify revenue, margins, and growth trajectory

   Request full revenue data for the trailing 24 months and verify against payment processor exports (Stripe dashboard, PayPal, Gumroad). Key verification steps: (1) Reconcile MRR with active subscription counts, the average revenue per user (ARPU) multiplied by active subscriber count should match reported MRR. Discrepancies indicate churn being hidden or revenue being mislabeled. (2) Verify infrastructure and API costs on a per-user basis, calculate gross margin after hosting, API calls, and third-party tool costs. A tool with $3,000/month MRR but $1,500/month in AWS and API costs has very different economics than the headline revenue suggests. (3) Check for revenue concentration, what percentage of MRR comes from the top 3 and top 10 accounts? If one account represents 20% or more of MRR, losing that customer post-acquisition would materially reduce profitability. (4) Verify growth trend, is MRR growing, flat, or declining? Flat MRR with low churn indicates stability; declining MRR requires a root cause diagnosis before proceeding.

7. 7

   Make an offer and structure the deal

   Online tools and web apps with subscription MRR and low churn typically trade at 3-5x annual SDE. Tools with only one-time purchase revenue trade at 2-3x annual SDE due to lack of predictable recurring income. Apply a discount if: (1) Monthly churn exceeds 3%, the value of the recurring revenue base erodes faster than the multiple implies. (2) The tool is heavily dependent on a single third-party API whose terms are unfavorable or pricing has increased recently. (3) The codebase has significant technical debt requiring immediate developer investment. (4) Revenue is concentrated, more than 20% from a single customer. Common deal structures: 100% upfront for small, stable tools under $30,000 with clean subscription MRR and low concentration; seller financing with 15-25% held over 6-12 months for larger deals; or a 30-day post-close MRR verification period where part of the purchase price is held in escrow and released only if the tool's MRR holds within a defined range of the sale price.

8. 8

   Complete the technical transfer

   Online tool transfers are primarily technical. The standard handover checklist: (1) Domain transfer, transfer the domain registrar login or initiate an EPP/auth code transfer for the primary domain. Allow 5-7 days for the registrar unlock and transfer process. (2) Hosting and infrastructure, transfer or migrate all server accounts, cloud providers (AWS, GCP, DigitalOcean), and deployment pipelines. Confirm all environment variables, API keys, and credentials are documented before the seller loses access. (3) Payment processor, transfer the Stripe, Paddle, or Gumroad account, or migrate active subscribers to a new payment account. Stripe supports direct account transfers for US businesses; international transfers may require subscriber re-subscription. (4) Codebase, transfer the GitHub, GitLab, or Bitbucket repository. Ensure the transfer includes all private dependencies, SSH keys, and CI/CD pipeline configuration. (5) App marketplace accounts, for browser extensions (Chrome Web Store), app store listings, or third-party marketplace listings, transfer the developer account ownership. Chrome Web Store group account transfers require Google's approval process. (6) Analytics and user data, transfer access to product analytics (Mixpanel, Amplitude, PostHog), error tracking (Sentry), and user databases. Confirm data transfer compliance with applicable privacy regulations.