Product2 publishers3 min readPublished
ServiceNow handed a small in-house team a startup mandate to answer Serval and Slack
ServiceNow says a small team with a founder-like mandate built Flow, its AI service desk for Slack and Teams, in three months. For IT teams whose staff already work in chat, the question is whether a desk with no setup project will still fit once request volume and complexity grow.
The Product Desk · Product desk
What happened
- ServiceNow says Flow can be set up within a day, with no implementation project, CMDB migration or infrastructure required.
- Serval, which says it intends to replace ServiceNow, reached a $1 billion valuation last December after raising $75 million in a Sequoia-led round.
- Sequoia partner Anas Biad said the last time the firm saw customer feedback that strong was when it backed ServiceNow itself 16 years earlier.
- Salesforce CEO Marc Benioff has noted that ServiceNow automates work for roughly 9,000 companies while Slack sits inside a million.
Compiled by The Product DeskSomething wrong?How this is made
Why it matters
- decision IT teams whose staff already work in chat can weigh a ServiceNow desk without budgeting a migration project, so a choice against Serval comes down to how well the agent handles their actual requests.
- cost Consumption billing moves the expense from an upfront project to a running cost that rises with every request employees send through Slack or Teams.
- exposure ServiceNow's plan needs Flow customers to outgrow it; if the simpler product stays sufficient as they get bigger, the cheap entry caps what each account pays.
- precedent A product built in three months and sold as ready on day one gives ServiceNow's large customers a benchmark to cite when full-platform implementations run long.
An employee locked out of an app types the problem into Slack or Microsoft Teams in plain words. ServiceNow says Flow's agent then either resolves it or escalates it [5]. Rivals have spent two years arguing that this is where employees want help: inside the tools they already use, with no separate portal [1].
Fast Company frames Flow as ServiceNow building a startup inside itself to take on AI-native rivals [18]. ServiceNow's executives tell the story through buyers. The company says Flow grew out of requests from leaner IT teams that wanted its automation without a full implementation [11]. Zavery said those conversations showed a buying preference that its traditional enterprise sales model was not built for [11]. "They want to get started immediately, without going through any kind of configuration process. They want to start using a product, see where it goes, and pay as they go. That's a consumption-oriented mindset," Amit Zavery, ServiceNow's president, CPO and COO, said [12].
Zavery said he staffed the team with people who knew IT service management and AI development tools [13]. "I said, you have no restrictions. It was like a well-funded startup, in a way," he said [13].
Salesforce's advantage is reach. Marc Benioff's figures put Slack inside about 111 times as many companies as ServiceNow automates work for [1]. Because Flow runs inside Slack and Teams, ServiceNow's desk sits on software that Salesforce owns, in front of those same employees [5][4].
Bill McDermott, ServiceNow's chairman and CEO, described the pricing in two sentences: "Zero upfront expense. Pay only for what you consume." [8] ServiceNow wants Flow to bring in companies that would not otherwise adopt its full platform, then grow those accounts [10]. "Flow starts with the service desk. It can become the platform you run your business on," McDermott said [16].
His case against simpler rivals also bears on Flow's light setup. "Anyone can vibe code a conversation. Very few can engineer an outcome. Without orchestration, context, security and trust, you're creating vibe slop that will flop," he said [9]. Flow's setup pitch skips the CMDB migration [6]. I think the question a buyer should put to ServiceNow is how much of that context the agent has without it. Flow is still in controlled availability, and the report includes no per-request price or resolution figures [6].
Keith Kirkpatrick, vice president of research at Futurum, sees Flow as part of a wider push for established vendors to package their expertise in products that are quicker to adopt and simpler to buy [15]. "ServiceNow is also positioning this as a way for larger enterprises to quickly stand up an AI-first support operation," he said [15].
I'd place a team on two axes before taking a demo. The first is where employees already ask for help, in chat or in a portal. The second is the split between simple requests, such as a reset or an access grant, and requests that need a hand-off to another system or person, the judgement ServiceNow says Flow draws on years of IT knowledge to make [17].
Chat with mostly simple requests is Flow's target buyer, and a one-day setup is cheap to test once the product opens up [6]. Chat with heavy hand-offs calls for a pilot where the escalation rate is the figure to track, since each escalation lands on a person. A portal handling simple requests gives little reason to move. A portal with heavy hand-offs describes the full-platform customer ServiceNow already sells to, and for that customer Flow is at most a fast start [15].
The count that places a team is the share of last quarter's most common request types that ended with a hand-off.
What to watch
- Whether Flow leaves controlled availability with a published per-request price.
- Whether ServiceNow reports how many Flow customers move onto its full platform.
- Whether Salesforce introduces its own service desk to existing Slack customers through those relationships.