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 business. Show all posts
Showing posts with label business. Show all posts

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!

Friday, March 21, 2008

Who wrote the book on freelancing?

If you're thinking about getting ready to take the leap into a freelancing career for yourself, you may be wondering...who wrote the book on freelancing? Is there a definitive source of information for all the complex quandries you will have - all the scenarios running through your brain, all the excitement? All the fear?



Well, I've taken a peek at How to be a Rockstar Freelancer and I think it does a pretty solid job! It is written by some guys who really have some great experience in freelancing and have an obvious passion for it. You get the vibe from the opening quote in the book:
"Beginning a freelancing career is one of the most exciting things you'll ever do. Maybe it's the thrill of giving your nine-to-five the flick, maybe it's the prospect of being your own boss, or maybe it's just the knowledge that you are the master of your own destiny."
Here are a list of the chapters and topics that are covered in this book:
  1. Getting Started - what is freelancing, your job and freelancing on the side, etc.
  2. Your Brand - what is branding for a freelancer, what can branding do for you?, etc.
  3. The Working Day - home or office, a happy workplace, equipment, etc.
  4. Getting Your First Projects - your portfolio, your first leads, referrals, etc.
  5. Project Scope and Timing - taking a brief, documenting a brief, estimating timeframes, etc.
  6. Pricing Yourself - your costs and your break-even rate, calculating your hourly, etc.
  7. Doing the Project - setting expectations, tracking your hours, communication, etc.
  8. Clients - leads and clients, essential client skills, etc.
  9. Getting Paid - invoicing, cash flow, bookkeeping and accounts, etc.
  10. Marketing Yourself - positioning yourself, marketing cycles, etc.
  11. Expansion - subcontracting, partnerships, hiring staff, etc.
Notice that doing the project is #7 on the list! That is very true! There is much preparation that needs to be done - and much that I wish I would have done when I first first getting into this - in order to have a smooth ride along this path.

Monday, March 17, 2008

Get Your Portfolio Up

If you're on the road to building your freelancing business, and you're answer to the question "Can I see your portfolio?" is any one of the following, you have a problem:
  • Ya, I worked on it in one of my classes but don't have it finished yet.
  • Yes, I have it on a CD, but its not online.
  • Yes, but its not ready yet.
  • No
You need to realize that your portfolio is the most important touch point to the outside world. When potential clients consider working with you, their initial impression is going to depend almost entirely on what they see in your portfolio.

"Well I don't have one, yet", you say? Not a problem. This is your first homework assignment. And there's good news, there are tons of people out there just waiting to take advantage... ahum... help you. Now, you don't want to work with just anyone who will work with you, and you're in luck because you have a rare moment in your career and business life to be picky! Pick whoever you want to work with and realize that although they are helping you build your portfolio, you are really helping them! Also, there's no reason you shouldn't be able to get at least some minimal pay while building your portfolio. But, unless you absolutely can't afford it, I highly recommend that you pick some high-end, nice sites to work on, because even if you're not paid up front, the value of having nice portfolio pieces will pay off in the long run.

Since I started working freelance gigs, I completely stopped providing resumes even when people asked me. I took it as a sign, that they as a client weren't very well informed about how to find a good developer, so I wouldn't even humor them by providing one of my older versions. And really, as you are working freelance and building your business, you need to get beyond the resume mindset, and realize that your reputation should go beyond that.

Now, once you get your portfolio up and running, that's great! However, you need to continue to update it periodically over time. Don't let it get rusty, and probably at least once a year you want to do a nice overhaul on it. I can't emphasize enough how much a nice portfolio will pay dividends by helping you bring in more business down the line. You can also tie it into a newsletter to further increase your reach.

Friday, March 14, 2008

Persistance


Wanted to share some perspectives on the topic of persistence. I feel that I learned a good deal about persistence in my experience finding and converting sales leads for my web development business. And it seems like the more people I come into contact with, the more I realize how few people have this skill down.

To give a little background on how I worked my sales leads, but without giving out all the secret sauce, I'll put it this way. Basically I had a simple system for following up with warm leads a certain number of times in a non-spammy way.

It seems like so many people and organizations either fail to be persistent at all or they setup some sort of spammy system which is not well thought-out and which leads ultimately to a lot of frustration and annoyance for the user. As an example, I remember calling Authorize.net about a question I had and I somehow gave them my email, and have been receiving like weekly emails ever since, I've probly received at least 100 emails by now. And the first time or two I really thought the emails were coming from the account exec I spoke with originally, at least they had a decent email template set up. But after like the 6th one I realized I had been duped! And from then on, my opinion of them just continued to go down until I setup a gmail filter so I never again saw their emails....ah yes the blessed gmail filter!

Wednesday, March 12, 2008

Collaborating with Developrs and Other Geekery

I picked up a little inspiration for a post that has been marinating in my brains for a little while now, which is to lay out some effective techniques I've gained in working with (don't use the "m" word) developers or as the article I referenced so endearingly puts it - geeks. And if you don't know already, geek is in fact an endearing term, and "uber-geek" quite an honor...more on that later.

Little background on myself. I was a math major in college, took a bunch of comp sci classes, and got into my first web developer position out of college. I too, am a geek....or was, well I'm not really sure which. So in all fairness it does help me quite a bit because I understand the lingo and have a similar brain chemistry to the geekdom - but really more than that I think its that I understand the common problems plaguing developers, how one feels as a developer, and simple ways to work with them in a non-intruding manner.

First off, I'd say you definitely want to have a casual style. Tech's aren't impressed by fluff or pomp and circumstance, they like to get right down to the meat of the matter, and it matters to them what you think, the content of your argument or statement. They just don't enjoy formal business attitudes or fronts very much at all.

Be nice. This one should be obvious but in the midst of urgent situations, fires that need to be put out, or clients that are confused and flailing their arms about looking for a solution, it can be easy to pass tasks off to them without acknowledging their effort or that they are busy with something else. So if you're going to ask for some help - something like "hey man, if this isn't a good time lemme know but I had a question for you". Also recognize the kinds of things that they don't like to do - repetitive or simple things that are a distraction from the complex work they are focused on - and try to work around their level of concentration at any given moment.

Communication Protocol. Tech's are most likely going to prefer to communicate by IM or email, even if they're sitting five feet away from you. They prefer it because it forces you to be more specific in your requests, and it can be much more efficient for them to respond to. And again, concentration. You have to realize this is a developer's currency - without concentration they can't get anything done, and what they do get done will be buggy, which....well that's a whole 'nother topic. So if they repeatedly ask you to IM or email them some detail, or to submit it by an online bug tracker, just get used to it - you're going to get more mileage out of their time, and they'll enjoy interacting with you much more.

Respect their time. You need to realize and really internalize that these guys are very smart and talented and they're doing important work. Think twice before asking them a question - especially if it has to do with troubleshooting Outlook, they most likely hate troubleshooting Outlook, or I don't know....maybe that was just me. And the stuff that you do need to pass off to them, do it in batches - don't give them onesy twoesy's all day long. That way, when you need something important, you'll have a good track record with them and they'll be willing to help because they realize you don't cry wolf all the time.

Hope some of these tips are useful....look forward to feedback on either side of the fence.

Sunday, March 9, 2008

On Motivation

As I reflect on the level of motivation I've had throughout the various work and business situations I've been in at various times in my life and career, it becomes increasingly clear to me how critical the intangible factor of motivation is. You have to be passionate about what you do. You have to do something that gives you the opportunity to create new things, to use all your potential, and with a minimal amount of criticism and negative feedback from those you work with.

Passion. It's the driving force behind what we do. It's waking up in the morning and the first thought that comes to mind is that project you're excited about. Sometimes it requires cultivation in periods of repetitious work that may be required in a certain season. Sometimes it comes like an avalanche and there's nothing you can do about it, you're drawn to venture out on a whim, to start a business, to start a family, to spend all day coding a cool web app.

It's hard to work without passion and motivation. As much as you tell yourself that you'll do whatever you need to do to survive and to thrive, there comes the time where you can get burnt out by what you are doing, and you don't have any juice left. At that point, you may have to make a decision, you may need to take another path in your life.

I believe that your authentic passion and excitement for what you do will show through to your customers as well as your colleagues. If you've gotten to the point where you're just coasting and not really excited about what you're doing, it will become obvious to those around you. So be honest with yourself, be honest with what you love and don't love to do - and strive to keep your internal motivation, drive, and passion to succeed!
Showing posts with label business. Show all posts
Showing posts with label business. Show all posts

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!

Friday, March 21, 2008

Who wrote the book on freelancing?

If you're thinking about getting ready to take the leap into a freelancing career for yourself, you may be wondering...who wrote the book on freelancing? Is there a definitive source of information for all the complex quandries you will have - all the scenarios running through your brain, all the excitement? All the fear?



Well, I've taken a peek at How to be a Rockstar Freelancer and I think it does a pretty solid job! It is written by some guys who really have some great experience in freelancing and have an obvious passion for it. You get the vibe from the opening quote in the book:
"Beginning a freelancing career is one of the most exciting things you'll ever do. Maybe it's the thrill of giving your nine-to-five the flick, maybe it's the prospect of being your own boss, or maybe it's just the knowledge that you are the master of your own destiny."
Here are a list of the chapters and topics that are covered in this book:
  1. Getting Started - what is freelancing, your job and freelancing on the side, etc.
  2. Your Brand - what is branding for a freelancer, what can branding do for you?, etc.
  3. The Working Day - home or office, a happy workplace, equipment, etc.
  4. Getting Your First Projects - your portfolio, your first leads, referrals, etc.
  5. Project Scope and Timing - taking a brief, documenting a brief, estimating timeframes, etc.
  6. Pricing Yourself - your costs and your break-even rate, calculating your hourly, etc.
  7. Doing the Project - setting expectations, tracking your hours, communication, etc.
  8. Clients - leads and clients, essential client skills, etc.
  9. Getting Paid - invoicing, cash flow, bookkeeping and accounts, etc.
  10. Marketing Yourself - positioning yourself, marketing cycles, etc.
  11. Expansion - subcontracting, partnerships, hiring staff, etc.
Notice that doing the project is #7 on the list! That is very true! There is much preparation that needs to be done - and much that I wish I would have done when I first first getting into this - in order to have a smooth ride along this path.

Monday, March 17, 2008

Get Your Portfolio Up

If you're on the road to building your freelancing business, and you're answer to the question "Can I see your portfolio?" is any one of the following, you have a problem:
  • Ya, I worked on it in one of my classes but don't have it finished yet.
  • Yes, I have it on a CD, but its not online.
  • Yes, but its not ready yet.
  • No
You need to realize that your portfolio is the most important touch point to the outside world. When potential clients consider working with you, their initial impression is going to depend almost entirely on what they see in your portfolio.

"Well I don't have one, yet", you say? Not a problem. This is your first homework assignment. And there's good news, there are tons of people out there just waiting to take advantage... ahum... help you. Now, you don't want to work with just anyone who will work with you, and you're in luck because you have a rare moment in your career and business life to be picky! Pick whoever you want to work with and realize that although they are helping you build your portfolio, you are really helping them! Also, there's no reason you shouldn't be able to get at least some minimal pay while building your portfolio. But, unless you absolutely can't afford it, I highly recommend that you pick some high-end, nice sites to work on, because even if you're not paid up front, the value of having nice portfolio pieces will pay off in the long run.

Since I started working freelance gigs, I completely stopped providing resumes even when people asked me. I took it as a sign, that they as a client weren't very well informed about how to find a good developer, so I wouldn't even humor them by providing one of my older versions. And really, as you are working freelance and building your business, you need to get beyond the resume mindset, and realize that your reputation should go beyond that.

Now, once you get your portfolio up and running, that's great! However, you need to continue to update it periodically over time. Don't let it get rusty, and probably at least once a year you want to do a nice overhaul on it. I can't emphasize enough how much a nice portfolio will pay dividends by helping you bring in more business down the line. You can also tie it into a newsletter to further increase your reach.

Friday, March 14, 2008

Persistance


Wanted to share some perspectives on the topic of persistence. I feel that I learned a good deal about persistence in my experience finding and converting sales leads for my web development business. And it seems like the more people I come into contact with, the more I realize how few people have this skill down.

To give a little background on how I worked my sales leads, but without giving out all the secret sauce, I'll put it this way. Basically I had a simple system for following up with warm leads a certain number of times in a non-spammy way.

It seems like so many people and organizations either fail to be persistent at all or they setup some sort of spammy system which is not well thought-out and which leads ultimately to a lot of frustration and annoyance for the user. As an example, I remember calling Authorize.net about a question I had and I somehow gave them my email, and have been receiving like weekly emails ever since, I've probly received at least 100 emails by now. And the first time or two I really thought the emails were coming from the account exec I spoke with originally, at least they had a decent email template set up. But after like the 6th one I realized I had been duped! And from then on, my opinion of them just continued to go down until I setup a gmail filter so I never again saw their emails....ah yes the blessed gmail filter!

Wednesday, March 12, 2008

Collaborating with Developrs and Other Geekery

I picked up a little inspiration for a post that has been marinating in my brains for a little while now, which is to lay out some effective techniques I've gained in working with (don't use the "m" word) developers or as the article I referenced so endearingly puts it - geeks. And if you don't know already, geek is in fact an endearing term, and "uber-geek" quite an honor...more on that later.

Little background on myself. I was a math major in college, took a bunch of comp sci classes, and got into my first web developer position out of college. I too, am a geek....or was, well I'm not really sure which. So in all fairness it does help me quite a bit because I understand the lingo and have a similar brain chemistry to the geekdom - but really more than that I think its that I understand the common problems plaguing developers, how one feels as a developer, and simple ways to work with them in a non-intruding manner.

First off, I'd say you definitely want to have a casual style. Tech's aren't impressed by fluff or pomp and circumstance, they like to get right down to the meat of the matter, and it matters to them what you think, the content of your argument or statement. They just don't enjoy formal business attitudes or fronts very much at all.

Be nice. This one should be obvious but in the midst of urgent situations, fires that need to be put out, or clients that are confused and flailing their arms about looking for a solution, it can be easy to pass tasks off to them without acknowledging their effort or that they are busy with something else. So if you're going to ask for some help - something like "hey man, if this isn't a good time lemme know but I had a question for you". Also recognize the kinds of things that they don't like to do - repetitive or simple things that are a distraction from the complex work they are focused on - and try to work around their level of concentration at any given moment.

Communication Protocol. Tech's are most likely going to prefer to communicate by IM or email, even if they're sitting five feet away from you. They prefer it because it forces you to be more specific in your requests, and it can be much more efficient for them to respond to. And again, concentration. You have to realize this is a developer's currency - without concentration they can't get anything done, and what they do get done will be buggy, which....well that's a whole 'nother topic. So if they repeatedly ask you to IM or email them some detail, or to submit it by an online bug tracker, just get used to it - you're going to get more mileage out of their time, and they'll enjoy interacting with you much more.

Respect their time. You need to realize and really internalize that these guys are very smart and talented and they're doing important work. Think twice before asking them a question - especially if it has to do with troubleshooting Outlook, they most likely hate troubleshooting Outlook, or I don't know....maybe that was just me. And the stuff that you do need to pass off to them, do it in batches - don't give them onesy twoesy's all day long. That way, when you need something important, you'll have a good track record with them and they'll be willing to help because they realize you don't cry wolf all the time.

Hope some of these tips are useful....look forward to feedback on either side of the fence.

Sunday, March 9, 2008

On Motivation

As I reflect on the level of motivation I've had throughout the various work and business situations I've been in at various times in my life and career, it becomes increasingly clear to me how critical the intangible factor of motivation is. You have to be passionate about what you do. You have to do something that gives you the opportunity to create new things, to use all your potential, and with a minimal amount of criticism and negative feedback from those you work with.

Passion. It's the driving force behind what we do. It's waking up in the morning and the first thought that comes to mind is that project you're excited about. Sometimes it requires cultivation in periods of repetitious work that may be required in a certain season. Sometimes it comes like an avalanche and there's nothing you can do about it, you're drawn to venture out on a whim, to start a business, to start a family, to spend all day coding a cool web app.

It's hard to work without passion and motivation. As much as you tell yourself that you'll do whatever you need to do to survive and to thrive, there comes the time where you can get burnt out by what you are doing, and you don't have any juice left. At that point, you may have to make a decision, you may need to take another path in your life.

I believe that your authentic passion and excitement for what you do will show through to your customers as well as your colleagues. If you've gotten to the point where you're just coasting and not really excited about what you're doing, it will become obvious to those around you. So be honest with yourself, be honest with what you love and don't love to do - and strive to keep your internal motivation, drive, and passion to succeed!