business
Marketing 101 – Your business website
I’m probably the last guy in the world who should be blogging about sales and marketing, I’m a techie after all (and like most techies, for a long time, I thought if you did good technology the customers would follow without any persuasion required). But maybe some of what I say will resonate with other techies out there more than if it comes from a sales and marketing guy. This blog started out as Marketing 102 – Business cards but as I wrote the introductory paragraph I started talking a little about the preceeding step of preparing your business website and, well, here we are.
I’ll get back to the business cards in a later post including some recommendations for who to use to print a small volume of nicely finished cards and what you should put on the cards.
I guess for a technology company (large or small), I figure your first step in marketing should be putting together a website for your business, possibly accompanied by a blog (if you have the time and energy to write regularly and you have something useful to say). At a minimum, your website should answer the following questions,
- Who
- What
- Why
The who involves telling the customer a little about you, your background as well as providing the obvious such as contact details (email, phone and physical address) and maybe some details on what your company’s mission is.
The what involves telling the customer what you actually do. When you start on this, if you’re a techie, you’ll enter a brief fugue state where you start spewing technical terms and concepts that only other level 7 nerds will understand (hey it’s ok, I’m one too, I understand). Once you get over this, step back, and translate these terms into plain english that a (non-technical) customer can understand (so, while Atlantic Linux can deploy a large-scale event management framework utilising SNMP, IPMI and active and passive agents to quantify the availability of your enterprise infrastructure – in plain english we do remote system monitoring or even Linux systems support).
The why is the little bit about why customers should be talking to you instead of the company down the road for the services they require. This is similar to what you do but more about the customer than you. It can be summed up in three words,
Benefits, not features
So, rather than telling the customer about your 20 years of experience with Linux, tell them about how that 20 years of experience means that you’ve seen all the things that can go wrong in their systems and you know how to fix them. Rather than talking about how you’ve used 15 different Linux distributions on 10 different types of computer, tell the customer about how you have enough knowledge of Linux distributions to know which one will suit their needs (obviously, if you’re a software developer or a Windows consultant then you might want to talk about software development or Windows rather than Linux but you get the idea).
Putting a good website together is a long, painstaking process and will involve frequent rewrites and pruning (I reckon it’s a good sign if you find yourself taking stuff out rather than putting stuff in). We’re still working on our one but I think we’re getting close now (for the last year or so :).
Categories
Archives
- September 2010
- February 2010
- November 2009
- September 2009
- August 2009
- June 2009
- May 2009
- April 2009
- March 2009
- February 2009
- January 2009
- October 2008
- September 2008
- August 2008
- July 2008
- June 2008
- May 2008
- April 2008
- March 2008
- February 2008
- November 2007
- September 2007
- April 2007
- March 2007
- February 2007
- January 2007
- December 2006
- September 2006
- July 2006
- June 2006
- April 2006