Most IT Admin’s at some point deal with Vendor’s directly. No matter if they are the ones to write the check, there is quite the negotiation involved when it comes to getting the product you want, for the price you want. And even after the fact, sometimes you forget what required components you needed, and end up buying other services for a higher price.
1) Single vendor relationships are not good to drive value. Competition is key, this does not mean that every bid should be competitive, there aren’t enough hours in the day and everyone gets tired. But every eighteen months, pick a technology area and review it. Do both a technology review and a commercial review. Your review cycles may be shorter, it depends on your work load.
2) Review street prices regularly; there are a variety of sources for this, some formal, some informal. Vendors do not like it but they know it happens. But it is important to understand why prices differ; it could be size of organisation or it could be a prestige thing. Let your sales-man know that you are paying above street price and that you are reviewing things.
3) New requirements need to go competitive. A sign that things have got too comfortable is that you simply default giving new business to the incumbent.
4) Be aware of the market, talk to the incumbent about competitive products; let them know that you are aware of the competition. Attend trade-shows; talk to other vendors, I know sales-guys are irritating but when the incumbent phones up and finds you are in a meeting with their rivals, there will be a moment of doubt.
And when you are doing the deal, here’s a few tips and thoughts. I am not a procurement expert but I have spent a few million here and there on storage.
1) List price is meaningless; discount levels are meaningless. Vendors should produce a cost of manufacturer and then try to negotiate a premium on this. Vendors also hate breaking things down by line-item as it reveals that you are paying massive amounts for commodity items. Do not let a vendor flannel you with a cost for a solution, get it broken down and understand what you are paying for.
2) Maintenance; you should always be able to negotiate improved maintenance terms. Hardware maintenance is pretty easy to get extended gratis, software is often harder. Review maintenance regularly; if a piece of software is at or close to it’s terminal release, consider dropping the maintenance. If you really need it at a latter point, you can often re-instate, you’ll have to pay the back maintenance but you’ll likely not need it anyway. Make sure this is contractually agreed.
3) Technical refresh/take-out; if you are refreshing with the current vendor, only pay maintenance on one lot of kit whilst the refresh is happening. If you are refreshing with a new vendor, agree that the new maintenance/warranty period only starts when the migration is complete. Always try to negotiate a trade-in.
4) Software licensing; try to negotiate a pay for the amount you use as opposed to the pay for the whole frame! And always try to agree that software licenses are transferable between frames.
5) A vendor TCO model is worthless unless they are willing to guarantee it without caveats. If they think their kit will save you money, skin in the game is key!
6) Training; I have had teams which have had more training than any other team in a department because I ensure that any deal is sweetened by the provision of training for ‘free’. Big deals should come with free training and I am amazed at the number of people who do not leverage this.
7) One-off-deals; one-off-deals, you know the end of quarter/year specials? We all do them, we all regret them at times. Plan your one-off-deals, you know they’re coming but treat them like a normal deal. You know when the vendor quarters/year-ends are; so try and align your procurement cycles if you can. And I’ve never had the pricing on a one-off-deal pulled because I have missed the cut-off.
8) Guaranteed price decline, the cost of kit goes down all the time; ensure that you’ve got a guaranteed price deflator on a quarter-by-quarter basis to reflect this
I think these are great things to think about, and 7. has relevance, as I know a few Admin’s that have taken that path.
Please read his full post, as I didn’t quote then entire article.
Thanks to Storagebod.