1. Library
  2. Podcasts
  3. Road to Growth
  4. Ep. #1, Introducing Road to Growth and Yaron Sadka
Road to Growth
27 MIN

Ep. #1, Introducing Road to Growth and Yaron Sadka

light mode
about the episode

Thanks for listening to Road To Growth, a bi-weekly podcast exploring what it takes for a sales team to succeed beyond merely hitting quotas. Our first guests include Iron.io CEO, Chad Arimura, LaunchDarkly CEO, Edith Harbaugh, Bluenose Analytics CEO, Don MacLennan, and Keen.io CEO, Kyle Wild. Each has a different perception of sales, and each offers valuable lessons for success that you can’t miss.

To join the show as a guest, contact us at roadtogrowth@heavybit.com or tweet at us at @roadtogrowth_

Everyone that tries to grow a company accumulates a wealth of knowledge as to what drives an upward or downward trend. A key driver of growth is sales, but what does that actually encompass?

Road To Growth hosts leaders from top companies with a spectrum of perspectives to discuss sales beyond simply hitting quotas. Marketing heavily influences the top of the sales funnel. Support and customer success contribute to account growth and retention. Fundraising requires managing a pipeline of leads and opportunities. Product and engineering teams keep battle cards tilted in your favor. Sales is everywhere, and we want to share it all with you.

Road To Growth will empower you to make better decisions when faced with the tough problems surrounding your sales organization. Ideas and processes we discuss may not be the route you choose, but with a deeper understanding of how sales can be integrated throughout your company, the scales will tip in your favor… and isn’t that all you can ask for in sales?

For more Road To Growth and to find out about new episodes you can follow the show on Twitter at @roadtogrowth_.

Chad's Path Into Sales
Early Pricing and Customer Feedback
From Utility Pricing to Plans
Hiring the First VP of Sales
Building the Team Around the VP
What He Would Do Differently
What's Paying Dividends Now

transcript

Chad Arimura: As a CEO and a founder, you have to get over that fear and get in front of your customers. You can't be scared to ask for money.

Our job as a sales organization is to protect the value of what we've built. Our customers' best interest is that we build a successful business.

Yaron Sadka: Hi, I'm Yaron Sadka, sales engineer at Iron.io. You're listening to Road to Growth, a podcast about startup sales organizations brought to you by Heavybit, a nine-month program for developer-facing startups. Road to Growth is a bi-weekly series that breaks down SaaS sales organizations one piece at a time.

From the first person to kick off sales at a company all the way down to the partnership and cohesion with the marketing and product teams, we'll take you through what it takes to build a powerful, fine-tuned sales organization. If you're interested in being a guest, have a topic for us to discuss, or a role you'd like us to dive into, send an email to roadtogrowth at heavybit.com.

In this episode, I'm joined by Chad Arimura, co-founder and CEO of Iron.io. Chad and I discuss his early sales experience as CEO, the importance of your first sales hire, and the idea that a sales organization's primary purpose is to defend the value of your product.

Chad's Path Into Sales

Today we have Chad Arimura. He's the CEO, co-founder of Iron.io. Been around for a few years now, gone through some rounds of funding and all those different phases. So welcome, Chad. Thanks for coming.

Chad: Thanks, Yaron.

Yaron: Tell us a little about yourself, your history and how you got to where you are today.

Chad: Sure. So my name is Chad Arimura. I'm the co-founder and CEO of Iron.io. How did I get to where I am today? Well, I guess it started in the college dorm room back in 98.

Started my first company in college where I got together with some co-founders at the time. Well, actually I got roped into it because I was an engineer and the business guy wanted someone to build something.

So back then, registering URLs was kind of difficult and it wasn't widely easy known. And GoDaddy, I don't think, even was around at the time. So I helped him register the domain name and I became co-founder overnight. So that was pretty exciting. That became seven years of my life, actually.

Built a business around marketing to college students, so helping big brands, Fortune 500 companies reach the college market. And I was the CTO, co-founder then, helped architect the initial applications, building big monolithic apps using Perl at the time.

And so at that point, we built a pretty good business and ended up selling it. It was a student-ran business, sold it in 2005 or six-ish timeframe. From there, that's when I got initially into sales.

So I started off as a sales engineer at Sprint, did that for a few years or about a year and a half, and then I went quickly into Oracle where I was field sales, Fusion Middleware sales the time, so it was a bit of a hybrid role between sales engineering and direct sales, selling the Oracle middleware line.

And that's where I really started to cut my teeth on how enterprise software was sold and understanding how buyers operated and the philosophies and techniques for sales. And Oracle, if you're familiar, is a quite interesting sales organization. So I learned a lot being there.

It was pretty exciting. And then to complete the story, I went from there and met up with my co-founder, who at the time was at Siebel, and both of us said it's time to get into business again. And started our own thing. So we started a consulting company building and writing software. And that's where the first products were built that are Iron today.

Yaron: Awesome. So, taking that to the start, then you weren't originally seeing yourself in sales or anything like that, going to school for engineering and then kind of fell into more of a sales role. Is that kind of how the story came together?

Chad: Yeah, actually I had never intended to go into sales. A buddy of mine who was one of the very early employees at my first company, AllDorm.com, after we sold the company, he left a little bit earlier than that and he went into sales and he said, "Chad, you have to get into sales because the market for technically savvy or people who can speak the technology language, but also speak the language of people and be able to just interact with people and have conversations and articulate the value of technology, they're in high, high demand."

And so he is one of the best salesmen I know personally, and so he sold me on the idea and I was super nervous. I mean, I went into this interview. I'd never been in an interview before, by the way, because I did my own company for a long time. And so it was really like my first job interview.

And I walked into the office and my buddy, his name's Mike, he said, "Don't worry, you're shoo-in. Just go to the interview. You're in." And so I walked in there and the sales manager, he set his phone down on the table and he said, "Sell this back to me." And I was like, "Oh my gosh."

So luckily I had read a couple sales books. I think SPIN Selling is one of them. So I basically just regurgitated the same stuff from that in front of me. He's like, "Great, you're in."

Yaron: Better than selling a pen back to somebody, I guess, which is the normal thing you get at the conferences.

Chad: Exactly. Well, this was for Sprint, so naturally selling a phone was kind of part of the process. But it turned out to be a really great move because I loved it.

I had a great time. I became the guy that just sort of went around the country and talked about technology but didn't have to be really held accountable for the exact sales part of it because we had sales reps. I was an overlay rep at the time.

And then when I went to Oracle, I had a really cool gig there where I was just helping architects and talk to customers about their architecture. And it was like the best of both worlds. But then I had to get back into building it myself.

Early Pricing and Customer Feedback

Yaron: Great. So then now, talking about Iron, since we are kind of focused more on the startup environment, you had the sales background, you met up with Travis, he takes the lead on the more engineering side, you take the lead more on the business side. So what was your sales strategy when you guys first started off? Probably not in the first few months, but you hit year one and now you need to have some sort of sales to prove yourself to investors.

Chad: The sales strategy was get anyone to pay you anything for whatever it is the hell that you're building. Travis and I, I think, had pretty good intuition around what we wanted because we were our first customers. Our clients at the consulting business that we built all relied on our technology to build the software and manage the software that we were building for them. And we knew that there was value.

So putting together a strategy was just around, how the heck do we price this thing? How do people buy? Calling up all of your friends, calling up all of your family members and saying, "Try this out, please try it out, pay us anything." "Twenty dollars is too expensive. Okay, fine, pay us ten."

And that's really the first major phase of, I'd say, product market fit, is just seeing who and how many you can get to pay pretty much anything and what the value is of them at the time. And that evolves a ton over time, but in those early days it's just about getting people to give you feedback and, as they say, partying with some of their hard-earned dollars.

Yaron: Yeah. So feedback is a big part that people kind of forget about sales, when you have your reps talking to clients and taking the information that the client gives you and kind of feeding it back to product and engineering. That's a big part that people don't realize about sales, is how much it drives products sometimes.

So at the beginning, I should say that the sale wasn't necessarily money. It was more about a long-term, right? The sale is in this kind of really young phase. We're not looking for the money, but we're looking for the feedback. That's the value that you're giving us right now as a company.

So when you're first starting out, that's great. You have all these cycles that you can go through. As you grow and the company kind of grows with you, you get more and more removed. So how do you kind of keep control and keep tabs on the feedback customers are giving you without necessarily being on these calls and talking to clients on a day-to-day basis like you used to be?

Chad: Well, a big part of that is trusting your team as you grow. A couple of comments about what you said a second ago.

Yeah, I mean, the feedback loop is critical. It's all about creating something of value and then capturing that value in the way that you go to market. And if you're creating value and people love what you build and they are getting value out of it, it's about capturing that value. And you can't be scared to ask for money.

And a lot of the times it's just about continuing to raise the prices until you've met that sort of value match to what you're selling.

And it's not about scamming customers or being unethical or not being in their best interest. It's about our customers' best interest is that we build a successful business and that we continue to capture the value of our intellectual property and that we can offer a great service and great solutions to our customers.

And if we give it away or we mark it down because they can save a few dollars on their budget, ultimately that puts us at risk, which ultimately puts our customers at risk as well.

One of the best lines I heard at Oracle... Oracle tends to be on the other side of the spectrum where it's raise the price as high as it can possibly go, and then just almost never budge until you found that maximum value. And I, as an engineer, I had a big problem with that.

And one day I was talking to someone pretty high up and they said at Oracle, "Our job as a sales organization is to protect the value of our IP. It's to protect the value of what we've built. It's not to scam our customers or use every dollar in their possible budget. It's simply to build a successful business." And that's really resonating with me.

So to answer your question about how to stay in tune with your team and your customers, it's trusting your team, trusting that you're bringing on the right people. There's a very, very big trust exercise. As anybody who's building something, you start to lose, I wouldn't call it control, but you just lose visibility and you lose this sense of control.

And it's like a trust fall almost, like falling backwards and having someone catch you. If they don't catch you, you're gonna have a hard time trusting those people in the future.

But the more you do it, the more you trust those people and you begin to just set up processes and workflow where information gets back to you eventually. But also don't forget about the customer. So I'm still on customer calls probably twice a day, consistently every single day. And that helps make sure that I'm in the loop.

Yaron: That's great. And bringing back the value piece, you inherently understand the value of your product, as you built it, you kind of came up with the idea for it. How do you communicate that now to a sales team that you are putting together that may or may not be technical necessarily and don't understand the day-to-day value that your product provides?

Chad: For me personally, one thing that helps me a lot is talking to our customers and hearing personally from them what they see the value in our product is. And so making sure that the team has the opportunity to talk with customers who advocate for our technology, talking to happy customers, hearing from their mouths what they see is in the value.

As a founder and especially a CEO, you can constantly harp about, "We're the best, we're the best," harp about, "There's so much value built up, just go and sell it."

But to hear it from your customers is just a thousand times more powerful, I think, because it really starts to drive home for the sales team what it is that they're selling and what they're creating for customers, not just selling something, but creating value and helping customers solve problems.

And I think that's critical, is setting them up early with customers that can be successful and are successful already.

From Utility Pricing to Plans

Yaron: So you take that piece and now you actually have to value your company and put a dollar amount on it, which is hard to do when you're talking to clients of varying sizes and different people within the organization. So you come out, you start with a freemium model, you just get users in the door, get customer feedback, and then now you need to start charging. So what was that process like for Iron? You started day one, here's the pricing, and then how did that evolve as you grew?

Chad: Well, the big thing for us was that we started off as a utility where we were charging per minute for our worker processes, or basically the time that you were running code, we were charging. And then for IronMQ, our messaging service, we were charging per million messages.

And that's a very comfortable way to sell your service or sell your product, because then people pay what they use, only for what they use, and then you end up with a ton of customers paying you about a dollar seventy-five per month. And it's a great way to feel comfortable about the value, but also it's a great way to build a losing business model.

Because suddenly you're comparing your company to companies like Amazon who are doing multiple billions of dollars per quarter and are just commoditizing every piece that can be commoditized. And you start to be compared to those companies as well. And then not only that, but then you start building a company in that light.

So the big evolution for us initially was to start releasing plans. And those are what we called our starter, our developer plans. At the time, I think we called them iron and ore and gold and silver and platinum and that kind of thing.

Yaron: Keeping with the theme of...

Chad: Exactly. And charging monthly and understanding that the value is captured in the plan, not in the utility usage of that plan.

So we stopped charging per minute, we stopped charging per message, and we started charging around what are the things that customers really value about our service. And that turned out to be first in, first out, FIFO ordering of queues, that turned out to be priorities of jobs we ran and be able to jump priority in order. Get dedicated workers, being able to ensure that you have capacity always to run.

That was the second evolution of our company, is when we realized that enterprises really valued things like SLA. Well, choice and control are the big thing for enterprises that we hear consistently. So having control, having choice, the flexibility to ensure that they have SLAs in place, that they have dedicated capacity, dedicated infrastructure just to them.

They have VIP white glove support from our team, they're able to ensure that they have capacity when they need to run something, that it's gonna get run, and that they can rely on you as a business and not just a company selling to everybody and this kind of faceless software organization.

So the second big iteration for us was marrying the best of both worlds, where we can grow with our customer but also capture that value as well. And so we started charging for things like clusters and regions and concurrent workers as opposed to just raw minutes.

And we're continuing to move more into the solutions-oriented sell, where we deliver a solution for X dollars per month as opposed to you're using this much resources and that type of thing. So that was the big evolution that we've taken as a company and it's done really well for us so far.

Yaron: Yeah. So it sounds like the value really that you've found is stay away from resources and see what it is that companies really need, because the need is the value, not the want. So when you talk about enterprises, they're more so focused on the service part than the software. They can build the software, but they don't want to do that and they're looking for the service piece, whereas younger developers or smaller teams are just looking for the software because they don't have the time. And they're not so worried about the servicing because they have time to do the servicing themselves if they have to.

Chad: That's right.

Hiring the First VP of Sales

Yaron: So now you have these plans together, you're starting to sell, the company's growing a little bit. And you're leading the sales team, right? As the CEO, you're focused on the business aspect of the company.

What kind of triggers do you look for? Is it time of day, is it the amount of volume of customers coming in? What flags and triggers really say, okay, you know what, now it's time to kind of start looking for either a sales team or somebody to focus their time on more of the sales aspects of the company?

Chad: Well, definitely wasn't a sales team, because a team would warrant having multiple people in place. I think the best way to look at that is you got to bring in sales people or a sales leader the second you can afford it and the second that you know that you have something that customers are willing to pay for.

Whether that means one customer paying you five thousand dollars a month or a hundred customers paying you ten dollars a month or fifty dollars a month or whatever it is that you're selling, if you've got enough of them and maybe you get to your first ten thousand dollars in MRR, that's a pretty powerful message to say, okay, now we need someone to come in early and start to wrap strategy around this.

Because your first VP of sales should be your first hire, if you can find, which they're very hard to find, because a VP of sales position is very difficult, especially in a startup. You've got your traditional VP sales who works at a large organization, and it's really hard for them to transition into a company of five people.

Because that VP sales from day one is not just going to be selling a product that's created, they're going to be packaging the product, they're gonna be marketing the product, they're gonna be talking to the engineers, they're gonna understand the DNA of it and how to capture that value. And they're gonna build the strategy for how you go to market, not just for today, but over the next couple years. That's really, really hard to find in someone.

I was fortunate that I had that sales experience, so I was able to get the company to around $35,000, $40,000 in MRR. And at that point I just couldn't handle the workload anymore and there was just too much going on for me. And as a CEO, you're pulled in so many different directions.

And I was also fortunate to have known our VP of Sales, Morgan, for probably ten to fifteen years at that point, and we'd been talking for up to a year and a half before that about him coming on board, and we couldn't move any quicker. So it was great to get him on board. And he's really built up the company from there.

Yaron: That's awesome. So luckily you had that sales experience, so you knew, I mean, you could grow the company a little more and you knew what to look for in a VP. Most CEOs don't have that experience. They have no idea who to hire. They hire, let's say, an account executive right off the bat who fails because they don't have the right team around them.

What things did you look for? What did Morgan have that prove to you I can bring this guy in or this gal in as a VP of sales and know that they'll succeed?

Chad: I would say three things. I'm sure I could come up with a million different things, but number one would be experience. It's really hard to learn that role.

You can't bring in someone who's, quote unquote, I'm doing air quotes, quote unquote, business-y and have them become a salesperson for you, because understanding how to articulate value and talk to customers and ask for money is a skill that you learn. It's not something that's oftentimes just inherited or it's not just inside of someone.

There's skill there. And sales is a process. More than anything else, sales is a process.

But the hardest thing is marrying that process to the strategic, the creative aspect of a startup. Because there's no process in place initially and a VP sales is not going to be handed any type of process. They have to create the process for the startup and they have to be creative enough to be able to find the strategic process to grow a company from ten thousand dollars in MRR to a couple million dollars in MRR.

Okay, so there's three things. One would be experience. Two would be, I believe, a thirst for knowledge, because if you bring in someone who thinks that they know the way the world works, they're not gonna survive, because a startup is, you take a lot of hits and it's a constant learning process.

So a thirst for knowledge, understanding who your right advisors to put around you are, understanding other startups in your space and going to talk to them, someone who wants to learn about that or has built it multiple times in the past and can do it for you. It's like a playbook. And then number three would be data driven, understanding, well, data driven and process driven, because those are the most important things.

You're creating repeatable processes that can scale. You're understanding the data and what's driving customers to buy and how they buy more over time. And if you're not data-driven, you have no idea. It's like trying to find someplace without a map, right? You have no blueprint, no history.

So you have to create all that, but you have to be data-driven without prior data. And so those three things are really critical, I think, to finding that first sales hire.

Yaron: Yeah, I mean, those are definitely good points, and I've had a lot of time with Morgan, so I know exactly how he is and the kind of team that he's looking to put around him, which is great.

Building the Team Around the VP

So talking about the team that now goes around a VP of sales, especially at a B2B tech startup, right? If they don't know the technology or even technology in general, what's the kind of timeline that they're looking to fill in terms of heads and personnel to put around them so that they are successful in moving the company forward? Is there a timeline? Is there a right move or a wrong move? What have you learned during your time with that?

Chad: Yeah, I mean, because the VP of sales are your first strategic sales hire, in order for them to maintain that level of strategic, they're gonna have to bring on a team as quickly as possible, because they're gonna be not only your number one salesperson and they're gonna be selling as much as possible, but if the company continues to grow the way it should be, they're gonna have to hire a team as quickly as possible.

And vetting a team and bringing on reps, bringing on engineers, sales engineers and architects early on is critical because they're going to lose sight of being able to focus on what they need to focus on, and that's building the process, understanding the data, understanding the strategic level of what they're selling.

Because again, a startup, you can be a startup from zero to ten million, you can be a startup from zero to twenty, thirty million in revenue. You're constantly adjusting to market dynamics, especially in a market like ours that's not very well understood. It's very noisy. There's a lot of various competition and noise on understanding how to architect the modern app.

You're constantly on a strategic level with your VP of sales. So it's critical that they're able to think strategically. So long story short, bring in the team as quickly as possible and as quickly as you can afford it. And you gotta raise enough money to at least get out ahead of it.

Yaron: So it seems like at least in your space it's bringing a VP of sales first and then the team around them kind of starts with technical support. And then from technical support, it kind of grows into more of a typical or standard sales team where you have account executives, you have inbound sales, outbound sales, all that good stuff. So it seems like the first step is first technical people underneath the VP.

Chad: Yeah, I mean, again, that's like in my mind, that's my ideal playbook, is to bring in that strategic sales thinker early. And if you can find that person to be your best salesperson, but also become your VP of sales and grow, that's ultimately what you need because you need a sales champion next to your side.

Bringing in a rep early, someone who doesn't have that strategic level visibility and doesn't necessarily want to build a team, you definitely need to bring in salespeople, but you're gonna lack that feedback loop that you need from that person, the strategic level of participation. And when you need to grow a team, you're just gonna have to go find it anyways. And so yeah, that's the order that I would do things.

What He Would Do Differently

Yaron: Awesome. And so now again today you have a sales team of how many? Just off the top of your head.

Chad: Probably about six.

Yaron: Okay. Cool. So you built a sales team of six now, they're probably doing well moving you forward. Looking back from the start, from when you first started to now, what kind of things do you wish, you know what, looking back like that, we should have done this differently, or we should have done that differently? Anything come to mind off the top of your head?

Chad: Yeah. Well, I would have done it earlier. I think it's a scary hire. And again, I had known Morgan for over a decade before we started even talking in any formal capacity.

And even that was scary because it comes down to like giving up control. It comes down to trust. I mean, this is your baby. This is like, it's such a critical hire that you're so scared to make the wrong one, and rightfully so, because the wrong hire can be pretty, you know, you can lose a lot of time if you bring in the wrong VP sales. And it takes you six to eight months to figure out whether that person is right or wrong.

So it's scary, but I guess hindsight is 20/20. Now that I know he's been a phenomenal addition to the team, I would have did it earlier. I would have brought him in earlier so that we could have built out the strategic level thinking at the table earlier.

Other than that, I would say investing in marketing early, because one thing that we did well is build a product and we found value in that product and we started selling it. But then you have to always remember that the marketing activities that you do, they're the leading indicator.

So bringing leads to the top of the funnel and ensuring that the sales team can continue to grow beyond what's on the table now, because you grow that team really quickly and if you don't have the marketing support, then eventually they're hopefully going to have enough tailwind to the activity that they'll have enough leads coming in. But you always want them to be more busy than they can handle because that means you're scaling and growing as fast as you can.

But you know, we brought on a fantastic VP marketing about four months ago. And she's been great so far and the team started to get more and more enterprise logo leads and things are growing nicely now.

What's Paying Dividends Now

Yaron: Awesome. So, I mean, last piece, now you get to kind of brag a little bit. Looking back at the sales process, what were the two things that you did back then that, hey, it's paying dividends now, and I'm glad that that was put in place when it was?

Chad: Well, I mean, just sound like a broken record, bringing on the sales team and bringing on the great VP of sales.

Not being scared to get in front of your customers and not being scared to fly out and sit and shake hands, because your first hundred customers are going to be your best friend. They're going to be your comrade. They're going to be your beta tester. You're going to call them at night and say, "I've got this problem and I can't figure it out. I need your help understanding how we can get around it."

Seriously, your first hundred customers are gonna be like that to you, and you're gonna feel like they are everything to you when it comes to the business, of course.

And that's an important feeling, I think, for a founder and a CEO, because you want to cherish those first customers, because they're gonna feel it and they're gonna help you grow and evangelize the business.

And it's all about getting to some initial scale, and they're gonna help you get there and build that value. And so I guess for me personally, having that experience, because when I first started in sales, it was scary getting in front of customers.

Like, I remember my first sales calls. I was nervous. I was the guy that was way overdressed. I overdressed for a long time, actually.

Yaron: And now you're in a t-shirt and jeans.

Chad: And I would sit in the car and I would pump myself up and I would listen and I would try to say, "It's not that big a deal, it's not that big a deal," but at the end of the day, it's a big deal. And so having that experience over and over and over again, it was no problem for me to get in front of customers.

But even if you have a fear of it, as a CEO and a founder, you have to get over that fear and get in front of your customers, because sitting behind a wall or sitting behind a computer and trying to sell, it's not gonna work.

Yaron: So it seems like doing that, along with your due diligence and your VP of sales, is kind of the two pieces, like customers one, great VP of sales two, and that can kind of push your sales team forward.

Chad: Yep, yep. And obviously building something that people want to buy.

Yaron: Yeah, I mean, it always comes down to product.

Chad: Yeah. But even then though, there's plenty of valuable products out there that have no go-to-market. And there's plenty of crappy products that have a great go-to-market. So at the end of the day, it's really all about how you get to market.

And so build something that people want to buy and get in front of your customers and just figure out how you're gonna get to market as quickly as possible, and you can build a great business.

Yaron: That's great. I think our listeners are gonna have a lot of good information to take away from this talk. So thank you again, Chad, for joining us. Appreciate the time. And we look forward to having you again soon when Iron reaches its hundred millions in MRR.

Chad: I'll see you next year then. Thanks, Yaron.

Yaron: That's all we have time for today. Questions? Feedback? Contact me at roadtogrowth at heavybit.com. Thanks again to Heavybit for sponsoring our program.

To learn more about Heavybit's nine-month program for developer-facing startups, visit heavybit.com. And while you're there, make sure to check out their library. It's packed with great educational talks from developer company founders and industry leaders. Thanks again for joining us. Have a great week.

Subscribe to Heavybit Updates

You don’t have to build on your own. We help you stay ahead with the hottest resources, latest product updates, and top job opportunities from the community. Don’t miss out—subscribe now.