Most of what gets written about acquiring small online businesses is aimed at people who have never run anything. The advice tends to skew toward generic checklists and toward dramatizing the difference between a product that bills three hundred dollars a month and one that bills three thousand. If you have spent any time around bootstrappers, the picture on the ground looks different. There is a real and active market in tiny revenue streams, most of it is invisible from the outside, and the buyers who do well in it are the ones who treat the process as a normal procurement decision rather than a romance.
This is the rough mental model we keep coming back to in advisory calls when a founder asks us whether they should buy a small product instead of building one. It is not legal or accounting advice. It is the version we would give a friend over coffee.
Where they actually live
The headline marketplaces are the obvious starting point and the worst place to actually transact. Acquire.com, Flippa, Tiny Acquisitions, IndieMaker, and the smaller boutique brokers all publish a steady flow of listings, and reading those listings will teach you a lot about what these businesses look like even if you never bid. The catch is that the strong listings tend to close quickly to repeat buyers, and the listings that linger have usually lingered for a reason that the seller has decided not to surface in the headline numbers.
The right way to use the marketplaces is as a shopping window rather than a deal source. Read every listing in your category for a few weeks, run rough numbers in your head, and form a view on what a normal asking multiple looks like for the kinds of products you would actually be willing to operate. By the end of a month you will have a working sense of the market, a feel for which listings are real and which are dressed up, and a shortlist of brokers worth giving your inbox to.
Off-market deals are where most of the genuinely good outcomes happen. A bootstrapper running a quiet thousand a month product nobody talks about is rarely listed on Acquire.com. They are usually on Indie Hackers, on a small Discord, on Twitter, or simply running their thing quietly and answering email. If you can identify a niche you understand and you reach out personally to the operators inside it, you can have completely different conversations from the ones happening on public listings. The cost is real time investment over months. The upside is that you are often the only buyer at the table, which changes the math substantially.
A third source worth mentioning is your own network. Founders who decide to sunset a product almost always tell at least one peer first. If your peer group includes people building things, make sure they know you are the kind of buyer who would take a small product off their hands cleanly. You will see deal flow that never reaches any listing.
Get clear on what you are actually buying
Before evaluating any specific deal, get clear on what category of asset is on the table, because the right questions depend on it.
A small product business is some combination of code, customers, brand, content, distribution, and the founder's labor. The mix varies enormously. A productized service with two thousand a month in retainers and a personal email signature attached is mostly the founder. A self-serve micro SaaS with a thousand monthly customers and a clean Stripe dashboard is mostly distribution and code. A content site that ranks for a stable set of keywords is mostly content and links. A side product that lives entirely inside another platform's marketplace is mostly platform risk pretending to be a business. Same headline number, very different assets.
A working rule of thumb. If the founder personally is a meaningful share of why customers stay, you are not just buying a product, you are buying a transition project. That can still be a very good deal, but you need to price the transition into your offer rather than discover it after closing.
What to look for
Once you have a candidate in front of you, the questions you want answered fall into a few groups. None of them are clever. The cleverness shows up in how seriously you push for real answers when the seller would prefer to hand you a dashboard screenshot and move on.
The first group is revenue quality. You want to know who is paying, how long they have been paying, and how concentrated the revenue is across customers. A product with one thousand a month spread across two hundred small customers is a different asset from a product with one thousand a month coming from two enterprise contracts that renew once a year. Ask for an anonymized export of the last twenty four months of charges directly out of Stripe or whatever billing system runs the business. If the answer is "we don't have that," that is itself information about how the business is run.
The second group is churn and engagement. Logo churn matters, revenue churn matters more, and engagement matters most of the three. A subscription product where customers have stopped logging in is a subscription product whose customers will eventually cancel, even if the current month looks fine. Ask for active session counts, last login distribution, and the trend over the last twelve months. Sellers who run their business this way will produce these numbers. Sellers who do not should still be able to pull them quickly given access to their own logs.
The third group is the operator role. Spend an honest hour mapping what the current owner does each week to keep the lights on. Customer support, billing exceptions, content updates, infrastructure babysitting, partnership emails, the renewal nudges. Multiply your honest answer by a small fudge factor because founders consistently underestimate their own labor. If the picture you end up with does not match a role you would actually be willing to fill yourself, the deal is wrong for you regardless of price.
The fourth group is the technical surface. You do not need a perfect codebase. You need a codebase that you can take responsibility for without holding your breath. Look for a stack you can hire for, a small number of moving parts, a clean deployment story, and an absence of dependencies that only the current owner knows how to refresh. A scrappy app on a boring stack is almost always a better acquisition than a clever app on an exotic stack at the same price.
The fifth group is growth dynamics. You want to know whether the current MRR is the natural ceiling of the current effort or the floor. Products that grow because the founder runs ads are very different from products that grow because customers tell their friends. A product whose growth depends entirely on the founder's audience may have a much lower steady state value once that audience has moved on to a new project, which it eventually will.
How to think about price
The temptation is to anchor on a multiple. Three times annual profit, four times, five times. Multiples are a useful sanity check but a poor anchor. The right starting point is your own model of what the next twelve months will actually look like under your ownership, with realistic assumptions about churn, your own time, the cost of any tooling you would change on day one, and a haircut for the inevitable surprise. Whatever price falls out of that model is the upper end of what you should pay. A reasonable offer sits comfortably below it.
If you cannot build a believable twelve month model from the diligence material in front of you, the deal is not ready to be priced. That is not a moral judgment about the seller. It just means the package needs more work before either of you can transact responsibly.
When to walk
A few signals reliably mean walk. Numbers that do not reconcile across the dashboard, the bank statements, and the export. A seller who declines to answer specific questions in writing. Concentration of revenue in a customer who happens to be a personal friend of the seller. Hidden dependencies on infrastructure that lives in the seller's personal accounts. Any structure that requires the seller to stay in the loop indefinitely after closing.
None of these are individual dealbreakers. They are all expensive to clean up. If you choose to take them on anyway, take them on with your eyes open and your price adjusted.
What buying changes for you
The last point is the one most buyers underweight. A product that bills monthly is not a piece of software you bought. It is an ongoing operational commitment with customers attached. You are now the person whose inbox is on the receipt, whose late night incident page is the page, and whose name eventually goes on the email when the renewal cycle hits. Buy something whose work you would do anyway, at a price you would still feel good about if revenue stayed flat for a year, and acknowledge to yourself in writing that you are signing up for an operating role rather than acquiring a passive asset.
Done well, buying a tiny revenue stream is one of the cleaner ways to put capital and time to work in software. Done badly, it is an expensive lesson in how rarely a deck and a dashboard tell the whole story. The difference is almost always how much real work you did in the boring parts of diligence before you signed.