# Selling a community TLD: who buys it and how the sale runs > For holders of a TLD that names an interest, a culture or a community: the logical buyers, the argument that works, and what sets this sale apart. Source: https://hush.partners/selling-community-tld Category: Selling Published by Hush Partners. --- A TLD that names an interest, a culture or a community sits at an unusual intersection. The word it holds may carry genuine affection among the people who live under it, yet those people rarely have a treasury. The holder knows the asset has value. Identifying who will actually pay for it, and in what currency of argument, is the real problem. This article is for that holder. It covers who the buyers are, what moves each of them, what can go wrong, and what slows or accelerates the process. The general mechanics of a TLD sale (how a mandate works, how a file moves from first note to closing) are set out in [the stages of a file](/how-it-works) and get only a brief treatment here. What follows is specific to TLDs that name a shared interest, identity, practice or cultural affiliation. By the end, you will have a working map of the buyer landscape and a clearer sense of what to prepare, what to say, and what to avoid. ## What makes a community TLD different from a trademark TLD A [trademark TLD](/trademark-tlds) is a word that one organization already controls in commerce. The buyer for that kind of TLD is almost always identified before the outreach begins: it is the organization whose mark the TLD reflects. The sale is, in essence, a negotiation about price and timing with a party that already has a structural reason to own the asset. A community TLD is different in every one of those respects. The word it holds belongs, in the cultural sense, to a group and not to a single entity. Usually no organization has an exclusive legal claim to it. The people who feel most connected to the word are often precisely the ones least positioned to pay. And the buyer is not obvious: it must be reasoned out from a pool of candidates whose interest is indirect and whose internal approval paths are long. This distinction matters for how you approach a sale. With a trademark TLD, you are answering a latent need the buyer already recognizes. With a community TLD, you are often constructing the buyer's interest from scratch, showing them why they should want a thing they may never have considered owning. There is also a governance dimension that does not arise with trademark TLDs. Because the word carries community meaning, any buyer who is seen to capture, exploit or restrict it may face public opposition. That prospect shapes who will come forward, what terms they will accept, and how much weight they give to a quiet transfer. In this article the example is `.yoursector`, read as a word that names a practice or a scene, with names such as `name.yoursector` issued to the people who belong to it. ## Why the community itself almost never buys The most logical steward of a community TLD is the community. In practice, the community almost never has a buyer. Communities built around a shared interest (a sport, a creative discipline, a cultural tradition, a professional practice) rarely have a legal entity with both the authority and the budget to acquire a digital asset. Where a formal body exists, such as a nonprofit association or a federation, it typically has governance structures that make rapid decisions difficult: committees, annual votes, restricted funds. The authority to spend on what a finance officer will classify as a speculative technology asset may simply not exist. Where the community is less formally organized, as a scene, a subculture or a fandom is, there is no entity to sign at all. Enthusiasm is not a purchase order. Even when individual members are willing, pooling funds for a TLD acquisition requires coordination, legal structure and a champion willing to carry the risk, all of which take time that most informal groups cannot sustain. This does not mean community groups are irrelevant to the sale. A community that visibly welcomes a transfer adds legitimacy to the buyer and reduces the reputational risk of the acquisition. But endorsement and payment are different things. The party that signs is, far more often, a commercial organization that serves the community, not the community itself. ## The buyers who actually sign Three kinds of buyer are worth reasoning about for a community TLD. They differ in their motive, in where the budget sits and in their pace. **Platforms and marketplaces that serve the community.** A company whose revenue depends on a particular interest group has a commercial reason to own the TLD that names that group. The TLD can anchor the platform's identity onchain, give members a recognizable name, or serve as a namespace for payments and wallet addresses. The case for acquisition is operational: without the TLD, the platform would have to build around a word it does not control. Budget authority tends to sit in product or business development, where a decision usually needs fewer signatures than one that starts in a legal department. **Brands and sponsors with deep community presence.** Some brands define themselves by their association with a community more than by a product category. For these buyers, owning the TLD is a statement of commitment: it gives them a place onchain that carries the community's word and may support naming schemes for partners, ambassadors or events. Budget authority often sits in marketing or partnerships, which means the decision depends on how the acquisition reads in those terms. **Operators and investment vehicles.** A smaller category of buyer acquires a community TLD in order to run it as an active namespace, or to hold it as an asset. An [operator](/operators) evaluates on fundamentals: who would take a name, on what terms, and what it costs to reach them. These buyers decide with fewer people in the room and are less sensitive to how the purchase reads in public. They will usually value the TLD on what it can earn, where a strategic buyer values it on what it lets the business do. The table below sets the three side by side. | Buyer type | Primary motive | Budget home | Typical pace | |---|---|---|---| | Platform or marketplace | A namespace for its members | Product or business development | Medium | | Brand or sponsor | Alignment with the community | Marketing or partnerships | Slow to medium | | Operator or investment vehicle | Running or holding the namespace | Principal | Fast | One practical consequence follows from the table. The buyer who decides fastest is the one furthest from the community, and the buyer the community would most readily accept is often the slowest. A holder who wants both speed and a welcome will rarely get them from the same counterparty, and it helps to know which of the two matters more to you before the first conversation. ## The risk of a buyer the community rejects A community TLD carries a social contract the holder may not have thought much about. When a word names something people care about, whether a practice, a culture or a creative form, those people feel a proprietary relationship with it even though they have no legal one. A sale that they see as hostile can produce a response that damages the buyer's position and, in some cases, the usefulness of the TLD itself. This risk is not evenly distributed. A platform that already serves the community is in a different position from a brand that most community members have never heard of, and both are in a different position from an investment vehicle with no public profile in the space. The further the buyer is from the community's own orbit, the greater the chance of a cold reception. The practical consequences of rejection vary. At the mild end, the buyer faces public criticism and a slower rollout. At the serious end, the people the buyer hoped to reach gather under a different word, or under the same word in another naming system, and the audience splits. A name under a community TLD is only worth something if members choose to take it and use it. Nothing obliges them to. That is why hostility from the community is a real cost to the buyer and not only an embarrassment. A sensible buyer knows this and will ask about it early. If you have no answer, the buyer has two reasonable responses: to lower what they are prepared to offer, or to step away. Neither is bad faith. They are pricing a risk you left open. It follows that the reception of the sale is part of the asset. A holder who can show that the word has been looked after, that members who hold names have been treated fairly, and that there is a credible account of what the next owner intends, is selling something more complete than a holder who can show only the registry record. ## Platforms and brands: how their interest is built Strategic buyers for community TLDs do not usually go looking for a TLD. The holder or their adviser must therefore build the case from the buyer's own priorities. For a platform, the argument starts with what the TLD enables operationally. A namespace under a community word gives the platform a lasting onchain layer for member identity: a name issued under `.yoursector` means more to its bearer than a string of characters, and on Freename the holder of a TLD is the only party able to issue names under it. A platform that owns the TLD therefore decides who receives a name and on what terms. The [subname revenue calculator](/subname-revenue-calculator) estimates revenue from names issued under a TLD, which gives a product team a first figure to test its own assumptions against. Treat the result as an estimate built on inputs you chose, and say so when you share it. For a brand, the argument is different. The brand's core concern is not infrastructure but presence. Owning the TLD that names its community gives it something a sponsorship does not: the ability to issue names under that word, and to anchor events and campaigns in a namespace the community recognizes as its own. The questions a brand's team will ask are about meaning and conduct. What does owning this word commit us to? How will members read it? What would we do with it in the first season? The honest limits belong in this conversation too. Onchain names do not resolve through the ICANN DNS root, so an ordinary browser needs added support before it opens one, and wallet and browser coverage for Freename names is partial and changes over time. For a website that must work for every visitor without preparation, the DNS is simply the better tool. A buyer who hears this from you first will trust the rest of what you say. A buyer who discovers it alone will reread everything you told them. In both cases, the buyer's interest has to be built through explanation before it can become an offer. That phase is one of the main reasons a community TLD takes longer to sell than a trademark TLD. ## The argument that works for a community word and the one that backfires The argument that works for a community TLD is specific and operational. It starts with what the buyer already does, identifies the gap the TLD fills, and shows concretely how ownership would change what they are able to build. For a platform, that means a namespace plan. For a brand, it means a concept for how members, partners or events would be named. The argument lands when the buyer can see the TLD inside their existing roadmap. The argument that backfires is the one built on scarcity and haste. Telling a buyer that they should move before someone else does, or that the TLD is valuable simply because the community is large or passionate, does two things: it invites doubt about everything else in your note, and it casts you as a vendor instead of a counterpart in a considered decision. The same applies to any suggestion that the word might end up somewhere the buyer would find uncomfortable. That is pressure, a careful organization recognizes it as such, and it ends conversations. The buyers who sign are the ones who have understood why the asset fits their own situation. A second argument that often backfires is leading with royalties. Freename runs a royalty program under which a TLD's holder is paid a share of every registration fee for names registered under that TLD; half is the advertised ceiling for that share, and what the holder of a community TLD actually receives turns on the registry's current terms and on activation conditions. For a buyer who intends to hold or operate the TLD for income, this is relevant and worth raising, together with its cost: the TLD has no annual renewal fee, but taking part in the program carries an annual cost set by the registry. For a platform or a brand, opening with it can make the TLD sound like a passive income product when they are looking for a piece of infrastructure. Strategic buyers want to understand what the TLD does for them operationally. Revenue from registrations is a benefit they will weigh later; it should not lead. A third weak argument is to speak for the community. A holder who claims that members "want" a given buyer, without anything to show for it, is making a promise that only the community can keep. Say what you know: who holds names, what they use them for, what you have heard directly. Leave the rest for the buyer to find out. ## What weakens the asset before the sale Several things can reduce the value or the saleability of a community TLD before a transfer is agreed. **An empty namespace.** A TLD with no names registered under it is harder to argue for than one where active members of the community have already claimed names. The existence of live names, even a small number, shows that the namespace is real and that the community recognizes it. Where the holder has never issued a name, the buyer takes on the whole risk of finding out whether anyone wants one. **A sale conducted in public.** If word has circulated that the holder is seeking a buyer, strategic buyers have a reason to wait and see how the price moves. A community that hears the TLD is for sale may also form a view against the sale before any buyer is identified, and that view then attaches to whoever comes forward. Quiet, directed outreach preserves both the asset's value and the room to negotiate. The [TLD readiness score](/tld-readiness-score) is a useful self-check before outreach begins. **A holding period the community resents.** If the holder has used the TLD in a way the community views as exploitative or contrary to its values, that history travels with the asset. A buyer doing basic diligence will find it. Clean stewardship of the namespace during the holding period is worth more than it appears. **Unresolved name conflicts.** Names under the TLD may be in use in ways that would concern a buyer: passing off, or impersonation of known figures within the community. Those conflicts should be resolved or at least documented before outreach begins. It is better to find them yourself than to have a buyer raise them in the middle of a negotiation. **Names issued carelessly.** The most recognizable names under a community TLD are the ones a platform or a brand would want to grant itself: the names of roles, events, places and formats the community uses every day. A holder who has handed these out without thought has sold part of what the buyer was coming for. Before a sale, issue sparingly and keep a record of what has gone to whom. ## Why patience is usually required and what sets the pace A community TLD sells slowly by the standards of other onchain assets. No honest figure can be put on it, because the pace is set almost entirely by the buyer's organization and not by the holder. Four things decide it. **The explanation phase.** Strategic buyers who have not thought about owning an onchain TLD need time to understand what it is, weigh this particular TLD against their priorities, and build agreement inside the organization. This phase cannot be compressed much without losing the buyer. It is the main driver of a long timeline. **Internal approval.** Even after a buyer is interested in principle, the acquisition must travel through legal, finance and sometimes the board. For a brand, this may involve a procurement process; for a platform, a product committee. The holder has no control over this phase except to provide clear, complete information promptly. **The buyer's calendar.** If the buyer wants to announce the acquisition or build the TLD into a product the community will see, they may tie the decision to a moment of their own, such as a gathering, a launch or a partnership. The transfer then waits on a date that has nothing to do with you. **Competing priorities.** Buyers for community TLDs are active organizations with other things on their agenda. An acquisition that nobody inside is championing will slip behind those things. This is ordinary, and it is not a signal about the value of the TLD. Patience is easier on a holder of this kind of asset than on most sellers. A Freename TLD carries no annual renewal fee, so waiting does not add a recurring registry cost to the holding. The token stays in your wallet, and nothing lapses while a committee meets. What waiting does cost is attention: answering questions well, months apart, without changing your account of the asset. The holders who manage this best have done the preparation before outreach, keep the number of open conversations small, and are in a position to wait. A sale of a community TLD made under time pressure rarely produces a good result, because the buyers able to move at short notice are the ones who value the word least for what it means. ## What to prepare before outreach begins Preparation has two sides: the documents and the argument. On the documentary side, a serious buyer will ask for the basics. Ownership needs no special proof: the registry record is public, and anyone can look it up on a block explorer. Add a description of the names registered under the TLD, and a clear account of where the TLD stands with the registry's royalty program under its current terms. If names are live, compile what you know about their use. If you have had earlier discussions with potential buyers, tell any adviser you work with, even if they went nowhere. On the side of the argument, you need a credible use case for each kind of buyer before the first note goes out. That means knowing the platforms and brands that serve your community well enough to say what the TLD would enable for each one specifically. A generic note, saying only that the TLD is available and valuable, seldom works for a community TLD. The buyers worth approaching have their own priorities, and the opening argument has to reflect them. You also need to have thought through the reception before a buyer asks about it. What is the community's relationship with the TLD, if any? Are there voices within it who would welcome a well-framed transfer? Is there a stewardship account the buyer could carry: keeping the namespace open, issuing names to members on fair terms, giving the community a say in how names are granted? These are not only questions of communication. Some of them can be written into the agreement as commitments, and whether and how to do so is for each side's own counsel. Finally, form a view of value before anyone asks you for a number. A [private valuation](/private-valuation) request is one way to do that. Knowing the range in advance avoids the two common errors: anchoring too low, or opening with an ask that a serious buyer dismisses as uninformed. ## Running the sale and where to start The general structure of a TLD sale (mandate, outreach, negotiation, closing) applies here as it does elsewhere. A few points are specific to community TLDs. The pool of buyers worth approaching is usually small. A word that names a whole industry may interest many companies in that industry. A community TLD may have only a handful of platforms or brands that are placed to benefit. Targeting matters more than volume: a short list of well-chosen organizations, each approached with an argument written for it, does more than a wide mailing to organizations with no particular reason to care. Confidentiality matters more here than in most TLD sales, because the community is watching in a way that the customers of a company seldom are. When a file runs through Hush Partners, a standard mutual NDA applies to every exchange, and the desk never says who is selling a given TLD. A holder approached directly by a buyer may want the same protection from the first substantive conversation; your own counsel decides what is appropriate. Closing takes place through onchain escrow on an aftermarket. Freename's is used unless the client prefers another marketplace. The [escrow and transfer](/escrow-and-transfer) page describes that part of the work. If you want a buyer found and approached on your behalf, the service is described under [sell-side mandates](/sell-side-mandates). The desk's fee is a fixed amount and not a share of the price, and it is charged only to the client who gives the mandate. If you are not at that point, the [page for holders](/holders) is the place to begin, and the most useful thing you can do in the meantime costs nothing: write one page on what each of your three likeliest buyers would do with the TLD. If you cannot fill that page, the sale is not ready. ## Questions people ask ### Can a community organization be set up to acquire the TLD? In principle, yes. A nonprofit or a cooperative could be formed or designated to hold the TLD on the community's behalf. In practice, this adds time and legal complexity to a transaction, and the resulting entity still needs funding. It is worth considering where there is strong community interest and a willing donor or grant-maker, but it is not a default path. The rules for such entities vary by country, and your own counsel advises on the structure. ### What happens if a buyer withdraws after a long negotiation? The holder has spent time, and the same argument cannot simply be sent to the next organization, because it was written for the one that left. The way to limit the damage is to keep the preparation for the second and third candidates current while the first conversation runs, so that a withdrawal does not send you back to the start. That is different from playing one party against another. Each conversation should stand on its own merits, and none should be presented to a buyer as a reason to hurry. ### Does resolution support matter to the buyer? It matters, and you should describe it accurately. Freename names are supported in Bitcoin.com Wallet, in MetaMask by way of Freename's resolver, and in desktop browsers with the Freename Web3 extension installed. That coverage is partial and it changes, so nobody should be promised that a name will resolve everywhere. A platform building identity for wallet users will assess this closely; a brand that mainly wants to grant names to partners may weigh it less. The site's page on what is live lists each capability with its source. ### Should the holder mention the royalty program? Yes, plainly and without overstating it. Say whether the TLD is in the program and point the buyer to the registry's current terms and activation conditions, which are what govern any payment. Say also that participation has an annual cost set by the registry, and that some TLDs were registered under earlier terms that include the program for life. The buyer should confirm with the registry how the arrangement applies after a transfer, including whether such earlier terms pass to them; do not answer that for them. For a buyer who intends to operate the namespace, it is a meaningful part of the case. For a platform or a brand, present it as secondary. ### What if the community word is also a trademark held by someone else? Check before any outreach. Trademark rights are granted by country and by class of goods or services, so a word that is free in one field may be protected in another. If a third party holds a mark on the same word in a relevant field, a well-advised buyer will ask about it before signing, and the answer shapes both the list of buyers and the terms. The free Trademark Name Check on the site is a first look, not a clearance. Your own counsel decides what the result means for a sale.