discuss Why Stripe, Loom, and Notion All Paid 6-Figures for Their .com?

[Deleted Account]

The biggest SaaS brands of the last decade quietly paid six figures to acquire their .com. Here is why it was the highest-ROI line item on their balance sheet.

Stripe. Loom. Notion. Figma. Square. Each one paid six figures sometimes seven, to secure their .com after launch. From the outside it looks extravagant. From the inside it was the highest-ROI decision they ever made.

The math the press release never shows​

A typical seed-stage CAC for a B2B SaaS sits between $200 and $1,200. Direct-traffic conversions cost approximately zero. Even a conservative 5% lift in branded direct traffic over a 5-year window pays back a $250k domain acquisition many times over.

The .com is not an expense line. It is a permanent reduction to your customer acquisition cost.

Why they waited​

Most of them did not buy the .com pre-launch, as they could not afford it. They shipped on a workaround (.io, .ly, a misspelling) and bought the .com once revenue justified it. The catch: by the time they could afford it, the price had moved 5–20x because the squatter saw the traction.

The lesson is not "wait until you can afford it." The lesson is "buy it as early as you can, before your own success inflates the price."

How to skip the waiting tax​

The reason these acquisitions cost six figures was almost always the negotiation, not the asset. The buyer reached out, the seller saw a funded startup, and the price quintupled.

A request-first marketplace fixes this. The buyer posts a brief without revealing identity. Sellers compete on price for an anonymous, qualified buyer instead of pricing against your funding announcement. Combined with [structured escrow](/blog/domain-escrow-explained-2026), the deal closes at fair market, not "Series B markup."

What this means for you​

If you are early, treat the .com as a Series Seed line item, not a Series B reward. The discount you get from buying early -and buying anonymously- is the difference between a $30k acquisition and a $300k one.

 

[Jannes]

by the time they could afford it, the price had moved 5–20x because the squatter saw the traction

Squatter? Which side are you on?

 

[E. Silvera]

Hi @Nomirio ,

Welcome to NamePros.

For the sake of clarity, please provide your definition of "squatter". Each domain name can be held legitimately, or squatted, depending on certain specific circumstances.

Squatter? Which side are you on?

It's not a matter of "sides", which is subjective, but of concept, which is objective and has been precised for legal purposes by the competent authorities.

 

[E. Silvera]

A request-first marketplace fixes this. The buyer posts a brief without revealing identity. Sellers compete on price for an anonymous, qualified buyer instead of pricing against your funding announcement. Combined with [structured escrow](/blog/domain-escrow-explained-2026), the deal closes at fair market, not "Series B markup."

Regarding this, specifically: if the potential buyer wants one name, and that name only, and such name is already taken, there's no possible "seller competition".

Each domain name is unique, and was first made available for registration on a "first come, first served" basis; hence, scarcity: the key factor determining market value.

 

[E. Silvera]

So, this boils down to the fundamental question: is the current owner a legitimate holder or not?

If the latter is true, there are established mechanisms to act and seek a solution.

If, instead, they are legitimately holding the domain, they are free to keep on holding it (even for the sole purpose of waiting until the right sale happens), develop it, or give it away/let it drop. Negotiation is the only feasible option in that case.

 

[E. Silvera]

This is some of the worst AI slop I've seen in a while. Factually wrong on many levels and I will be suing for time wasted reading it.

OP does appear to have been AI-generated, sure.

As for my posts, I spent some of my time. which is as valuable as yours or anyone's, replying to OP and @Jannes, because I thought it could contribute to a reasonable discussion. I take that that didn't happen, eventually.

But I would sincerely appreciate your feedback on what you think is wrong in what I wrote.