Short answer: pick the .com before you fall in love with the name. Conventional naming advice generates ideas first and checks availability last, which guarantees that most of your best candidates are unbuyable. Inverting the order — filtering for obtainable .coms early — produces a shortlist where every option is real.
The problem with conventional naming
The standard process runs like this: define your brand values, brainstorm broadly, narrow to favourites, then check whether the domain is available. It is taught everywhere and it fails reliably.
It fails because availability is not a final check — it is the binding constraint. By the time you reach it, you have spent weeks generating options, built emotional attachment to two or three, and socialised them with your team. Then you discover every one is registered, and you either start over or compromise on an extension you did not want.
The emotional cost matters as much as the time. A founder who has decided on a name and then cannot have it will accept a worse alternative — a hyphen, a .co, a deliberate misspelling — rather than begin again. The process manufactures exactly the compromises it should prevent.
Inverting the order
The domain-first framework runs the same steps in a different sequence:
- 1. Define the constraints, not the name. Length range, syllable count, sound qualities, degree of category signalling, and budget. This is a specification, not a shortlist.
- 2. Source obtainable candidates. Look only at names where the .com is actually available or purchasable within budget. Everything you consider is real by construction.
- 3. Filter on the hard tests. Radio test, trademark search, handle availability, meaning in other languages. Eliminate ruthlessly — you have not committed to anything yet.
- 4. Narrow to three. Only now allow preference and taste to operate.
- 5. Test with real people. Strangers, spoken aloud, typed rather than written.
- 6. Buy immediately. The moment you decide, secure it. Deliberation is where names get lost.
Writing the specification
Step one is where most of the value sits, and it is the step people skip. A good naming brief specifies constraints without specifying answers:
| Constraint | Questions to answer |
|---|---|
| Length | What character range fits your logo, app icon, and email? |
| Sound | Hard and punchy, or soft and warm? Which fits the category? |
| Signalling | Should it hint at what you do, or stay neutral? |
| Headroom | What might you sell in three years that the name must accommodate? |
| Audience | Which languages and accents must it survive? |
| Budget | What is the actual ceiling for the domain? |
Write this down before you generate a single candidate. It converts naming from a matter of taste into a matter of fit, which is what makes group decisions possible without producing bland consensus.
Why this produces better names, not just available ones
The objection to domain-first is that it constrains creativity. In practice the opposite happens.
Unconstrained brainstorming converges on the obvious — the same category words, the same trendy suffixes, the same patterns everyone else is generating. Constraint forces genuine novelty. A specification that demands five letters, two syllables, no category word, and a soft consonant profile eliminates the lazy options immediately and pushes toward names nobody else is considering.
It also removes the worst failure mode entirely. You never end up building on a compromise, because compromises never enter the shortlist.
Common objections
- “I want the perfect name, not an available one.” The perfect name that you cannot own is not a name. It is an idea about a name.
- “Buying a domain first is expensive.” Less expensive than a rebrand, and the asset retains value.
- “What if I change direction?” Then a category-neutral name — which the specification should require — still fits.
- “My team wants input.” Give them the specification and the final three. Groups test well and decide badly.
At a glance
- Conventional naming checks availability last, which guarantees compromise
- Domain-first makes every candidate real by construction
- Write a specification before generating any names
- Constraint produces more originality, not less
- Buy the moment you decide — deliberation loses names
Frequently asked questions
Does this work for rebrands too?
Especially well. Rebrands have the same failure mode with higher stakes, since you are also carrying migration cost.
What if nothing in budget fits the specification?
Relax one constraint at a time, starting with length. Adding a letter opens up supply dramatically.
Should I involve a naming agency?
If budget allows, but give them the specification and require that every proposal comes with an obtainable .com. Agencies routinely present unbuyable names.
Start with step two
Every name in our collection is available today with a transparent price — so your shortlist is real from the first candidate.
