>> Live, from Bellevue, Washington. It's theCUBE. Covering, Smartsheet Engage 18. Brought to you by, Smartsheet. >> Welcome back to theCUBE's continuing coverage of Smartsheet Engage 2018. I am Lisa Martin with Jeff Frick. We are in Bellevue, Washington or, as I like to call it, not Vegas. Excited to welcome to theCUBE, Robin Sherwood, the Senior Director of Product Management at Smartsheet. Hey Robin. >> Hi, how's it goin? >> Great. This is, been a very buzzy morning, for Jeff and I here on this side. Lot's of people, this event has doubled in size. This is your second annual, so... >> Big growth in just a year. There's a, I think, Mark Mader, your CEO, shared some sats this morning. There are 1100 companies represented here customers. >> Correct. >> From twenty countries, there are more than fifty customer speakers, which is, I think there's no more validating voice, than the voice of a customer using the technology. When I was doing some research on Smartsheet, was looking at, you guys are partners with, some of your competitors. One of things I wanted to understand is, where do you have integrations with technology, versus where do you have connectors? What's the difference between those two, and how does is work >> Yeah. >> In a Smartsheet world. >> You know, I think, the integrations really are, where you're going to, you're really interacting with that other product directly, right? So, maybe it's, I want my outbound messages and notifications to go into a Slack channel, right? That's an integration. Or, I want to be able to connect to Google Drive, or 03 Secure, One Drive document, in those native stores. So, that's where we really see an integration. It's something that the end user themselves, is really interacting with. Where you see connectors is more around where I've got big systems of record in my organization, and I need data to flow between those tools. >> Like a Sales Force. >> Like a Sales Force, or a JEAR, or something like that. Microsoft Dynamics, right? I've got data there, when something happens in that system, I need it to flow magically into Smartsheet, or when something happens in Smartsheet, I need it to flow back into those systems. Cause, those are the systems of record, that my company cares about. >> So, a connection is a much bigger step in integration? >> They're just different. >> Connectors are really about the flow of data back and forth between systems of record and integrations are more about user content and user direct interactions. So, things like Drive and Box and Dropbox, and Slack and Teams and, stuff like that. Or, the web content, which we just announced. We want to be able to embed a Youtube video in a dashboard. That's not integrations, it's not, there's no data flowing back and forth, it's just a link, right? >> Got it, thank you. >> Yeah. >> So, lot of customer's we have, I think fifty customer's presenting, which is amazing out of 2,000 people in the whole conference. I don't know what the percentage is, but it's, (laughs), >> Yeah. >> Awfully large. So, just some of the all chatter here. You've been here for a couple of day now, you guys had some early training yesterday. What is some of the things you're picking up? You obviously love to hear back from the customer's. Kind of, what's the buzz on some of the new offerings, and what are you hearing, amongst the constituent here? >> I mean, it's always, you know, this is only our second year. But the energy from them is always amazing. And, you know, people were, I was talking to someone earlier and they were just blown away. By just the big list of things that we shipped, this week. And, as I was reflecting, like, I don't remember doing all that much. But then, when you see it all on one big slide, with everything listed out, it's incredible. So, it's hard to say if anybody latched on to one thing or another. Obviously, there was lots of applause during the product... >> Yes. >> Session, and we're really excited to have shipped, the multi-assign to feature, which has been our number one customer request for a while. But, it's not a, game-changing feature. Whereas, I think some of the Automation Rules ,and Updates there, and Workflow Builder, are really. People are going to go back and it's going to to change the way that they work. And, so people are really excited about that. But, really excited about Dynamic View. And being able to really, taylor the information that is shared across their organization. >> The word collaboration, like symbionic or bi-directional collaboration, popped into my mind. When Gene Pharaoh, your SVP of Product, who we had on earlier, was talking about some of the features and it was a really interesting dynamic with the audience. In that, number of times, you mentioned, the audience broke into applause. And, it probably feels pretty good. Like, yes, we're listening to you, we're doing this. Enabling, them to have technology that allows them to collaborate with and amongst teams and functions within an organization. But, you're also taking their feedback, directly and collaborating with customer's, to further innovate your product. With the spirit of collaboration, we had, Margo Visitacion on from Forrester. And she was talking about the collaborative work management CW as an emerging market. With respect to collaboration, you guys can enable sharing. I can be a licensed user, and share it with you who's not. How is that type of collaboration a differentiator for Smartsheet? >> Well, you know, I think there's a lot of tools where they're collaborative where you can comment on them. Google Doc, and that's great. But, I think where Smaresheet really excels, is really in this free collaborator model. That's not bounded by your particular organization or your team. And it really allows you to create, to spread, and create connections across customer's and vendors and other orgs within your team. And, this is where you're starting to see this these sort of step function changes in these organizations. Where, you know, you see this Office Depot example. And, he talks about, you know, taking a workflow in their organization they, going from, you know, four to six weeks, down to twenty-four hours. And, enabling people who are putting in budget request, to take action on that request, the next day. And, those are the kinds of things, that are going to fundamentally change those businesses. And so, that's where I think the collaboration piece is really powerful. You can't get that kind of compression in time. Unless, you can really span those traditional business hours. >> So Robin, one of the great things that happens always is, with tech companies is the application versus the platform exchange, right? Everybody wants to have a platform, it's really important. You get an ecosystem, lot of stuff going on, but nobody's got a line item in their budget for 2019 to buy a new platform, right? >> It's always, >> Correct >> Application centric, right. I got a problem, I've got to fix it. At the same time, you guys, you do have a platform. Meaning, you can go across a lot of different applications. So, when you're trying to balance out your priorities with the platform. Priority, in terms of more of, kind of a general purpose underly, versus and app priority, like you said, multi, how do you call... >> Multi-assignment. Yeah. >> Multi-assignment, you assign two people to the (laughs). To the no correct product management protocol, but everybody wants it, cause it's the real world. How do you kind of prioritize that? How do yo kind of look at the world when you're deciding, what are you going to roll out next, what are you going to roll out next, ware are you going to roll out next? >> It starts and ends with having conversations with real people. We've taken lots of data and we have enhancement request and usage data on how people use the product. Multi-assigning, actually, was less than 3% of all answered request in the last couple of years. But, it's our number one request. And so, it sort of. >> Oh, Wait, wait wait. So it was less than 3%. >> Of all enhancement request. >> But it was number one? >> But it's our number one. >> So you've got a giant laundry list. >> Giant laundry list of things, right. So, we can't just look at some metric and go, these are the next features we should build because we have this really strong signal. We actually, have a very, very weak signal when we look at it from a quantitative standpoint. So what we have to do is we really have to dig into these customer use cases. We have to meet with them. All of our project teams have dedicated researchers, and dedicated user experience. People that are going out, we're actually talking to people. We're testing stuff with them and we're trying to understand what commonalities exist between multiple cases across all of these different use cases. Because, there're so many different ways people use the product. There not enough people asking for one thing. >> Right. >> They're all asking for slightly different things. So, we really have to dig in and have a real, qualitative conversation with them. To understand, and bring that back and say okay, these things are related. We can build something that solves, all of these problems in a compelling way. >> Well, it's definitely more than 3% of the people cheer. When, when that. (laughs) >> Yes. >> When the feature was announced, that's for sure. So the other, kind of (mumbles), that you've got to wrestle with is, kind of a low code, no code, we want to be for everybody, yet at the same time, you want a sophisticated application. You want integrations and connectors to all these other applications. So, again, that's kind of a delicate, balancing act as well. Cause, you want to let everyone have access to be able to manipulate the tool, work with the tool, set up the tool, but at the same time, you got to keep it, pretty sophisticated to connect to all these other things. How do you kind of balance those. >> Well we... >> Priorities. >> We just try to hide as much of that as possible. You know, Smartsheets always been this tool, where it's like, it sort of looks like a spreadsheet, and it sort of looks like project management. But it's got this underlying flexibility built into it. We don't force you to, you know, if you've got a date column, we don't force you to put a date in there. If you don't know the answer, you can type in TBD. Whereas, a lot of purpose built applications, their like, this is a date, you have to enter it in the proper date format, or it doesn't work. We've always had this, sort of, flexibility and complexity trade off. The trade off is, if you give us real data, if you give us something that looks like a date, we'll draw a Gantt Chart for you. We don't need much more, it doesn't need to be more (mumbles) than that. We just won't draw the bar if you type in TBD. And so, we've always sort of danced this line, with making the tool super flexible and assume the users know what they're doing. When they're interacting withhe tool we assume they an intention and they're trinna do something. And, we shouldn't force them down a particular path. And that, sort of, plays out in all these features. The other thing that we do, is like I mentioned earlier, we do a lot of user research and we get in front of a lot of customers. And we put stuff out there, well in advance in releasing it. In a situation like this, we announced a bunch a capabilities around workflow and multi-step approvals and multi-step workflows. And, I think that's a complex feature set. That's gone through more iterations of design and review and scrapping it and back to the drawing board, than any feature I've seen at this company. But, it's probably one of the more complex features we've ever build, as well. And so that's what we would expect, right? We're not going to get this right, by just having a bunch of designers and engineers sit in a room and go, oh, we know that perfect solution to workflow management. >> Right. >> Most of our customer's don't even necessarily, use the term workflow. >> And if you look in the app, it doesn't even say. It says words and actions. You know? And little things with words matter. We have technical writers that are very specific on what we label something. It's not an if statement. It's when this happens, do this. And there's a lot of nuance and subtlety into all of this. To try and drive the complexity out of it as much as possible. >> Right. >> You can't avoid it, but you know. >> So, in hiding it, the last thing which your going to do, going forward is machine learning and artificial intelligence. Which we hear about all the time, but really the great opportunity in the field, is for you to leverage that under the covers. To hide. >> Absolutely. >> The nasty complexity to help suggest the right answer. To help suggest the right path. So, that's got to be a huge part of your roadmap. Integrating those types of capabilities, underneath the covers. >> Yeah and, there's been a lot of, we've have had tons of discussions and obviously we bought the Converse Chatbot Company back in January. And, that's been a huge sort of arrow in our quiver, so to speak, right, in that regard. We feel that we have a lot of really good information. But, at the same time, there's a lot of talk about machine learning and AI. And, the reality is, that relies on huge data sets. And it relies on a lot of analysis. And that data is not something that we can just look at, right? We take our customer's data, security data privacy very seriously. And we don't have access to that kind of information. So we need to look at this, the machine learning and the AI capabilities from a very different lens, then say a consumer product. That's sort of, you're getting to use it for free, they sort of do whatever they want with your data. And you don't really have a lot of recourse, other than leave the product. We don't start from that, we start from, your data is yours, you own it, we can't look at it. But we want to enable you, to turn these types of features on. So, we need to look at more of like an off-end model, where a customer can say oh, if I'm a big enterprise user at Smartsheet, I can turn certain capabilities on for my users, knowing that that information is going to stay in our, is going to comply with our data governance, and our data privacy rules. That our IT team puts forward. >> So the spirit of talking about abstraction, abstracting complexity, Hiding it, (mumbles). I'm curious, when you walk into a customer. Cause here we are in Bellevue, we're not in Vegas, But, we're neighors with AWS, with Microsoft, Microsoft announced Teams, about eighteen months, or so, ago. You partner with both, you compete, but you, also, you're competing with Teams. When you walk into a customer and an enterprise, likely has a mixture of, tons of different software appications, right. But they probably have, 360, Office 365, Para Bi, Excel... Why would a customer, who has such a familiarity with, say a Microsoft, work with Smartsheet versus, well we'll just extend our Microsoft expertese and bring in something like Teams? >> Yeah. >> I'm just curious, what...You've seen in that? >> Well, you know, I think it's that Smartsheet's always been good at sort of, orchestrating the actual work that's being done. And, there's a lot of tools out there where, you're having conversations and tools out there where you're creating content, and there's not a lot of tools out there, that are sort of bringing the conversation and the content together. In an actionable and accountable way, right? And that's the sort of, Gene will, you'll sometimes here hims say, use this term, shared fabric. The Smartsheet, really provides this shared fabric, that ties a bunch of these tool together. And we really, we want to partner with all these people, because every organization is different. Every organization has a different set of tools that they've already embraced. They have a different set of goals around how many tools they're going to embrace. You talk to some customer, they're like, I love Smartsheet, it's going to allow me to get rid of ten apps. And, you talk to another customer that's equal size or equal complexity two minutes later, then they'll be like, I love Smartsheet, it allows me to work with all the tools that I've already got. Very different, and they just have to different coperate goals and objectives there. And so, I think that the reason people like Smartsheet, is it doesn't, it's back to that kind of, hey, you don't have to put a date in a date cell. It's flexible. It's going to work with you and not force you to adopt the Smartsheet way about things. It's going to say look, oh, if you want to use, if you want to us Teams for your communications vehicle, and One Drive for all of your document storage, great. You want to embed a PowerPoint document in a dashboard in Smartsheet, great. We want that to be the case. We do that internally, right, we use all those. If you look at us internally, we're just like every other mordern company. We have a dozen tools or two dozen tools that we're using. And it's different from team to team and department to department. So, it's all about just embracing the reality, that as modern business and modern application, the ecosystem of applications that we all deal with on a day-to-day basis. >> So that flexibility is key. So we said about 1100 companies represented here, at this event. 2,000 people or so, fifty plus customer speakers. Is there one customer example that comes to mind, whether they're speaking here or not, that really is a great demonstrator of, we have a plethora of applications in our environment. We want to work with Smartsheet because it enables us to integrate and use these tools so much better? I didn't mean to put you on the spot. >> Yeah, no. I'm trinna think of a good. I don't know that I have a good standout example. I think that we hear little tidbits of that from everyone. And it's not, it's a very common theme. So, I don't know that. It's sort of back to the 3% thing, right? Nobody really stands out because everyone is doing that. Everyone is, I hear things, I'm going to replace this tool because you did this. Or, I'm going to now pull, integrate with this tool because, you've added this. So, you sort of take some and give some, on the same sentence almost. >> Yeah. You can do both. >> Yeah. >> Well Robin, thanks so much for stopping by. We appreciate your time. We're excited to be here. This is our first Smartsheet event. And we have some customers coming up, so looking forward to hearing some more these cases in action. >> Great, thanks a lot. >> Thank you. >> Thanks. >> We want to thank you for watching theCUBE, I'm Lisa Martin with Jeff Frick. You're watching us from Smartsheet Engage, in Bellevue, Washington. Stick around, Jeff and I will be right back, with our next guest. (tech music) (tech music) (tech music)