You are here
For the foreseeable future, Mollom will continue to be offered as it is today. I will continue my role as general manager of Mollom, Ben will continue to lead the development of our products and the Mollom team will remain unchanged. If you are a user or customer of either Mollom or Acquia, everything will remain exactly the same.
When Ben and I started Mollom almost 5 years ago, we wanted to do something important. While most people were trying to figure out the social web, we were paddling out ahead of the wave, knowing that many websites would soon have to deal with increasing amounts of spam and content moderation. In the past five years, we have helped tens of thousands of people fight spammers on their websites, including some of the world's leading organizations.
We have blocked almost a billion spam messages since we started. It has been very rewarding for us to see that we have helped make the web a slightly better place. At the same time, we also built a healthy business. We successfully bootstrapped Mollom, and organically grew a team of 6 people.
The social wave keeps on growing; we're helping more and more people and organizations every day. But now that social wave has grown so big, we can't rest on our laurels. There are more business opportunities to explore, some of which we have been working on for a while.
At the business level, it made a lot of sense to merge Mollom into Acquia. Ben and I were looking to raise capital for Mollom to help fund future product development and expand our operations. It was clear that it would require a long-term commitment of my time – just at the point when I wanted to focus more on promoting Drupal globally and driving Acquia's growth and expansion. By having Acquia acquire Mollom, I can still be a part of Mollom, and Mollom could receive the resources to accelerate our efforts and create an even more exciting future for Mollom. It also allows me to double down on Drupal and Acquia. In short, I'm really excited to have Mollom as part of the Acquia family.
Keep an eye on us!
Given that there live one billion people in India, many of which great engineers, one can only imagine what would happen if Drupal gained serious traction there. To that extend, I decided to make a trip to India, and spent last week there with Jacob Singh and Ron Pruett from Acquia. The purpose of the trip was to increase awareness of Drupal in India in 3 ways:
- by organizing DrupalCamps to help create a grassroots community of volunteer developers, freelancers and small to medium-sized Drupal shops (bottom-up strategy),
- by talking to the large system integrators that will employ hundreds of Drupal developers (top-down strategy),
- by doing traditional PR with the media and press.
Together with Acquia's partners, we organized 3 DrupalCamps: nearly 300 people showed up in Delhi, 200 people showed up in Mumbai and 350 people showed up in Hyderabad. In addition, I gave a fourth keynote at ISB, India's premier business school, where about 150 people attended. At each of these events, more people showed up than originally expected. More importantly, this implies that there must be thousands of Drupal developers in India alone, especially since we didn't visit many other big cities like Bangalore, Pune, Chennai, etc.
Furthermore, we met various large system integrators in India: Accenture, Capgemini, Wipro, Virtusa, Cognizant, and more. Each of these are multi-billion IT sevices companies that employ thousands of engineers in India. Most of them have 1,000+ employees in their content management practices alone. Many are using Vignette, Liferay, Adobe CQ5, OpenText and Alfresco. Joomla! and WordPress seemed non-existent with the large system integrators, but all of them were eagerly starting to build a Drupal practice. The size of their Drupal teams ranged from 30 to 120 Drupal people, with all of them trying to hire 5 to 15 new people a month. All of them were rather bullish about Drupal and were hearing about it directly from their clients across the globe.
In general, I'd say that the Drupal community is about 3 or 4 years behind with the Drupal community in North America and Europe. However, they are catching up fast and it won't take long before many of the world's biggest Drupal projects are delivered from India.
Our ears perked when we learned time after time that well-known Drupal sites that we assumed were developed in the US or Europe were primarily delivered from India. And it didn't stop there; we learned that the Indian teams are also instrumental in the sales and pre-sales process. They are often responsible for making the CMS platform decisions for all of their clients regardless of country or industry. In other words, a lot of decisions are made in India and it is of strategic importance that the large system integrators have a good understanding of Drupal. They recognize this is important to their success, and all want to invest in training to build more capacity and to increase the expertise of their existing teams.
Interestingly, the Indian culture is big on software training and professional certification, more so than anywhere else in the world. All Drupal companies -- small or large -- asked about training and professional certification.
Another highlight is that at DrupalCamp New Delhi, about 15 Drupal companies from Delhi met for the first time. Later the same day, we helped organize the first CXO event for Drupal executives. In many ways, these were formative meetings that reminded me of early DrupalCon meetings. For the first time, they got to know each other, explored how to work together, started sharing best practices and toyed with the idea of specialization. I've seen this movie before, and I know what happens when a community of passionate developers start working together. Exciting times are ahead.
Last but not least, I gave about 15 press interviews, many of which resulted in an article in an Indian newspaper or IT magazine.
After 5 days of intensive travel and back to back meetings in three cities, I left India feeling excited about the size of the opportunity for Drupal. It is impossible to grasp the magnitude of the technology community and the influence India is gaining ... without having been to India. There are a lot of reasons to pay close attention about how the local Drupal community will evolve. I like to believe my trip helped accelerate Drupal's growth in India.
A number of concerns have been voiced from the community about the substantial growth Acquia has achieved since its inception, the number of key contributors who are now employed by Acquia, and the subsequent influence that this allows Acquia to have on the project.
While some of these concerns have validity, I also think there is also a fair share of FUD (fear, uncertainty and doubt) being spread. So, let's clear up a few points.
In terms of growth, Acquia currently employs about 150 people. However, fewer than half of Acquia's employees work directly with Drupal; the majority of Acquians work in sales, marketing, hosting operations, finance, HR, etc. In a way, this makes us smaller than Phase2, Node One, Forum One, Propeople, Capgemini, and dozens of other shops in terms of Drupal staff. We have a different mix than most other Drupal shops.
In terms of influence, Acquia employs fewer than 10% of the contributors to Drupal core. Admittedly, on a "per Drupalist" basis, Acquia probably contributes significantly more code and magnitudes more dollars to the Drupal community than any other organization. We are investing in expanding the Drupal community through major learning initiatives. We sponsor more DrupalCamps, where new people are introduced to Drupal, than anyone. We sponsor more interns than perhaps the rest of the community combined, where high school and university students learn how to build a career in Drupal. Not to mention we contribute a lot of code.
I like to believe that is a great thing for Drupal and that not doing so would be a big loss for all of us.
It certainly helps to have venture capital money when making investments in the community, but it is not a magic bullet either. It is not free money. I've explicitly chosen to give up part of my equity in Acquia in exchange for money so that I can invest it back into the Drupal community to help Drupal advance.
I understand that my involvement with Acquia is tricky because its well-being is intertwined with Drupal's. But I help drive the decision-making process at Acquia, and I set those directions with the best interests of Drupal in mind at all times. Making Drupal successful and Drupal's well-being is my primary concern, regardless of the "hat" that I wear. We want Drupal to power as many sites as possible, both small and large. We want lots of Drupal entrepreneurs to thrive in a growing ecosystem. If you look at Acquia's actions, you'll see tons of contributions here. We sponsor DrupalCamps and DrupalCons, and pay employees to improve Drupal modules and themes.
Recently, our acquisitions of Cyrve and GVS have been a topic of debate. I'd like to point out that acquisitions are a two-way street: they don't happen unless both parties are really excited about it. Contributors come to Acquia for different reasons. Sometimes they would rather hand things like business development, sales, and support off to someone more set up for that, so they can stay focused on doing things they really enjoy. Others thrive more in a larger team of smart people working on interesting things, rather than toiling away on their own. Still others have put in huge amounts of their own personal time over a sustained period to help improve Drupal, often at great personal sacrifice, and are looking for an arrangement that makes this commitment to the project more sustainable. Painting these contributors as "bad guys", or the company who allows them to pursue a career that they love as "bad guys", is not healthy for our community, or the individuals involved.
The clear solution to the influence concern is to grow our community, particularly our contributor community. If more individuals and Drupal shops are contributing in a bigger way, this mitigates the risks of any organization, Acquia or otherwise, from exerting too much influence on the overall project.
So as a community, we need to re-frame this question. We need to be asking ourselves: (1) What can we do to grow the community? (2) Why aren't more people who depend on Drupal contributing to it? and (3) How can we encourage Drupal shops to contribute back?
As followers of this blog, you might have read that Acquia acquired two Drupal companies; security specialist Growing Venture Solutions and migration expert Cyrve. We wanted to do these acquisitions because they create a win-win-win situation; it is beneficial for the Drupal community, our partners and our customers. I personally championed and led those acquisitions so I want to take a moment to explain why.
How do these acquisitions affect Drupal?
I believe these acquisitions benefit Drupal by expanding its reach. Migration from legacy systems (like Vignette, RedDot and Interwoven) and from expensive enterprise solutions (like Jive Software, Adobe CQ5 and Sitecore) represents some of Drupal's biggest opportunities -- if not the biggest. My hope is that by acquiring and expanding Cyrve, we'll be able to bring more projects into Drupal. That leads to more site building work, more contributed module patches, and more people talking about their Drupal successes.
Similarly, Acquia's involvement in GVS gives it the resources it needs to pursue new security initiatives that will make Drupal more attractive to everybody. As always, we'll continue to return many developments to the community.
How do these acquisitions affect Acquia's customers?
Acquia's customer base has been growing rapidly, both in number and size. We plan to use these acquisitions to provide our customers with more product options and more experts. We will:
- Offer automated, self-service security tools as part of the Acquia Network.
- Integrate the services of both companies into our Professional Services group. We'll be expanding our security and migration teams, both by training existing consultants and by bringing new employees into the fold.
- Incorporate their curricula into our existing materials so we can help train many more experts on Drupal security and Drupal migrations.
All of these are good for Acquia's customers. But they're also good for the Drupal community at large: we need more migrations and security experts in the community.
How do these acquisitions affect Acquia's partners?
Many of our partners build Drupal websites, but few have in-house security or migration expertise. With Cyrve and GVS, we can all approach joint customers with more-complete offerings. This enables our partners to go after bigger projects.
In short, I believe these acquisitions are beneficial for Drupal, our partners and our customers. However, some people have expressed concerns that, with these acquisitions, Acquia is sucking up a lot of the Drupal talent. Because that concern is not limited to these acquisitions, I've decided to address that in a separate blog post: Does Acquia suck up all the Drupal talent?.
I'm thrilled to announce that Acquia has received $15 million in its fourth round of funding -- that is about twice as much as any of our earlier rounds (series A, series B, series C). Our previous investors affirmed their confidence by participating in this round; they were joined by Tenaya Capital, which has roots in both the San Francisco Bay Area and our home turf of Boston. Tenaya brings more than money: Tenaya's Brian Paul will join our Board of Directors as well.
This is an incredibly exciting time to be at Acquia. Since the series C last November, our staff size has almost doubled, from 70 to 130. We're bursting out of our office space and will be moving to a bigger, 35,000 square feet office soon. We needed all those people to service our thousand-plus enterprise customers, and to plan for the future with new initiatives, such as Dev Cloud and the newly revised Acquia Network. We broke revenue records in Q1 and Q2 this year, following an extremely successful 2010.
Fundraising rounds usually occur either when a company is doing very well, or when it's doing very badly. When it's doing well, investors want to get in on the action to score big. When it's doing badly, current investors hope to turn it around to avoid losing everything they'd already put into it. By all measures, Acquia is doing very well, and this round of funding only confirms that. This is what is called a "growth round", with the money directed toward two objectives:
- Increase sales and marketing, particularly outside the U.S.. It's clear that there are tremendous opportunities for enterprise Drupal outside of the U.S., as our partners prove every day. We'll start by focusing on Western Europe, but are already planning expansion into Asia.
- Acquire talent and products that complement Acquia's own. These "acquia-sitions" (as we jokingly call them) will continue to beef up our staff, expand our product offerings, and respond to requests we've gotten over our three and a half years in business.
Acquia's growth is a testament to the growth of Drupal; we'll continue to give back to the Drupal community in everything what we do. Acquia wouldn't have made it this far without our customers, our partners, our employees and our friends. Thank you!
I'm tracking my work related activities because people often ask me what my days look like. For one month, I'm posting a weekly summary of my work week (e.g. Monday - Friday, not including weekend work). I'll post four summaries in total as that should give people a good sense. This is the summary of the second week. You can compare it with the summary of the first week, if you like.
|Business development||Acquia||5||Meetings with (potential) partners|
|Human resources||Acquia||2.5||Interviewing potential hires|
|Management meetings||Acquia||2.5||Weekly status meeting with updates from sales, marketing and engineering.|
|Staff meeting||Acquia||2.5||All company update meeting|
|Product / engineering management||Acquia||5||Reviewed marketing, sales and engineering progress of different Acquia products, and brainstormed about resource allocation|
|Transportation||Acquia||12||Driving to work and trip to Washington DC|
|Preparing presentation slides||Acquia||2||Gave 2 presentations that required preparation. Fortunately got some help from marketing.|
|Attending conferences||Acquia||6||Gave one keynote at a cloud event, and gave one presentation at 360info/AIIM in Washington DC|
|Blogging||Drupal||2||Wrote 3 short blog posts|
|Drupal 8 initiatives||Drupal||4||Talked to potential initiative owners for Configuration Management, HTML5 and Design|
|Drupal Association||Drupal||1||Started planning a face-to-face meeting with the Board of Directors in early May|
|Reviewing Drupal core patches||Drupal||2|
|Press interviews||Drupal||1||Did two short interviews about Open Source and online collaboration|
|Mollom||2||Helped close two large new customers|
|Product / engineering management||Mollom||1||Refined our engineering methodology and reviewed some user interface designs|
Every week, people ask me what exactly I do and how I balance my time. As such, I've decided to keep track of my work related activities and to record the time that I spent on them. The next four weeks, I'll try to post a weekly summary of my work week (e.g. Monday - Friday).
|Business development||Acquia||2||Meetings with (potential) Acquia partners|
|Human resources||Acquia||1.5||Career guiding, interviewing potential hires|
|Management meetings||Acquia||5||Strategic planning/brainstorming/review meetings with sales, marketing, engineering, etc|
|Product / engineering management||Acquia||4.5||Roadmap planning for Drupal Gardens, Acquia Cloud, Acquia Network and Drupal Commons|
|Sales meetings||Acquia||2||Meetings with (potential) Acquia customers|
|Transportation||Acquia||6.5||Driving to work and driving to meetings|
|Investor relations||Acquia||0.5||Communicating with investors|
|Attending conferences||Drupal||6||Gave one keynote at Harvard Club and one presentation at the IBM Innovation Center for IEEE/ACM|
|Blogging||Drupal||2||Processed my DrupalCon pictures and wrote 3 short blog posts|
|Drupal 8 initiatives||Drupal||3.5||Talked to potential initiative owners and read up on proposals|
|Drupal Association||Drupal||4||Drupal Association board meeting, phone calls with other Board Members, and working with Executive Director in preparation of the board meeting|
|Preparing presentation slides||Drupal||3||Gave 2 presentations that required preparation|
|Radio interview||Drupal||1||Interview with Federal News Radio to talk about Drupal in government|
|Reviewing Drupal core patches||Drupal||0.5|
|Management meetings||Mollom||1||Weekly planning/review meeting|
|Product / engineering management||Mollom||6||Reviewed the results of the last engineering sprint, and coordinated the next engineering sprint|
This week may have been slightly more busy than normal. Also, most weeks I spent more time reviewing Drupal patches -- this week most of that time went into starting up the Drupal 8 initiatives and catching up with things after DrupalCon. Other than that, this was a pretty common week.