What a buyer map is, and how one is built

Every holder who wants to sell a TLD eventually asks the same question: who should we approach? The answer looks simple until you try to produce it. You can name a few obvious organizations in ten minutes. A structured, ranked, confidential document that tells you who to approach first, through which function, in what order, and why takes more than a list.

That document is called a buyer map. It is the first piece of analytical work in a sale, and it comes before pricing and before any note goes out. This article explains what a buyer map contains, how it is assembled step by step, how it differs between the two main types of TLD, and how you can judge whether a map given to you is useful.

By the end, you will know what to expect from a map, what questions to ask about one, and what it means when a map is missing pieces.

Why the map comes before the price

A valuation tells you what a TLD is worth under a set of assumptions. A buyer map tells you who could realistically pay that, and why they would. The two documents are related but not interchangeable, and the map informs the price more than the price informs the map.

The reason is simple: price is conditional on use. A TLD is worth more to an organization that will run it as a namespace for a product than to a party that would only hold it. It is worth more to the one organization whose own name it spells than to anyone else. Until you know who your realistic acquirers are and what each would do with the TLD, a single figure hides more than it shows.

The dependence runs in one direction. A change in the map changes the price: if the organization with the strongest reason turns out to have no use for a namespace, the top of the range was never real. A change in the price does not change the map. The organizations with a reason stay the same whatever number you have in mind. That is why the map is drawn first and the range is read against it.

There is a second reason. Sequence matters in any approach. A note sent to an organization with no real reason to care wastes a first impression, and people inside a sector do mention to one another what lands on their desks. A map that sets the order of approach is also a way of managing that risk: it keeps a poorly targeted early contact from coloring the conversations that matter.

For this reason, serious preparation for a sale starts with the map. A sell-side mandate is the arrangement under which a holder asks a desk to find a buyer, and finding a buyer starts with knowing who could be one.

From the string to organizations with a reason

The first question in building a map is: given this string of characters, which organizations have a structural reason to want it?

“Structural reason” is deliberate. Finding a TLD interesting is not enough. An organization has a structural reason when the TLD would solve a problem it already has, extend an asset it already owns, or fit a plan it is already carrying out.

There are two broad types of TLD, and the entry points differ.

A trademark TLD matches a brand, a product name, or a trading name. The set of organizations with a structural reason is, in principle, small: the trademark owner, an organization that licenses the brand, and a group company that manages the name in some territories. The set is bounded by who uses or has rights in that name. For a trademark TLD, the map is about depth, not breadth.

A market TLD is a sector or category word, a string that a whole industry might want to operate as a namespace. The set of organizations with a structural reason is wider: any operator that runs a service in that market and could issue names to its users, participants, or assets. On Freename, issuing names under a TLD is reserved to whoever holds it, which is what gives an operator a reason to hold the TLD itself instead of renting a name under someone else’s. For a market TLD, the map is about breadth and then filtering.

In both cases, the analyst works outward from the string itself and writes down every organization that plausibly passes the structural-reason test, without ranking yet. This longlist is the raw material, not the map.

From the organization to the function that cares

A longlist of organizations is still not a map. Organizations do not decide to buy a TLD; people inside them do. And the people who care about a TLD are not always the ones you would expect.

For a trademark TLD, the function that typically cares first is brand protection or intellectual property. These teams follow where the brand’s name appears and decide what, if anything, to do about it. General counsel is usually close behind, because an acquisition needs a contract and may have trademark implications. Marketing or digital may be involved if they see a use for the TLD after closing, such as putting pay.yourbrand to work.

For a market TLD, the function that cares first is usually product, digital infrastructure, or the team that decides how participants on the operator’s platform are named and addressed. Legal is involved at the contract stage, but the initiating function is often technical or commercial. The operators who run a market TLD as a namespace think about it as product infrastructure, and a map written for them has to speak that language.

This matters for how a note is written and where it is sent. A note framed around a brand’s name means little to a product team. A note framed around namespace infrastructure means little to a brand protection team. The map must identify not just which function, but which framing fits each organization.

Reading the org chart from the outside

Identifying the right function from outside the organization is partly inference and partly public record. Annual reports, product announcements, job postings, and regulatory filings all carry signals about how an organization structures its digital and brand assets. The analyst does not need a name at this stage. The task is to work out which function holds the decision.

From the function to the person who can sign

Identifying the right function narrows the target. The next step narrows it to a role: who, inside that function, has the authority to approve an acquisition of this kind?

For most organizations, a TLD acquisition is an unusual transaction. It does not fit neatly into recurring procurement, domain renewal budgets, or standard IP maintenance spend. It will likely need approval from someone more senior than a routine domain purchase would, and it may need input from more than one function before it reaches that person.

The map should identify, for each organization on the longlist, the likely decision-maker by role and the likely path to that role. It answers questions such as whether a note addressed to the general counsel will be acted on there, passed to the IP team, or redirected to a function somewhere else entirely.

An organization that has already built onchain infrastructure, such as a wallet integration, a payments product, or an identity layer, has probably given someone responsibility for that territory. That role is a better addressee than a general inbox. The map notes this where the public evidence supports it.

What a map leaves out

A map stops at roles and public facts. It holds no private contact details, nothing drawn from personal accounts, and nothing about an individual beyond the position the organization itself publishes. A note reaches a role through the organization’s ordinary front door. If a map you are shown contains more than that, the extra material is a liability for you as well as a discourtesy to the people in it, and data protection rules, which vary by country, may apply. Your own counsel decides what is acceptable.

Ranking: strength of reason, ability to act

With organizations identified and functions mapped, the analyst can rank. Two variables drive the ranking: the strength of the organization’s reason to want the TLD, and its ability to act.

Strength of reason depends on how directly the TLD answers a problem or opportunity the organization already has. An organization that is building a digital product a dedicated namespace would clearly improve has a stronger reason than one for which the TLD would be a speculative asset. An organization that holds a trademark on the string has a stronger reason than one for which the word is merely relevant.

Ability to act depends on scale, the speed of decisions, and strategic focus. A large organization with diffuse governance may have a strong reason but move slowly. A smaller, well-funded organization with a focused digital team may act faster. Both matter. An organization with a strong reason and no way to act in a reasonable time ranks below one with a somewhat weaker reason, a clear internal owner, and a budget.

The ranking also looks at fit: for some organizations the TLD does something no other asset would, while for others it is one of several ways to reach the same end. The first group ranks higher, for the plain reason that a conversation with them is more likely to lead somewhere.

When the evidence is thin

Some entries cannot be scored with confidence. Public record may show that an operator is active in the market without showing whether it has any interest in naming. An honest map says so. It marks the entry as uncertain, states what would resolve the doubt, and places it where an early, low-key conversation can settle the question. A map in which every entry carries a confident score has usually replaced evidence with optimism.

Order of approach and why it matters

The ranked longlist produces an order of approach. This is where the map becomes operational.

The general principle is to approach in declining order of fit, the best-matched organization first, with three adjustments.

First, approach few organizations at a time. A note sent to everyone at once reads as a circular, and a circular rarely gets a considered answer. A quiet, sequential approach to well-chosen organizations lets each recipient treat the note as addressed to them, which it is. This is why confidentiality, discussed below, is not optional.

Second, let conversations inform one another. If an organization declines and says why, that reason may sharpen your understanding of how the TLD fits elsewhere, or show that an assumption in the map was wrong. Where the fit of the top-ranked organization rests on an untested assumption, it can be sensible to test that assumption in a lower-stakes conversation first.

Third, some organizations on the map compete with each other. The map should flag these relationships so that each conversation stays separate and nothing said in one travels to another. The point is discretion. A map is not a device for setting one organization against another, and an approach that mentions rival interest to hurry a recipient is the kind of pressure a careful seller avoids. Each organization is told what is true: the TLD exists, it can be acquired, and a refusal is a perfectly acceptable answer.

The stages that follow the map, from mandate to transfer, are set out on the site.

1. String analysisIdentify every category of organization with a structural reason to want this TLD: trademark owners, operators in the relevant market, organizations managing related digital infrastructure.
2. Organization longlistWrite down the specific organizations that meet the structural-reason test. No ranking at this stage. The longlist may be long.
3. Function mappingFor each organization, identify which internal function is likely to initiate and which holds formal approval. Note where these differ.
4. Decision-maker inferenceIdentify, by function and seniority, the role likely to receive and act on a note. This is an inference from public record, not a search for contact details.
5. RankingScore each organization on strength of reason and ability to act. Mark the entries whose reason or ability is uncertain.
6. Order of approachSet the sequence, noting which organizations compete with each other and which conversations should come after an assumption has been tested.

What a map looks like for a trademark TLD and for a market TLD

The structure of a map is the same in both cases, but the content differs substantially.

A worked example shows the difference. It is fiction, and these are its assumptions: .yoursector is a generic English word for a market, no organization holds a trademark on it, the market has eight active operators of comparable scale, and three operators from adjacent markets have expanded into it.

The longlist for this TLD is the eight operators plus the three adjacent ones: eleven organizations. The function that cares in each is likely digital product, not brand protection. The decision path runs through a technology or product lead, with legal involvement at the contract stage. The ranking turns on which operator is most actively building products in which name.yoursector would be an identifier its users see. Suppose public record shows that four of the eleven have such products. Those four form the top of the ranking, and the other seven are kept on the map with a note of what would move them up.

Now run the same exercise for .yourbrand, a fictional string that is the trading name of one organization. The longlist is short: the trademark owner, a licensee with a significant interest, and a holding company that controls the brand in some territories. The initiating function is IP or brand protection. The decision path runs through general counsel. The ranking is nearly settled before it starts, because the trademark owner has a reason that no other organization can match.

The second map is not thinner work for being shorter. With one natural reader, everything depends on the function analysis and on the tone of a single note. The effort moves from filtering to understanding one organization well.

Keeping the map confidential

A buyer map is not a marketing document. It is a working paper, and it is sensitive in its own right, for three reasons.

First, the map names organizations that have not asked to be on it. An organization that learns from a third party that it appears in someone’s sale papers, and where it ranks, has good cause to be irritated, and a conversation that starts that way rarely recovers. The map should be seen only by the people directly involved in the sale.

Second, the map records your own reading of who has the strongest reason and why. That reading is provisional. If it circulates, it will be taken for a settled position, and it can shape a conversation before the conversation has begun.

Third, the map contains inferences about how other organizations are structured and how they decide. The sources are public, but gathering and interpreting them for a commercial purpose makes the result something to handle with care. It should not travel beyond the people working on the file.

Where Hush Partners is involved, a standard mutual NDA applies to every exchange, so a map discussed with the desk is discussed under it. Holders who build a map on their own should ask counsel what protection is in place before the document goes to anyone else.

Judging a map

If someone gives you a buyer map, whether as part of a proposal, an advisory engagement, or your own team’s research, here is how to evaluate it.

Does it distinguish structural reasons from superficial ones? A map that includes any organization in a loosely related sector has not done the analytical work. A strong map explains, for each organization, why it specifically has a reason tied to an existing problem or asset.

Does it go past the organization to the function? If the map stops at “Company X” without saying which team inside Company X would initiate and which would approve, it is a list, not a map. The function-level analysis is what makes a map usable.

Is the ranking explicit and explained? Ranking by instinct produces a map that looks complete and cannot be checked. The ranking should state its criteria and apply them consistently. If strength of reason and ability to act are the criteria, each entry should be scored on both, and uncertain entries should be marked as such.

Does it address sequencing? Order of approach is a decision, not a by-product. A map that ranks organizations without stating the order, and the reasons for it, leaves the most practical question unanswered.

Is the longlist the right size for the type of TLD? A trademark TLD with dozens of entries suggests the structural-reason filter was not applied. A market TLD with only a handful suggests it was applied too narrowly. The right size depends on the string, and the map should explain how it arrived at its number.

Does it stay within public information about roles? A map that reaches into personal details has gone beyond what the work requires.

Was it handled as confidential? A map that was drafted casually, shared widely, or circulated with no NDA in place may already have undermined the sale it was meant to support. Ask how it was handled before you rely on it.

A map that passes these tests also gives the price something to stand on. A valuation is built on assumptions about use, and the map is where those assumptions meet named organizations. If the range you have been given assumes an operator will issue names at scale, the map should show which operators could do so. If it cannot, either the range or the map needs another look.

Where a holder starts

If you hold a TLD and are considering a sale, start with the first two steps yourself. Write down the categories of organization with a structural reason, then the organizations in each. An hour of this will show you whether your TLD has a narrow field or a wide one, and it will make you a better judge of any map you are later shown.

Two things on the site help with the rest of the preparation. The TLD Readiness Score is a free tool that scores how ready a TLD is to be sold. A private valuation can be requested through a form, and it is the natural companion to the map: the valuation gives the range, the map gives the field it applies to.

If you would prefer the search for a buyer to be carried out for you, that is what a sell-side mandate with Hush Partners covers. One named partner stays with the file from the first note through to closing, and the desk never names the seller of a given TLD. A holder who wants the map drawn for them opens that conversation with the desk on the site, where the contact form is the way in.

Questions people ask

Is a buyer map the same as a target list?

No. A target list is one part of a buyer map: the ranked shortlist of organizations to approach. The map includes the work that produced it, namely the structural-reason assessment, the function mapping, the decision-path inference, and the reasons for the sequence. A target list handed over without the map is a set of conclusions without the reasoning.

How many organizations appear in a completed map?

There is no universal answer. A trademark TLD for a distinctive brand name may leave a very short shortlist after filtering. A market TLD in a fragmented sector may leave a much longer one. What matters is not the number but whether every entry has a documented structural reason for being there.

Does the map change during the process?

Yes, and it should. A first conversation with any organization produces information about its priorities and its timing that may change the ranking, or point to an organization that was not on the original longlist. A map treated as fixed from the day it is written is being used as a checklist. Revise it after each conversation.

Is there an equivalent of the map on the buying side?

An organization that wants to acquire a TLD can mandate a desk to find the holder and approach them. The preparation is a mirror image of the buyer map: one counterparty in place of several, and the questions are what that holder’s reasons for selling might be and how to open the conversation well. The habits of mind are the same, and so is the need for discretion.

What if the most natural buyer is the trademark owner?

This is common with trademark TLDs, and it calls for particular care in tone. The first note should be factual and short. It states that the TLD exists, that the registry record is public and can be checked on a block explorer, and that a private conversation is available if the organization wants one. It makes no claim about the organization’s rights and sets no deadline. A recipient who prefers to pass the note to counsel, or not to answer, is free to do so, and the map should record that outcome without treating it as a setback to be overcome.