How to name your killer software start up

bridgwatera | No Comments
| More

Company names have a certain special place in the information technology industry.

If you are about to launch the "next big thing" in cloud-based mobile next generation web 2.0 enabled geo-location aware Software-as-a-Service computing then you will want to know how to name your company right?

So how do you do it?

While companies often like to capitalise all the letters of their name to try and conjure up some extra degree of impact, we know that NVIDIA is really Nvidia,
CAST Software is Cast and so on.

Of course if you do have acronyms to show off then use them if they work. It seems to have worked out for International Business Machines and Gesellschaft für Software und System Entwicklung mbH really is better as SUSE isn't it?

Then there is the new trend -- start with lower case and then throw in some caps in the style of eSnips, coComment or ownCloud Inc.

Many of course go the whole hog and stick to lower case for their entire moniker.

Alternatively, some firms opt for the caps on/off routine a la YouTube.

Then there is real next gen style as in (delicious)

Not to forget the old "leave a letter out because it's trendy" misspelling technique as evidenced at Flickr, SoonR and even Zoomr.

You could try the portmanteau style blended approach that seems to have worked pretty well for Microsoft (microcomputers + software), Skype (sky + peer-to-peer network) and Wikipedia (wiki + encyclopedia).

Perhaps Shakespeare's Juliet had it right after all:

"What's in a name? That which we call a rose. 
By any other name would smell as sweet." Romeo and Juliet (II, ii, 1-2)

Ah no but it is important, so why not try the random technology business name generator linked here - it looks like I am launching Total Cyber Paradigm Megacorp Inc.

Hands off, I saw it first!

Facebook pic.jpg

Leave a comment

Subscribe to blog feed

About this Entry

This page contains a single entry by Adrian Bridgwater published on February 15, 2012 3:22 AM.

Serena: can we fix requirements management? was the previous entry in this blog.

How do we manage the BYOD boom, at the technical end? is the next entry in this blog.

Find recent content on the main index or look in the archives to find all content.