Startup Websites That Work: Avoiding Common Mistakes

About This Blog

This site is for  entrepreneurs.  A full RSS feed to the articles is available.  Please subscribe so we know you're out there.  If you need more convincing, learn more about the site.



And, you can find me on Google+

Connect on Twitter

Get Articles By Email

Your email:


Blog Navigator

Navigate By : 
[Article Index]

Questions about startups?

If you have questions about startups, you can find me and a bunch of other startup fanatics on the free Q&A website:

Subscribe to Updates


30,000+ subscribers can't all be wrong.  Subscribe to the RSS feed.

Follow me on LinkedIn


Current Articles | RSS Feed RSS Feed

Startup Websites That Work: Avoiding Common Mistakes


My prior article, “Startup Websites That Work” continues to be one of the most popular articles on this site.  I’d like to follow-up on this topic with some additional practical tips on making sure your startup’s website works for you.  I review several new startup websites a week and there are simply too many of them that are making simple, common mistakes.

You need to get good at getting your website to work for you (see prior article).  Part of this process is avoiding the common mistakes. 

Tips For Avoiding Common Startup Website Mistakes
  1. Don’t Have A Flash Intro:  Sure, a really cool Flash intro was included as part of the template you purchased from somewhere for $79.  Guess what, nobody cares.  Just because it came for free doesn’t mean you have to use it.  Today’s web users are an impatient lot.  If you’re running a startup, the last thing you need is to lose a single potential customer simply because they didn’t have the most recent version of Flash, were annoyed by the load time, couldn’t wait for the intro to finish, and didn’t have the patience to click on the “skip” link.  Unless you’re selling software to the fashion industry or some other creative sector, the chances are pretty high that a large majority of your site visitors don’t care much for Flash.  Quick question:  When was the last time you came across a website with a slick Flash intro that was just sooo cool that you were whipping our your credit card so you could buy the product/service offered?  

  1. Focus On The Message, Not The Mechanics:  If you’re like me and have a development background, you tend to want to spend time on the “structure” of the website.  Things like using CSS for layout instead of tables, making sure the site is compliant with every known universal standard, passes every possible HTML “validator” and is in general representative of The One True Way For Site Design.  The reason for this is simple:  It’s much easier to focus on the code, because that’s what we programmers do.  Passing an HTML validation test is kind of like getting code to compile.  It’s structured.  It’s clean.  There’s a clear “end result”.  Problem is, nobody cares.  Not really.  You should be spending 95% of your time figuring out what you want to say.  You need to tweak the language.  You need to have people review it, and listen really well to the feedback they give you.  Too many startup founders spend all of their time on getting the code for the site “just right” making the actual content an after-thought.  This is plain wrong.

  1. Get A Freakin’ Domain:  If I see one more startup website that is running as a sub-domain at or some other hosted service, I’ll scream.  Really, I will.  It’s not pretty.  A domain costs < $10 year.  There’s simply no reason to have a bunch of people link to  Trust me, those guys don’t need to visibility and backlinks.  You do.  It’s a pain in the neck to try and change domains later.  Avoid the hassle and just register your domain name now.  It’s just good, clean living.

  1. Don’t Write Your Own Content Management System (CMS):  As programmers, we tend to oversimplify things and end up writing code that we shouldn’t.  My rule of thumb is:  The only lines of code you should be writing are those that go into your product.  Everything else is a distraction and waste of time and money.  There are any number of workable software products out there for creating and managing a website.  Pick one.  I sincerely doubt that your needs are just so special that none of the off-the-shelf solutions will work.  Resist the temptation to roll your own.

  1. Don’t Try And Become A Designer:  Chances are, you’re not a web designer and don’t play one on TV.  Sure, you were the smartest kid in your class and can learn just about anything in an hour, but design is not about a skill – it’s about talent.  There are few people in the world that are both exceptional designers and exceptional software developers and exceptional business people.  Accept your limits and either hire a professional or use a professional designed website template.  Website templates are cheap, plentiful and there’s something out there for everyone.  Spend the money, not the time.

Summary of My Point:  None of the above should be particularly controversial.  If you think they are, we really need to talk.  As a startup founder, you have a thousand things to worry about (and that’s just today).  Your website is important.  Your message is important.  Just get the simple things right and avoid some of the common mistakes.  

Posted by on Mon, Jul 17, 2006


1. Flash is useful if done correctly and does only take part of the screen.
2. Agreed
3. Agreed
4. Agreed. Can you recommend any free/open source software?
5. Agreed. In my case, it is my design and I am not a designer. The green area is for a flash/still message.

posted on Tuesday, July 18, 2006 at 2:58 AM by Manoj Ranaweera


This is probaly not the proper forum and Dharmesh can delete this comment.

4. I am happy with Drupal. At least it should be in consideration.

On further thought I will probably start/find a thread on this in the forums...

posted on Tuesday, July 18, 2006 at 5:01 AM by

Great ideas. Developers REALLY need to learn how to integrate their code with pre-exisiting tools. It took me awhile to realize this, but it's finally sinking it.

posted on Tuesday, July 18, 2006 at 9:59 AM by Trent

Making sure that every single line of code validates is a loss of time, I agree, but advocating tables vs CSS for layout is very wrong. You do not see any value in all the talks about using semantic markup?

posted on Tuesday, July 18, 2006 at 11:54 AM by Jean Moniatte

Completely agree with you. I did a related post sometime back at
<a href=
It's really all about keeping it simple (not simplistic) and not reinventing the wheel.

posted on Wednesday, July 19, 2006 at 6:22 PM by Intrepid

Nice article. Good practical advice. I really agree with number 2: I spend ages making sure everything is validated layed out etc. and whilst it is reasonably important, its not as important as the actual thing I'm trying to create.

At the end of the day I need a working website that meets the needs of the user as best as possible and within a reasonable amount of time.

posted on Thursday, July 20, 2006 at 3:15 AM by James

I agree that standards are important. However, I think this is not a black and white issue in the context of getting a startup off the ground. Yes, focus on standards-based development (tables for layout = bad). But should you really spend 3 extra days working out that nasty IE/FF padding discrepancy? Is it really worth an extra week to stamp out those last few issues that are keeping you from validating XHTML strict? I think that's the larger point -- yes, these things are important, but not at the exclusion of moving forward with your product and building your business. In the end, that is really what's important -- that spotless source view won't do you much good if your business fails.

posted on Thursday, July 20, 2006 at 3:20 AM by

#5 is irrelevant if you're say, a game development, or web development company.

posted on Thursday, July 20, 2006 at 9:15 AM by Alexander Curtis

I am employed as a programmer, yet I have always been interested in web design. After all, I got my interest in programming from wanting to create a CMS for my websites. Forcing myself to try and learn PHP, which at the time when I was quite young was a big step. Since helping me through college and university as I had a head start above a lot of students.

I do feel I can manage to do BOTH programming and design, although I need some help with the business side of things at the moment. Which is where my girlfriend becomes more useful.

Good article though. Interesting read.

posted on Monday, July 31, 2006 at 11:10 AM by noginn

Hi Dharmesh, 
I totally agree that developer shouldn't start writing CMS of their own. But there are needs for which you have to create your own CMS, take for example twitter. Do you think that any existing CMS solutions fits for twitter?

posted on Wednesday, April 22, 2009 at 10:43 PM by Yogesh Agrawal

Comments have been closed for this article.