Jeff Yoshimura of Elastic: Building an Epic Brand

All right, guys, we're gonna get started. This next hour is all about marketing. And we have two pretty incredible CMOs and VP of Marketing from companies that you've heard of coming on stage. So first I'd like to introduce Jeff Yoshimura. Jeff was one of the very first folks@salesforce.com and the marketing team. He was there when they were just a small Little startup under 300 employees and he helped grow Salesforce to IPO. He was one of the founding team members on the AppExchange team and he helped launch that Epic brand. And he's gonna talk about Epic brands today. And then he was one of the founding members of the team at Zora and he helped drive that brand around the subscription economy. And now he's at Elastic, who powers the developer platform called elasticsearch and he is running marketing there. He is here today to talk to us about building an Epic brand. And by the way, I forgot to introduce myself, Emmanuel Scala, VP of Sales from Influitive. I all day talk to marketers. So it's a pleasure to be here with Jeff today. I'm going to hand it over to Jeff and we're going to take some questions at the end.

Hello, everybody. Welcome to, I guess Thursday. Today's the last day of the event. Super excited to be here today. Thank you for the introduction. I've known Emanuela and the folks over at Influuted for a long time. So congratulations on all of the great work that you guys are doing on the ecosystem. You know, there's a lot of things that I could talk about when it comes to building a brand and clicker, So I'll go without the clicker. So there's a lot of things I can talk about about building a great brand. And the things that I won't talk about are I'm not going to talk about marketing pyramids or brand pyramids, messaging platforms, things that you guys can read about in blogs. You guys can read about these things on hbs. Saster does a great job with their blog. First Route Capital does a great job with their blog. But what I am going to talk about are some real life experiences that I've had over the past 15 years or so, really helping kind of build four different brands. And what's been really interesting as a reflect on today is every experience has been a little bit different. There's really kind of no one size fits all formula. There's a lot of iteration and adaptiveness that you need to take in building your company. So if you're just starting out your company, or if you're at that phase where you're growing your business from that first 5mil to 10mil in revenue, or if you're accelerating, hopefully there's something that each of you can take away from today. I'm going to start with the App Exchange. The App Exchange was a project that got kicked off in 2005 and it was kind of a Skunk works project. And Marc Benioff wrote on a piece of paper, I want to build the ebay of the business applications. And he handed that paper to Tien Zhou, who was chief Strategy Officer Employee number 11 and the first CMO of Salesforce. And he said, go figure this out. Go figure out how to create this marketplace. This was pre App Store. This was pre any type of real kind of marketplace that exists today. And Salesforce was still pretty new. 2005 was a year after the IPO. 2005 was really when the company started to unleash some of the new tools around S Force and building custom scripts and the ability to do kind of integration within the platform. So it was really something that was kind of this hindsight idea. Can you pull this off? Well, fast forward to today. The App Exchange has grown to a million plus installs. They just had a 10 year anniversary party about a month ago in San Francisco and a lot of the old members of the team were there. And some of the things that we learned from that early early experience was the first 100 apps that we built weren't really apps. These were apps that we took from the field. These were apps that sales engineers were building, these were apps that professional services people were building, or these were apps that some of the early partners were building. And these were simply just ways to get around a lot of the at the time, a lot of the kind of deficiencies of Salesforce, meaning that you couldn't really customize the application to work for financial services, you couldn't customize the application to work for media. For high tech manufacturing, Salesforce really didn't work. So this concept around these packaged applications really became the workaround for an S sales engineer and a sales rep and a customer success team to go and showcase how Salesforce can be extended. So the way that we got our first hundred apps was we went internally and we said, we need to get 100 apps within 60 days. And we had this massive influx of internal requests from folks that I'm building this app for this use case and that use case. And we really curated the concept around the App Exchange Internally, we also did a lot of experimentation. So for those of you who recall, there was a building on 101 at 92 and 101 that used to be the old Siebel Building. Well, Salesforce acquired that building. We ran into the App Exchange. There was a little bit of media buzz around. You know, Siebel is dead. It's just now Salesforce is building because that used to be the old Siebel building. But we did a lot of experimentation. We had an incubator there in that building. We had this concept of category experts. So we took people from internally within Salesforce to look at the different, really categories of applications that are gonna help drive user adoption of Salesforce. We did things around certification. We did things around online advertising. When we first launched that marketplace, some of the things that really were special, things that we focused on were things around. Let's think of the App Exchange as something that is going to help our customers be successful with the deployments of Salesforce. And some of the key takeaways that we really got from that experience that might be applicable for folks here in this audience is back in 2005, 2006, this was not a brand. The App Exchange was just a concept. And it was a secondary, maybe even a tertiary brand within Salesforce. But the team that was working on the App Exchange, we all believed in Mark's vision that this was going to be something that would be really, really special. So we treated it like a brand, and we invested in ways to make sure that we got the word out. So we did a series of launches. So when we got the first hundred apps, we did a launch. When we got the next 1000 apps, we did a launch. We did vertical launches around financial services and media. We went to large ISVs and recruited big ISVs to go build applications because we knew that if we attracted the big ISVs, it would also attract the smaller developers. So we really treated it like a brand. And as you've seen kind of Dreamforce, if you've been to Dreamforce, grow over time, that brand has also matured. In terms of the early days at Dreamforce, when the App Exchange launched, we had this program called certification, where all the partners would get certified, and then we'd say, partners, we want you to unleash your press releases on day two of Dreamforce. And there would just be a flood of press releases. It would be big machines, launches on the App Exchange, Eloqua launches on the App Exchange, Marketo launches on the App Exchange. So it just created this really spread of really kind of buzz around this new ecosystem. So letting partners participate and developers participate in the building process to, to help build your brand and extend the brand was something that we really learned as a critical success factor. Thinking very big. If you look at a lot of the early articles back to 2005 and 2006, there were a lot of people that said, this is a crazy idea, it's not going to work. And there are a lot of skeptics that said what we did with all this feedback was we channeled this feedback internally to make that product better, to improve the packaging, to improve the user experience, to improve the customer experience, to channel all that feedback back into product development and make sure that that gets in so that product becomes better and better and more impactful to end users. I'm gonna talk about Zora. I left salesforce.com to become one of the first employees at Zorra. Ironically, we incubated ZORA inside of the App Exchange building. So teen Zoe was employee number 11. He's CEO and co founder of Zora. He was my boss and my boss of many, many years. And he came to me and said, I have this crazy idea. I'm going to leave Salesforce after nine years and start this company Zora. Mark's going to invest in the company and I want you to be one of my first employees. We were out on a business trip out of New York. So I said, sure, why not? What else am I going to do? So I went off and we started ZORA inside of the App Exchange building in San Mateo. We'd work evenings on a lot of the early concepts. And at zora, what we really played around with a lot was messaging and how do we elevate our brand? How do we elevate our messaging? No one really knew of this subscription billing model or subscription business model. Back in 2007, 2008, a lot of the great SaaS companies that today are very successful, multi billion dollar companies didn't even exist. So how do you get the word out that the world is different when you run a subscription business? So we just really kind of had this concept where the old world is all about kind of you buy now, single track commerce. And the new world is about relationships. It's about this recurring revenue stream. And we really drew the line in the sand around this concept called the subscription economy. And this wasn't the first thing we came out with. We had to come out with. We started with on demand billing, we started with something called subscription billing. We must have played around with so many different variations before we came up with Subscription Economy. And it wasn't until a reporter named Tom Tolle, he writes for Forbes today, great guy. He wrote an article called the Netflix Economy and the Netflix Economy within that article talked about the shift of business models. He referenced ZORA in that article and that's where we came up with the idea. Subscription Economy. And eight years later, this is something that is still being used at zora. One of the other things that we decided that we really needed to do is if you've ever worked for Teen or if you know Teen, he's a bit crazy. He's. He's always online and he's pinging you with crazy ideas. So one night at midnight, he pinged me and said, In 48 hours, Apple is going to launch something at Moscone. So I want you guys to go out there and campaign in front of them. And I was like, this whole campaign thing is not going to work. We're not going to protest, put signs up. We're going to get kicked out, get thrown on the street. So this was also a time when social media was just starting out. So what we decided to do was launch a social media campaign around Twitter and we set up a site called SaveYarpress. And this was also the time when Apple was really not being too friendly to media companies and publishers. And we were also selling to a lot of media companies and they were saying, we want to use Zora, we don't want to use this Apple thing. This 30% cut isn't going to work for our business model. So we dressed up as Newsbees and we created this flyer that was like an onion like piece. And we went out there before the Apple launch and we picketed around and we gave it to all the reporters. This was a press launch, by the way. So we handed these things out to reporters and they were like, who are you guys? We're from Save Our Press and we're here to save the media industry. You sure? Not from a company? No, no, no. We're from Save Our Press. Some of the folks that were here that there that day, Shannon Murray's right there, Katrina Wong, they were on my team and we pulled this kind of stunt off and we ended up getting a lot of press and we ended up getting a lot of really good press around kind of what we're doing and a point of view. But it all pointed back to the subscription economy. It was all about this movement and shift of goods and services to the subscription business model. So have A lot of fun and kind of think out of the box. And I really have to thank teen for pushing us to do things like that. So a couple things in terms of lessons learned at Zora. Company name does matter. You know, it was not easy creating the brand for Zora. This whole thing of Z, Zuora, is it Zuora, is it Zora? It was especially hard for salespeople out there making calls. People couldn't spell it. So these were things that we really, really had to work on. There was contemplation in the early days, should we change the name to something else? We ultimately opted not to do that. We actually told a couple of early customers and said no, we like the Z. Well, you know, later on, as time goes on, it gets harder and harder to change that name. So if you are going to make a name change, do it really, really early on before you launch, before you get some funding. We talked about kind of elevating the message which doesn't have to relate just to your product. Subscription economy. ZORA is a high level category. And then don't give up. Tien is one of the hardest working people that I've ever met and he does not give up and he's always there for the long haul. So this is something that there were a lot of people that had worked for ZORA or that were collaborating with us and God, the subscription content message is not going to work. Well, eight years later, Tina is sitting on CNBC with Jim Cramer talking about not Zora. He's talking about the subscription economy and how there's all these different kind of macro trends happening. So don't give up if you have an idea that you really like. Now I'm going to shift gears to the space that I'm working in today. It's more kind of space around big data. I had the opportunity to be one of the first people at a company called Ayazd. It's a really kind of abstract technology that is different than your Pure SaaS Play application. It's machine learning, taking all this data inside and without even asking a question of the data, it pops out kind of what the correlations and answers are. So this is developed by three mathematicians from Stanford University and I was the first business hire of this company and it was really raw, it was pre funding. We were working inside of basically a house in Palo Alto and you know, my job was to figure out how to launch this company, how to get this company off the ground. I got three mathematicians, brilliant people, including the professor of mathematics at Stanford University. And how do you actually go get this company off the ground to know Khosla had already committed to investing the first $10 million in the company. And there was also this thing that they kind of were doing called topological data analysis. I said, what the heck is topological data analysis? This is no category. How can I launch something like this? No one is ever going to know what this is or can they even say it. So what we ended up doing was spending a lot of time around how do we take this really deep mathematical concept that today is actually the formation of a lot of graph theories and graph networks, which is a really popular thing in the data space. But how do we take this really complex thing that has been around for hundreds of years and make it really, really simple? So what we launched with was something around the concept of a lot of companies in the space. Just take IBM, Watson. We're talking about finding insights through asking questions of data. So we said, you know what, we're the anti, anti finding asking questions of data. With our technology, you don't have to ask a single question. You throw the data in and we're going to get you the answers. It's a little far fetched, but we would lead you to where the answers are. So we launched the company about six months after I joined and we got a ton of coverage. I mean, nobody knew about the company. And I had three mathematicians on the COVID of the Wall Street Journal in print, they were in Bloomberg in a print article, they were on NPR talking on here now. I mean, they were all over the place. And this was at a time when Big data was also just getting started. So our job was to look different than everybody else who was talking about analytics or insights. And a lot of these common buzzwords you hear in Big data. So the lessons that we learned from this experience are that experts aren't always right. So when I joined, I was like, man, this name is tough. I already dealt with a Z name. I don't know if I can deal with an A name. So what do I do? And I had really two options because the CEO said, well, we have to launch the company. So I don't want to go through a naming exercise because I already did that and I already spent a lot of money doing that. So before I came on board, given that I was the first business hire, they had paid an agency and invested in resources to actually change the name. And the name that this agency came up with was Phenom. And it wasn't even phenom.com, it was phenom.net, i was like, are you crazy? And then I said to the founders, how do you guys feel about this name? We're a little bit uneasy. I mean, I know we're mathematicians and we think we're brilliant, but this Phenom thing is kind of not a really good play on what we really want to do because they're very humble, down to earth people, just great people. So over a weekend, I said, you know what? We're killing the name. We're going to go back to Iyazdi. It has meaning. It means two Sikh and Cherokee Indian. We have the.com URL. It's the name that you guys like and feel really, really comfortable with. So we went back to the VCs and said, okay, guys, we're not changing the name to Phenom. We're going back to a Yazdi. And we shifted gears and pivoted really quickly with about two months before we launched. We talked about kind of simplifying complexity, which is what we had to do. And we're kind of moving away from this concept of topological data analysis. And then the last thing that we did was really work on telling a great media story. And these were three mathematicians from Stanford that had never been inside of a company before. And that requires putting the right discipline around, training in place, but also right sizing it for them. So there's a lot of folks out there that do media training and there's a lot of great PR people out there, but you need to really right size things. So what I did was I looked back back at companies that had an academic rooting. And I hired a group that trained Diane Green and the team over at VMware because they were academics. And I used them to train the founders of Yazdi because that was a great kind of bridge. And they felt really, really comfortable being with the trainers because they had worked with people in academics. And we did a roadshow out in New York and it was kind of two months before launch to get these folks comfortable with some of the media and journalists people that I knew. And then we ended up kind of launching a month and a half later and the rest is history. The company has gone on to raise about $100 million in funding. And I was there for about the first two years of that. Where I am today, I'm at Elastic. Elastic is the company behind the open source projects, elasticsearch, Kibana Logstash and others. Just walking through kind of the hallway, there's a lot of end Users. So if you folks aren't developers, maybe your developers are using our technology underneath your systems. I see some of the folks out there like totango, that's elasticsearch under the covers. And with Elastic, what has been unique is because we are open source, we have a massive community. So we've had 45 million downloads over the past two and a half years and we have 50,000 community members worldwide. We have endless number of users out there who are willing to tell their story. So the platform that I use around kind of building the brand is a little bit different. It's more about getting users to tell the story and to use those stories to talk to other developers and other architects. So it's less about telling a business story and trying to get these folks in front of the New York Times and Wall Street Journal and Bloomberg, but more about telling a user story that is going to resonate with other people like them. So Elastic powers NASA, for example, which is a pretty exciting story. So, you know, four times a day from the NASA Mars rover, there's streams of data that comes into elasticsearch and they use that data to power all the space missions. And there's many, many other stories like that. So with Elastic, the things that I'm learning now that I've been here for the past year or so is build a community. So I have a team focused just on building the community and building the ecosystem. We don't really care about leads. In fact, we don't put these people into our lead gen database. These are community people. And we do about 500 meetups a year around the world. And we spread the gospel about Elastic and it comes from the community. So the best case is you have somebody from the community run the meetup organization, not somebody from Elastic, not a salesperson, for example, or a marketing person, but somebody who is actually a developer in the community. We also go out and curate a lot of stories in the wild. So we see a lot of things that are happening around the use of our technology. So we'll go get any user story and have these people tell their story and and author a blog on our side or speak at one of our events or go speak at a meetup. And then the one thing that we're trying to do different here is I have an editorial staff that we're trying to build a very special voice. And right now it's not evident across our site properties and our mediums, but we really, really want to be different. And if you talk to our founders, they don't want to sound like any other data company and they want this personality to be fun and engaging and lively. And you know, we're doing a user conference next week and you know, a lot of the keynote deck is going to insert a lot of the thinking from our founders where he's a big movie, a movie buff and there's a lot of quotes and themes from different movies that he wants inside of the keynote. So it's really kind of having this fun play on what we do, but obviously relating it back to our technology. So, you know, I make this statement that you have to find the voice and channel that voice of your founders into how you go out there and create your brand. It's super, super important as you think about the longevity of your company and the longevity of your go to market strategy. So in summary, no experience or company is the same. Every experience is unique. So again, it's not a one size fits all. And really think long and hard about how you want to be different than what you've experienced before or how you want to do something different than what you've done before. And that's one of the things that at least I take a lot of focus in terms of where I move from is not taking the same playbook and saying that it's going to work over and over again, because it usually doesn't. So being able to adapt and brand building takes a lot of time. Salesforce.com in 2008 was not that big of a company. It was 3,000, 3,500 people. Today it's 15, 16,000 people. It wasn't that big of a company. Building the brand of Salesforce, building the brand of AppExchange. It took 10 years to do the AppExchange brand and to get it to where it is today. Salesforce took a long time. So building a brand takes time. To remember that is that it does take time. And then having the right team and the team can be internal, it could be external resources. But building the right team around you is super important. But aligning that to the right goals that you have for brand building, is it to generate awareness? Is it lead gen? Is it to launch the company? What are those goals? I think making sure that you have alignment to what those goals are, are super, super important. And you know, keep, keep iterating, right? Keep iterating. And you know, don't fire somebody just because they didn't achieve something. If you hire the right team, work with them, iterate with them, it's going to take some time. So those are the things that I would say in summary and in closing with that, I think we have five minutes or so for questions.

Yeah. Great. That was great, Jeff. Thank you. So I'm just going to ask one question, actually want to piggyback off of the end of what you just said. There's a lot of young companies out here, and if it's going to take 5, 10 years to really build your brand, how do you measure that you're on pace? How do you measure that you're on track after, let's say, year one or year two? How do you know that you're heading in the right direction?

I think first thing you got to do is you got to listen to your customers, you got to listen to your early users and adopters and you're going to get great feedback from these early folks. Are you on pace? And obviously product, brand, market, product market fit, these things all need to come together. But those first three to five years of just listening to your customers or your target customers is super, super important. We had to do that at ZORA in the early days. In fact, we pivoted a lot of the early. Early customers were really, really tiny startups. But we decided that that wasn't actually the right set of customers for what we were trying to achieve. So we actually went a little bit upstream and we changed the bar from really selling to companies that had less than a million dollars in revenue to focus on companies that were between a million and five to ten mil. So, and that was all based on feedback that we heard from our customers that our system was a little bit too complex for their needs.

Great. So try something, listen to your customers iterate and keep trying. Awesome. So there are some questions out in the audience.

Thank you so much for sharing. For B2B companies that have products that are used by end users as well, how do you draw the line between letting the stories of those end users come up, but also, you know, having stories of your actual clients come up? Does that question make sense? Yeah. At least for us at Elastic, we don't really care. We will because we have massive amount of end users and then our customers are actually pretty large. We have a couple thousand customers customers, but we don't discriminate between end users and customers. What we do want customers to tell is how they are using really what we call our open core model, which are some of our commercial extensions. They're getting value from our commercial support. But for end users, we view that there's a user journey and that a user who starts off As a free user, an open source user, as they mature in their development cycle or as their company matures, they have the potential, if they want to, to become a customer. So you know, we don't, we just want to get as many great user stories out there as possible. And we actually look at that when we have a user conference is we want a balance. We don't want to just have all the paying customers be speakers at our conference.

Other questions over there. There's some mics coming.

Thank you. I have a company name that starts with Z as well and my investors are concerned because we'll be at the bottom of all lists. Can you give me your view on that? Going from Z to A was actually nice because we actually appeared at the top of the list. So that is a valid concern. That said, I think you can build, build a great brand with a Z or a Y name. If you just take a consumer property like Yelp, they have a great brand. You know, there's plenty of other companies that have names at the end of the Alphabet that are doing well. I think it's how you get out there and promote your brand and get the right set of stories out there. So if you have a great name with a Z, I wouldn't worry about it. I would just keep it as is. Trying to find an A name is, is a little bit crazy.

We have time for one or two more. There's one over here.

We heard from one of the other speakers earlier today that as a startup, you know, you're probably better off hiring talented young people rather than competing for experienced people. Does that work for marketing people as well? I mean, you mentioned the people in the press. You know, someone who's straight out of university ain't going to know no one. I think in marketing, if you're just getting started, I think you can do a couple things. One is you can have a set of advisors that can advise on helping you get your company off the ground. And then you can hire somebody who's maybe mid level or someone who's between kind of just getting started in their career. But they've seen a little bit of growth, maybe two or three years at a company and they're going on year four. But they can really kind of take their career off and use this opportunity as a platform. And as long as they have a good network where they can still learn from other people that are either mentors or advisors to them, I think that's a perfectly fine solution. I don't think you need to. If you're just getting started and you're bootstrapping your company. If you just raised your first 1mil or 2mil, you probably don't need to go hire a VP of marketing out of the gate. I would focus on how do you get product market fit or how do you just get your first 10 to 20 customers in the door if you're B2B? If you're B2C, then how do you get your first 1000 users and learn from that?

All right, let's thank Jeff. That was epic. Really appreciate it. Thank you.