How to name a SaaS
A name is worth an afternoon and not a fortnight. It matters less than founders think and costs more to change than they expect.
The short version
- An afternoon, not a fortnight. The name matters less than the product.
- Five patterns cover almost every good software name.
- Three tests: say it on a phone call, spell it from hearing it, search it.
- Check trademarks and app stores before you buy a domain, not after.
- .com is nice, not necessary. Software has lived on .io and .app for years.
How much does the name matter?
Less than the time founders spend on it implies. No product has failed because of its name, and none has succeeded because of one. What a bad name does is add friction (people mishear it, misspell it, cannot find it), and what a legally unavailable name does is force a rename later, which is the only genuinely expensive outcome.
So the goal is not a brilliant name. It is a name with no problems, chosen quickly, so the afternoon it takes is not a fortnight stolen from scoping the thing you are actually building.
You are not looking for the best name. You are ruling out the ones that will cost you something.
Five patterns
| Pattern | Shape | Trade |
|---|---|---|
| Descriptive | Says what it does | Clear now, constraining later |
| Compound | Two real words joined | Available, easy to spell, common |
| Real word, borrowed | An ordinary word used sideways | Memorable; hard to search for |
| Altered spelling | A word with a letter changed | Domain available; spelling support forever |
| Invented | A coined word | Free legally; means nothing until you make it mean something |
For a first product from a solo founder, descriptive or compound is usually right. An invented name is a marketing budget you do not have: it carries no meaning until enough people have encountered it, and "enough people" is the thing you are short of.
The altered-spelling trap. Dropping a vowel gets you the domain and commits you to correcting people for the life of the product: in every support email, every podcast, every conference introduction. It is a small tax charged forever.
The three tests
Say it, spell it, search it. A name that passes all three has no problems; a name that fails one will cost you something every week, quietly.
- The phone test. Say the name to somebody who has not seen it written. If they need it spelled, it fails.
- The spelling test. Can they type it correctly from hearing it once? This is the one that eliminates clever spellings.
- The search test. Search the name alone and the name plus your category. If page one is a bank, an established product or a medical term, you will be fighting for your own name indefinitely.
- The read-aloud-in-a-sentence test. "We use ___ for that." Names that sit awkwardly in that sentence are names nobody recommends out loud.
- The unfortunate-meaning check. Search it in the other languages of the markets you will sell in. Free, thirty seconds, occasionally saves you everything.
Before you buy a domain
Check availability in the order that matters legally, not in the order that is easiest. The domain is the last step, because a domain you own for a name you cannot use is a wasted purchase and an anchor you will be reluctant to abandon.
- Trademark registers in the countries you will sell in, in the relevant class. A free search on the official registers takes ten minutes.
- The app stores, if you will ever ship a mobile app. Names there are enforced separately and aggressively: launching on the App Store alone.
- Existing software in your category. A name already used by a competitor is a problem whether or not it is registered.
- Social handles. Not decisive, but a name with no available handle anywhere is a name in heavy use.
- Then the domain.
On trademarks: registration is per class of goods and services, so the same word can legitimately exist as a software product and a brand of paint. That is a general principle and not advice about your situation. If there is any real overlap with an existing mark, a short paid conversation with a solicitor is far cheaper than renaming a product with customers on it. SaaS legal basics covers the neighbouring questions.
When the .com is gone
Which it will be. Software has run on .io, .app, .dev and .co for years and nobody is confused by them. A good name on a non-.com beats a compromised name on a .com, and the domain is not the decision: the name is.
| Option | Verdict |
|---|---|
| yourname.io / .app / .dev | Completely normal in software |
| getyourname.com / tryyourname.com | Works; slightly dated |
| yourname.com held by a parked page | Sometimes buyable: ask, expect four figures |
| yourname.com is an active business | Pick a different name |
| your-name.com with a hyphen | No. Unsayable on a phone call |
Whatever you pick, own the domain outright and keep it in your own registrar account rather than inside a website builder. It is the one asset that has to survive every rebuild, and it is the first item on the list in how to build a SaaS without code.
An afternoon that ends with a name
- Write thirty candidates in twenty minutes. Quantity first; do not judge while generating.
- Cut to eight on sound alone: say each one out loud.
- Run the three tests. Most of the eight will fail one.
- Check trademarks and stores on the survivors.
- Buy the domain for the one left, plus the obvious misspelling if it is cheap.
- Stop. Go and build the product.
The last step is the one worth enforcing. Naming is pleasant work that feels like progress and produces none, and it is the most common place a first product loses a week: the name only starts to mean anything once there is something behind it.
Frequently asked questions
Does the name of a SaaS actually matter?
Less than founders think. It has to be pronounceable, spellable from hearing it, and not already taken in your category. Beyond that, products succeed and fail for reasons that have nothing to do with the name. Spend an afternoon, not a fortnight.
Do I need the .com?
No, but it is worth real money if it is available and reasonable. A .com you own outright avoids a class of future problem; a good .io, .app or .dev is completely normal in software and nobody is confused by them.
Should the name describe what the product does?
It helps at the start, when nobody has heard of you, and constrains you later if the product widens. A descriptive name plus a clear tagline is the safest default for a first product.
How do I check a name is free?
Search the trademark registers in the countries you will sell in, search the app stores, search the name plus your category, and check the social handles. Do all four before you buy a domain, not after.
What if the exact name is taken by a company in another industry?
Often fine, since trademarks are registered per class of goods and services, but not always, and this is the point at which a short conversation with a solicitor is cheaper than a rename. Never assume based on a web search alone.
The system behind this, written down
Everything above is the map. The Income Loop is the work inside it: modules 0–6 from the problem you solve to the offer that pays for it, plus ten traffic paths: the deeper post banks, the content sales systems and the full software build sequence, in one place.
Get The Income LoopNot ready to pay for anything? The Basic Income Loop is free and includes a complete seven-day starter for Threads, Instagram or software, enough to find out which one suits you before spending anything.