Darcy Burner's WebLog

Software vendor central

Software vendors, aka "ISVs" in Microspeak

Imagine, if you will, that there is somebody in Microsoft whose job it is to make sure that companies who want to develop software on the Microsoft platform have everything they need to do so successfully.  They need to have developer tools like Visual Studio, they need information (MSDN and MS Press books, for instance), they might need training.  That's not all, though.  What else do software companies need in order to be successful?

I have some theories, but I suppose it might help to introduce myself.  I'm a program manager at Microsoft, currently working on ISV (”independent software vendor”) programs (as in “offerings“, not as in “software programs“).  I've been at Microsoft for almost four years, mostly doing marketing (Wait! Don't leave yet!  I'm not doing marketing these days - please don't hold it against me!); before that I worked as a programmer and in other technical roles at a number of independent software vendors, including Asymetrix (now Click2learn), CenterLine, and Lotus.  My early career was competing with Microsoft when I was working at Lotus, and spent a whole bunch of time working on Unix (Centerline made Unix C and C++ compilers and interpreters).  So I hope I have, at the very least, some empathy for our ISV community, and all of the reasons they might love and fear Microsoft simultaneously.

Okay, so for those of you still reading (Hi Dad! Are you the only one?), here's where we're at: we have a bunch of things we give ISVs, including free or heavily-subsidized training, MSDN subscriptions, the MSDN website, the Microsoft Partner Program, the opportunity to list their solutions in catalogs (like the Windows Catalog at www.microsoft.com/windows/catalog), and logo programs (such as the “Designed for Windows XP” program).

What else should we be providing?

Published Friday, January 23, 2004 5:03 PM by DarcyBurner

Comments

 

Shannon J Hager said:

Someone to clean the spam [and possibly answer questions, maybe even pose questions] in the isv newsgroup.
January 23, 2004 5:10 PM
 

Darcy Burner said:

Okay, that's a good start. :-) Concise and actionable. I believe the newsgroup you're referring to is http://communities.microsoft.com/newsgroups/default.asp?icp=isv&slcid=us, correct? (Give me a week or two to get it sorted out.)
January 23, 2004 5:26 PM
 

Scott Sargent said:

What about some programs for very small software vendors? Sole proprietors or single person operations. As someone who seeks to eventually start my own business entering into the ISV market seems daunting at times. Having the Certified / Designed for Windows __ logo would certianly help. I'm not sure of the cost of the logo programs but I've heard its pricey. What might be really cool (and this may very well already exist) would be a roadmap of sorts to help ISVs to become logo certified; ie Step one, step two, step three...
January 23, 2004 6:01 PM
 

Avonelle Lovhaug said:

I'll second Scott's thoughts on programs for very small software vendors. Sometimes it feels like Microsoft is only focused on larger organizations. Those of us who are on our own would love help from Microsoft from many areas: technological assistance, marketing assistance, whatever. But I don't mean to imply that I'm unhappy with Microsoft. Really, I think you guys do a lot already.
January 23, 2004 6:21 PM
 

Adam Hill said:

I third the very small software vendor idea. Power and Empower are very cool, but Empower has *ahem* requirements some might find onerous.

MSDN Dev Centers and the possibly open beta of Longhorn are very nice as well.
January 23, 2004 6:30 PM
 

Scott Sargent said:

Yes, Avonelle said it perfectly. On the technical side Microsoft's support of me and my career have been incredible. I honestly couldn't ask for more. I've been very fortunate to be a part of the ASPInsiders organization & recently awarded MVP status.

Microsoft is arguably the best at the software industry. Some roadmaps and case studies that are based on MS's experience producing,marketing & shipping products would help point businesses/individuals like me in the right direction. IMO the toughest thing about becoming an ISV on a small scale is that there's a huge fundamental difference between writing code and producing,selling, and supporting software products.

Ok, I promise not to write a book on someone else's blog. :)
January 23, 2004 6:41 PM
 

denny said:

About the Tablet PC:

I have some ideas but right now I can't go buy a tablet PC, I know that I can do alot of the development on XP but I'd love to have away to run the XP Tablet OS without having to spend 1500-3000 bucks up front.
a) give us a way to get the OS and let us make the cat on the digitizer part.
b) do a program with hardware folks to get developers tablets realy cheap.

I bet if all the folks who are interested had a chance to get a Tablet for say .... $600 USD as a NFR -- and add a "I will be developing a program" statement.... then you might get a whole lot more tablet sales faster and more new programs for them...
January 23, 2004 6:52 PM
 

denny said:

About the Empower Program:

$400.00 for MSDN is awsome! now how many folks know it's there??

I only heard this by seeing a blog here.

I have recently been to an MSDN local event and the guys there did not say anything about it. I have not seen any messages on GDN.com about it. I have not seen alink on msdn.microsoft.com for it...
so how are new ISV's supposed to find out they can get in the door for 400 bucks??

tell folks to link to it and talk it up at your events.... I just told a buddy and he was dumb struck at how cool getting all the MSDN good stuff for 400 was, and was amazed at how hard it was to find out about.
January 23, 2004 6:58 PM
 

Danny Boyd said:

My reaction to your question would lead me to suggest the notion that select Universities be considered ISVs of a sort, albeit unique. I work at a large public institution in the Southeast that has standardized on Microsoft products for everything from MS Office applications and automation processes to Web development platforms, programming paradigms, and tools. Yet we still pay a hefty price for the useful references, services, and training that so many large ISVs receive at a substantial discount (or free). Given the impact that our IT environment has on students, and consequently the future knowledge workers in the US, it would seem in Microsoft's interests to assist us. Appreciating our University’s goal of fully utilizing the technologies and tools selected and purchased to operate our campus, conduct research, and educate students, it would seem advantageous for Microsoft to move us closer to the head of the class.
January 23, 2004 7:18 PM
 

Avonelle Lovhaug said:

I think the Empower program looks cool too. But as a small ISV, I'm worried about agreeing to things that will end up costing me a lot of money. For example, while it doesn't say this everywhere, in the program guide for Empower is says this about the requirements: "Upon expiration of your membership, make a reasonable commercial effort to join the Microsoft Certified Partner Program based on successfully passing one of the software tests authorized by Microsoft and listed in the table below**." From what I can tell, getting my software tested is going to cost me $800 or more.
Also, I can participate in the Empower program for only 12 months. I understand why, but it doesn't appear to leave me with a direction after the first year. I don't have any intentions of becoming more than just "an army of one" so to speak, and one of the requirements for Microsoft Certified Partner is that there be at least two certified people in my "organization". So I'll be back to square one after that.
January 23, 2004 7:24 PM
 

Mary McRae said:

We signed up as an ISV partner last year when we began working with the Office 2003 beta releases and developing smart document solutions. We just signed up for empower - how can you pass up $400 for a year's Universal MSDN subscription! To those that have been asking, there's tons of info on the microsoft partner site. (http://www.microsoft.com/partner) You can sign up to be a registered partner for free - no logos for use, but access to all sorts of wonderful info including marketing materials, training, discounts, listing in the solutions directory, ... We've just submitted our first application for certification - oh yeah, received an email with a code for a FREE certification test! So whether you sign up for empower or not or become certified/gold or not, sign up to be a registered partner! Last year when we initially signed up we only had 4 full-time employees (including our office manager) so don't let size deter you.
January 23, 2004 7:26 PM
 

Avonelle Lovhaug said:

Hmmm. I wonder if I can renew my existing MSDN subscription with this, or if I have to purchase it separately. I already have an MSDN Universal subscription, and it doesn't expire until April or May.
January 23, 2004 7:35 PM
 

denny said:

"says this about the requirements: "Upon expiration of your membership, make a reasonable commercial effort to join the Microsoft Certified Partner Program based on successfully passing one of the software tests authorized by Microsoft and listed in the table below**." From what I can tell, getting my software tested is going to cost me $800 or more. "

if you fail you have no further cost....

if you are able to make any kind of resonable cash then I would say that the "Next steps" that are logical is to keep building the relationship with MS.

if you don't want to work with Ms then why buy VS.NET and other developer stuff??

and as I see it the whole point is to give new developers/software businesses a decent "Bootstrap" / "Kickstart"

whats wrong with that??
January 24, 2004 8:01 AM
 

Avonelle Lovhaug said:

Denny - I agree that if your software fails the test, then you probably have no further cost. I also agree that if you want to build a relationship with Microsoft, you will probably have to invest both time and money, and that isn't an unreasonable expecation.

However, I'd make two observations:

1) I'm not sure how building that relationship with Microsoft will really benefit me. I'm a one-person shop. I don't intend to get bigger. Since Darcy asked, I'll tell him that something that could really help me with Microsoft is to help me with sales and marketing. Help me connect with people who might use my product, or help me figure out how to get my product (based on Microsoft technologies) listed in a case study on their site. But honestly, I don't *expect* Microsoft to do this. It would be nice, but as a little guy, I figure Microsoft is probably interested in organizations a lot bigger than just me. That's okay, too.

2) I like Microsoft's products - that's why I buy VS.NET and use their stuff. I don't have to have to "work with Microsoft" to want to use their developer tools. But since Darcy asked how Microsoft could help small ISVs, I'm trying to answer the question. That said, I'm not sure I have any good answers. I'm just trying to think through what would help me, as an ISV.

While I mainly do custom software development, I'm getting ready to release my first product. I'm interested in the Empower program, and I'm interested in geting my software "tested". But I can't just look at the cost of the Empower program as $375 - I have to look at what the entire effort will cost, and see if it makes sense. I'm not convinced that saying my product is "logo certified" or whatever is enough to make the investment worth it. Maybe someone could tell me how that will translate into more dollars for me? I mean, do people really buy their software based on that distinction? I don't, but perhaps I'm in the minority.
January 24, 2004 12:09 PM
 

Mary McRae said:

Hi Avonelle,

It doesn't cost a thing to register as an ISV partner. You don't HAVE to join the empower program. Just get yourself listed, and then you have access to all of the Microsoft marketing materials. Most of the "special" benefits are only for certified/gold certified, but we were able to get listed in the Solutions Directory, attend the partner conference, etc. - all by just being a registered partner - for free. You'll still have to buy your MSDN Universal, but if that's all you need, then it sounds like the best deal for you.
January 24, 2004 4:36 PM
 

Avonelle Lovhaug said:

Mary - thanks for the advice! That is probably what I will end up doing. I'll still be interested in Darcy's feedback about this thread, because I would like to hear how he believes the small ISV fits into the picture with Microsoft.
January 24, 2004 9:17 PM
 

-:[web caboodle]:- said:

January 26, 2004 10:39 PM
 

-:[web caboodle]:- said:

January 26, 2004 10:50 PM
 

-:[web caboodle]:- said:

January 26, 2004 11:28 PM
 

Richard said:

$400 for MSDN Universal is a great deal, but it appears that Microsoft doesn't really want small companies as partners. I tried to register my company tonight but get a

"We are not able to process your application at this time. Please contact your Regional Service Center for further information." message at:

https://partners.microsoft.com/partnerprogram/IdentifyOrganization.aspx

So much for partnering...

Three companies and seven years ago, I participated in one of Microsoft's partner programs (they even sponsored my company at the time for a good marketing event for startups). At that time, Microsoft wanted small company partners. Now, this error message says it all...

Richard
May 17, 2004 6:42 PM
 

Darcy Burner s WebLog Software vendors aka ISVs in Microspeak | Paid Surveys said:

May 29, 2009 4:29 PM
 

Darcy Burner s WebLog Software vendors aka ISVs in Microspeak | debt solutions said:

June 19, 2009 12:37 PM
Anonymous comments are disabled

© 2009 Microsoft Corporation. All rights reserved. Terms of Use  |  Trademarks  |  Privacy Statement
Microsoft
Page view tracker