How Murky is Your Techsoup?

In response to my last post, Seanan from Techsoup (site) simplified Microsoft's charity software policy (link) as best as possible. It helped some, so for that I thank Seanan, but after reading the clarification I could not stop laughing. It was that hysterical, maniacal sort of laughter that usually ends in shuddering and tears. Microsoft has really handed Techsoup a lemon. The problem is compounded by the fact that different software manufacturers have given Techsoup limes. In the end it is doubtful that non-technical staff trying to gain control of their software inventory (instead of leaving it in the hands of consultants) could ever work with these policies. I'm a technical person and I am having trouble with them. I now know what staff feels when I start spouting tech jargon. I also spoke with a Techsoup customer service rep and even he had to consult with a few people to answer my questions about Microsoft licensing. The ball is still in Billy's court.

Techsoup offers an outstanding service but for the last several years it has been the same service with the same problems. Non-profits are starting to grow and building up their infrastructures. Techsoup could be the tool these organizations increasingly rely on. But that is not going to happen under these complex licensing agreements. Of course, that's not Techsoup's fault but they can do something to make things simpler.

Since I have a venue I'm going to make a suggestion. Techsoup, use it if it makes sense: Don't force people to learn the complex structures of the purchasing part of these policies. Since you have decided to provide software to non-profits, please make it easier to obtain them. Upon registration, provide the registrant a set number of Tokens for each manufacturer. If I were the registrant, I would start off with a Purse that had 6 Microsoft Tokens, one for each title I am allowed to buy, and 4 Adobe Tokens for the 4 titles they allow me to buy, etc. In addition, I would have Shopping Bags for each order I'm allowed to place. For Microsoft there would be 2 bags good for 2 years. The purpose of all this is so when I get to the checkout I can see how my Purse has been allocated allowing me to reconfigure the cart to maximize my purchasing ability. Additionally this would allow me to consider all the other wonderful software that would be available to me if I didn't have to figure out all those policies. I can't imagine this would be too hard because someone at Techsoup must already be keeping track of who is purchasing what and how much. This would also allow customers to review their purchasing options at a glance instead of setting aside an afternoon.

In addition to simplifying purchasing, I would love to see bundles or easily navigable suggestions like those that retail shopping sites offer. So for Windows Server products, show me that I can get a 50 CAL package, server licenses, and Exchange 2003 with link in the description. Also tell me what I need to make the purchase work. It would suck if a project ended costlier than it should have because the organization didn't understand either a manufacturer's policy, Techsoup's policy, or both.

Help us out Techsoup.