Posts Tagged ‘Marketing’

10 Rules for Vendor Negotiations

Monday, December 7th, 2009

Almost all technologist get the opportunity at some point in their career to negotiate with vendors and/or manage a vendor relationship. Often this is a critical part of the job for the VP of Operations or the CTO/CIO. Below are some ideas on how to make the negotiation and ultimately the relationship with the vendor successful.

  1. Be honest. Don’t lie to vendors about anything. It’s often tempting to stretch the truth about other vendors and their offers, timelines, budgets, approval requirements, etc. It’s better to say nothing, lies will damage the relationship forever.
  2. Don’t take things personally. The vendor’s sales reps do this day in and day out, most aren’t going to lose sleep worrying about if you like them or not. Your loyalty and motivation should be to your investors.
  3. Consider the relationship. While negotiating is often viewed as a game, be aware that your behavior will follow you into the relationship. See rule #1.
  4. Give yourself time. Time is your best friend in negotiations. Many vendors have rearranged their fiscal year because their clients know how desperate many sales reps are to close sales and receive their commission during these times.
  5. Give yourself options. Follow our advice on scalability so that you are vendor neutral and can change vendors with little effort or concern.
  6. Do your homework. Find out about the vendor, their customers, their solvency, their post sales support, etc.  Use your network, find out what other people pay for similar services. Be prepared for there to be huge differences based on the total size of a purchase a company makes but at least know the ballpark range.
  7. Keep negotiators separate from implementers. If possible have the people negotiating the deal different from the people who have to work daily with the vendor. This way in the event either party feels slighted in the deal they don’t have to work with the same people the next day.
  8. Don’t discuss your budget. The vendor has no need to know how much you can afford to spend on this purchase. It’s okay to let them know that you will need additional authorization to make the purchase if you think the price is beyond your ability to authorize.
  9. If it’s not in writing it never happened. Lots of things get said during negotiations that get put into the contract and therefore never get delivered. If it’s important get it in writing.
  10. Ask for anything. Once you’ve exhausted the pricing negotiation ask for other things that aren’t cash related such as additional modules, higher support levels, steeper discounts for future purchases, etc.

Perception is Reality

Sunday, August 16th, 2009

We’ve all heard that saying “perception is reality” but do we really believe it applies to us? We all probably think we’re competent at our jobs but being so is only half the journey. We need to demonstrate that competency to our peers, employees, bosses, and customers in order for it to matter.

In good counseling sessions we should receive some praise for what we’ve done well and some feedback for areas that we need to improve. My advice to people receiving feedback is first determine if it is factual. Do you really write poor quality code? Are you actually tough to work with? If you believe the feedback is not factually correct, don’t become defensive and try to refute it because the blame is still yours! Even if the facts are incorrect but your peers, boss, or customers perceive them to be correct, you own this perception.

People usually hate to hear this and think they should just have to focus on their skills and everything will work out but the reality is that you need to own people’s perception of you. The same goes for customers. You cannot just focus on building a good product and assume customers will flock to you. You have to own your customers perceptions, which means you have to consider not only the quality of the product but how you introduce the product, how you roll out the code, how you perform maintenance on it. All of these ultimately result in your customer’s perception of the product, not just the number of bugs.