How to Evaluate 10 Small Digital Projects Without Losing Your Mind

A two-stage framework for evaluating multiple small digital projects fast – without spreadsheets, second-guessing, or decision fatigue.

You start with enthusiasm. You look at the first three listings carefully – revenue charts, traffic sources, seller notes. You ask good questions. You feel like a serious acquirer.

By project seven, you're comparing it to a memory of project two, which you're now not sure you read correctly. By project ten, you've forgotten what you were looking for. You're still evaluating. Nothing has moved.

This is how most first-time buyers stall. Not from lack of trying – from lack of a system. Evaluation without a repeatable framework doesn't compound. It just accumulates.

The buyers who close deals at this size aren't necessarily more analytical. They're faster and more ruthless at the front end.

Why your process breaks down before you realise it

The problem isn't the tenth project. It's the third.

Without a consistent filter, every new listing gets evaluated on its own terms – you adjust your criteria based on what you're seeing, which feels reasonable but is actually just anchoring to the last thing you read. A project with impressive traffic but no revenue starts to look acceptable if the one before it had neither. Your standards drift without you noticing.

The cognitive load compounds. Each project you add to "the shortlist" isn't just one more option – it's another comparison point you have to hold in your head. At ten projects, the mental overhead of the shortlist is larger than any individual project deserves.

What experienced acquirers do is structurally different. They don't evaluate projects more carefully. They eliminate them faster.

Stage 1: the 15-minute screen

Before you read anything else, run three checks. In order.

First: revenue consistency, not growth. Review whatever monthly revenue history exists – a clean twelve-month record is rare at this size, so the last three to six months is usually the signal that matters. You want a stable base – flat is fine, slow growth is fine, seasonal dips are fine if they're predictable. Erratic swings with no explanation are a signal to stop, not investigate. If the seller can't account for the variance, neither can you after you own it.

Second: traffic source. Where does the majority of traffic come from? One channel – paid ads, one social platform, a single referral partner – is a dependency worth noting. It isn't automatically fatal, but it changes what you're actually buying. A project built on organic search is worth a different price to one built on the founder's Twitter following that won't transfer with the domain.

Third, and this is the one most buyers skip: transferability signal. Can this project realistically operate without its current owner? Look for documented processes, no personal brand dependency, automated or outsourced delivery, customer relationships that aren't founder-specific. If the answer requires significant assumptions, note it and move on.

Total time: 15 minutes. If a project fails any of these, stop. Not pause – stop. You're looking for reasons to eliminate, not reasons to continue.

Most listings won't pass this screen. That's correct. The purpose of Stage 1 is to make Stage 2 rare.

Stage 2: the one conversation that matters

Projects that pass Stage 1 earn a real conversation. On most small deals that's a focused back-and-forth by message rather than a call – though either side can suggest one, and a short call is sometimes the fastest way through. However it happens, the goal is the same: direct questions, direct answers, and room to follow up.

This exchange is the most information-dense window in any sub-$50k acquisition. Documents can be prepared, numbers can be cherry-picked, and listings can be optimised. A direct back-and-forth – especially once you start asking follow-ups – is harder to stage-manage. You're watching for what's easy to answer versus what gets vague, deflected, or quietly skipped.

The single question that reveals the most: "Describe your average week running this."

Not "what are your responsibilities" – that's rehearsed. Not "what does the business do" – you know that. Ask them what they actually do with their time. A seller who runs a genuinely transferable project will describe tasks. A seller who is the product will describe relationships, judgment calls, and context that took years to develop. Both can be worth buying. They are not worth the same price, and they don't carry the same risk.

Secondary questions worth asking: What broke in the last six months, and how did you fix it? What would you do differently if you were starting today? What's the thing you're most uncertain about?

Watch for specificity. Vague answers aren't always dishonesty – sometimes they're just a sign the owner hasn't thought about it. Either way, it tells you something.

Comparing across a shortlist

After Stage 1 and Stage 2, you should have a small shortlist – two to four projects, ideally fewer.

At this point, the temptation is to build a detailed comparison matrix. Resist it. At sub-$50k deal sizes, the matrix creates false precision. You don't have the data quality to justify 40-column spreadsheets.

Instead, score each project on three dimensions only:

1. Revenue consistency – how predictable is the cashflow you'd be acquiring?
2. Transferability – how much of the value walks out with the seller?
3. Your fit – do you have, or can you develop, whatever this project needs from its operator?

Weight them equally. The project with the best combined score is usually the right one – not the one with the highest multiple or the flashiest growth chart.

One more note: at this deal size, growth potential is a bonus, not a criterion. You're acquiring an operating asset. Buy it on what it is. If you make it grow, that's value you created, not value you paid for.

When to stop evaluating and decide

There's a version of due diligence that functions as a delay mechanism. You haven't decided not to buy – you've just kept yourself busy enough not to have to decide yes.

Good projects at this size sell. Not always fast, but fast enough. The window between "I'm seriously interested" and "I need to move" is shorter than most buyers expect, particularly on projects that are priced accurately and have clean metrics.

"Good enough to move" looks like this: the revenue is real, the traffic source is defensible, the seller can explain their operations clearly, and the transferability risk is something you can manage or price in. Not perfect. Manageable.

The opportunity cost of evaluation at volume is invisible until it isn't. While you're comparing projects twelve and thirteen, project one – which passed your screen and your seller call – went under offer to someone with a faster process.

Decide on the criteria before you start evaluating. Apply them consistently. Stop when something passes them.

The buyers who acquire well at this scale are not the most analytical. They're the most consistent. A repeatable two-stage filter applied to every project you look at will serve you better than a bespoke deep-dive applied to whatever catches your eye.

On a well-curated platform like Indiemaker, pre-screened listings with verified metrics compress Stage 1 considerably – the obvious eliminations are already done. Stage 2 is still yours to run. That conversation can't be delegated or skipped.

The framework isn't complicated. The discipline to stop at Stage 1 when something fails is.

Further reading:
- Thinking in Bets – Annie Duke – on how to make decisions with incomplete information, which is every acquisition decision you'll ever make