My blog has moved!

You should be automatically redirected in 2 seconds. If not, visit
http://www.programmersmind.com/blog/
and update your bookmarks.

Showing posts with label clients. Show all posts
Showing posts with label clients. Show all posts

Tuesday, March 25, 2008

You Need an Elevator Pitch!

As a freelancer, you're constantly in sales mode. You want to present yourself well to the outside world, to existing clients, and potential clients. In order to do this, you should have a well-polished elevator pitch that you can share quickly and concisely with people you come into contact with.

First impressions matter. When people first meet you, and especially if they are not technical/design-saavy people - which most clients are not - they are not going to understand much of what you say, if you get too far into the details of what you do right away. They need something easy, digestable, and memorable - something that distinguishes you in their memory.

I think that, at least from my own personal experience, technical people tend to get into details to quickly. Someone asks you what you do - you start off by saying "I'm a programmer", and if they ask any follow up question, before you know it you're getting into your favorite object oriented framework, and the obscure bug that you started working on before lunch and which is dominating your mental activity at the moment!

If you don't have something quick and concise, they will just label you in their mind as a "computer guy" and will probly call you the next time their anti virus software is blocking their email!

OK, so what's your pitch, smart guy? ... I'm glad you asked :)

I run a small web development company that specializes in small to medium web applications, especially community websites. Two of the significant problems that I've solved within my own business are finding and converting good sales leads, as well as finding and managing good, cost-effective development and design talent. I enjoy mentoring other developers, as well as bringing value to my clients.

Sunday, March 23, 2008

Don't Give Discounts

You can expect your clients from time to time to ask you for a discount. It may be an existing client or a new client - most of my tips here apply to the latter case, as obviously an existing client you will have a relationship with and will already have an understanding regarding pricing an quality with your client.

Below are the five reasons not to offer discounts to your clients when they ask.
  1. They'll undervalue your services. Whether stated or not, the minute that you offer a discount on your services, the perceived value of your services just went down. You may feel that you are somehow doing the client a favor, although you will of course not state that explicitly. They, on the other hand, might even feel like they're doing you a favor because at least they're giving you the work, and if you accept the discount, they probly think that you need the work enough to accept a discount. Strange sort of contradiction...

  2. They won't expect discounted quality. Even though they know they are paying less for the work, they will want you to pick up the slack. They will still expect the same level of support, and their internal vision of how the product should work will not be changed by the concept that they received a discount. And, in a sense, it's a valid point - for example, when you buy a discounted shirt at the store, you don't expect it to come without one sleave. Now, we know that consulting services are a different beast than retail products, but that mentality is still there.

  3. They'll expect discounts in the future. If you accepted a discounted job once, what's to stop you from doing it again? Although its difficult because you feel like you are being inflexible, you have to realize that's just business, and if you do it once, they will expect it again down the line. You would do the same! If all of a sudden the store never had any more sales ever again, we would feel cheated in some way!
There was a post on a forums I frequent where a real-life scenario embodied exactly this situation. The developer gave the client a bit of a discount up front. Now when things got a little hairy with the project, the developer expected the client to have some level of flexibility, due to the discount. But the client didn't! They wanted their website to work exactly the way that they had imagined it initially - discount or no discount!

Tuesday, March 18, 2008

Taming the Beast: Managing Client Expectations

There are few things in your consulting business which have as large an impact on your bottom line and on your overall piece of mind as managing client expectations. What may sound like a fluffy buzzword is actually an amazingly critical component to your success. It is the difference between getting a second project from the client and only getting one. The difference between getting the project done gradually over time, on schedule, and on budget - and wasting a whole weekend getting things finished up.

Now this business of managing expectations is a sticky issue and I definitely don't pretend to have all the answers. I don't have some experience though and have been through the trenches a bit and can offer a few hints in the right direction. I don't have sufficient space in this post to even go over everything, perhaps I will do a series on this topic later.
  1. Expect the unexpected. Realize up front and get it burned into your mind - the client is going to creep the scope on you! They are going to change their minds on you as much as they humanly can. They are going to say everything is a "small thing", a little change, something that "should be easy, right?". Don't expect the client to somehow understand when they are going out of scope, just realize that they will and stay on your toes!

  2. Early and often. You need to reinforce the scope of your project early in on the beginning of the project and mention it almost every time you speak with them. Remind them that they need to get everything figured out, get everything spec'd out, finalize the scope. Say it in as many ways as possible, because for some reason, it just doesn't get into their heads. You need to train the client on what the development process is - they will not know it coming in, unless someone else has already trained them, and they will not learn it easily. It is, from their perspective, very counter intuitive.

  3. Red flags. You need to keep your eyes open for some classic red flags that your project is going out of scope. Sometimes you'll be talking with them and they'll quickly mention - "oh ya and it should just tie into the database", or "and it will do some emails", or various other sweeping statements that although they sound deceptively simple, will add thousands of dollars to your budget. I remember, early on, being tempted to glaze over those details in the interest of time, or because I was just too tired at the moment to belabor the details. I beg you - belabor the details! Because if not, they will end up belaboring you, my friend!! Every hour you spend up front on scope and discovery will save you 3 on the back end.
Here are some quick tips to make sure you are staying on top of the client's expectations and keeping the scope manageable.
  1. Written contract up front - this is a must, you gotta have something in writin.
  2. Discovery phase - have a defined stage of the process where you are collecting information, and setting up the architecture for the application or website. This stage should have a definitive end date.
  3. Repetition. Again, you have to train the client to understand the necessity for clear specs up front.
After putting these tips into practice, you should be well on your way to managing client expectations in a way that will keep them happy, keep the project on track, and keep you with at least an ounce or two of sanity at the end of the day! ;)
Showing posts with label clients. Show all posts
Showing posts with label clients. Show all posts

Tuesday, March 25, 2008

You Need an Elevator Pitch!

As a freelancer, you're constantly in sales mode. You want to present yourself well to the outside world, to existing clients, and potential clients. In order to do this, you should have a well-polished elevator pitch that you can share quickly and concisely with people you come into contact with.

First impressions matter. When people first meet you, and especially if they are not technical/design-saavy people - which most clients are not - they are not going to understand much of what you say, if you get too far into the details of what you do right away. They need something easy, digestable, and memorable - something that distinguishes you in their memory.

I think that, at least from my own personal experience, technical people tend to get into details to quickly. Someone asks you what you do - you start off by saying "I'm a programmer", and if they ask any follow up question, before you know it you're getting into your favorite object oriented framework, and the obscure bug that you started working on before lunch and which is dominating your mental activity at the moment!

If you don't have something quick and concise, they will just label you in their mind as a "computer guy" and will probly call you the next time their anti virus software is blocking their email!

OK, so what's your pitch, smart guy? ... I'm glad you asked :)

I run a small web development company that specializes in small to medium web applications, especially community websites. Two of the significant problems that I've solved within my own business are finding and converting good sales leads, as well as finding and managing good, cost-effective development and design talent. I enjoy mentoring other developers, as well as bringing value to my clients.

Sunday, March 23, 2008

Don't Give Discounts

You can expect your clients from time to time to ask you for a discount. It may be an existing client or a new client - most of my tips here apply to the latter case, as obviously an existing client you will have a relationship with and will already have an understanding regarding pricing an quality with your client.

Below are the five reasons not to offer discounts to your clients when they ask.
  1. They'll undervalue your services. Whether stated or not, the minute that you offer a discount on your services, the perceived value of your services just went down. You may feel that you are somehow doing the client a favor, although you will of course not state that explicitly. They, on the other hand, might even feel like they're doing you a favor because at least they're giving you the work, and if you accept the discount, they probly think that you need the work enough to accept a discount. Strange sort of contradiction...

  2. They won't expect discounted quality. Even though they know they are paying less for the work, they will want you to pick up the slack. They will still expect the same level of support, and their internal vision of how the product should work will not be changed by the concept that they received a discount. And, in a sense, it's a valid point - for example, when you buy a discounted shirt at the store, you don't expect it to come without one sleave. Now, we know that consulting services are a different beast than retail products, but that mentality is still there.

  3. They'll expect discounts in the future. If you accepted a discounted job once, what's to stop you from doing it again? Although its difficult because you feel like you are being inflexible, you have to realize that's just business, and if you do it once, they will expect it again down the line. You would do the same! If all of a sudden the store never had any more sales ever again, we would feel cheated in some way!
There was a post on a forums I frequent where a real-life scenario embodied exactly this situation. The developer gave the client a bit of a discount up front. Now when things got a little hairy with the project, the developer expected the client to have some level of flexibility, due to the discount. But the client didn't! They wanted their website to work exactly the way that they had imagined it initially - discount or no discount!

Tuesday, March 18, 2008

Taming the Beast: Managing Client Expectations

There are few things in your consulting business which have as large an impact on your bottom line and on your overall piece of mind as managing client expectations. What may sound like a fluffy buzzword is actually an amazingly critical component to your success. It is the difference between getting a second project from the client and only getting one. The difference between getting the project done gradually over time, on schedule, and on budget - and wasting a whole weekend getting things finished up.

Now this business of managing expectations is a sticky issue and I definitely don't pretend to have all the answers. I don't have some experience though and have been through the trenches a bit and can offer a few hints in the right direction. I don't have sufficient space in this post to even go over everything, perhaps I will do a series on this topic later.
  1. Expect the unexpected. Realize up front and get it burned into your mind - the client is going to creep the scope on you! They are going to change their minds on you as much as they humanly can. They are going to say everything is a "small thing", a little change, something that "should be easy, right?". Don't expect the client to somehow understand when they are going out of scope, just realize that they will and stay on your toes!

  2. Early and often. You need to reinforce the scope of your project early in on the beginning of the project and mention it almost every time you speak with them. Remind them that they need to get everything figured out, get everything spec'd out, finalize the scope. Say it in as many ways as possible, because for some reason, it just doesn't get into their heads. You need to train the client on what the development process is - they will not know it coming in, unless someone else has already trained them, and they will not learn it easily. It is, from their perspective, very counter intuitive.

  3. Red flags. You need to keep your eyes open for some classic red flags that your project is going out of scope. Sometimes you'll be talking with them and they'll quickly mention - "oh ya and it should just tie into the database", or "and it will do some emails", or various other sweeping statements that although they sound deceptively simple, will add thousands of dollars to your budget. I remember, early on, being tempted to glaze over those details in the interest of time, or because I was just too tired at the moment to belabor the details. I beg you - belabor the details! Because if not, they will end up belaboring you, my friend!! Every hour you spend up front on scope and discovery will save you 3 on the back end.
Here are some quick tips to make sure you are staying on top of the client's expectations and keeping the scope manageable.
  1. Written contract up front - this is a must, you gotta have something in writin.
  2. Discovery phase - have a defined stage of the process where you are collecting information, and setting up the architecture for the application or website. This stage should have a definitive end date.
  3. Repetition. Again, you have to train the client to understand the necessity for clear specs up front.
After putting these tips into practice, you should be well on your way to managing client expectations in a way that will keep them happy, keep the project on track, and keep you with at least an ounce or two of sanity at the end of the day! ;)