Slack and the New Model for Business Process Software
Beginning life as an internal messaging app for an internal development project, Slack has quickly become one the most prominent messaging apps used today. The momentum is moving beyond Slack itself, as a plethora of third-party companies are building out new functionality based on Slack, in effect turning the work chat app into a platform for running business processes. Startups with a focus on providing developer tools, in particular, are seeing that in order to gain market traction, they need to integrate or otherwise leverage Slack.
Since the middle of this year, enterprises have been a key adopter of the team chat app. Often introduced in a company by a particular team wanting to work on their own collaborative project, the app tends to get noticed quickly by other colleagues and filters through an organization. Commenters have noted that the app’s ease of adoption and allowance for autonomous use by business teams has been the entry leverage point that precedes more widespread adoption, a route software is often unable to follow to gain uptake in a corporate environment where SaaS products are usually bought in a more centralized manner.
MemSQL, Spotify, PayPal, Expedia, Demandbase, Quandl, Eventbrite, Box, and Bitly are all known to use Slack in their operations. (Slack has created a specific job posting board to share new positions available at organizations that use Slack.)
Slack was created in 2013, and had an estimated 8,000 signups on its first day. The idea of the app was to enable team communication by providing chat rooms, organized by themes, as well as offer private messaging and private group messages.
The app — created by the team behind Flickr — was particularly adopted by developer teams and startups, mirroring the app’s original use case: it had been created as an internal tool for developers of an online game so they could communicate on their builds. Since then, it has seen a fairly constant growth rate. In the past six months, website statistics site SimilarWeb, for example, has estimated visitors to the Slack website have grown from just under 40 million to just under 60 million. This figure is calculated for website visitors and reflects levels of engagement with the web app, not the number of actual customers, which Fortune reported at 1.1 million in the middle of the year.
As a mobile app, App Annie reports that in the iTunes App Store, the Slack app is ranked first in the business category in 12 countries, and in the top ten business apps in 101 countries. Amongst developers tracking the Slack API, API Changelog reports that it is one of the most followed APIs in their catalog and growing each month, with 171 developers currently monitoring the Slack API.
A Fast Growing Ecosystem
Slack is now seeing an ecosystem emerge around it that is enabling other businesses to springboard off the Slack phenomenon. Convergely, for example, has built itself around offering productivity tools that surface from Slack chats. Last month, Startup investor at PointNineCap, Rodrigo Martinez, posits that there are some greenfield opportunities in building a business on top of messaging, and singles out Slack as being “an open platform in the corporate environment” because of its user adoption, integration mindset and core base of developers as customers. Martinez links to a ProductHunt list showing some of the bots, tools and ecosystem businesses already being created on top of Slack. Services like SlackStack have sprung up to facilitate the discovery of Slack tools.
Meanwhile, Bloomberg recently noted that Slack has been hiring compliance and policy staff to help position the app company for an enterprise plan that can address needs of particular verticals like finance. As that comes to fruition, more players will seek to build their own business products on top of Slack’s new ‘spine’ in a way we have seen with Docker partners and ecosystem products.
At the recent API Days London, Nicolas Debock, an investor at Balderton Capital, said that he is expecting to see a series of Slackbot funding proposals in their next round of funding.
This emerging Slack ecosystem growth goes beyond integrations — although there are those too — and shows how central Slack is becoming to the developer workflow for now, but how it could be set to transform the whole business process software market.
“Slack is already solving a lot of communication problems and is becoming the day to day communication tool for teams,” said April Underwood, Head of Platform at Slack. “Increasingly, developers and B2B are hearing that early on and are differentiating themselves by providing integrations on the Slack platform.”
Underwood said that a lot of dev teams that are building software are using it throughout their product development processes, and that in turn is helping them generate new ideas about how to offer Slack-based products and integrations to end users. “We have had significant demand from developers early on in our platform,” said Underwood.
New Products in the Slack Ecosystem
LaunchKit is a prime example of how Slack is both inspiring new ideas for dev tools and then being used as a way to leverage an end product’s entry into the market. LaunchKit is a suite of tools built for product managers and app dev teams aimed at helping devs market apps in app stores, monitor app store reviews, manage app sales, and build websites for apps.
“The end user for us is either a product manager, a programmer or a marketer,” said Brenden Mulligan, CEO at LaunchKit. “We launched our first product in February. Our team had previously worked on a bunch of apps, and we saw the same pain points happening over and over again. We had to keep building the same tools over and over, so we started describing that in a blog post. Then we released some source code around how to do notifications in iOS.”
With positive reaction strong, Mulligan’s team began to invest in creating the new suite of tools.
One of the first was Review Monitor that pushes summaries of reviews to Slack so that the whole dev team gets a sense of how an app is being perceived by end users. The idea for the tool came from using Slack, said Mulligan.
“Slack was the main inspiration for us. I was going to the iTunes App Store and looking at our reviews. The rest of the dev team was never really getting involved with that. So I would copy and paste the reviews in an email. Then I hacked together from an RSS feed that Apple provides and connected that to Slack. It was ugly, it wasn’t a smart post, but suddenly the whole team got a feel for how many reviews we were getting. So from a team collaboration point of view, it really helped us understand our user base.”
Mulligan said central to sparking team collaboration is bringing the data into Slack. “That’s the most important. We see that now with our users: most people use Review Monitor because of the Slack integration. We did a roadshow and spoke with 50 developers, and when we showed them the Slack notifications, everyone’s eyes widened. Any dev team that has an iOS app and is using Slack instantly wants to get Review Monitor.”
While there have been messaging and workchat apps like Flowdock and HipChat available — and whole services like Akana that offer feeds that aim to show what team members have been working on — Mulligan believes part of the secret to Slack’s success has been the mobile app experience and the continued work on new features:
“I think there are a lot of subtleties with Slack that I don’t understand. The main thing that got us to make the switch from HipChat was the mobile experience. The HipChat mobile experience was so terrible, that was what made us switch over, and then we found there are these moments of delight in using Slack on mobile. It is a more beautiful interface: they spent some time creating some delightful things in the UI, a little bit more whitespace, a slightly better organization. HipChat is very utilitarian. So in the end, it wasn’t so much that Slack was so much better, it was that Slack was a little bit better in a hundred different ways.”
Mulligan sees Slack as having helped them build products that let business and tech sides of an enterprise communicate more effectively: “How does a product manager work more seamlessly with the developer while the app is being built? With our Slack notifications, we aim to help put tools in the hands of people who have to use them.”
The User’s Workflow
Slack integrations are blooming out from an initial developer use base within the enterprise and extending into other roles. That’s why Blockspring has focused on Slack with it’s second key tooling after spreadsheets.
Blockspring is a service that wraps APIs into existing tooling like spreadsheets so that non-technical users can make use of the underlying power of APIs. Recently, they have been working on an integration so that from within Slack, users can identify what APIs may help them get the data they need or can outsource particular functions via API.
“We focus on whichever tools businesses want to use. We believe business becomes better when you have access to APIs. We also use Slack internally a lot and we saw the potential immediately. Slack is built into the behavior of the user: they use event-driven integrations that come into the tool. That is a little different than going out to a web service, so we thought that would be really cool to integrate there,” said Paul Katsen, CEO of Blockspring.
“We always design within existing behavior of end users. Our team have all come from a past of trying to build new tools for end users. But whenever you want to give devs new functionality, it turns out neither the end user nor the developer wants to learn a new tool. Devs want to create really cool functionalities, and for end users the first question is usually, ‘where is the export data button so I can put this in a spreadsheet?’”
The goal for Blockspring then has been to bring their service in front of users in their workflow, and today that means being accessible within Slack.
One of Slack’s key benefits is that it helps center work relations around connection and communication beyond a task or document. Speaking with the Financial Times, Slack Cofounder Stewart Butterfield said this is integral to what sets the app apart from other team-based cloud software like Dropbox, who center the interaction around a document and are therefore “probably just wrong”.
New Model for Business Process Software
And while other team-based software has attempted to create a newsfeed-like feature that updates business colleagues about what recent interactions have occurred and what tasks have been accomplished, Slack is able to do this at a higher, cross-business scale. With a J-curve of integrations being created by apps to enable Slack notifications from their services, Slack is offering a single, global update within the business setting: alerts from customer service software, online shop-carts, IT monitoring, and order fulfillment all in the one flow. The Financial Times said this makes Slack “a digital spine for a business,” drawing in both human and machine-generated data.
It is this potential that may see Slack morph from being solely a workchat and collaboration tool to being a new type of business process management platform. But to get there, developers creating integrations need to think through what information is useful in a notification that can help end users wherever they are in their process. It also means Slack has to aid discovery of integrations that can help businesses get their jobs done without taking them out of their workflow.
John Sheehan, CEO of API testing service Runscope, sees Slack as being the platform where the developers are. “Slack is important because it is so popular right now. For us, it is more important to think about integrations. Between Slack, HipChat and PagerDuty — which has some different use cases — notifications is a well-covered space. It doesn’t make sense for us to focus on notifications when there are so many more API monitoring issues to solve. We want to be ingrained in the developer’s workflow. And for that, integrations are absolutely essential. We want to be a first class citizen in other ecosystems with our integrations.”
Slack has been instrumental in driving new user adoption for Runscope. “Their list of currently supported integration providers is a great source of signups for us. That has been one of the things that has driven adoption. Slack is about four times more popular than the next most popular third-party integration we have.”
“The problem we are now trying to solve is: there are already great applications built on our API that people can’t find,” said Underwood. “We make it easy for devs to create great experiences on Slack, but we need to make sure business and enterprise teams can find those integrations and make use of them.
“We need to make it easier for teams to find the integrations they need. It is our job to help teams work more effectively. We will have to do something smarter to help teams find the integrations for them. We have a lot of work to do.
“Then, further down the road, we will look at how we make Slack the command center: how to do that in a way that reduces the contact-switching. We want to build the experience so that engineers can sit within their Slack channel and don’t need to go back and forth into different applications.”
If Slack is to become more a complete business process tool — a spine of command center — Slack will need to enable discoverability capabilities in the same way that Blockspring is seeking to do by enabling APIs to surface from within a Slack channel. But to realize the command center vision will also require developers to build the sorts of rich experiences that mean end users can rely on using Slack as a central hub for their workflows.
At LaunchKit, Mulligan is thinking in terms of “what makes a good Slack post? What is valuable for the whole team to see? So, for example, for some devshops, getting a new review is not a big deal, so that is why we have a little toggle in our tool for setting how many stars you want, so you only need to see certain reviews. It is a critical piece of information, so when we build out new tools that provide feedback, we will enable them to post to Slack. We think about what is the critical information that will help a team with their business?”
Sheehan agrees on the importance of providing the right type of information: “One of the tricky things going into Slack is that you can’t post live updating graphs. I want it to update the data as you are talking about it. As the platform matures, I am sure they will give us the facilities to do that, and that means people won’t need to leave Slack and that good for us because it keeps people engaged with our product.”
Sheehan is comfortable with this command center idea. “Slack and messaging services are at the beginning of what they are going to be offering in future. For example, we send a daily email to our users on all of the APIs they are monitoring with us. That is something we could offer through a Slack notification if we could get the right UI into it. The types of data Slack can support and the presentation layer they offer is evolving quickly. It is good to see them investing in improving the Runscope experience for our end users.”
This command center-like role is what Underwood see as transforming business process and workflows within collaborative teams. “Often a business team might start with Trello or a Google Doc and then the design team starts building in InDesign, then engineering uses GitHub,” Underwood said. “Slack really provides the space from start to finish for the steps in the product development process: that’s the concrete way that Slack is changing how teams work.”
The next six months will be key for Slack. They are currently at a stage where if they don’t solve the integration discoverability issue, users will limit their expectations of the platform so it remains solely a workchat tool. At the same time, as integration partners expand, those partners need to be savvy enough that they are offering valuable notification experiences to Slack’s end users rather than just seeking to ride the Slack wave with fast and clumsy integrations. And all this is occurring while Slack chases the enterprise market.
With its rapid uptake, Slack is in the early days of morphing now into being more than just a messaging app for teams. This is where the ecosystem has the opportunity to expand beyond just integrations that work well with Slack and that instead lead to the creation of products — like LaunchKit that can stand alone, but make more sense as components that link into Slack to deliver their information. Along with this outcrop of new products will be a growing ecosystem platform that existing services will want to link into, in the way that Runscope are positioning their availability to Slack users. And finally, there is the issue of discoverability, which has the opportunity to profoundly change the expectations enterprises have for business process tools, where a degree of automation can help users identify what functionalities or data exist without already needing to know what is out there. Slack might just be what business process software and API aggregation workflow tools look like in the future.