I sold npc.ai for $250,000. I have not sold a domain for more than $10,000 since. That is an awkward way to open a valuation guide, but it is the honest place to start.
Domain valuation is not a magic number. It is a discipline for deciding whether the evidence is strong enough to keep going.
Quick answer: value a domain name by combining five things: the buyer's real use case, comparable sales, the quality of the name itself, the risk and liquidity of the asset, and your walk-away limit. Automated appraisals and seller claims can be inputs, but they should not decide the price for you.
I run ono.ai and hold premium AI-related domains. I am an interested party. I want good names to sell. But that is exactly why I think buyers need a calmer valuation process. If a buyer cannot separate evidence from excitement, a seller does not have to do much work.
This guide is the broad hub. If you only want premium .ai valuation, read the premium .ai valuation guide. If you are specifically checking comparable sales, read the comps guide.
Start With the Buyer, Not the Domain
The most common valuation mistake is starting with the domain as an object.
Short. One word. Exact match. Old. Brandable. Clean extension. These qualities matter, but they do not answer the buyer question by themselves.
The better first question is: what job would this domain do for this buyer?
A domain can help a buyer in different ways:
| Buyer job | What the domain may improve | What it cannot guarantee |
|---|---|---|
| brand memory | easier recall, spelling, and word of mouth | customer adoption |
| category signal | faster explanation of what the product does | market demand |
| trust and polish | cleaner launch surface | investor trust or conversion |
| paid media | easier ad copy and destination clarity | cheaper acquisition |
| defensibility | fewer weak alternatives in the exact naming lane | legal ownership of a category |
| resale optionality | possible future buyer interest | liquidity or profit |
The same domain can be valuable to one buyer and overpriced for another. A bootstrapped tool with six months of runway should not value a domain the same way a funded company values a name that will sit on pitch decks, product UI, ads, onboarding, customer calls, and investor updates.
This is why "What is the domain worth?" is often too broad. A better question is: what is this domain worth to this buyer, now, with this budget, this timeline, and these alternatives?
The Five-Part Valuation Stack
Use this stack before you talk yourself into a number.
| Layer | Question | Output |
|---|---|---|
| buyer-use value | What business job does the domain do for us? | use-case score |
| comparable evidence | What similar domains have sold for? | evidence range |
| name quality | How strong is the name as a string and brand asset? | quality adjustment |
| risk and liquidity | What can go wrong after purchase? | discount or pause |
| walk-away limit | What price still leaves enough runway and confidence? | final ceiling |
The order matters. If you begin with comps, you may let someone else's old transaction become your price. If you begin with an appraisal tool, you may let a black-box number anchor the conversation. If you begin with the seller's asking price, you may spend the rest of the negotiation reacting to it.
Start with your use case. Then test that use case against evidence.
Layer 1: Buyer-Use Value
Buyer-use value is the value the domain creates for the company that will actually use it.
For a founder, this is often more important than resale logic. You are not buying a stock certificate. You are buying the address, name, or category signal that your product may carry for years.
Ask these questions:
- Will this name reduce explanation cost?
- Will customers remember it after hearing it once?
- Does it match the product category without trapping the company?
- Does it make sales, recruiting, fundraising, support, or word-of-mouth cleaner?
- Does it avoid a rebrand you would otherwise have to do later?
- Does it remove confusion with a similar brand?
- Does it give the team a name they can commit to?
The last question sounds soft, but it is not. A team that hesitates around its own name pays a coordination cost. Every landing page, pitch deck, demo video, customer call, and launch post becomes slightly harder.
That said, buyer-use value has a ceiling. A domain can make a good company easier to explain. It cannot make a weak product work. It cannot create retention. It cannot guarantee SEO ranking, investor confidence, conversion, press, or revenue.
Write buyer-use value in plain language:
This domain is worth considering because it would reduce explanation cost for our AI research product, give us a clean category signal, and avoid a likely rebrand. It is not worth paying more than X because we still need runway for product and distribution.
If you cannot write that paragraph, the domain may still be nice, but your valuation is not ready.
Layer 2: Comparable Sales
Comparable sales are useful because they pull you out of pure feeling.
My own rough valuation starting point is simple: meaning, length, and public transaction records. I do not pretend to run a precise appraisal model. I look at what the name means, how usable it is, how short it is, and what broadly similar names have sold for.
The danger is pretending every comp is equal.
Use this table:
| Comp question | Why it matters |
|---|---|
| Same extension? | .com, .ai, .io, and other TLDs do not behave the same way |
| Similar length? | a two-letter name and a two-word name are not close comps |
| Similar meaning? | exact category words and abstract brands have different demand |
| Similar buyer type? | end-user sales and investor-to-investor sales can imply different ceilings |
| Similar date? | old sales may not reflect current market conditions |
| Similar venue? | auction, brokered sale, marketplace listing, and private deal may differ |
| Similar category heat? | AI, crypto, finance, health, and consumer categories attract different buyers |
The right question is not "Can I find a high comp?" You almost always can if you look long enough. The right question is "Would a skeptical buyer accept this as genuinely comparable?"
If no close comps exist, do not panic. That does not mean the domain is worthless. It means you should rely more heavily on buyer-use value, alternatives, and walk-away discipline.
For a deeper treatment, use the comparable domain sales guide.
Layer 3: Name Quality
Name quality is where buyers often over-simplify.
Short helps. It does not decide everything.
Exact match helps. It can also trap you.
Brandable helps. It may require more explanation.
Premium helps. It can still be overpriced for your stage.
Use a quality scorecard:
| Signal | Strong | Weak |
|---|---|---|
| length | short enough to say and remember | long, clumsy, or easy to mistype |
| meaning | clear word or strong category signal | obscure, forced, or hard to explain |
| spelling | obvious after hearing once | repeated spelling needed |
| pronunciation | easy in calls and demos | ambiguous or awkward |
| category fit | supports the current and likely future product | locks the company into one feature |
| extension fit | extension reinforces audience expectation | extension creates confusion or credibility drag |
| confusion risk | distinct from active brands | close to active competitors or lookalikes |
| upgrade path | likely long-term home | likely temporary placeholder |
In my own view, short plus meaning is the strongest combination. A short name with clear meaning has a natural advantage because it reduces explanation cost. But the buyer still has to ask: meaning for whom?
A short domain can be empty. A longer domain can be more useful if it tells the customer exactly what the product does. A weird one-word name can be valuable if the company has the budget to teach it. A descriptive name can be valuable if the company intends to stay in that category.
Quality is not abstract beauty. It is usability under pressure.
Can someone say it on a call? Can another person spell it? Can a customer remember it tomorrow? Can your team write it on a slide without explaining the joke? Can the name survive a product expansion?
That is the practical version of quality.
Layer 4: Risk and Liquidity
A domain can have strong use value and still deserve a discount.
Risk changes value.
Check these risks:
| Risk | Why it changes value |
|---|---|
| trademark/confusion | legal review or rebrand risk can outweigh naming value |
| transfer complexity | a messy transfer path creates execution risk |
| renewal burden | some TLDs cost more to hold than buyers expect |
| category uncertainty | the product may move away from the name's meaning |
| liquidity | resale may be slow, uncertain, or impossible at your price |
| concentration | the domain may absorb money needed for product or distribution |
| opportunity cost | a cheaper name plus more marketing spend may be better |
Liquidity is especially easy to misunderstand. A domain can be valuable and illiquid at the same time. It may take the right buyer, the right seller, and the right timing. I like .ai domains long term, but I also know selling can depend on luck and timing. After npc.ai, I have not repeated that kind of sale.
That should make buyers more careful, not more cynical.
If you are buying to use the domain, resale should be a fallback, not the main justification. If you are buying as an investor, liquidity deserves a much heavier discount.
For a deeper buyer-side liquidity discussion, read Domain Liquidity: What Premium Domain Buyers Should Know Before Overpaying.
Layer 5: Walk-Away Limit
The walk-away number is where valuation becomes real.
A valuation range is not useful until it meets budget.
Set three numbers:
| Number | Meaning |
|---|---|
| comfort price | you can buy without harming product, runway, or distribution |
| stretch price | you need strong evidence and internal agreement |
| walk-away price | above this, the domain may be nice but no longer rational |
The walk-away number should be set before negotiation begins. If you set it after the seller names a price, you are negotiating with your own fear of missing out.
For founders, the walk-away limit should include more than the purchase price:
- purchase price;
- legal review;
- broker or escrow cost if relevant;
- renewal cost;
- transfer and security work;
- rebrand or migration cost if replacing an existing name;
- product and distribution budget you will not spend if you buy the domain.
The cleanest sentence is:
We can justify this domain up to X because it solves Y and the evidence supports Z, but above X we would rather keep runway and use a cheaper name.
That sentence is not glamorous. It is useful.
Build a Low, Base, and Stretch Range
Many buyers ask for one number too early. A single number feels decisive, but it can hide uncertainty. A range is usually more honest.
Use three valuation bands:
| Band | Meaning | When it applies |
|---|---|---|
| low | the domain is useful, but evidence is thin or alternatives are acceptable | early inquiry, weak comps, unclear seller expectation |
| base | the domain solves a real buyer problem and evidence supports the range | serious offer, good internal alignment |
| stretch | the domain is unusually useful to this buyer and alternatives are clearly worse | strong strategic fit, clean diligence, budget owner agrees |
This is not a trick to justify paying more. It is a way to keep the team honest about uncertainty.
For example, imagine a startup evaluating a short AI-related domain. The name is memorable, fits the product, and could reduce explanation cost. The team finds a few broadly similar sales, but none are perfect comps. In that situation, a low/base/stretch range might sound like this:
| Range | Reasoning |
|---|---|
| low | useful name, but comps are loose and a cheaper fallback exists |
| base | strong enough fit to justify a serious offer if transfer and legal checks are clean |
| stretch | only justified if the team would otherwise rebrand later and the domain becomes the long-term company name |
The stretch range should be hard to reach. If every domain quickly becomes a stretch case, the team is not valuing domains. It is rationalizing desire.
The range should also include confidence. A $25,000 to $40,000 range with high confidence is different from a $25,000 to $40,000 range held together by one old comp and a seller's story. Write the confidence level next to the number.
Let Alternatives Pull the Number Down
A domain is rarely valued in isolation. It is valued against alternatives.
Before making an offer, list at least three fallback names. They do not have to be perfect. They only need to answer the practical question: what would we do if this deal fails?
| Alternative type | What it tests |
|---|---|
| cheaper premium domain | whether the desired name is uniquely strong or just nicer |
| hand-registered name | whether budget should stay with product and distribution |
| longer descriptive name | whether clarity beats brevity for this product |
| different extension | whether the TLD matters to customers or mostly to the team |
| temporary launch name | whether timing pressure is real or imagined |
Alternatives are not just negotiation leverage. They reveal value.
If three fallback names are almost as good, your ceiling should fall. If every fallback creates spelling issues, category confusion, or a likely rebrand, the ceiling may rise. That does not mean you should pay any price. It means the domain is solving a bigger problem than the string alone suggests.
This is where founders should be especially careful. A domain can feel irreplaceable after you stare at it for a week. The alternative list breaks that spell. It forces the team to compare the name against real choices, not against an imaginary perfect brand.
Ask:
- Would we still launch confidently with the best fallback?
- Would customers understand the fallback after hearing it once?
- Would the fallback create legal, spelling, or extension confusion?
- Would we likely rebrand away from the fallback within a year?
- What would the saved money buy in product, hiring, or distribution?
The last question matters. A $50,000 domain is not competing only with other domains. It is competing with engineering time, design work, paid experiments, content, sales help, legal review, and runway.
If the alternative plan is good, the domain has to earn a lower ceiling. If the alternative plan is weak, the domain may deserve a higher ceiling, but only if the company can afford it.
Score Evidence Confidence Before You Negotiate
Not all valuation evidence deserves the same weight.
Use this confidence table:
| Evidence | Confidence | How to use it |
|---|---|---|
| close public sale in same extension, similar length, similar meaning, recent date | high | strong anchor, still adjust for buyer use |
| several imperfect comps pointing to the same broad range | medium | useful range builder |
| seller's statement about private offers | low | conversation input, not proof |
| automated appraisal number without clear support | low to medium | prompt for questions, not a price |
| your team's strategic need | medium to high | important, but budget-limited |
| investor excitement or founder taste | low | useful only if tied to customer use |
The purpose is not to eliminate weak evidence. Sometimes weak evidence is all you have. The purpose is to label it honestly.
If your valuation depends on low-confidence evidence, reduce the offer, ask more questions, or wait. If your valuation has several independent supports, you can negotiate with more confidence.
This also helps inside the company. Instead of arguing whether a domain is "worth it," the team can argue about a specific piece of evidence. Is the comp close enough? Is the alternative really acceptable? Is the legal risk small enough? Is the name likely to be the long-term brand?
Those are better arguments.
Valuable in General Is Not the Same as Valuable to You
Some domains are genuinely good and still wrong for a specific buyer.
A category-defining name may be valuable, but too narrow for a company that expects to expand. A short abstract name may be valuable, but too expensive to teach if the product has no marketing budget. A descriptive exact-match name may be valuable for paid search or category clarity, but awkward if the product roadmap moves.
Separate these two sentences:
This is a valuable domain.
This is a valuable domain for us at this price.
The second sentence is the one that matters before an offer.
This distinction protects both sides. A buyer can respect a seller's asset without accepting the asking price. A seller can hold out for the right buyer without pretending every buyer should pay the same amount.
For a startup, the practical question is not whether the domain deserves admiration. The question is whether owning it now improves the company's odds more than the next best use of the money.
That is why I like valuation language that includes the buyer stage:
| Buyer stage | Better valuation question |
|---|---|
| pre-product | does this domain reduce enough confusion to justify less runway? |
| early launch | will this name improve memory and credibility in the first market? |
| funded growth | does the domain reduce rebrand risk or support a larger category move? |
| mature company | does the domain protect brand architecture or simplify acquisition? |
| investor | is there enough resale demand and patience to justify holding risk? |
The same domain may get different answers across those rows. That is not inconsistency. That is valuation doing its job.
This is also where end-user value and investor value split. An end user may justify a higher price because the name removes real operating friction from the business. An investor needs a different case: future buyer pool, holding time, renewal cost, and resale uncertainty. If you blur those two frames, you may use an end-user argument to justify an investor purchase, or an investor comp to pressure an operating company.
For a deeper version of that split, read the end-user value vs investor value guide. The short rule is simple: use the valuation frame that matches your actual reason for buying.
That frame should be written in the offer memo. If the buyer is an operating company, the memo should talk about launch clarity, naming friction, customer memory, and runway. If the buyer is an investor, the memo should talk about likely buyer pool, holding cost, renewal discipline, and exit uncertainty. Mixing the two makes the price sound stronger than the evidence really is.
How to Use Appraisal Tools
Automated appraisal tools can be useful as a prompt. They are dangerous as a decision-maker.
Use them to ask better questions:
| Tool output says... | Ask... |
|---|---|
| high value | what evidence supports that range? |
| low value | is the tool missing end-user value or category demand? |
| exact number | what assumptions created that number? |
| confidence score | does it explain extension, comps, length, and demand? |
| comparable list | are those comps actually comparable? |
An appraisal number is not a buyer's budget. It is not a seller's obligation. It is not a court ruling. It is a signal.
If a tool gives you a number that conflicts with your buyer-use value and the comps you trust, do not blindly average everything. Find the disagreement. Maybe the tool sees search demand you ignored. Maybe you see strategic value the tool cannot know. Maybe the seller's price is anchored to a fantasy comp.
The goal is not to make every input agree. The goal is to understand why they disagree.
A Practical Domain Valuation Worksheet
Use this before you make an offer.
| Step | Question | Your note |
|---|---|---|
| use case | What exact job would this domain do for us? | |
| alternatives | What are three acceptable fallback names? | |
| quality | Is the name short, meaningful, memorable, and easy to spell? | |
| comps | Which public sales are truly comparable? | |
| risk | What legal, transfer, category, or liquidity risks exist? | |
| budget | What price preserves runway and execution budget? | |
| walk-away | What number should stop the deal? | |
| next step | What evidence is missing before we offer? |
If the worksheet is mostly blank, you are not valuing the domain. You are reacting to the domain.
If the worksheet is clear, you can negotiate without pretending. You can say what you value, what you still need to verify, and where the deal stops.
That is the whole point of valuation.
Common Valuation Mistakes
Mistake 1: Treating the asking price as evidence
The asking price is a signal of seller expectation. It is not evidence of market value by itself.
Mistake 2: Using one high comp as a universal anchor
One sale can be informative. It can also be an outlier, a special buyer, a different venue, a different year, or a different category.
Mistake 3: Ignoring buyer stage
A domain that makes sense for a funded company may be irresponsible for an early side project.
Mistake 4: Paying for optionality you will not use
If you will never resell, never expand into the category, and never use the exact-match benefit, do not pay as if you will.
Mistake 5: Forgetting the cost after purchase
The domain still needs renewal, security, DNS management, legal hygiene, brand rollout, and internal ownership.
Where ONO Fits
ONO is a curated premium AI-domain marketplace. I run it, and I hold names I would like to sell, so this is a disclosed next step.
The right way to use ONO is not "find a name and then justify any price." The better way is:
- browse names that fit the product category;
- write the buyer-use paragraph;
- compare alternatives;
- check quality signals;
- decide what evidence you need before inquiry;
- set a walk-away limit before the conversation gets emotional.
If you are already evaluating a premium AI-related domain, you can browse ONO domains with that worksheet open.
If the worksheet says the domain is too expensive for your stage, believe the worksheet.
FAQ
What is the simplest way to value a domain name?
Start with the buyer's use case, then check comparable sales, name quality, risk, and budget. The simplest useful output is not one exact value. It is a justified range and a walk-away number.
Are domain appraisal tools accurate?
They can be useful inputs, but they should not decide the price for you. Use appraisal tools to surface assumptions, comps, and disagreements. Then compare those signals against your specific buyer-use value and budget.
Are comparable sales the best valuation method?
Comparable sales are one of the best reality checks, but only if the comps are genuinely comparable. Extension, length, meaning, date, venue, buyer type, and category all matter.
How much should a startup spend on a domain?
Enough to solve a real naming or brand problem without starving product, distribution, legal, or runway. A domain can be strategically important and still be too expensive for your current stage.
Does a short domain name always have more value?
No. Shortness helps when it improves memory, spelling, meaning, and category fit. A short name that nobody understands can still be expensive to use.
When should I walk away from a domain?
Walk away when the price exceeds your evidence-backed ceiling, when the seller cannot support key claims, when legal or confusion risk is too high, or when buying the domain would consume money needed for the product itself.
