{"id":137,"date":"2016-05-18T21:12:41","date_gmt":"2016-05-18T16:12:41","guid":{"rendered":"https:\/\/thedevcouple.com\/?p=137"},"modified":"2017-07-17T09:16:52","modified_gmt":"2017-07-17T04:16:52","slug":"woomattic-turns-one-a-critical-analysis-by-wpcouple","status":"publish","type":"post","link":"https:\/\/thedevcouple.com\/woomattic-turns-one-a-critical-analysis-by-wpcouple\/","title":{"rendered":"WooMattic Turns One! A Critical Analysis by WPCouple"},"content":{"rendered":"<p>Probably, it would have been the same summers of May last year\u00a0when Matt Mullenweg and his team at Automattic were preparing to shake the pillars of the WordPress community. The news of <a href=\"https:\/\/www.woothemes.com\/\" rel=\"nofollow noopener\" target=\"_blank\">WooThemes<\/a> being acquired by Automattic spread like a fire, and it came as a shock for some but a surprise for many.<!--more--><\/p>\n<blockquote><p>Anywho, WooMattic Turns One Today!<\/p><\/blockquote>\n<h3>Some Mind Boggling Stats<\/h3>\n<p>You will be surprised to know that during this one complete year the plugin successfully crossed the 14.4 million downloads with 30% share of the global eCommerce. I am sure the journey would have been an incredible one for all the Woo Ninjas out there especially those who&#8217;ve made this plugin grow from 0 to the 10M figure. If my recollection of lost isn&#8217;t misleading me then WooCommerce had about <a href=\"https:\/\/web.archive.org\/web\/20150318134131\/https:\/\/wordpress.org\/plugins\/woocommerce\/stats\/\" target=\"_blank\" rel=\"nofollow noopener\">6.7 Million downloads before its acquisition<\/a>.<\/p>\n<p>[ecko_fullpage_image]<br \/>\n<img decoding=\"async\" loading=\"lazy\" class=\"aligncenter size-full wp-image-301\" src=\"https:\/\/thedevcouple.com\/wp-content\/uploads\/2016\/05\/WooMattic-One-Year-Downloads.jpg\" alt=\"WooMattic-One-Year-Downloads\" width=\"1920\" height=\"1200\" srcset=\"https:\/\/thedevcouple.com\/wp-content\/uploads\/2016\/05\/WooMattic-One-Year-Downloads.jpg 1920w, https:\/\/thedevcouple.com\/wp-content\/uploads\/2016\/05\/WooMattic-One-Year-Downloads-300x188.jpg 300w, https:\/\/thedevcouple.com\/wp-content\/uploads\/2016\/05\/WooMattic-One-Year-Downloads-768x480.jpg 768w, https:\/\/thedevcouple.com\/wp-content\/uploads\/2016\/05\/WooMattic-One-Year-Downloads-1024x640.jpg 1024w, https:\/\/thedevcouple.com\/wp-content\/uploads\/2016\/05\/WooMattic-One-Year-Downloads-1680x1050.jpg 1680w, https:\/\/thedevcouple.com\/wp-content\/uploads\/2016\/05\/WooMattic-One-Year-Downloads-1240x775.jpg 1240w, https:\/\/thedevcouple.com\/wp-content\/uploads\/2016\/05\/WooMattic-One-Year-Downloads-860x538.jpg 860w, https:\/\/thedevcouple.com\/wp-content\/uploads\/2016\/05\/WooMattic-One-Year-Downloads-680x425.jpg 680w, https:\/\/thedevcouple.com\/wp-content\/uploads\/2016\/05\/WooMattic-One-Year-Downloads-500x313.jpg 500w, https:\/\/thedevcouple.com\/wp-content\/uploads\/2016\/05\/WooMattic-One-Year-Downloads-400x250.jpg 400w, https:\/\/thedevcouple.com\/wp-content\/uploads\/2016\/05\/WooMattic-One-Year-Downloads-200x125.jpg 200w, https:\/\/thedevcouple.com\/wp-content\/uploads\/2016\/05\/WooMattic-One-Year-Downloads-50x31.jpg 50w\" sizes=\"(max-width: 1920px) 100vw, 1920px\" \/><\/p>\n<p>[\/ecko_fullpage_image]<\/p>\n<blockquote><p>Last year WooCommerce had\u00a0<a href=\"https:\/\/web.archive.org\/web\/20150318134131\/https:\/\/wordpress.org\/plugins\/woocommerce\/stats\/\" target=\"_blank\" rel=\"nofollow noopener\">over 6.7 million downloads<\/a>; fast-forward one year of WooMattic acquisition and the download stats are 14.4 million.\u00a0That&#8217;s\u00a07,686,069 downloads and 114% increase in just one year.<\/p><\/blockquote>\n<h2>A Glimpse At The Past<\/h2>\n<p>Acquisitions are nothing new when it comes to Automattic; they&#8217;ve done it before since 2007 from <a href=\"https:\/\/en.gravatar.com\/\" rel=\"nofollow noopener\" target=\"_blank\">Gravatar<\/a> till 2014\u00a0when they acquired the WordPress security plugin <a href=\"https:\/\/wordpress.org\/plugins\/bruteprotect\/\" rel=\"nofollow noopener\" target=\"_blank\">BruteProtect<\/a>. Likewise, all the previous acquisitions\u00a0didn&#8217;t meet\u00a0such an uproar which was witnessed last year in May 2015. So what paved the way for Matt to acquire Woo at a price that some reports say to be six times anything the company has acquired done till date?<\/p>\n<p>Similarly, the fact that Matt has repeatedly spoken <em>high<\/em> about the scope of eCommerce businesses globally cannot be ignored. Many speculations had\u00a0gone into the reasons why this massive takeover occurred, but this is not something which I&#8217;ll discuss.<\/p>\n<p>However, the general opinion you mostly find on this topic is that Automattic preferred this way as opposed to building its in-house eCommerce platform. Since we all know how tough that could be. And talent acquisition that was a huge plus factor.<\/p>\n<h2>A Big Leap of Faith<\/h2>\n<p>Regarding the repute and power,\u00a0both Woo and Automattic were considered to be the <em>leaders of the pack<\/em> and their combination; boy what do I say about that. It was a big leap of faith for both companies since thoughts like &#8220;is it worth the risk&#8221; would&#8217;ve been pretty difficult to deal with. Amalgamating 55 new employees from 16 countries with a total of 370 Automatticians was a significant challenge to accept.<\/p>\n<p>An article in which, <a href=\"https:\/\/twitter.com\/mark_forrester\" rel=\"nofollow noopener\" target=\"_blank\">Mark Forrester<\/a> (Co-Founder of WooThemes) <a href=\"https:\/\/www.woothemes.com\/2015\/10\/woomattic-update\/\" rel=\"nofollow noopener\" target=\"_blank\">wrote three months after Woo&#8217;s acquisition<\/a> narrates that team integration was the biggest issue they faced initially but enjoyed this transition and called it a privilege working with Automattic.<\/p>\n<h2>WooMattic Turns One!<\/h2>\n<p>Can you imagine, it&#8217;s May already and\u00a0<em>WooMattic is now one-year-old<\/em>. Throughout these 12 months, I&#8217;ve keenly observed how well these two companies, gelled together negating all the rumors which once prevailed. I think both companies had a great year together, and the power of Automattic has for sure taken the core plugin to a next level. Woo as a brand has scaled up which clearly reflect\u00a0the supreme managerial role Automattic has played.<\/p>\n<p>Automattic&#8217;s takeover also gave birth to a new debate which predicted about the future of WordPress and WooCommerce. People came up with different viewpoints but so far everything seems great. I can&#8217;t judge that how many predictions turned out well. But I&#8217;m sure that after reading this post you&#8217;ll be in a much better position to evaluate WooMattic by yourself.<\/p>\n<blockquote><p>Therefore, I am writing from the perspective of a WordPress community member; about what changes I saw at Woo which can be accredited to the\u00a0WooMattic acquisition.<\/p><\/blockquote>\n<h3>Corporate and Community Support<\/h3>\n<p>One single concern which populated the most about this acquisition was the company size. Automattic was already a team of 370 people when WooThemes joined it. This is quite a big number, and Matt has done an excellent job in regards to managing all of them. Big companies do confront problems with their &#8220;Support&#8221; system, and WooThemes was already struggling through it for quite some time. I mean leading a family of users in millions is not a piece of cake is it? So, this is where I felt Automattic played its part and helped Woo improve its support system.<\/p>\n<p>Right after being acquired, an all-new support system for WooThemes was announced which aimed to make\u00a0<em>every single interaction<\/em>\u00a0with the Woo Ninjas productive. A tab for submitting &#8220;Tickets&#8221; was introduced in your WooThemes account just like you would do in <a href=\"https:\/\/vip.wordpress.com\/documentation\/contacting-vip-hosting\/\" rel=\"nofollow noopener\" target=\"_blank\">WordPress.com<\/a>.<\/p>\n<p>But this revamped support system didn&#8217;t end their struggle as users experienced long ticket response times which <a href=\"https:\/\/twitter.com\/mikeykrapf\" rel=\"nofollow noopener\" target=\"_blank\">Michael Krapf<\/a> (Woo&#8217;s support lead) also expressed in one of his\u00a0blog posts.<\/p>\n<p>To cater this issue, Woo took some constructive steps like hiring and training new support ninjas, improving products documentation and <a href=\"https:\/\/www.woothemes.com\/2015\/07\/woocommerce-sidekick-training\/\" rel=\"nofollow noopener\" target=\"_blank\">partnering with companies like Sidekick<\/a>, which provides guided tour and training right inside your online\u00a0store. All these efforts were not possible without a strong backing from Automattic.<\/p>\n<h3>Content Marketing Strategy<\/h3>\n<p>Since its acquisition, I&#8217;ve observed a significant shift in Woo&#8217;s content marketing strategy. All those who speculated that can &#8220;Automattic make selling online just as easy as publishing content&#8221; must have observed the change. If you scroll through the <a href=\"https:\/\/www.woothemes.com\/blog\" rel=\"nofollow noopener\" target=\"_blank\">blog posts of WooThemes<\/a>, you&#8217;ll find a great level of diversity in the featured content.<\/p>\n<p>WooCommerce pairs well with WordPress and makes web users and potential shoppers brace the plugin as a top-notch eCommerce solution for their websites. WordPress has proved itself to be best CMS for publishing content, and that&#8217;s why it seems that the Woo authors have started to make the most out of it via content marketing.<\/p>\n<p>Now apart from the general tips and announcements, you&#8217;ll find some niche specific and user focused articles like how to run <a href=\"https:\/\/www.woothemes.com\/2016\/04\/coffee-subscriptions-guide\/\" rel=\"nofollow noopener\" target=\"_blank\">coffee subscription business<\/a>, <a href=\"https:\/\/www.woothemes.com\/2016\/04\/bookings-store-success\/\" rel=\"nofollow noopener\" target=\"_blank\">booking-based website<\/a>,\u00a0and a\u00a0<a href=\"https:\/\/www.woothemes.com\/2016\/03\/food-store-tips\/\" rel=\"nofollow noopener\" target=\"_blank\">food store<\/a>. As someone who believes in content marketing, I&#8217;d say it&#8217;s a healthy sign of growth at WooMattic.<\/p>\n<p>Also, it seems that Woo has started to rely more on\u00a0<a href=\"http:\/\/wptavern.com\/\" rel=\"nofollow noopener\" target=\"_blank\">WP Tavern<\/a>\u00a0for all the walkthrough news of the community just like any other project would do that is run by Automattic. This could be the possible reason for not publishing their monthly round-up\u00a0which used to run under the name &#8220;<em>The Month in WordPress:&#8212;&#8212;<\/em>&#8220;. Its last edition was published\u00a0for the month of May 2015 which explains a lot.<\/p>\n<h3>Back to Back Versions<\/h3>\n<p>Few days back, <a href=\"https:\/\/twitter.com\/BFTrick\" rel=\"nofollow noopener\" target=\"_blank\">Patrick Rauland<\/a>, one of the WooMatticians,\u00a0<a href=\"http:\/\/speakinginbytes.com\/2016\/05\/speed-above-all-else\/\" rel=\"nofollow noopener\" target=\"_blank\">penned down his 10-month experience at Automattic<\/a>. The prime focus of his article was to talk about &#8220;how <em>fast<\/em> everything is (at Automattic)&#8221; that Automattic is faster than WooThemes ever was. Which is incredible. I for one found that article to be full of insights and enjoyed reading about what&#8217;s possible even with 400+ employees at Automattic. I guess now it would be easy for everyone to understand how WooThemes managed to release two major versions for WooCommerce in a single year.<\/p>\n<p>Back in August 2015, WooCommerce launched its version 2.4 under the name of <a href=\"https:\/\/www.woothemes.com\/2015\/08\/woocommerce-2-4-release\/\" target=\"_blank\" rel=\"nofollow noopener\">Helpful Hedgehog<\/a>. Its main highlight was the onboarding wizard to make things simple for users on what to do next (and we loved it ?). Despite this version catered quite a lot of users&#8217; needs but just in two weeks time, their developers realized the missing backward compatibility for third-party theme developers.<\/p>\n<p>So, they geared themselves for the next release and launched version 2.5 i.e. the <a href=\"https:\/\/www.woothemes.com\/2016\/01\/woocommerce-25-dashing-dolphin\/\" target=\"_blank\" rel=\"nofollow noopener\">Dashing Dolphin<\/a> in January 2016. Fast enough, though! This version focuses mainly on the\u00a0speed of your online store. A session handler was introduced which tells WooCommerce what&#8217;s in your cart. Apart from this, a new feature was added that added support for WPCLI which is obviously an amazing feature to have.<\/p>\n<h3>Win-Win Strategy<\/h3>\n<p>WooThemes&#8217; takeover came as a shock for those who were associated with its products in one way or the other. But later it proved quite fruitful because\u00a0the growth of WooCommerce with Automattic benefited the current users as well as facilitated the large retailers. The support which came from Automattic was in itself a winning moment for all the subscribers, partners, and third-party developers who create products for WooCommerce. Some of them even experienced an increased number of sales and business growth.<\/p>\n<p>Likewise, Automattic&#8217;s strict policy of no side projects for its workers also came as a blessing for some. One such example was of WooCommerce&#8217;s lead developer <a href=\"http:\/\/mikejolley.com\/\" rel=\"nofollow noopener\" target=\"_blank\">Mike Jolley<\/a>, who sold\u00a0his side-business\u00a0<a href=\"https:\/\/wpjobmanager.com\/\" rel=\"nofollow noopener\" target=\"_blank\">WP Job Manager<\/a>\u00a0plugin to Automattic as a result of the takeover. Brian Krogsgard at PostStatus did a fascinating Q&amp;A with Mike about the acquisition of <a href=\"https:\/\/poststatus.com\/automattic-to-acquire-wp-job-manager-from-mike-jolley\/\" target=\"_blank\" rel=\"nofollow noopener\">WP Job Manager by Automattic<\/a>.<\/p>\n<h3>A Much Consolidated Organizational Structure<\/h3>\n<p>The intervention of Automattic brought some positive changes inside WooThemes&#8217; organizational structure. It seems that now the Ninjas have set the ball rolling towards achieving new milestones. The launch of <a href=\"https:\/\/www.woothemes.com\/wooexperts\/\" rel=\"nofollow noopener\" target=\"_blank\">WooExperts<\/a> is a reflection of how Automattic is scaling up WooThemes as it should.<\/p>\n<p>Like users get badges on their WordPress profiles, in the same way, this verified developer program assigns badges to the WooExperts based on their skill and experience. The project also bade farewell to their previous <em>Affiliated Woo Workers Page<\/em>, which featured every developer or agency regardless of their experience.<\/p>\n<p>To ensure and meet the quality standards of Automattic this program was revamped and they came up with a three tier membership structure. Moreover, they smartly worked on the marketing strategy and came up with the concept of <a href=\"https:\/\/www.woothemes.com\/showcase\/\" rel=\"nofollow noopener\" target=\"_blank\">WooCommerce Showcase<\/a>, displaying some amazing work which developers and agencies have done with WooCommerce. I like to think that these changes have helped attract more people to adopt WooCommerce as their ultimate eCommerce solution.<\/p>\n<h2>Why the acquisition became a big hit?<\/h2>\n<p>This was not an ordinary purchase. Several factors backed it to become a superhit. In my opinion, there could be numerous reasons for it. But a worth noting point is that Matt Mullenweg maintained the sanctity of WooThemes and its products. Apparently, apart from barring its workers from side projects we didn&#8217;t find any hindrance which would have affected their workflow.<\/p>\n<p>However, improvements were\u00a0made to take the company to a different level. The newly incubated team were welcomed very warmly and integrated quite well. They enjoyed all the resources which were accessed by regular Automatticians. WooThemes even celebrated their seven successful years. It seems that they had every right to celebrate their success being an independent unit as well.<\/p>\n<h2>What Does the Future Hold?<\/h2>\n<p>It&#8217;s a moment of joy for all the WooMatticians considering how they&#8217;ve done so well together. This was just the first year, and we have witnessed awesome folks doing amazing work. It&#8217;s not about winning or losing because the ultimate winner of this takeover was WordPress for sure. I think this acquisition has made WordPress platform more strong than ever. It&#8217;s just the beginning. I can tell you the future is bright for WooMattic.<\/p>\n<p>By making use of the current WooCommerce customer base, Automattic can come up with improved selling options for its users. With Automattic leading from the front, would make it easier for WooCommerce to compete\u00a0with the existing giants like <a href=\"https:\/\/magento.com\/\" rel=\"nofollow noopener\" target=\"_blank\">Magento <\/a>and <a href=\"https:\/\/www.shopify.com\/\" rel=\"nofollow noopener\" target=\"_blank\">Shopify<\/a>\u00a0and who knows it may even launch a SaaS solution of their own.<\/p>\n<p>Automattic can even make its entry into the commercial theme market and rise as a competitor to <a href=\"https:\/\/envato.com\/\" rel=\"nofollow noopener\" target=\"_blank\">Envato<\/a>. Moreover, the venture proved to be a successful one regarding\u00a0the number of Ninjas who continued to stick with their jobs inside the new setup. Only a handful people left the lot which is a convincing fact about Automattic&#8217;s working environment.<\/p>\n<h3>What&#8217;s on Your Mind?<\/h3>\n<p>So what&#8217;s next? Can we expect a few more acquisitions from Automattic? I think we can. What about you?\u00a0Was this a good year for both WordPress and Woo? Did you think something went wrong? Do you have a suggestion for Matt Mullenweg? Comment below or <a href=\"https:\/\/twitter.com\/home?status=Did%20you%20know%20%40WooCommerce%20acquisition%20by%20%40Automattic%20turned%20one%20today?%20Read%20A%20Critical%20Analysis%20by%20WPCouple%20http%3A\/\/thedevcouple.com\/?p=137\" target=\"_blank\">Tweet about it<\/a>.<\/p>\n<h3>Update<\/h3>\n<p>Apparently, Matt Mullenweg read the article and found it to be great ?<\/p>\n<blockquote class=\"twitter-tweet\" data-width=\"500\">\n<p lang=\"en\" dir=\"ltr\"><a href=\"https:\/\/twitter.com\/mrahmadawais\" rel=\"nofollow noopener\" target=\"_blank\">@mrahmadawais<\/a> <a href=\"https:\/\/twitter.com\/MaedahBatool\" rel=\"nofollow noopener\" target=\"_blank\">@MaedahBatool<\/a> <a href=\"https:\/\/twitter.com\/TheWPCouple\" rel=\"nofollow noopener\" target=\"_blank\">@TheWPCouple<\/a> Great article!<\/p>\n<p>&mdash; Matt Mullenweg (@photomatt) <a href=\"https:\/\/twitter.com\/photomatt\/status\/733438073246097408\" rel=\"nofollow noopener\" target=\"_blank\">May 19, 2016<\/a><\/p><\/blockquote>\n<p><script async src=\"\/\/platform.twitter.com\/widgets.js\" charset=\"utf-8\"><\/script><\/p>\n<p>Don&#8217;t forget to reach out at Twitter <a href=\"https:\/\/twitter.com\/mrahmadawais\" target=\"_blank\" rel=\"nofollow noopener\">@MrAhmadAwais<\/a> and <a href=\"https:\/\/twitter.com\/MaedahBatool\" target=\"_blank\" rel=\"nofollow noopener\">@MaedahBatool<\/a><\/p>\n","protected":false},"excerpt":{"rendered":"<p>Probably, it would have been the same summers of May last year\u00a0when Matt Mullenweg and his team at Automattic were preparing to shake the pillars of the WordPress community. The news of WooThemes being acquired by Automattic spread like a fire, and it came as a shock for some but a surprise for many.<\/p>\n","protected":false},"author":3,"featured_media":300,"comment_status":"closed","ping_status":"open","sticky":false,"template":"","format":"standard","meta":{"jetpack_post_was_ever_published":false,"_jetpack_newsletter_access":""},"categories":[6],"tags":[16,15,14],"coauthors":[],"jetpack_featured_media_url":"https:\/\/thedevcouple.com\/wp-content\/uploads\/2016\/05\/WooMattic-one-year-wpcouple.jpg","amp_enabled":true,"_links":{"self":[{"href":"https:\/\/thedevcouple.com\/api\/wp\/v2\/posts\/137"}],"collection":[{"href":"https:\/\/thedevcouple.com\/api\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/thedevcouple.com\/api\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/thedevcouple.com\/api\/wp\/v2\/users\/3"}],"replies":[{"embeddable":true,"href":"https:\/\/thedevcouple.com\/api\/wp\/v2\/comments?post=137"}],"version-history":[{"count":0,"href":"https:\/\/thedevcouple.com\/api\/wp\/v2\/posts\/137\/revisions"}],"wp:featuredmedia":[{"embeddable":true,"href":"https:\/\/thedevcouple.com\/api\/wp\/v2\/media\/300"}],"wp:attachment":[{"href":"https:\/\/thedevcouple.com\/api\/wp\/v2\/media?parent=137"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/thedevcouple.com\/api\/wp\/v2\/categories?post=137"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/thedevcouple.com\/api\/wp\/v2\/tags?post=137"},{"taxonomy":"author","embeddable":true,"href":"https:\/\/thedevcouple.com\/api\/wp\/v2\/coauthors?post=137"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}