Seven pricing mistakes onchain TLD holders make

Most holders arrive at a number before they have spoken to anyone. The number feels grounded because it came from somewhere: an asking price they saw, a conversation with another holder, a rough projection of what names issued under the TLD might one day earn. The problem is that none of those sources answers the question a buyer will actually ask, which is not “what is this worth to you?” but “what is this worth to me, compared with everything else I could do with that capital?”

The gap between those two questions is where deals fail. A number that cannot survive a buyer’s first round of diligence either collapses the negotiation or prevents it from starting. The holder is left with the asset, often without understanding what went wrong.

This article walks through seven specific errors that produce a number a buyer will not accept. Each one is common, each one has an internal logic that makes it feel like sound reasoning at the time, and each one has a correction. Hold your own number against each of them in turn. The section after the seventh describes how a defensible range is built instead of a single figure.

Mistake 1: pricing the string, not the buyer

The string is the characters that make up the TLD. The buyer is a specific organization with a specific reason to want control of that namespace. These are not the same thing, and pricing the string instead of the buyer is the most expensive error a holder can make.

It is tempting because the string is the only thing you can see from where you sit. It is short or long, a dictionary word or an invented one, easy or hard to spell. Those properties can be compared across TLDs, and comparison feels like analysis.

A string acquires value only when a particular buyer has a use for it. Consider an invented case: a mid-length word that happens to be the registered trademark of a mid-sized manufacturer in a regulated industry. To a casual observer comparing it with other TLDs of similar length and apparent appeal, the string looks ordinary. To the manufacturer’s general counsel, control of that namespace is a brand protection matter with a budget behind it. The ceiling for that one buyer is far higher than for any other, and nothing in the string itself reveals it.

The correction is to think about the population of organizations for which this TLD is not merely attractive but specifically necessary or strategically significant. A TLD such as .yourbrand, which matches a registered trademark, sits in a different conversation than a sector word such as .yoursector. A TLD whose names already resolve in the wallets a buyer’s users rely on sits in a different conversation than one whose names do not. A TLD under which a community has already formed sits in a different conversation than a blank namespace. Knowing which conversation you are in before you set a number is the foundation of sound pricing.

The practical test is short. Write down the names of the organizations, or at least the precise kind of organization, that would have a reason to hold this TLD and no substitute for it. If the list is empty, the string is being priced on its looks. If the list holds one entry, the number depends almost entirely on that one buyer’s situation, and you should know it before they do.

Mistake 2: anchoring on someone else’s asking price

Asking prices are public. Closing prices are rarely disclosed. A holder who forms a number by looking at what other holders ask for their TLDs has anchored on the least reliable data available.

An asking price reflects what another holder hopes to achieve, not what a buyer agreed to pay. The difference can be substantial in either direction. An asking price that has stood for a long time without a sale is evidence that it was too high, not evidence that the market will eventually meet it. An offer that was withdrawn without explanation could mean a sale closed privately below the figure, or above it, or that the holder simply changed their mind. None of those outcomes is visible from outside.

The broader problem is that anchoring on an asking price imports someone else’s mistake into your own reasoning. If the other holder priced the string instead of the buyer, you have now done the same thing at one remove. If the other holder had unrealistic expectations about subname revenue, those expectations are now embedded in your number without your knowing it.

There is also a selection effect. The asking prices you notice are the ambitious ones, because ambitious figures get repeated and modest ones do not. A sample built from what caught your attention leans high before you have done any reasoning at all.

The correction is to treat asking prices as background at most. They tell you something about the general mood among holders. They do not tell you what your specific TLD is worth to your specific set of potential buyers. Only the buyer’s own situation can tell you that.

Mistake 3: treating a single unverified sale as a comparable

A comparable sale is a data point from which a range can be inferred. A single unverified sale is an anecdote. Holders often use anecdotes as if they were comparables, and the results are poor.

The problems with a single reported sale are layered. First, the terms are usually unknown. Was the consideration paid entirely in cash, or partly in tokens at a value that has since changed? Were there deferred payments tied to future registration volume? Was the seller also receiving services from the buyer that had their own value? A number stripped of its terms is not a price. It is a figure.

Second, the sale may not have occurred as reported. The registry record is public, so the fact that a TLD moved from one wallet to another can be checked on a block explorer. The consideration attached to that transfer usually cannot be, unless both parties disclosed it. Claims about prices travel faster than verifications.

Third, even a genuine, fully understood sale describes a transaction between two specific parties for a specific string under specific conditions. The buyer’s identity, their strategic situation and the state of the namespace at the time all shaped the outcome. None of those variables carries directly into your negotiation.

The correction is to use a sale as one input among several, hold it lightly, and be honest about what you do and do not know about its terms. A useful discipline is to write next to each sale you rely on what you can verify yourself, what you were told, and by whom. A buyer who asks how you arrived at your number will probe every comparable you cite. An unverifiable anecdote probed hard becomes a liability in the negotiation.

Mistake 4: counting subname revenue with no identified population of registrants

Freename operates a royalty program: when a name is registered under a TLD, part of the registration fee goes to that TLD’s holder. Half is the most the registry advertises for that share, and what a given holder receives turns on the current terms and on activation conditions. This is a real economic feature of the asset, and it is reasonable to include projected subname revenue in a valuation argument. The operative word is “projected.”

A projection is only as good as its assumptions. The assumption that almost never appears in a holder’s calculation is this: who, specifically, will register names under this TLD, why, and how many of them are there? Without a named or at least a well-described population of likely registrants, a revenue projection is not a financial model. It is a hope expressed as arithmetic.

The arithmetic problem compounds quickly. If you assume a registration fee, a volume of annual registrations and a royalty share, you will arrive at a figure that looks precise. Precision is not accuracy. Each of the three inputs is a guess, and multiplying three guesses produces a result less reliable than any one of them. A buyer’s counsel will ask for the basis of the volume assumption. “Other TLDs have seen registrations” is not a basis. “There is a defined group of organizations in this regulated sector, each with an operational reason to register a name under this TLD, and here is the evidence” is a basis.

Notice, too, that the advertised share is a maximum and comes with conditions. A model that takes the top of the advertised range as a given, without reading the registry’s current terms, has an error in it before the volume question is even reached. The model also needs a cost line. A Freename TLD has no annual renewal fee, but taking part in the royalty program carries an annual cost set by the registry, and a projection that omits it overstates what the buyer would keep. Some TLDs were registered under earlier terms that include the program for life; whether those terms pass to a buyer is something to confirm with the registry before closing.

The correction is either to build the revenue model around an identifiable population and state every assumption explicitly, or to leave subname revenue out of the rationale for your number and let a buyer assign their own value to it. The Subname Revenue Calculator, a free tool on this site, estimates revenue from names issued under a TLD. Whatever tool you use, the inputs are yours to justify. A number that a buyer can interrogate is more useful in a negotiation than one that collapses under scrutiny.

Mistake 5: ignoring what is already issued under the TLD

A TLD that has names already issued under it is not the same asset as a blank TLD. Depending on what those names are and who holds them, existing issuance can either support a higher price or create complications that a buyer will price in as risk.

On the supportive side, a TLD with active names under it has shown that the namespace functions and that registrants found it useful. Where the royalty program is active, it has also shown revenue received in place of revenue projected. A buyer does not have to take the seller’s word for the issuance: the onchain record is public and can be read on a block explorer.

On the complicating side, names already issued cannot simply be withdrawn. If an organization acquires a TLD intending to use it as an exclusive brand namespace, any names already in circulation under it represent an existing population of holders it did not choose. Depending on the registry’s terms and on how the smart contract (the program that records and enforces the registry’s rules onchain) is written, the acquiring organization may have limited or no ability to revoke those names. A buyer’s counsel will examine this carefully.

This mistake has an unusual feature: the holder already has the facts. Only the holder of a TLD can issue names under it, so every name in the namespace exists because you, or a previous holder, put it there. The error is not ignorance. It is presenting the TLD as if the existing issuance were not there, or assuming a buyer will not look. That leads to a price that does not reflect reality and a negotiation that stalls when the buyer’s diligence turns up what the holder did not mention.

The correction is to take an inventory before you set a number: how many names exist, what they are, whether they were issued to yourself, to people you know or to strangers, and whether any of them would trouble the most likely buyer. A holder who raises the inventory first is in a stronger position than one who is asked about it.

Mistake 6: stating a number in public

This mistake is different in character from the others, because it is not an error of reasoning. It is an error of tactics that the other six make more likely.

When a holder states a number publicly, whether on a forum, in a community channel or in a social post, they create an anchor they cannot easily move. If the number is too high, well-advised buyers see it and decline to engage, and those who do come forward are the least prepared to close. If the number is too low, the holder has capped the negotiation before it began.

The damage runs both ways. A number that turns out to be too low cannot be walked back without appearing to negotiate in bad faith. A number that is too high follows the holder into every later conversation, because what has been published stays findable.

The deeper issue is information. A buyer who knows your number before the first exchange knows your ceiling, or thinks they do, and that is an advantage they did not have to earn. They can plan their opening around it. You, meanwhile, know nothing yet about their situation, which is the one thing your price should depend on.

The correction is simple: do not state a number in public. Price discovery belongs in a private process, under a non-disclosure agreement, with a counterparty who has been identified and whose interest is real. This is the setting a desk provides. Exchanges with Hush Partners are covered by a standard mutual NDA, and a holder who wants a buyer found can give the desk a sell-side mandate instead of publishing a figure.

Mistake 7: confusing the holder’s need with the asset’s value

A holder who spent significant time developing a TLD, who is attached to the string, or who needs a specific amount of capital for an unrelated purpose will sometimes arrive at a number that reflects those facts and not what the asset is worth to a buyer. This is understandable. It is also a reliable way to prevent a sale.

Buyers are indifferent to the seller’s cost basis. They do not pay for the effort it took to develop the namespace, for what the holder spent to acquire and set it up, or for the opportunity the holder feels was lost by holding instead of selling earlier. They pay for the value the asset has to them in their own situation. These are different numbers, and they do not converge because the seller needs them to.

The same error runs in the other direction. A holder who needs liquidity and underprices the asset because they feel they cannot wait for the right buyer is also confusing their own position with the asset’s value. Here the structure of the asset matters. A Freename TLD carries no annual renewal fee, so the passage of time does not add a holding cost to the TLD itself. Where pressure to sell exists, it comes from the holder’s wider circumstances, and it should be recognized as such instead of being read into the price.

The correction is to separate the holder’s financial situation from the asset’s valuation entirely. The holder’s situation determines timing and process: how quickly they need to close, whether they can afford to wait for a strategic buyer, whether they have the time to run a longer process. The asset’s valuation is determined by the buyer’s situation, the characteristics of the namespace and the state of comparable evidence. None of the inputs that go into how a TLD valuation is built is a fact about the seller’s finances.

Building a sound range instead of a single number

The alternative to all seven errors is not a single “correct” number. It is a range, built from several independent lines of reasoning, each with its assumptions stated and its limits acknowledged.

A range also tells the buyer something about the holder: that they understand their asset and are not brittle about it. It is constructed by working through five questions and taking the results seriously even when they are inconvenient.

What does the string represent to the most natural buyer? Map the buyer population and identify the buyers for whom the TLD is strategically significant, not merely interesting. Then think about what acquiring it is worth to them relative to the alternative, which is living without it. Where the TLD matches a trademark, the organization on the other side may be considering a brand namespace recovery, and your range should be built with that buyer in mind.

What does the namespace contain? Count the names already issued. Examine what they are and who is likely to hold them. Assess whether they support the buyer’s intended use or create complications. As a general ordering, a namespace with verifiable, relevant activity supports a higher range than a blank one, and a blank one supports a higher range than one whose issuance will create friction for the acquirer.

What can subname revenue plausibly support? If there is an identifiable registrant population, build the revenue model with explicit assumptions about fee levels, the pace of adoption and the royalty share as it actually stands under the registry’s current terms. If there is no identifiable population, leave this line of reasoning out of the range or mark it as speculative.

What does the buyer’s cost of inaction look like? If the TLD matches a trademark, the buyer’s alternative to acquisition may be a contested process that costs time and professional fees with an uncertain outcome. The legal position varies by country, and each side’s own counsel assesses it. If the TLD is a generic keyword with no natural owner, the buyer has more alternatives and the range will be lower. A brand team can measure its side of this question with the Namespace Exposure Score, a free tool that scores how exposed a brand is onchain. Expect a prepared buyer to arrive with a view of their own exposure.

What work will the buyer still have to do after the transfer? A buyer who acquires a TLD and then has to activate it, set up the issuing of names and connect it to their own systems is absorbing costs beyond the acquisition price. A TLD that is already structured for use, with the royalty program activated, issuance tested and some real activity in the namespace, hands over more value and can reasonably support a higher figure.

The range that emerges from these questions has a floor defined by the asset’s standalone value, independent of any particular buyer, and a ceiling defined by its value to the most strategically motivated buyer. The negotiation happens between those two points. Where the lines of reasoning disagree widely, that is not a failure of the method. It tells you which assumption carries the most weight and therefore which one to test first.

The table below sets the seven mistakes against the questions that correct them.

Test your number privately before any conversation

Price discovery should happen before the first conversation with a potential buyer, not during it. A holder who enters a negotiation without a tested range is setting their number under pressure, in real time, against a counterparty who has usually thought about the question longer than they have.

Start on your own. Take the number you have in mind and write down, in one line each, where it came from, which buyer it assumes, which sale or asking price it leans on, what revenue it counts, what is issued under the TLD and what part of the figure is really about your own needs. Each line that you cannot fill with something verifiable marks one of the seven errors. Then rebuild the figure as a range from the five questions above.

If you want a second view, a holder can request a private valuation from Hush Partners through the form on this site. The exchange is covered by the desk’s standard mutual NDA. The TLD Readiness Score, one of the free tools on the site, scores how ready a TLD is to be sold. It is not a valuation, but working through it before any discussion is useful preparation.

The page for TLD holders is the place to begin if you are considering a mandate for the desk to find a buyer. Lawyers and advisers who act for a holder and want to refer a file will find their own page for advisers.

All of this work can be done quietly, before any disclosure and before any counterparty sees a figure.

Questions people ask

Can a TLD with no names issued under it still command a strong price?

Yes. Existing issuance is one factor, not the only one. A blank TLD whose string matches a registered trademark may be worth more to the right buyer than an active namespace on a less strategic string. The absence of issuance removes one line of evidence from the valuation argument and leaves the others intact. For a buyer who wants an exclusive namespace, a blank TLD is also the simplest one to take over.

What happens if a buyer’s offer is far below any defensible floor?

A low offer is information before it is a negotiating position. It tells you either that this buyer does not see the asset’s strategic significance, in which case they may not be the right buyer, or that your floor is higher than buyers will bear, which is also useful to know. Neither conclusion requires you to accept the offer. Both require you to examine it honestly instead of dismissing it as proof that the buyer is wrong.

Does the registry’s royalty structure affect what a buyer will pay?

It can, in both directions. A buyer who intends to issue names under the TLD as a commercial product will count the royalty stream in their business case. A buyer who intends to keep the namespace closed, issuing names only to their own organization or users, may give the royalty program no weight at all. Knowing which type of buyer you are talking to changes which features of the asset are worth emphasizing, and it decides whether a revenue model belongs in your range in the first place.

Should a holder engage an adviser before setting a range?

If the TLD is likely to attract a buyer for whom the acquisition is strategically significant, particularly where trademark considerations are in play, having counsel review your position before any disclosure is a sensible step. A valuation is not legal advice, and trademark law differs from one country to another. The review of your legal position is a separate task, and your own counsel decides it. The two are complementary, not interchangeable.

Is the price different when a sale is negotiated privately instead of advertised publicly?

The closing price may differ, but not because the asset is different. A private negotiation with an identified buyer, approached in confidence, creates the conditions for that buyer’s strategic motivation to be reflected in the price. A publicly advertised figure reaches a wider audience, but much of that audience is browsing and has no specific reason to act. An organization with a strategic reason to acquire may also prefer not to show its interest in the open, so the most motivated buyer for a given TLD may never respond to a public figure at all.