u/Dramatic-Mess4084

After seeing a bunch of small SaaS deals and trying to price a few ourselves, we kept running into the same problem:

Everyone is either guessing or using completely inconsistent logic.

Some people anchor on revenue multiples, others on “what they feel it’s worth”, others on random comparable listings.

The result is always the same: → same type of product
→ wildly different valuations
→ no real baseline

What made it worse is that even when you have some data (traffic, early users, Stripe, niche demand), it still doesn’t translate cleanly into a single number.

So we ended up building a simple structured way to break it down:

• risk level (how fragile the product is)
• takeover complexity (how easy it is to run)
• traction signals (users, traffic, retention)
• revenue reality (if any exists)
• market demand strength

The goal wasn’t to “perfectly price SaaS”, just to stop pure guessing and give founders a consistent starting point before they list or negotiate.

It’s still early and pretty simple, but it already removes a lot of back-and-forth uncertainty we kept seeing in deals.

Curious how other founders here handle this — do you just rely on intuition, comps, or do you actually structure it in some way?

One thing I didn’t expect when building small projects:

Pricing them for sale is way harder than building them.

When it’s your own product, it’s hard to separate:

• time invested
• emotional attachment
• actual market value

I found myself either justifying higher numbers or second guessing everything.

What helped a bit was forcing myself into a more structured way of thinking about value instead of pure intuition.

Still feels like a gray area though.

How do you guys stay objective when pricing something you built yourself?

Trying to sanity check pricing before listing.

Let’s say a SaaS has:

• ~1–2k monthly visitors
• a few paying users (not stable yet)
• simple, clean codebase
• clear niche, not super competitive

No strong MRR, but also not just an idea.

I’ve seen similar things listed anywhere between $3k and $15k.

If you were buying this, what range would you realistically consider?

More importantly — what would make you increase or decrease that number?

After looking at a lot of listings and talking to a few buyers, I’m starting to think most micro SaaS founders get pricing completely wrong.

It’s usually one of two extremes:

• way too high → no serious buyers
• way too low → sells fast but leaves money on the table

And the main issue seems to be no clear baseline.

People mix:

• effort
• potential
• random comps
• gut feeling

And try to turn that into a number.

I had the same problem until I started structuring it a bit just to avoid guessing.

How are you guys avoiding this?

Or is everyone just accepting that pricing is mostly trial and error?

Trying to understand how buyers think before listing.

Let’s say a SaaS has:

• small but real traffic
• a few paying users (not consistent)
• clean codebase
• clear niche, but not super competitive

No strong MRR yet, but not just an idea either.

Would you consider buying something like this?

If yes — what would matter most in your decision?

Trying to figure out what actually reduces perceived risk from a buyer’s side.

Every time I try to estimate the value of a small SaaS, I end up overthinking it.

You’ve got:

• traffic
• niche demand
• tech stack
• revenue (if any)
• growth potential

And somehow you’re supposed to turn all that into a single number.

I’ve seen people either massively overprice or just throw a random number and “see what happens”.

Recently I tried using a simple structured approach just to get a baseline instead of guessing, and it actually helped a bit.

Still curious though — how do you guys do quick valuations without going too deep into analysis?

Something I’ve been trying to understand recently:

When it comes to selling a small startup, what matters more — actual revenue or early traction signals?

For example:

• consistent traffic
• growing user base
• strong niche demand

I’ve seen cases where projects with low revenue but clear traction seem more attractive than ones with small but stagnant income.

Makes me think buyers are sometimes optimizing for potential rather than current performance.

How do you guys see it?

If you had to choose, would you rather buy revenue or momentum?

I’ve been thinking about this a lot lately.

There are tons of small online projects and SaaS tools out there — some with a bit of traffic, some with a few users, some with early revenue.

But it’s not always clear when something crosses the line from “just a project” into something that’s actually sellable as a business.

Is it revenue? Profit? Stability? Or just having a clear path to monetization?

I’ve seen projects with barely any revenue still get acquired, while others with decent numbers struggle to sell.

Feels like there’s something more going on than just metrics.

How do you personally think about that threshold?

I’ve been browsing different marketplaces and communities where people sell micro SaaS, and I noticed a pattern.

A lot of projects with little or no revenue are listed at surprisingly high prices.

For example:

• $0 revenue but asking $10k+
• very small MRR but priced at 4x–6x multiples
• unclear traffic, but still positioned as “high potential”

I get that there’s always some subjective value (idea, niche, execution), but it still feels like many founders are just guessing the number.

Maybe I’m wrong, but it made me wonder:

How do you actually decide what your micro SaaS is worth?

Is there any logic behind it, or is it mostly trial and error?