Why I Built NamoLux: Turning a Startup Shortlist into a Decision

Choosing a name for a startup is one of those jobs that looks small from the outside. You put a few words into a generator, scroll through a list, look up a domain and move on.

In practice, it rarely works like that.

For a founder, a name has to carry a surprising amount of weight. It has to make sense to the people you want to serve. It has to be memorable enough to survive a conversation. It needs a domain you can realistically use. It needs room for the business to grow. And, once you have narrowed the field, it needs a reason to beat the other names you liked.

I am Andrew Barrett, a developer from Rhyl, North Wales, and the founder of NamoLux. I build practical web products, and I became interested in naming for the same reason I care about product design and search: small decisions at the beginning can shape an enormous amount of work later.

NamoLux started with a simple belief. Generating ideas is useful, but choosing a name deserves a more disciplined process. The product is built to help founders bring a shortlist into one place, see domain evidence clearly, compare names consistently and make a decision they can explain.

The problem is not a lack of names

Most founders do not begin with an empty page. They begin with too much input.

There are notes from a meeting, messages with a co-founder, a half-finished spreadsheet, domains saved in a registrar, and ideas produced by several different tools. The resulting shortlist can be exciting, but it can also create a false sense of progress. A long list is not a decision.

Traditional name generators are good at one narrow job: producing possibilities quickly. That is a worthwhile starting point. The problem is what happens next. A founder still has to work out whether a candidate is easy to say, whether it feels credible in the intended market, whether the domain is available and whether the name will still make sense when the product changes.

The usual workflow fragments that work. Ideas live in one tab. A registrar is in another. A notes document contains the reasoning. A second spreadsheet becomes the comparison table. By the time the decision is made, it can be difficult to remember why the winning name won.

That fragmentation matters because naming decisions are easy to overthink. Founders can become attached to the first name that feels clever, or settle for a name simply because the matching domain is available. Both choices can be expensive later.

The common mistakes are understandable

The first mistake is treating availability as quality. An available domain is useful evidence, but it is not proof that a name is distinctive, clear or worth building a company around. Plenty of weak names are available precisely because no one else wanted them.

The second is treating a score as a verdict. A model, a rubric or a colleague can reveal a useful pattern; none of them can know every part of a founder's strategy. A naming tool should help a person notice trade-offs, not make the decision invisible.

The third is trying to solve every branding question before the name has earned its place. A polished logo, a colour palette and a landing page can make a weak candidate feel more convincing than it is. The name should stand up before those layers arrive.

Finally, there is the temptation to be too literal. A name that describes one feature may look sensible today but become restrictive as the product expands. The strongest names are not always abstract, but they leave enough room for a company to become more than its first release.

A name has to survive real conditions

It is easy to judge a candidate in the quiet of a browser window. The more useful test is whether it survives the ordinary situations a business will face.

Can someone type it after hearing it once? Can a prospective customer find it after a recommendation from a friend? Does it sound credible when introduced in a sales call? Does it create a confusing result when it is searched alongside the category? Would a new team member feel comfortable putting it on a presentation, an invoice or an app icon?

These are not glamorous tests, but they are often where a name proves itself. A clever spelling may look distinctive until it has to be dictated over the phone. A trendy suffix may feel current until the company needs to speak to a more conservative customer. A name that is so broad it could mean anything may make search, referrals and positioning harder than it needs to be.

The aim is not to find a name that cannot be criticised. Every viable option will have a compromise. The aim is to choose the compromise that matches the business. A technical tool may sensibly choose an alternative extension if the audience understands it. A local service may benefit from a clearer, more familiar name. A company with global ambition may need to spend longer on pronunciation and meaning in its priority markets.

Founders often ask whether a short invented name is always better. It is not. A coined word can be memorable and ownable, but it can also be empty if it is difficult to say or has no emotional foothold. A descriptive name can be clear and trustworthy, but it can become generic or limiting. A compound can make an idea easier to understand, but it can quickly become clumsy. The right choice is the one that creates the least unnecessary work for the business that will use it.

That is also why the name should be considered in context. Put it beside a one-sentence description of the product. Put it in a search result title. Put it at the top of a simple landing page. Put it in an email sign-off. Those small exercises reveal whether the name gives the business a useful starting point or asks the copy to do too much explaining.

The idea behind NamoLux

NamoLux was designed around the moment after inspiration: when a founder has candidates worth discussing and needs evidence rather than more noise.

The public workflow is intentionally focused. A founder can paste a shortlist of up to 50 names into Bulk Check. NamoLux checks six extensions — `.com`, `.io`, `.co`, `.ai`, `.app` and `.dev` — and presents the results together. Availability is best-effort information, not a promise of registration, so it should always be confirmed with a registrar before money changes hands. But seeing the same evidence across every candidate is far better than guessing or checking one name at a time.

Once a shortlist is serious, the founder can use Founder Signal. It is not legal or trademark advice. It is a consistent way to look at useful naming qualities such as clarity, memorability, pronunciation, extension strength, character quality and brand risk. The aim is not to announce that one name is objectively perfect. The aim is to make the reasoning legible: why does this candidate feel stronger, where is it weaker, and what still needs human judgment?

That distinction is central to the product. Good naming is part language, part strategy and part practical due diligence. No score can replace a trademark search, customer research or a founder's understanding of the market. But a clear comparison can prevent a decision from being driven solely by the loudest opinion in a meeting.

From generation to judgment

I do not think founders need another tool that tells them they have a hundred names. They need help moving from "interesting" to "worth building on".

That is why NamoLux keeps the evidence close to the shortlist. A founder can compare finalists, keep notes, export the decision record and share a view-only report when a co-founder, adviser or client needs to understand the choice. The product is deliberately more interested in the decision than in an endless feed of ideas.

There is an important constraint in this approach: a tool should stay honest about what it knows. Domain availability can change. A name can be available as a domain but conflict with an existing business or trademark. A high Founder Signal result does not create legal rights. The final checks remain human work, and serious decisions deserve qualified advice where the risk warrants it.

A score should invite a better question

There is a particular failure mode in software: presenting a number with so much confidence that people stop asking what it represents. I did not want NamoLux to do that.

Founder Signal is useful when it becomes a prompt for a better conversation. If one candidate is easier to pronounce but another has a stronger primary-domain position, the score can help make the tension visible. If a name is memorable but risks feeling too generic, that is something to discuss. If two options are close, the decision may depend on the customer's language, the founder's product strategy or feedback from a small group of people in the target market.

In other words, a result should lead to questions such as: “What does this name make people expect?” “Where would it be difficult to use?” and “What evidence would change our minds?” Those questions are more valuable than a false sense of certainty.

This is also why the workflow asks the founder to select a primary extension before scoring a shortlist. A `.com` may matter most for one business, while an `.app` or `.ai` is more relevant for another. Comparing every candidate against the same chosen extension is fairer than allowing different domain preferences to distort the comparison after the fact.

The score should never hide a candidate or suggest that a lower-scoring name cannot work. A founder may have real strategic information the system does not have: a connection to a particular word, a customer insight, an existing community or a reason that the name fits the product's future direction. The tool's role is to make the decision more considered, not less personal.

Building a product around the awkward parts

As a developer, I enjoy the visible part of product work: a clear interface, a responsive layout, a focused flow. The more difficult work is often invisible.

Domain data is a good example. A result should appear quickly enough to support a founder's momentum, but the system also needs to be transparent when a provider cannot give a conclusive answer. That is why NamoLux treats uncertainty as information. A result that needs verification should be shown as such, rather than quietly presented as a certainty.

The same is true of scoring. Founder Signal is calculated on the server so the scoring logic stays consistent and a browser cannot silently change the result. The score is accompanied by context because a number without an explanation encourages the wrong kind of confidence.

The product also needs to behave well for people who use it on a phone, between meetings or alongside a co-founder. The best workflow is not the most elaborate one. It is the one that lets someone understand the candidates, act on the result and return later without reconstructing the reasoning from memory.

Reliability is part of the product, not a technical footnote

There is a temptation with AI products to focus entirely on the moment a result appears. For a naming product, that is only one part of the experience. A weak result, an unclear availability response or a score that changes without explanation can damage trust faster than a slower but transparent workflow.

NamoLux is a name decision workspace for solo founders. 3 Bulk Check runs and 1 Founder Signal run per UTC calendar month. Pro is £7.99/month. 120 Bulk Check runs and 120 Founder Signal runs per UTC calendar month. Pro also includes saved projects, CSV exports, shareable decision reports, and an ad-free workspace.

Those details are not the reason someone visits a naming tool, but they affect whether it feels trustworthy. A founder is already dealing with uncertainty. The software should not add more of it through hidden failures or unexplained behaviour.

That practical focus comes from the kind of work I do more broadly. On my developer portfolio, I write about building fast, SEO-ready websites and useful product prototypes. The common thread is not a particular framework or visual style. It is trying to remove unnecessary friction between a problem and a useful next step.

What "brand intelligence" means here

Brand intelligence can sound grander than it is. For NamoLux, it means asking concrete questions in a repeatable order:

• Does this name communicate something useful without being trapped by a literal description?
• Can a first-time reader say it, spell it and remember it?
• How does it look next to the other candidates, rather than in isolation?
• Which primary domain extension matters for this business, and what does the availability evidence show?
• What needs a separate legal, market or language check before a founder commits?

This is not a shortcut around hard decisions. It is a way to make hard decisions less chaotic.

What founders can do before they commit

The right name is not usually found in one prompt. It is developed through comparison. Here is the process I would use whether or not NamoLux was involved.

Start with a brief, not a list of suffixes

Write down the product, audience, category, personality and future ambition. Be specific about what the company does, but do not let the present feature list become the name. A product for independent retailers may need to feel dependable and practical; a tool for a creative team may need more energy and openness. Those differences change the naming territory.

It also helps to list what the name must not imply. If the business may expand internationally, a very local reference can be a poor fit. If it will serve serious financial decisions, a playful name may create unnecessary resistance. A good brief gives later ideas a direction without forcing them into a cliché.

Create variety before you evaluate it

Make room for several routes: descriptive compounds, evocative real words, invented but pronounceable words, and names that combine a familiar root with a new form. Do not compare ten near-identical options and conclude that naming is impossible. A meaningful shortlist contains contrast.

Then read the candidates aloud. Send them in a sentence. Imagine introducing the company in a podcast, on a sales call or to a customer who has never seen the spelling. A name that is elegant only on a screen may be a burden everywhere else.

Choose the domain question deliberately

There is no universal answer to the `.com` question. For some companies it remains the clearest default. For others, a relevant `.io`, `.ai`, `.app` or country domain may be a practical choice. What matters is that the decision is deliberate and that founders understand the trade-off.

Check the extension you care about first, but do not hide the rest of the picture. A candidate with a strong `.com` but a problematic name may not be better than a distinctive candidate with a well-considered alternative extension. Use the NamoLux pricing and workspace overview only when you need more runs, saved work or reports; the underlying discipline is the same on any plan.

Separate domain availability from legal clearance

This is worth stating plainly. A domain lookup does not tell you whether a name is legally clear. It does not establish whether another business has earlier rights, whether a mark is registered in a relevant class, or whether the name creates a risk in a particular market.

Use domain information to narrow the shortlist. Then search official trademark databases in the jurisdictions that matter, look for active businesses in the category and take professional advice when the investment or exposure is material. A domain may be purchasable and still be a bad business decision.

Keep a written reason for the winner

When a team chooses a name, write down why. The note can be short: the audience, the product promise, the domain choice, the drawbacks considered and the checks still required. This helps the founder communicate the decision internally and makes later brand work more coherent.

That is the point of a decision record. It does not make the name permanent; sensible companies revisit assumptions as they learn. It gives the first version of the brand a foundation that is more deliberate than "we all sort of liked it".

Naming, SEO and the work that comes after launch

A name by itself does not rank a website. There is no special string of letters that removes the need for useful content, a clear offer, accessible pages, technical quality and genuine trust. Search visibility is earned through the work a business does after launch.

But names still influence the work. A clear, distinctive name can make direct searches easier to interpret. It can reduce friction in referrals and word of mouth. It can give a site a more coherent subject to build around. Conversely, a generic name can make it harder to tell whether people are looking for the company or for a broad phrase.

That is why I think of naming as part of the product foundation, not an isolated creative task. The next steps — messaging, pages, a domain, product onboarding and content — all inherit the decision.

NamoLux has an About page that explains the decision-workspace focus, and the Journal is where we publish practical guidance about naming and domains. The long-term roadmap is guided by the same principle: add capabilities only when they reduce real uncertainty for a founder. That may include better ways to develop a brief, compare options or organise the checks around a decision. It should not mean adding decoration just because it looks like progress.

What I want NamoLux to become — and what it should not become

The ambition is not to make a product that tries to own every part of branding. Founders have different needs at different stages, and specialist advice matters when the stakes are high. A lawyer should handle legal clearance. A researcher should help when a brand needs deep cultural or market work. A strong designer should shape an identity once the name earns that investment.

NamoLux should be useful in the space before those commitments: the period where a founder has ideas, needs to narrow them responsibly and wants a clean hand-off into the next piece of work. That is why the roadmap should be judged by whether a new feature improves the quality of the decision. A better brief can be useful. A way to find a genuinely different naming direction can be useful. A clearer report can be useful. A decorative feature that makes a weak name look finished is not.

It is an intentionally modest philosophy. The product does not need to claim that it can manufacture brand meaning in a click. It needs to help a founder recognise a candidate with enough clarity, potential and practical evidence to deserve their next hour of work.

About the founder

I am Andrew Barrett, a developer from Rhyl, North Wales, and the founder of NamoLux. I build practical web products for the point where an idea needs to become something people can use: fast websites, product prototypes, SEO-ready foundations and clearer decision flows.

NamoLux is my attempt to bring that builder's perspective to startup branding and domain naming. The product does not claim to choose a company's future for anyone. It gives founders a structured way to bring their own ideas, inspect the evidence and move forward with more confidence.

If the product does its job, a founder leaves with more than a list of names. They leave with a decision they understand — and a domain worth checking carefully before they build on it.