CEOs of Walkme, Zapier, Dialpad and Workable: How to Build Your First Management Team

In a 2017 panel moderated by Workable CEO Nikos Moratakis, the CEOs of WalkMe (Dan), Zapier (Wade), Dialpad (Craig), and RPX’s CBO Malan share practical insights on assembling a first senior management team in fast‑growing SaaS companies. They explore when to add senior hires, how to decide between "natural athletes" (founder‑type generalists) and subject‑matter experts, and the specific triggers (headcount, product‑market fit, enterprise sales) that signal a need for roles such as CFO, VP of Sales, VP of Marketing, and CTO. The conversation covers the challenges of integrating external executives into a tight‑knit founding team, the importance of clear KPIs and performance metrics, the role of trust and cultural fit, and the pros and cons of hiring via personal networks versus headhunters. Wade describes building a fully remote organization from day one, while Craig and Dan discuss the risk of monoculture versus the comfort of hiring familiar colleagues. The panel also touches on the painful reality of senior‑level mis‑hires, the need for a “dating” period before a formal offer, and the necessity of being willing to fire under‑performing executives quickly. Throughout, the speakers stress the iterative nature of building a management team: start with the function that complements the founder’s weakness, bring in experienced leaders at the right growth stage, set measurable expectations, and continuously evaluate cultural alignment.
Chapters
Please welcome CEO of Workable, Nikos Moratakis, to the stage.
Good evening. I'll introduce my co-panelists. This is Dan, CEO of WalkMe, and Wade, CEO of Zapier, and Malan, Chief Business Officer of RPX, and Craig from Dialpad. Thank you for joining us. Today's topic is dear to me, obviously. I can't imagine a chief executive not having lost some sleep over building a management team. I'm guessing it's probably the hardest problem to solve, hiring in general, let alone at this level. Um, I'd like to have an open discussion, so we won't go one by one, uh, but I already have a few good insights from the chat we had backstage. The way I understand this problem, briefly, just to set up a framework, is that there's a lot of interesting questions around it. One thing is the timing. When, what makes you feel that you need to level up your management, set up your first management team, however you want to call it. And is it a time? Is it a size of company that does it? Is it a particular event that triggers it? So I'd like to hear some personal stories about that. The second thing is like what you're looking for. Why are you doing this? Why, you know, why are you trying to bring it to the company? And the third and perhaps the most interesting is like how it fits with the dynamics, the existing dynamics in the of the company with existing people inside the company, the question of nurture versus outside hire, and how do people deal with this transition, which is a company transition, not just a personal transition. So, Malin, you're probably the most experienced of all of us here. I don't know about that, but— You've been telling me backstage, and I find this fascinating, this, this thing about athletes versus experts, and you know, what you expect to find when you hire executives. Can you tell us a little bit about that?
Sure. I think one of the challenges, right, is trying to determine when you're at a certain size of company whether you continue to hire what are natural athletes. And I think when you first start a company, Generally, you're hiring people who have whatever background. I mean, everyone here I think actually has a different background that they bring to the table, whether it's a programmer, whether it's in finance, whether it's in law. Do you know he used to be a lawyer? So did I, actually. And then, so the core man— I feel like the core team is generally a bunch of natural athletes, right? You come together because you have a common goal and a common vision. And then from there, obviously, you need to expand. So one of the examples I'll give you is what RPX does, because you probably have not heard of RPX. RPX reduces and insures against patent risk. And what that means is, as part of the business, we actually had to start an insurance company. An insurance company is, as you may know, a highly regulated business. So when we started the insurance business and we thought about developing the insurance business, we had a bunch of natural athletes, right? People who were super, super smart, who could research anything, but none of us knew anything at all about insurance. And so we learned it from the ground up. And so we were able to do things. We were even able to build your basic actuarial model with just some smart quant people who came from McKinsey who were part of my team. But at a certain level, what we realized is, especially in a highly regulated industry, you do need to bring in some adult supervision. And it's not to necessarily manage the entire team, but we needed someone who had experience in actually building an insurance business, who understood the regulations, who understood how we could do this thoughtfully, who had the relationships with things like the reinsurers. So I would say it depends on the stage of the company, but when you are starting to build out something, I think the natural athlete— I'll go with the natural athlete every single time. But there comes a stage, and you have to determine what is the right stage, where you need to bring someone who's actually a subject matter expert who has experience in the stage. And I know everyone has lots of thoughts about hiring that person too early, and how do you bring that person into the organization without making the original team feel like they've been topped.
Craig, you're 170 people now.
What's that?
170 people?
Yeah, 170 people now.
When was the time for you?
Yeah, it, um, well, the way putting the management team together was really around stages of the company. So at the beginning, we were, our, my vice presidents were engineering and product and a designer. And so making sure we have product-market fit was effectively number one. So build the product, get it into the market, start getting some feedback, and Then kind of as the evolution of the company, as we started moving up markets, started selling to enterprises, it was, "Okay, now we have to hire a VP marketing who has enterprise experience." We got this great guy from Zora, and then needed to hire a sales guy who had experience selling to the enterprise. We got the guy who ran enterprise sales at Rackspace. Then we had to hire a CFO to start counting the money and making sure that everything made sense and the margins made sense. We brought in a CFO from M-Blocks. But at each one of those stages, it really was, okay, now we gotta go to the next level. Now we gotta go to the next. I'd say if there's any, you know, so now it's been 5 years since we started. I would've hired the CFO a year earlier. Like I'd never, this is my third startup. I've never had a CFO before. I always resisted it. They always seemed expensive to me. And having a great CFO, and Mark Andreessen was on our board and he was telling us, You know, you need a CFO, you need a CFO. I resisted. I finally got one about 6 months ago, and it has made my life so much better. Like, he deals with everything that was very, very difficult. So if anything, I'd say do that a little sooner than you think.
And in your case, I understand your company also shifted slightly on the market, like from SMB to bigger customers. Does that bring you need— I mean, do you need to get different people for something like that?
Yeah, yeah. So our company, we do basically unified communications in the cloud. Dialpad effectively integrates with Google Apps or Office 365 to kind of give a cohesive product. And we also do UberConference. But UberConference started as this freemium kind of like funnel builder for later sales product, and so we didn't really have any enterprise DNA of how to support them, how to do POCs, how to implement, how to train, how to do change management, and so once we started getting enterprise customers, like Motorola was our first Dialpad customer, we realized that we were lacking enterprise skills of how to do those various things, which is why we we went and got this more mature staff. But getting them to have the right DNA and fit the culture of a company that had been around for 3 or 4 years was really important too.
Dan, 400 people in 5 years in a relatively flat organization.
Yeah.
How do you do that?
Yeah.
So we—
And how does this fit into the—
Yeah.
So we—
We started like in 2012, 400 people, different offices around the world. We don't have a CFO yet. And the organization is very flat. And to what you ask, I think that— I don't think there is a right time to hire a VP. There is no formula. I think that how we see it in WalkMe is First, we like that people will grow within the organization. As you said, yeah, people take it hard if suddenly you say, "Hey, this is your new EVP. You gonna do what he or she said. That's it." So when we do it, I look at it as build versus run. As the company grow, you need to build processes that only you know how it works in your company. There is no magician that comes from the outside and builds it for you. Of course, they can help you build it, but at the end, it's on you.
At this growth speed, though, do you always have the time to nurture an individual inside? Weren't there cases where you actually needed to bring experience from outside?
Yeah.
And how did that work?
Yeah, so I can't say that we didn't try. Actually, we had bad hires in the top levels that really hurt the company. I think it's the worst thing that can happen to a company to bring someone that high and then it's not working out. Because it's not just the damage that happens, it takes a long time to fix it. So—
So, Dan, can I ask a question? Yeah. So, you know, it's very painful, right, when a very expensive senior hire senior hire doesn't work out. So why didn't that senior hire work out?
Yeah, I think that a lot of senior hires, you bring them from a big company, Salesforce or Oracle or whatever company that you hire from. A lot of time in their mindset they want to do copy paste from what they did in the previous company. That worked for me at company X is going to work like that in WalkMe. No, WalkMe is completely different. You need to understand the basics of WalkMe, the culture of WalkMe, how we do things in WalkMe, and only then I think that you can build or run it in a very sufficient way. And if someone is trying to force it, it's just not working, and it's exploding in our face at the end.
I'm curious, and I know you're the moderator, but I'm curious. How can you tell? There are certain individuals who can come from a large company and go to a small company. Some of the people up here came from large companies and succeeded in small companies. I'd be curious, including what our moderator thinks, about how do you spot when that will work and be successful and when it will be someone who basically will just copy and paste? 'Cause I'm sure you did a lot of diligence in trying to figure out whether that person would succeed. [Speaker] Yeah, for sure.
I think setting the expectation with any high-up management, it's key. We have very clear KPIs that we know how we want to— what we want to achieve, what we want to see. And if they're not meeting those KPIs, they're not doing their job well. That's the only way for me to know if someone is doing their job. If they want to do something— and by the way, I strongly believe that if I'm bringing a manager, to the management, or even not to the management, they need to teach me what to do. I don't need to tell them what to do. And if— and the only thing that I can manage them is their KPI. So they get full freedom to do whatever they want, right? They can do it their own style, but there is a KPI. X amount of revenue, X amount of churn, X amount of growth in marketing, etc. That's it.
And I don't think that copy-paste is always a bad thing. Sometimes it's exactly what you want. But you have to be very deliberate. The way I think about it, there's cases where you actually want someone with experience who's done something before and they're gonna copy-paste it. In the good sense, like go and build the kind of organization and process that made them successful in the past. But you need to hire that kind of person when you're willing to make a big investment and a big change in that area. If you bring that person just to manage whatever you had and a little budget, you're just not getting any value. They're not gonna bring you your best people, they're not gonna do the things that you expect them to transform your organization. There's cases where you don't want the copy-paste guy, you want the builder. But, you know, there's no rule for that.
Yeah, I do wanna say that I don't think that it can't work. Of course it can, 100%. It didn't work for us doesn't mean that it doesn't work. I do think that, and from the insurance part, there is a risk that now as a growing company, and we're growing like very, very fast, not just revenue, headcount too. We are at the point that we can take that risk right now. Maybe later on we can take that risk and then it will make sense when when things will be— the processes will be in place. And then that's the time to bring more grown-ups to run the things. And this is the difference between build versus run. Now we're building a lot of stuff. And then when we feel that it's working, it's a machine, we can bring—
Yeah. And actually, we had some grown-ups in the company. But we started the company in 2008 and then took it public in 2011. And actually, a lot of those grown-ups were hired at that point where we were about to go public or public. So back to your question before is I actually generally go with a natural athlete versus the subject matter expert, except when you're at the stage where you need it. I don't know, Wade?
Yeah, I think the best folks are able to bring that experience to the table, but they are also able to mold themselves to the culture of the company as well, right? So when you're looking and hiring, you talk to them and have those honest discussions about this is what we believe as a company, this is how we operate. Can you, like, does that fit with how you as an expert in this field can operate too? So they can come in and maybe copy paste a little bit, but they can do it in a way that fits within your organization and then help you scale it and bring some of that expertise to the table.
[Speaker] We talked backstage and I think Wade didn't introduce the company, but they don't have an office. How do you do it?
Yeah, so we're 70 people without an office, 100% remote. And for us, it was pretty natural because we started as a side project. And so the 3 founders were working at Zapier, you know, coffee shops, at home, whenever we could find the time. And then when we started hiring, we'd already built this set of organization and how we work and things like that that were well documented. We knew to work through things like chat or the project management tool and stuff like that. And the people we knew to hire at the time were folks that didn't live in the same city as us. So we hired a colleague of mine from college who was in Chicago. I was in the Bay Area. Another founder was in Missouri. And so by de facto, we just became a remote company and started building that way. But because we had that organization there in place, it wasn't like we needed to be right next to of each other to figure a lot of these things out.
I'm really curious about the remote organization in the sense that typically when you bring the adult and experienced people, I imagine that they would be the least accustomed or confident that they can operate in an environment. Have you felt this resistance? And have you had people adapt to that?
Yeah, certainly. About a year ago, we started looking for a CFO as well. And I echo Craig's sentiment that CFO is like one of the most valuable things I've done in the last year. And we started our search, and we didn't restrict it to geography. I didn't necessarily need someone who was in the Bay Area, which is where we were at, and started the search. And we found someone in Atlanta, the former CFO at Mailchimp. And you know, first she was like, I don't know. You know, she's— Mailchimp has a weird and quirky culture. So she's like, gets that Zapier's weird and quirky culture. Quirky too, not so sure about the remote thing. And so we just started collaborating a little bit on the side so she could kind of get a feel for it. And then she's like, this is actually pretty effective. She found that she likes working, you know, having her own office that she can set up at home. You know, she's able to concentrate a little bit better with not a lot of distractions going on. And remote enabled that for her. And so for her, it was like, actually, this is pretty good, right? Just having a chance to give it a try. And so I think that's a lot of it is you want to find folks. If folks are totally against it, then they're clearly not going to work out. But folks that are like, I think this could work, like it's probably going to work pretty well for them.
I want to go into the tough topic, which is, you know, hiring executives means changing the organization of the hiring above people or topping people, maybe blocking their career path. Or at least they can perceive it like that. How do you deal with that? And who wants to share some war scars on this?
I don't know if it's necessarily war scars, but it's, you know, we had never, everyone in our company effectively was, this is our, again, our third startup, so our first 30 or some odd people had all worked together before, so had this understanding of how we worked. So when we started bringing in We weren't until we were about 100 people when we had a first headhunter and brought in a VP of sales and a VP of marketing. But I think, I mean, and again, just as I had never had a CFO before, I had never used a headhunter before. I always thought they were ridiculously expensive and I can find great talent through my investors. But these guys were great. And the slate of folks that you were able to see and the quality in their background and doing the reference checks and really just spending time with them before they got there. Like never really had any of that like jealousy or kind of broken glass of bringing a guy in that there's gonna be this big transition. It's always worked pretty well. And I think that that has to do with like any of these companies that have a strong culture to begin with. It's hard to come in even if you're a VP level, even if you're a CFO and just be a jerk and everyone's going to let you get away with it. It's just not going to happen. So although the headhunters are relatively expensive, I find that a lesson well worth it. And it's been a really nice fit.
I can say about WalkMe, we just acquired a couple of companies. And the idea is that we really believe that small groups work better. And the CEOs of the acquired company become manager of a unit, and suddenly someone from the outside comes and manage all the people that were with us for years. So I do think that it's not easy. There need to be a lot of communication with the employees. We like to solve a lot of things by just going out and have some drinks. And currently it's going very well. I can update you next year if the integration was smoothly, but I think they respect under-entrepreneurs that build a company and were successful themselves coming with that drive and now suddenly leading that unit. And they're looking at them and they're like, yeah, it makes sense. At least at our situation.
What about functions? I mean, I know you mentioned the CFO, and I agree with that. It was the first senior, truly senior hire that we made, and should have done it earlier. But usually when you start growing and you think you need to deck out a management team, what are the key roles do you want to go with first in a software company like ours, in a SaaS company? Where do you start? Where would you start if you did it again?
Yeah, we started with sales. As a B2B enterprise company, sales was our first key. I'm saying sales because I was the first developer in the company, so we got the development side covered. But if I wasn't at a programming background, probably CTO was a good idea. But for us, it was sales, definitely sales and marketing.
The same for everyone?
Yeah, I think you need to get what complements yourself too, right? So for us, like, my founder is way more technical. It makes sense that that would be like the role that comes in as the CTO. And you look at where you're weak, and that's where you need to hire first. I think it's pretty simple.
What was your first?
CFO. Basically was the one thing I was totally clueless about.
How early did you hire a CFO?
Not very early, at 50 people. Yeah, I don't know if that's early or not.
It was about the same as us.
What your CFO does, like what is responsibility? It's just finance or it's more strategic, like how you price, how you—
A good CFO quickly solves the finance problem. But then starts owning some strategic thinking about the business model of the company and what is efficient and how we should grow and how you should budget.
And how it works with the VP of Sales, for example?
Yes.
How it's working together?
They usually work together on comp plans and by defining whether it's efficient performance. They work with the CEO to figure out the financing strategy. You know, when you grow, you start— there comes a point where your financing cannot be, "Oh, it's a Series A." Series B, just raise some more equity. There's more ways to think about the cash flow and the financing of the company. Somebody who knows how to do this opens up your eyes, at least mine, because I was clueless for this.
Yeah, for me it was— it made it a lot easier to more confidently spend money. So, you know, she can go to our, the various VPs we have and say, hey, you know, this is a problem you're having, here's how you can spend money to solve these problems. Whereas before it was like, "Well, do we have the money for that or am I spending too much money here?" There's just some uncertainty there. A great CFO will come in and just renew all.
I know, Dan, you said you have a VP of Finance. You don't have a CFO. Everyone else has a CFO. We're a public company. We have a CFO. I'm curious what the difference is between a VP of Finance in your mind, and you didn't have a CFO in your other companies, versus a CFO.
Yeah, we had VP finance basically to make sure the books and the finance were rock solid, audit went well, money was well spent, the plan made sense. CFO in our case really was like operational cadence. What is the, what are our enterprise deal reviews? What are the reports we're generating? What is rep productivity? Rather than prior to having a CFO, we had a lot of just best efforts, tons of athletes, you know, like go out and kick ass as much as we can. And then to have a CFO really come in and drive metrics around that and say, okay, hey, here's where we are, here's, you know, here's our effective ramp period for an effective sales rep. If we raise and hire this many more, you know, what's the amount of leads? Is it gonna be enough to feed these guys? And you know, they'll be productive at this stage and then it's gonna be like this. And having really that discipline, to me, was really the difference. And, you know, just the credibility of having done it before and gone through and seen this motion of how do you scale an organization from, you know, $20 to $200 million. That's a really nice experience that, you know, frankly, a lot of people don't have.
For me, the VP Finance makes sure you don't go to jail. You don't run out of money. The CFO makes sure You invest your money cleverly. It's a slightly different level of financial management. They could as well. Actually, yeah, the CFO's role is also to make sure that, you know, they control the CEO. It's a very important function. You check on the CEO as well.
And one of the things that everyone touched upon, right, was was the right timing for hiring a management team or a senior hire. So one thing that I've had before is I've, like many of us, we meet with a lot of companies, we meet with a lot of founders, and what's interesting is how do you hire that first senior hire? Because I've met with people where I know them sort of casually and suddenly will say, the person will say, "Well, do you wanna come work here?" And I have to say that kind of is a little off-putting. And I actually think that there's a cadence to how do you bring in these super senior hires where the timing has to be right on both sides, right? It's not just about suddenly you're having coffee and says, "Do you wanna work here?" It's sort of awkward, I have to say, and I don't really see that person much anymore. But good CFOs are hard to find, good VPs of sales are hard to find. And I would actually love to hear your thoughts on that.
So it's kind of a dating period. So it's not immediately. Our EVP of sales, which is amazing, he actually started as a consultant. Like, he come and helped us. And like, that you can do better, that you can do better. And we build a relationship. And only few months later, we're like, OK, come work here. And like, all the reps already knew him. And everybody already knew him. And it was like— makes sense. That was our first hire. It was like, so makes sense. Took us almost 7 months to complete that hire. And we have the results, so it's great.
But it seems like when you hire that way, it's less jarring of an issue of the issue of topping, right? Because the team's worked with that person already. Because it's a really serious issue, right, when you hire someone who's coming in on top of the team who has been working really hard. And what I find is a lot of those natural athletes, are so good at so many things that they do think that they can do everything, right? But some of those natural athletes aren't great at managing, and it's hard for them to hear that they aren't great at managing. So doing it that way is always a little easier.
Yeah.
I don't know.
Yeah, that's been our approach too. You know, we brought in our CFO. I sent a ton of emails just to learn from different people, right? I just, hey, I want to learn more about how you think about this role, how it works for your company. So I could start to form my own opinions. And some of those started to develop into deeper relationships. And then with Jenny, our CFO, is like we actually ended up starting to work on little things here and there. And it's like over some time is like, this is going pretty well. Would you consider doing this full time with us? And, you know, that's how it worked out. So it wasn't just like, oh my God, you're the first CFO I've met. You know, come work.
You're great.
Can you come?
I need you.
And by the way, you won't get an office. You have to work from home.
Yeah.
One of the things that I found that was really helpful because, you know, hiring an enterprise VP sales or an enterprise marketing person or even a CFO, if you haven't done it before, I really did have no idea what to look for. Like, what are the traits? And that was one of the better things that our VCs helped us with. They're like, hey, don't hire any of these guys 'cause they're in other portfolio companies, but we're gonna set you up for lunches or meetings with, with 3 great CFOs, guys that we think are fantastic, or 3 great marketing guys, or 3 great sales guys. And after you spend time with them, at least you have a better understanding of what their commonalities are, what you're looking for in your actual candidate, which was entirely different from how I always used to hire. And it's much more effective that way. So meeting or talking to as many people who are great at it before you go out and hiring, I thought was—
How did you end up finding Yours?
A couple headhunters.
Okay.
Yeah, actually, that has always been my biggest problem is that for the functions you need the most, you don't know what great looks like. And actually, that brings me to another point. I know one of the things I always have a bias for is I usually try to turn to my own network and the close network, the people I work with. Very often, I'm tempted to hire someone who's I have not done this function before, but I have worked with before, I know they're a star. How many of you have hired people like that?
Yeah, for sure.
So, I know—
And is it a good thing or a bad thing? I just want to know for myself.
I can say that, and there is probably some Walk Me folks in the audience, a lot of my friends working in the company, people that were with me, I'm from Israel, that were with me in the army, We hire from the same unit, we know exactly what we want, people that we know for years, and it's amazing. Even if we bring someone—
Isn't there a risk there to create a monoculture? To bring the people that were successful with you in your previous company and build your previous company essentially, or part of it. Isn't it— When I've hired people I never knew before and came from a different culture, For me, it was great because they did some things I would never have imagined to ask for. So I know you have something there.
I'd go the opposite on that. Being able to have a level of familiarity and comfort in knowing that you guys have shared values and shared missions and you don't have to worry about someone doing the wrong thing, it really helps you just execute more quickly. And yeah, I know what to expect from them, but they've been awesome, so I know. To expect awesomeness, but it is a, it's a real comfort to have, you know, again, your first 20 to 30 employees that have all spent at least 3 or 4 or 5 years together working at other jobs, and then your next, kind of like next 20 hires are usually like one degree of separation from this kind of core group that really kind of gives you this unfair advantage of starting this startup that is a very, you know, tense, nervous, uncertain time with a group that feels very comfortable together. And I think that's been awesome. I mean, that's kind of a secret to the success.
You're suggesting that familiarity— I think it also has to do with trust. I mean, like, you know, you're going to cede control over big parts of your business. How about that? What advice do you have for this?
Yeah, trust is probably the most important piece, right? If you can't trust your management team, then you're always gonna be second-guessing them, right? You're always gonna be double-checking everything that they do, and it's just gonna drive you nuts. So you have to be able to build that trust with them and have that trust with them. And if you don't, like, it's just not gonna work out.
How do you do that?
Well, I mean, you get to know them, right? Like, how do you build trust with anyone, right? Like, you spend time with them, you get to see how they work. If they do, things well, then you're gonna build trust with them. If you take care of them well, they're gonna trust you.
So for us, even today, and again, we're at a different stage of company than some of you, I, as I'm sitting here and I hadn't thought about it before, not a single one of our senior management came from a headhunter or someone we didn't know. I just brought in two SVPs in the company and I've been, you know, recruiting them, talking to them for 3 years, but the timing had to be right on both sides. Because I agree that, especially in the early days, you have to be so lockstep in your mission and going forward. But it becomes— you also want to make sure that you bring in people who have experienced things different than what was in your original company, or else you're just going to do things the same way over and over again. That being said, we actually haven't brought people in that we don't know, but the folks on the management team have different enough networks that we've all brought in people. Like, I come from a big company background and others have never been in a big company, and so I think that that has actually been a key to why it's successful. And so even though we haven't gone, you know, the headhunter route, you're not bringing in a bunch of homogeneous individuals who are leading a company, because I think especially as you get a little bit more mature, that can be dangerous.
How do you onboard and integrate an executive that's coming in?
I think, and I will continue your point, it's all about KPIs. And when someone new join, and it's about trust as well, we need to know what the KPI is. And I think this is why this conference is awesome. It wasn't been there 10 years ago. What is SaaS metrics? What is good? KSP, how you do it? I think now it's more clear and there are benchmarks, so when someone new comes, you know what to expect from them. And then it's easier to integrate them because, okay, this is what I'm expecting in the first 6 months. That's the KPI. That's where we want to be. And when that is clear, I think it's very easy to work with a new hire. Because sometimes they have their own ideas or their own way, But as long as we are agreeing on the same KPI and that KPI needs to be achieved, then at least my work with my management team is super easy.
I understand that. In some cases it works. In some cases it's very simple because you know really what you want to achieve. Or you have an established structure inside the company, so you know the goals and basically hand someone the keys. And tell them to bring me that goal. But it's not always like that. For example, in my experience, when I hired the CFO, I'm not sure I really knew what success looked like, or the things that I had in my mind, the things that I had in plan and I asked for, were a fraction of what we ended up having to do over there. Always my personal struggle is like, you know, how much do you ask them to make the plan and define success? And in fact, I tend to think that the really successful executives are the ones who can actually do that part.
To exceed what you expect.
Not just to exceed, to actually define what success in this function should be like for the particular company. And it's really difficult for someone who doesn't know the company, even if you've been courting them for years.
For me, it will be extremely difficult to bring someone if I don't know what their KPI is. I would just not make the hire. At least for me.
Any thoughts on that?
Yeah, I mean, I'd say in a lot of these senior execs that you bring in later on, obviously they're coming in because they're filling a gap that you don't have. And so it's Had I not gone through the experience of getting to know what I was looking for beforehand or getting to know what a good set of outputs from any of these hires would be, you'd be a little bit lost and you'd be a little bit dependent on hoping you got a lucky hire or a good hire, but you wouldn't know until later. So really kind of understanding what success looks like, what those KPIs would be, And then checking references like crazy, and then dropping the guy in and giving them the freedom to do it. And I think that's where we're on. That's good.
I see that we're nearly done. Anyone want to have any final comments before the time runs out?
I do want to say, at least for the people here that are building their companies, as someone that got burned— like, the title here is How to Build or How to Hire Your Management Team. You need to know how to fire as well. The minute it's not working, just cut it, believe in yourself, and just— you know what's the best for your company. No one else does.
That's cheerful, no? Thank you very much. Thank you for attending. Thank you all.
More from Jason

Why Your Next Hire Should Report to an AI, Tragedy Apps, and Too Many AI SDRs? | The Agents #004

Our Agents Drove Our Salesforce Bill Up 80%, Marketo Hates Agents, and We Stealth-Churned Off Notion

Managing 20+ AI Agents: Lazy Agents, Our $500K AI Bill, Stealth Churn & the Death of 60% Solutions







