10 September 2007

eBox and Warp Networks

I met Ignacio Correas, CEO of Warp Networks (Spain), at the Open Source Business Conference last Spring. This is when I first heard about Warp Networks and the eBox platform. Warp Networks is a consultancy in Zaragoza, Spain, founded by some of Spain's more active open source developers from the Debian, Ubuntu, Gnome and MySQL projects.

eBox is an open source software project Warp Networks began. It allows one to easily install, configure, and manage a small enterprise server, for all the services one would need in a small and growing enterprise: VoIP, email (with integrated antispam and antivirus services), file sharing, etc. The community has been steadily building around eBox to the point that it will likely be the Ubuntu Gutsy Gibbon server configuration platform.

Ignacio is in the process of developing a separate company around the eBox platform and has begun funding discussions. Mikko Puhakka, Timo Teimonen, and I have all been invited to serve as directors prior to the commercial launch. eBox presents some great opportunities for a business based on open source software. (When you stop and think about it, it fills a very special niche.) I'm extremely happy to be on board! I'll certainly keep people posted as the business unfolds.

559D5241-9E84-4953-B95B-0C2792A04498.jpg


07 June 2007

Open Source Business 3 + 3

Mikko Puhakka began a challenge on his blog yesterday to list three success factors and three things to avoid when building businesses using free and open source software.  He then tagged five of us to jump on. (Mårten Mickos has already responded.)  So, here goes based on what I've seen and done: 

Three ways open source software can benefit your business:

  • Open source software is a great way to enable innovation on your platform.  We all know there are shrinking orders of magnitude differences between the number of people that use your software, to the number that report bugs, down to the number that deeply contribute BUT those contributions can be golden in keeping the creativity and ideas flowing, as well as just plain brilliant direct additions to your product space.  There is no predictability as to when such contributions arrive, but they won't arrive if you don't make the software available. 
  • Your community of users is an incredible asset to spread the word.  It's not just about people using your software for free and telling other people about it, but rather the fact that developers will start taking it to work and it will sneak in under the floorboards.  This is how the PC revolution started.  It's why Visual Basic is still huge.  It's how the Linux revolution happened.  So too with MySQL.  And then the CIO discovers it and they need to treat it as a proper product asset just like any other asset on which the business depends.
  • Use open source software to rapidly develop new product complements for your solution.  It helps amortize the cost of development/support/maintenance across the community of developers/users/customers/partners/competitors.  You must, however, be a good community player. 

And three "ideas" to avoid when thinking about open source software and your business:

  • Just because you published the source code does not make your product any more remarkable to your customers.  At the end of the day, you have a business to run, and that means customers need solutions to their problems.  A mediocre solution won't become "better", or the wrong solution won't suddenly fit the situation, because the source code is now available.
  • Understand your value proposition and your core competency, and choose your license wisely: if your entire core competency that enables your core value proposition to your customers is embodied in the software, DON'T publish it in such a way that you give away the company.  I have seen a situation in the security world where the software solution was everything.  If they had made the software available under the wrong license, they would have essentially given away their future growth.
  • Just because you published the source code does not mean the world is going to work for you for free.  It's been a while since we saw this level of naivety with the original Mozilla launch from Netscape, but I'm betting there are still a lot of business people that don't understand open source software economics that still have old ignorant opinions. 

So whom to tag next?  I'll reach for:

  • Michael Tiemann (an early and original player),
  • Manel Sarasa, OpenBravo CEO (keeping with growing interesting companies in other parts of the planet meme),   
  • Jonathan Schwartz (because a big company opinion is always good to have, and Jonathan is nothing if not original in his thinking and his willingness to push the envelop),
  • Stephen O'Grady (to get the analyst opinion in early), and
  • David Skok (to get an interesting investor opinion)

Okay.  I can't stop here.  Three more opinions I think would be important to have:

  • Javier Soltero, Hyperic CEO (because like Manel he too is in the throws of carefully building a company),
  • Taiwen Jiang "D.J." (because China is coming)
  • Amy Jiang (because China is coming, and Ubuntu is just plain important)

And Christopher Kuhn at OTRS jumped on board as well. 


01 June 2007

Microsoft Messaging on Patents and Open Source Software

Sam Ramji, Bryan Kirschner, Michael Francisco (and briefly Bill Hilf) from the Microsoft open source software lab were front and center last week at the Open Source Business Conference (OSBC), largely because of an article published the previous week in Fortune.  There were several discussions that centered around patents and software business from an open source perspective, and I realized there are several disconnects between the Microsoft legal team and their PR machine, and most of the rest of the world. 

The first disconnect appeared during Microsoft's day long event for open source ISVs the day before OSBC.  Microsoft represents a US$44B revenue stream.  Most of the executives from software businesses in the event represent companies that run US$2M to US$20M.  There is a world of difference between the way these companies need to behave with respect to intellectual property tools and their software assets. 

Most small companies don't care about patents in the same way as a large company must.  A small company will likely file for a patent or three because it can make a real difference in their valuation in both funding and M&A activity.  The management team, however,  applies a different calculus to the problem.  Filing for three patents with good patent attorneys could cost ~US$50K.  That's half a head count for a year.  And the patents won't be approved faster than 24-36 months.

Was the small company to discover a large company infringing their claims, they have very few real options.  They have a ticket to a negotiation implied in their ownership of the patent.  They can't afford to be greedy in the discussion because they can't afford the legal costs of a prolonged legal debate if business negotiations fail. Patent "cross licensing" deals with large companies with thousands of patents are not exactly balanced for small companies.

Most companies just don't live in the space of large cross licensing deals like a Sun, Microsoft, IBM, Intel, etc.  That doesn't mean the smaller company management teams don't respect intellectual property or don't care about it, they just value patents differently in their business model.  I imagine the average $20M company executive would happily entertain the painful and frustrating headache of $100M/year of inbound litigation with which Microsoft lives, if it came with a $44B revenue stream. 

These executives don't want "special" rules for intellectual property.  But neither do they need to think and apply the same rules the same way as companies that are Three Orders of Magnitude bigger.  Indeed, for most of these executives, trademark (i.e. brand management) and copyright management is everything to them, and they're very savvy with respect to copyright licensing. 

The second disconnect is the Microsoft talking point about return on investment for the R&D expense.  Microsoft rightly claims on the order of $7B spent each year on research and development.  The PR talking point is that "they want a return on that investment."  The rest of us see a $44B revenue stream and think, "and what part of that revenue stream shouldn't be considered ROI?"  This is what happens when you let lawyers (cost side of the balance sheet) think they can be a profit center. 

This brings us to the third disconnect.  The Microsoft executive and legal teams look to the IBM claims of $2B-$4B/year in IP licensing revenues and thinks, "why not us?"  Why not indeed.  Well let's look at some of the differences.  You see it's really a business marketing problem. 

Microsoft historically has a culture of putting programs in place so as to scale efficiently and keep margins high.  This is good business practice.   So the legal team did as well: here's the "IP Licensing" home.  [I think it's significant that the URL contains a segment named "about".  Remember --  legal is a cost center.  Most of the legal concerns that reach the public eye would rightly show up under "about" on most company web sites.]  As you explore this part of the site, you'll find all goodness about why you should license Microsoft IP through their licensing programs 'cause they're smart guys that invest a lot in R&D.  (And they are and they do.)

But it's different than the business model practices developed over the long haul by IBM.  Go look at the model Microsoft is chasing: here's the IBM IP licensing page.  The page starts with the statement that they're the market leader in awarded patents (regardless of R&D investment), and they're "expanding their use of intellectual property to accelerate the adoption of open standards and open source software through creative licensing and stewardship programs."  There's a prominent link on the simple page to all the program work in which IBM invests to modernize and reform the patent system and "reinvent the invention system."  It is a remarkable piece of positioning. 

Here is the company that clubbed Microsoft like a baby seal in the early cross licensing days, essentially playing the reformist hero.  It is masterful marketing. IBM thinks through the business strategy from all angles (including support for open source software), then tells a GREAT story about it.  [Indeed, an IBM executive would have wept for laughing so hard if they'd been present for the vaguely unprofessional bashing Sam Ramji took at the 451 Group reception at OSBC from a panel made up of Dan Kohn (Linux Foundation), Jeremy Allison (Google ex-Novell), and Eben Moglen. Andy Updegrove was the only balanced voice on the panel.  Sam had to stand in the audience with the rest of us plebes and wait his turn for the mic.]

It's not that Microsoft doesn't want reform in the patent system, they simply don't talk about the work they do sponsor.  And when they try to message reform it fails.  They come across complaining about the inbound $100M/year litigation costs, with the additional hammering they've taken by Eolas (~$500M) and the Sun license (another $2B).  They try to say they too want reform because they're victims too!  But it's a poor story up against the $44B revenue stream.   It has all the negative impact of Paris Hilton fretting about her approaching jail time while shopping for ten thousand dollar handbags.  (I wonder how much inbound litigation IBM takes a year?)

What they need is a leadership message.  One that resonates with a clean position with which the rest of us mere mortals can sympathize and possibly even support.  Daniel Chalef (CEO, Knowledge Tree) offered the start of one for them during the ISV day but it was likely lost and not recognized for the brilliance it represents.  Daniel suggested Microsoft take a leadership position in the EU AGAINST software patents

This is fabulous.  It could even be cleanly messaged as "encouraging the EU to not follow in the footsteps of the U.S. until such time as patent reforms have been implemented and proved."  They would not be saying no software patents, but rather encouraging the EU to not make the same mistake the U.S. made until the U.S. figures out how to clean up the mess we all agree exists.  It would show leadership, align with their current positioning, and not sound like victimized whining, nor would it clash with their licensing programs.   

IBM is leading the reform movement and winning friends with its messaging while happily licensing and defending its intellectual property.  It comes at a cost and maybe the margins aren't as good as Microsoft's historical packaged software margins, but business it is.  Sun has reinvented its executive messaging cleanly to say they've got to play the game as a large business in the U.S., and they'll only use the portfolio defensively.

It's time for Microsoft to do the same before they're again [possibly mis]quoted as making veiled threats against customers.   Microsoft is a software company.  It's about time they again acted as one and stopped pushing their IP licensing business to the forefront of their messaging.  It's not (nor will it ever be as big as) the business we (their customers) know they're in so it only serves as too frustrating a distraction.   



25 April 2007

Startup Mechanics: Compensating the Field

Matt Asay has a great post on the considerations he went through as vice-president of business development at Alfresco to develop the sales compensation plans.  Getting this right is so so important.  Sales people will exactly respond to the incentives in front of them.  We all joke about "dogs on the hunt" metaphors, but really, good sales people are like idiot savants in good clothes — they have an uncanny ability with mathematics.  (One look at you and they instantly know how much of next quarter's bonus you represent and will budget their time accordingly.) 

No amount of threatening, cajoling, or shaming a salesperson will move them off their comp plan.  And no good salesperson remains in an organization when they realize their comp plan is unattainable (whether because it's unrealistically set or the organizational support doesn't exist).  As Matt observes about his comp plan: "it aligns interests between the salesperson and the customer."   Exactly so. 


24 February 2007

Startup Mechanics: CommunityNext Founders Panel

Guy Kawasaki moderated a panel at CommunityNext entitled “Founders Panel - How They Got to over 5 Million Members and What Is Next”.  In his own words, "This is the most amusing panel that I’ve ever moderated, and the speakers defied many conventions of tech entrepreneurship—in particular the ones that venture capitalists believe are 'proven.'"  The panel includes:

The hour long video is up on Google.  It is simply awesome.  Each of the panelists is crisp and clear.  They all tell brilliant stories.  The stories all strike home. 

  • The panelists all made slightly different references to it, but at the end of the day you have to care about what you're building.  You have to have passion. Build what you know and love. 
  • Each company is small and focused and they fret about maintaining the cultural integrity of the team while they grow it.
  • Listen to your customers.  They will tell you what needs to be done, especially when they start to know "your product" better than you do.  (There was a great caveat about NOT listening to your customers, but this was more in the context of "how" to listen to your customers.)

Each was asked to tell the story of how they got going.  Apparently drinking is often involved.  If you're involved in a start-up or think you want to be, the video is definitely worth the hour of your time.

Picture of Panel


29 December 2006

Startup Mechanics: Culture comes from the Top

Culture comes from the top.  This isn't true only in start-ups.  It's true for all social  organizations.  (Revolution on the other hand comes from the grass roots.)  But it's very important to think about culture as you find your co-founders and especially as you begin to hire your first employees. 

I discovered Andy Monfried's awesome post (via Seth Godin) that describes the difference between a start-up's cultural environment versus a traditional company.  This is the sort of cultural leadership you embrace.  This is why I prefer small companies over big companies. 

Indeed, as the company grows, one no longer can simply consider the culture, but one has to determine how best to transmit it.  I've been having a debate recently with a friend on how culture transmits successfully.  Some organizations seem to be able to pull it off (e.g. USMC and Judaism).  Many can't. 

I suspect that culture begins to break down when the people at the bottom observe there's a multi-tier culture in place between the executive management at the top, and the plebes at the bottom.  When the observed reward systems, punishments, and purposes begin to diverge, the cultural system breaks down rapidly.  ("It's okay for me to <re-state options | sexually harass a direct report | focus on competitors instead of customers>, but not okay for you.") 

Published "values" and hallway art work don't transmit culture if the observed behaviour contradicts the message.  If you want your best employees to be the next line of outside-the-box innovators to grow your business, then you need to be outside-the-box first!   



21 September 2006

Startup Mechanics: Security, Responsibility, and Equanimity

I have been a cofounder twice in my career.  I have also left paying jobs to work as a contract consultant three times.  Every time I do this I hear from several different people (wistfully) that they "don't know how I can do it."  Invariably there's a remark about the security that comes with working at large companies, and the conversation moves on.

To be clear, that "security" is a myth.  Just ask anyone that currently works at Intel.  The last summer job I had was during the Summer of '80 working a melt shop floor in a steel mill.  We were in the depths of the "blue collar" recession in Canada, and the steel industry was taking it the teeth.  All the summer students were laid off mid-summer.  The first programming job after university I had was with a consulting firm that designed steel mills.  I watched them shrink from 350 people to about 15 over the next three years before closing their doors.  I got over the idea that the company was my friend early in my career.  I had many friends at DEC as it collapsed.  When you watch any company (big or small) go through that sort of turmoil you quickly learn that regardless of the message you get  about your position being safe, you won't honestly know until the pink slips stop falling.  Security is the myth we tell ourselves.

What a startup does require however is a different attitude towards responsibility.  There is no safety net.  Things need to be done.  The founders and early employees need to do them.  No one else is there to catch the ball.  There is no "staff" to take up the slack.  (Indeed this is why many executives from large companies make terrible startup execs.  They have always had staff to execute on their vision.  In a startup, you get to have your vision and deal with it too.) 

Decisions need to be made.  You need to be very comfortable with the idea that you will make mistakes and they will be plainly there for all to see.   My father (an engineer's engineer) was one of those few people I know that had a genuine mentor.  Early in my father's career his mentor took him aside and told him that there was a management study that demonstrated that one out of four decisions he made would be wrong.  Any more than this and he wasn't taking enough time to consider the decision.  Any less than this and he was taking too long to make decisions.  The trick is to ensure the mistakes are the less expensive decisions relatively speaking.  My father rapidly climbed the management chain moving from company to company at his own direction and was very successful.  He faithfully passed along this advice to me when I started working.

It wasn't until I was well into my first startup that I realized the truth.  I have never seen such a study.  I'm pretty sure his mentor gamed him.  He needed a young capable engineer to make decisions.  So he told him it was okay to make mistakes, told him the ratio that was "accepted", and that there was a study to prove it[1].  God bless him. 

In a startup you need to be very comfortable constantly making decisions with less than perfect data that will fundamentally effect the course of a small company.  Some of those decisions will be wrong.  Everyone on the team will know it.  How you behave about such mistakes will define your personal success more than the bad decision ever could.  How you behave when others on the team make their mistakes will fundamentally define the success of the team.  As the old saying goes, your successes belong to the team, but your mistakes are all your own.  No where is this more true than in a startup.

There's another feeling with which you need to be comfortable.  That's the feeling that comes from realizing not only all the decisions you're responsible for making (or things you need to do), but that there is a class of important (but less urgent) things for which NO ONE else is yet responsible.  Some things just don't have an owner yet.  These might be things like benefits.  Or 401K programs.  You suddenly need to be responsible for those decisions at a personal level rather than having "the company" make them for you.  Many people aren't comfortable with that feeling either.

To a certain extent, starting a company is a very Zen like affair.  You need compassion and equanimity.  It nicely balances the passion for your customers and the energy to build things.  That journey of a thousand miles does indeed start with one step — you just need to be comfortable knowing you're going to stumble in front of people with every fourth step — acknowledge it, be comfortable with it, and simply keep on walking. 

[1] If anyone ever hears of such a study, please pass along the pointer. It would have been published somewhere in the early 1960s.

Post to del.icio.us