# Negotiating with a legal department as a TLD holder
> When the buyer is an organization, the conversation runs through lawyers. Their pace, their questions and what moves them.
Source: https://hush.partners/negotiating-with-a-legal-department
Category: Selling
Published by Hush Partners.
---
Most TLD holders are used to deals between individuals: a price surfaces, both parties agree, and the transfer follows quickly. When the buyer is a company, none of that applies. The conversation goes through a legal department, and a legal department has obligations that slow everything down, introduce new questions, and occasionally stop a deal that both business sides already want.
That slowness is not obstruction. It is the predictable output of a system designed to protect an organization from decisions it later regrets. If you understand the system, you can give it what it needs and stop giving it what it does not want. This article describes the internal mechanics of a corporate acquisition, seen from your side of the table.
By the end you will know who makes the decisions on the buyer's side, what counsel needs before it can proceed, why silences of several weeks are normal, and which of your instincts will help and which will hurt.
## Who is in the room on the buyer's side, and who is not
The person you spoke with first is almost certainly not the person who will sign. At most large organizations, the business sponsor (the person who wants your TLD) has limited authority to commit funds and no authority to accept legal risk on the company's behalf. By the time they bring a proposal to their legal department, they have already done some internal selling. They believe in the acquisition. But they cannot close it.
Inside the buyer's legal team, the file typically lands with in-house IP or brand protection counsel. Depending on the size and structure of the organization, that person may also bring in the general counsel, external trademark attorneys, a technology or IT security contact for questions about the onchain infrastructure, and sometimes a procurement or finance team that manages payment approvals. Each of those people has a specific concern, and no single one of them has the complete picture at the start.
The people who are not in the room are equally important to understand. The finance executive who controls the budget is usually not reading your offer. The board is not involved unless the sum crosses a threshold the organization treats as material. Decisions travel upward only when an internal champion pushes them there, and that champion needs clean, complete information to make the case.
This means your job is not to win an argument with the legal team. Your job is to give the legal team everything it needs to say yes to the business sponsor, to the finance team, and to whoever must countersign. Friction at any point in that chain delays or ends the deal.
## What counsel needs before recommending anything
Corporate counsel cannot recommend an acquisition until it can answer a short set of questions in writing. The questions sound simple. Gathering the answers takes longer than you expect.
### Provenance
The first question is who holds the TLD and on what basis. Counsel starts from the way a registry such as Freename records a TLD: onchain, as a token held in a wallet. The registry record is public and anyone can check it on a block explorer, a website that displays the transactions recorded on the underlying chain. Counsel can therefore read the record without relying on your word. Be ready to say which wallet holds the TLD, how it came to you, and that no other claim exists.
### Encumbrances
The second question is whether anything is attached to the asset. Has the TLD been pledged as collateral? Is it subject to any license, partnership, or royalty arrangement that would survive the transfer? Is there any dispute, threat of dispute, or demand letter in its history? Counsel will ask. An honest and complete answer now is far better than a disclosure problem later.
### Trademark risk
The third question is whether the string, meaning the word or words that make up your TLD, conflicts with any mark the company or a third party holds. This is not about your use. It is about whether holding the asset creates a liability for the buyer. A TLD that matches another company's mark, for example, may be something the buyer cannot safely hold even if it wants the asset for other reasons. Trademark rules vary by country, so the answer depends on where the buyer operates.
### Transferability
The fourth question is how the asset changes hands. Onchain, a TLD transfer is a token transfer, and counsel will want to understand the mechanics and confirm that the transfer is final. Pointing to a written description of [onchain escrow and transfer](/escrow-and-transfer) saves a round of explanation: closing runs through onchain escrow on an aftermarket, and the new registry record can be checked publicly afterward.
### What the organization takes on afterward
The fifth question is the one holders forget. Counsel must tell the business what it will own the day after closing, and what that costs to keep. Here the facts of the registry help you. There is no annual renewal fee on a Freename TLD, so there is no recurring payment to budget for the TLD itself and no lapse date to track. The one recurring item is optional: taking part in the registry's royalty program carries an annual cost, which the registry sets. Some TLDs were registered under earlier terms that include the program for life, and whether those terms pass to the buyer is something counsel should confirm with the registry before closing. Only the holder of a TLD can issue names under it, which means the buyer controls what exists under the string from the moment the token arrives.
Limits belong in the same answer. Onchain names resolve outside the ICANN DNS, so an ordinary browser does not open them without support, and that support is partial and changes. A counsel who learns this from you, early and plainly, trusts the rest of what you say. A counsel who discovers it alone starts rereading everything you sent.
Prepare these answers before the process starts. A holder who arrives with clear documentation moves faster than one who assembles it under questioning.
## Why answers take weeks
Even when you provide everything counsel asks for, weeks pass. Holders who have not dealt with corporate buyers often read silence as hesitation or bad faith. It is rarely either.
Corporate legal teams carry many matters at once. A TLD acquisition is important to the business sponsor and to you, but it competes for time with contract renewals, regulatory filings, employment matters, and litigation. You cannot know your position in the queue, and frequent requests for updates are more likely to irritate than to accelerate.
Within the review itself, several steps each consume time. Trademark screening means running the string through national, regional, and international registers and reading the results. It takes longer when outside counsel is engaged. The technology review, if IT or security must weigh in on wallet custody and onchain infrastructure, can run in parallel, but it often produces follow-up questions that come back to you through counsel.
Then there is approval routing. Once counsel has completed its review, the recommendation travels to whoever must approve: a senior manager, the general counsel, a finance committee, sometimes a board committee. Each has its own calendar. A general counsel who approves acquisitions in a standing meeting will not break that cadence for a single file.
No reliable figure exists for how long this takes, and anyone who quotes one is guessing. What can be said is that an onchain TLD is unfamiliar to most reviewers, so the first review of one tends to run longer than the review of a conventional domain name would in the same organization. Plan your own affairs on the assumption that the calendar belongs to the buyer.
## Questions to expect
Counsel's questions are not random. They follow a pattern, and knowing it in advance lets you prepare rather than react.
**On ownership and history.** When was the TLD acquired? Through what registry? Has it ever been transferred, pledged, or licensed? Have any names been issued under it, and if so, to whom and on what terms? If you have issued names such as `name.yoursector`, counsel needs to know whether any obligation to the people who hold them survives the transfer.
**On the string itself.** Does the string match or resemble a name, a product, or a trademark, whether the buyer's or someone else's? Why did you acquire it, and what have you done with it since? Counsel is assessing whether holding the TLD could draw a trademark claim after the transfer. The UDRP, the dispute policy that applies to domain names registered through ICANN-accredited registrars, does not bind an onchain registry, so counsel reasons from trademark law in general and from the registry's own terms. Answer factually and leave the legal characterization to them.
**On the technical setup.** What chain? What kind of wallet? Who can authorize a transaction from it? Is it a single-key wallet or a multisignature wallet, one that requires more than one key holder to approve a transaction? If the TLD is enrolled in the registry's royalty program, what happens to that enrollment on transfer? Freename runs a program in which the holder of a TLD receives a share of each registration fee for names registered under it, advertised at up to half, subject to the registry's current terms and activation conditions. Counsel will read those terms itself. Say whether you are enrolled and do not paraphrase the conditions. These questions often come from the IT or security team and are relayed by counsel. Answer them completely the first time.
**On representations.** Will you state in writing that the TLD is unencumbered, that no claim exists against it, that you have full authority to sell, and that no name issued under it carries an obligation that binds the buyer? These statements, called representations, end up in the purchase agreement. Agreeing to them in principle early removes a later negotiation point. Their exact wording has legal consequences for you, and your own counsel decides what you can sign.
## What reassures counsel and what alarms it
The table below is a working reference. It covers the signals that help a corporate review along and those that trigger additional scrutiny or cause the process to stall.
| Signal | Effect on the process |
| --- | --- |
| Registry record matches what you said, checkable on a block explorer | Settles the first due-diligence question at once |
| No names issued under the TLD, or a clean list with no ongoing obligations | Removes a class of questions about inherited duties |
| Written representations accepted in principle | Fewer open points in the purchase agreement |
| Closing through onchain escrow on an aftermarket | Gives finance and security a defined mechanism to review |
| Mutual NDA in place before any substantive exchange | Lets counsel discuss intent and price candidly |
| Pressure, public deadlines, or threats to sell elsewhere | Escalation inside the legal team; the file may pause |
| Vague or inconsistent answers about history | Independent verification; more time |
| Hints that a competitor of the buyer is also in talks | Read as leverage; the buyer may withdraw |
| An encumbrance discovered after you said there was none | Trust is lost; the process usually ends |
What unites the first five rows is that each one lets counsel write a sentence in its memo without a qualification. What unites the last four is that each one forces counsel to add a risk it cannot quantify. A legal department can recommend a known risk at a known price. It struggles to recommend an unknown one at any price.
## Approval levels and why the number matters to them
Every organization sets financial thresholds that determine who must sign off on a purchase. A manager may approve expenditure up to a certain amount, a director above that, a senior executive above that, and the board above the highest executive threshold. The levels and their names differ from one organization to the next, and you will rarely be told what they are.
### What the price decides inside the buyer
To you, the price is what you receive. To the buyer, the price also decides which rule book applies. It determines how many people must say yes and how many approval meetings and budget reviews the file must survive. A transaction that sits just above a threshold is harder than one that sits comfortably below it, because it needs one more level of sign-off, and that level may meet infrequently.
The number also decides which budget pays. A modest sum may come out of a department's existing budget. A larger one may need a line that does not exist yet, and creating it is a separate process with its own owner. And the number decides how much justification counsel must write. For an onchain TLD there is seldom an obvious comparable to cite, so the memo has to explain the price from the asset itself: what the string means to the business, what it would cost not to hold it, and what the organization plans to do with it. The higher the figure, the more of that reasoning must be on paper.
### What you can do about it
You cannot negotiate the buyer's internal thresholds. You can avoid making the file heavier than the deal warrants. An opening position far above where you expect to settle may place the file, on paper, in a tier it does not belong in, and it stays there in the mind of whoever saw the first number. A clear price with its reasoning attached is easier to carry upward. A holder who wants an outside basis for that reasoning can read how a [TLD valuation](/valuation) is built before naming a figure.
This is also why counsel will sometimes ask for a formal written offer even after the business sponsor has indicated agreement. The written offer, with a stated price and stated terms, is the document that travels through the approval chain. A spoken agreement with the sponsor carries little weight inside a corporate process. The document is the deal.
## Getting from agreement in principle to signed terms
Agreement in principle, the moment both sides have said yes in substance, is not the finish line. It opens a second phase with its own timeline and its own risks. The path below is typical. An organization may merge or reorder steps.
A buyer's internal path from first contact to closing
NDA signedBoth parties sign a mutual confidentiality agreement before any substantive information is exchanged. It defines what each side can disclose, and to whom, during the process.
Intake and initial reviewCounsel receives the holder's ownership summary and preliminary terms. It assigns the file, runs a conflict check, and identifies which specialists (IP, IT, finance) need to weigh in.
Trademark and technical screeningIP counsel checks the string against trademark registers. IT or security reviews the onchain infrastructure, wallet custody, and transfer mechanics. Each team may produce follow-up questions.
Internal recommendationCounsel assembles its findings and makes a written recommendation to the business sponsor and to whoever holds approval authority. It addresses price, risk, and proposed terms.
Approval routingThe file travels to each required signatory in turn. Depending on the amount, this may be one step or several. Each follows the organization's normal approval calendar.
Term sheet or letter of intentOnce approval is granted, counsel drafts or reviews a short document that records the agreed price, the representations, the closing conditions, and the use of escrow. Both sides sign.
Purchase agreementCounsel drafts the full agreement. The holder's own adviser reviews it and negotiates any open points.
Closing through escrowThe transaction closes through onchain escrow on the agreed aftermarket. The registry record then shows the buyer's wallet as holder of the TLD, and anyone can check it.
The step that most often surprises holders is the gap between the term sheet and the purchase agreement. A term sheet agreed quickly can produce a purchase agreement that takes far longer to finalize, because this is the stage at which each representation is negotiated word by word. Counsel's job is to protect its client from future liability. It will not accept wording it has not reviewed. Give it time, and engage your own adviser so that you are not answering markups alone.
Two habits keep this phase short. First, treat the term sheet as closed. Every point you reopen has to go back to the people who approved it. Second, ask early which side produces the first draft of the agreement and in what form, so that the drafting does not begin with confusion over who holds the pen.
Once both sides have signed the purchase agreement, closing itself is the brief part. The mechanism was reviewed during screening, and nothing remains to be argued.
## Pressure, publicity, and the moves that stall a deal
A seller who pushes during a corporate review almost always lengthens it. The instinct is understandable: silence feels like inaction, and a holder who has set other interest aside to pursue a corporate buyer may feel exposed. But the corporate process does not respond to urgency from outside.
Pressure messages, stated deadlines, and references to other interested parties create a specific problem for in-house counsel. Counsel is expected to tell the people it advises about anything that changes the risk of a transaction. When a seller introduces urgency, counsel will usually flag it, and the flag opens a conversation about whether the seller's behavior is itself a risk factor. That conversation takes time and may lead to closer scrutiny of the file.
Publicity is worse. A holder who mentions the negotiation to industry contacts, or who writes about it in any public channel, gives the buyer's legal team a reason to pause. The buyer may not want the acquisition known. The mention may breach the NDA. Either concern is enough to stop the process until it is resolved.
What counsel responds to is consistency and patience. Do not add conditions after a term sheet has been agreed. Do not change the price once the purchase agreement is in draft. Each of those moves requires internal re-approval and restarts the clock.
## The NDA as a practical tool, not a formality
Many holders treat a mutual NDA as a box to check before the real conversation starts. Corporate counsel treats it as the foundation of the exchange. The NDA defines what can be said, to whom, and for how long. It is the document that lets both sides speak candidly about strategy, price, and plans.
For the holder, the NDA does something else: it shows where the buyer is in its own process. An organization that will not sign a mutual NDA before substantive discussion is either not ready to proceed or is running a less formal process than the one described here. Either way, you need to know that before you invest time.
Read what you sign. A mutual NDA binds you as much as the buyer, and it usually restricts whom you may tell that a discussion exists at all. If you intend to consult an adviser, check that the text permits it. Where a file runs through Hush Partners, every exchange is covered by a [standard mutual NDA](/nda), so both sides start from the same text. Whether any NDA suits your situation is a question for your own counsel.
## What to prepare before you approach
Before you approach a corporate buyer, or answer an expression of interest from one, look at your TLD the way a reviewing counsel will. Write the one-page ownership summary. List every name issued under the TLD and the terms on which it was issued. Note anything that could be read as an encumbrance, and decide how you will describe it. Then decide your price and the reasoning behind it, in a form you would be comfortable seeing forwarded to people you will never meet.
The free [TLD Readiness Score](/tld-readiness-score) on this site scores how ready a TLD is to be sold. It is a quick way to find the gaps before someone else does.
Some holders prefer not to run this process alone. A holder can mandate the desk to find a buyer under a [sell-side mandate](/sell-side-mandates). From the first note to closing the holder then deals with one named partner who follows the file, and the closing itself goes through onchain escrow on an aftermarket. For this the desk charges a fixed amount, never a percentage, and only the client who gave the mandate is charged. The [rules of engagement](/rules-of-engagement) set out how the desk works, the stages of a file are described under [how it works](/how-it-works), and the [page for holders](/holders) gathers what concerns you as a seller.
If your counterpart is a brand protection or IP team that is new to onchain TLDs, the page for [brands and legal teams](/brands-and-legal-teams) is written for that audience and may be worth pointing out early in the conversation.
## Questions people ask
### Can I negotiate the price directly with the business sponsor rather than going through counsel?
You can, but it will not hold. Anything agreed with the business sponsor is conditional on legal review and financial approval. If you settle a number informally and counsel's review reveals a risk factor, the number reopens. It is cleaner to state your price in writing from the start, addressed to the process rather than to an individual, and let counsel record it as the offer under review.
### What if the buyer asks for exclusivity during due diligence?
An exclusivity request is common and reasonable. It asks you to pause other conversations for a defined period in exchange for the buyer's commitment to run a serious process. The approval path above gives a sense of what the buyer must complete in that period. Make sure the term is in writing and has an end date. Open-ended exclusivity protects only the buyer.
### Does the buyer's counsel represent my interests at any point?
No. Counsel in a corporate acquisition represents the buyer only. Its job is to protect the buyer from legal, financial, and reputational risk. Nothing it says to you is advice for your benefit. Take your own advice before signing any document, including the NDA.
### What if the buyer goes silent after the term sheet is signed?
Silence after a signed term sheet is less common than silence during due diligence, because both sides have now put something in writing. After a reasonable interval, a single brief inquiry to counsel is appropriate. Frame it as a question about timing rather than a request to accelerate. If the silence continues after that, something has probably changed internally (a budget freeze, a change of personnel, or a strategic shift) and you are entitled to ask directly whether the process is continuing.
### Is an onchain TLD treated differently from a conventional domain name by corporate counsel?
In practice, yes. Counsel that has reviewed conventional domain acquisitions many times has a developed checklist. An onchain TLD does not fit it line by line, and counsel may need to understand the registry, the wallet custody model, and the escrow before it can apply its usual framework. This is not an obstacle. It is an explanation step. A clear, factual description is usually enough: the registry records the TLD as a token on a public chain, the transaction closes through escrow, and the new record can be checked by anyone. Plan for one extra round of questions.