Inside Tilt: Navigating AI & Role Clarity for Scale | Taylor McLemore (Podcast 576)

Taylor McLemore, CEO and COO of Tilt, discusses how his leave-of-absence platform handles up to 20 hours of admin work per leave across federal, state, and city regulations. He outlines Tilt's AI framework (explainable, auditable, secure, compliant) and a role-clarity system called RRNE that aligns leadership and teams.
Chapters
The hit from AI. Fortunately for us, AGI hasn't arrived yet. The robots haven't taken over. And if you go ask ChatGPT some really complex leave questions in terms of compliance, it's going to get it wrong.
Mm.
It's too situational. It's too context-dependent, like complex legal analysis. And I'm not saying never. I mean, we're building the stuff that will actually give you the right answers in AI. But for us, it's more of an opportunity than a risk.
Today on Second in Command, I'm joined by Taylor McLemore, CEO of Tilt, a company reimagining employee leave through empathy, technology, and human-centered design. Taylor is a venture builder, scale operator, and community connector whose work spans Techstars, Stand Together, Able, and multiple national boards focused on workforce, veterans, and entrepreneurship. He's also the founder of the Human Potential Summit and has helped launch and grow initiatives that empower builders, leaders, and communities all around the world. In this conversation, we explore the 4 principles Taylor and his team use to evaluate new AI tools to implement into their company. We also talk about the single document that creates clarity, performance, and alignment across his organization, and why the best operators give their teams creative space. Face help define how they are winning in their role. If you're a COO, integrator, or operational leader navigating scale, technology, and human potential, this episode is for you. Let's dive in. We are live with Taylor. Welcome to the show.
Thank you for having me. Excited to be here.
Of course. Yeah, this, this episode's been booked for quite some time, so I've been looking forward to it and talking about all of the things that you're up to in an industry I'm not actually super familiar with on, like, I've helped build a recruiting company, but in terms of like the more, uh, platform human resources side, that is a totally different world for me. So I'm excited to hear about what you guys are building and what you're up to. So let's start there. Tell us a little bit about Tilt. What do you do and who do you serve?
Absolutely. So At Tilt, we provide a platform and service for leave of absence management, which sometimes I think operators and others, you know, they're like, I know what that is, but most likely my HR team manages it. So it's all forms of leave. And I like to describe leave as the intersection of life and work. So whether that is one of your employees is welcoming a child into their family, so it can be the best of times, it can also be the saddest of times. Maybe they lost a loved one and they're on bereavement leave. It's all of those things where life and work intersect. And then we as employers and company leaders need to figure out how do we manage that, right? And there's a bunch of regulatory pieces. There's a bunch of laws that say what companies can and can't do. Some of that's federal, some of it's state, some of it's even city level. And then there's the choices you make as a company, like what is our leave policy? What is our parental leave? Those sorts of questions. And so it is a area that I deeply believe is underappreciated in a few ways. One, the scope of it. HR professionals usually spend 20 hours managing a single leave. So it's a big chunk of time. Yeah.
Wait, hold on. Just to make sure I heard that correctly, you said an HR employee could spend up to 20 hours just working on one leave?
You got it. So let's pick on an example. So remind me, you're based in California, correct?
No, I'm in Texas, but California sounds cool.
Okay. I apologize. I— so Texas is interesting because we can use Texas as an example. I love Texas. They— so if you are running a company in Texas, you know, and your HR team receives notice, hey, someone on the team is— and let's use traditional sort of giving birth as version of parental leave, but there's lots of versions of welcoming child into families. Adoption otherwise. But let's say someone's planning on giving birth and they're a woman giving birth. So there is a medical side to this. There is, you know, not only giving birth, but then recovering as a human after you, you know, went through the miracle of life, all these sorts of things. And your HR team is sitting there and you're like, I have to plan a bunch of stuff. If we're big enough, I have to consider if we need to comply with the federal laws around that. There's multiple ones. I won't bore you with all of them. For Texas, there's no state required family leave law. There's a voluntary one. So there's actually a thing you could opt into to utilize at the state level. That's a choice to be made. And so your HR team is making all these decisions off of just your employee saying, hey, by the way, I'm going to have a kid. Then you have to coordinate with the manager because that, like, the experience of that employee going on leave is going to be highly impacted by how their manager handles it. Some managers have a lot of experience with it. Most have very little and struggle. Honestly, and I'll keep on picking on this example of the thing that keeps our population growing, which is babies. You know, the number of times that managers go, I don't know how to talk about pregnancy with one of my employees. Like, that's a thing, right? Like, getting that right and not screwing that up, not easy. Once again, this is all pre-leave. Then you actually get to the moment of leave, and then that manager needs to figure out where's the work that that person was doing going while they're gone? So then you have a bunch of team impact, right?
Totally.
And then hopefully someday that person returns to work because you thought that they did amazing work and that they had such an amazing experience, even though their life has changed significantly, that their reentry goes well and their team welcomes them back with open arms and all these things go swimmingly and they continue to work at your company for years to come. Or it doesn't go well and you probably lose that person.
That explanation makes a lot more sense now. I guess when I think of someone leaving, I think of, yeah, the manager replacing that person and making sure that there is like temporary help or whatever. I've actually never really had that on any of my teams now that I think about it. People usually just, I, I had one person and she just ended up leaving the company. She's like, I'm just gonna go do this thing over here. But yeah, I guess for bigger companies. The impact on that would be quite substantial when you think about all the, the legal aspect, which I guess brings me to my next question. Are most of your clients more on the corporate side?
Yeah, well, uh, they're, uh, when you say corporate, I interpret that as like for-profit and bigger. Is that what you mean? Yeah, we do, uh, but we, we have a variety, uh, everything from, you know, sort of for-profit corporations anywhere from 100 employees to, uh, thousands of employees. Employees. We serve all of that, uh, sort of span, but it's not just for-profit. We also have school systems that we support. We also work with healthcare providers. A lot of healthcare entities are nonprofit versus for-profit, so we're pretty agnostic as it relates to, you know, whether they're for-profit or not. It's just, are they an employer and do they have responsibilities that they need to manage from a regulatory perspective? And then the thing that really gets us excited is how How do we help them see it as an opportunity? Because there's no question it's administrative overhead, all the forms, the process that we just described. But leave handled well is a massive opportunity to create a loyal employee that you retain for a long time, continues to be highly productive. Uh, you know, it's, uh, all— there are tons of different forms of leave, from military leave to medical leave to, you know, the list is 50-plus. But I'll continue to pick on one of the more common forms, which is parental leave and a special birthgiving. Um, and it's, uh, you know, imagine that that goes really well, that, that person likely will tell their friends, like, my company treated me extremely well, because not everyone gets that, which is so unfortunate. Um, and so it's this opportunity. And like, one of the things that we hold very true, there's an ROI to doing leave well. Now, it's hard to measure. Um, most things in HR world and HR tech are hard to measure, but, you know, we can draw direct lines to employee retention, productivity. And then the other thing is that when people return from leave that their career path continues, that leave isn't not just this gap where you lose people, but also when they came back, if they were a shining star before, were you able to set them back up on a path? And it's not that they have to maintain the same trajectory, but is it a meaningful one between the employer and the employee?
Awesome. Yeah. What about this mission? Because it— I can hear when you're talking about it there's some passion there. You get excited. What about this mission pulled you in?
Yeah, so, uh, the, the first is that, uh, and I, I don't believe I'm unique in this, I've had both very positive leave experiences personally and negative ones. So, uh, you know, to just give a quick thumbnail and color that in, on the positive side, uh, I had a family member who was sick and went into the ICU when I was, had only been at a company for less than 2 months. And I called my manager that I was reporting to the CEO, and I, I called, um, Mike, and I was like, what's going on? I, I don't, I, I don't even know what, which end's up. Like, our world's upside down. And his response was, go take care of what you got to take care of. Call me when, when you know what's going on. Like, we got you. And like, for being a brand new employee, and did I, like, had I signed the employee handbook? Of course I had. We, we, HR makes all of us do that, right? Um, did I have any idea what our leave policy was? I had no idea, but they showed up, um, in a deeply empathetic way. And so from go, I was so loyal because I was like, these people treated me with such respect and dignity from day one. Um, and that, and that was my longest career stop I've ever had. Um, so very positive. And then I've had, uh, you know, negative experiences, which I, you know, I don't know if they're that valuable to dwell on, but You know, it's like one time, you know, we had a, a medical, a, a different medical situation and I told my manager and she's like, yeah, I, I'm sure you'll figure it out. And it's like, how night and day different is that? And she's not a bad person. I still have a great relationship with her even though we don't work together anymore. She's the example of the manager who had no training and didn't know what to do. Mm-hmm.
Right.
So I've been on both sides of that and I just believe it's this really, it's a cool business model because we have, this compliance regulatory piece where people gotta kind of solve this problem, which is a nice thing when you're selling. And we are deep believers that there's so much upside with how you manage leave well.
Hmm. What was the journey like for you in finding this position? Did you know people at the company or did you just apply off of Indeed? Tell me about that process.
Yeah, I, it's a fun story. I, um, I started, uh, my relationship with Tilt back when I was a venture investor. So the quick history, like if you want to take the, you know, 30,000-foot view of my, of my career, it's started out in banking consulting, got the heck out of there to go be an entrepreneur, built some, was spent time as a builder, as a founder and CEO. And then I spent a season as a, as an early-stage venture investor. I was a managing director at Techstars and Tilt was actually my first venture investment ever. At Techstars. So I was fortunate, got to meet, you know, the founder and get to know her and the team. And this is, you know, early, early pre-seed days. So it's so incredible how they've matured and evolved the company. And then, as you know, I was embracing a new season. I was excited to get back into builder mode versus the venture investor mode. And they were at this fun point of of doing the hard thing of scaling. And so that, that's when the, you know, I went from, uh, being investor to being board observer to being COO.
All right. And you mentioned the owner, so you already had a relationship with her. Is she still running the business? Is that who you're working with?
Yeah, exactly. Yeah. Jen Henderson is the founder and CEO.
Amazing. Well, we'll talk a little bit later about y'all's relationship a little bit more in depth, but Tell us first, what does your role look like now? Because you've been with the company for, I believe, 6 years.
So in different capacities. I've been in the COO role for coming up on about 2 years now. So I don't get to claim that I'm new anymore, but I also haven't been around forever. And so the, the periods before that were in those other capacities of being an investor and serving as a board observer.
Okay, gotcha. What does your role look like now, day to day?
Yeah, it's, it's been an evolving portfolio is how I would say it, with traditional CEO responsibilities at the center of it. So responsibilities for operations, finance, HR, those sorts of elements. Now we're, we're a growth stage company. We raised a Series B back in 2024. Um, so we're not, uh, we don't have overly developed like corp dev activities or things of that nature, but we, we do, we're starting to get into more and more of that. So that's part of my portfolio as well. Um, and then there's a variety of the just sort of dynamic coverage of most important things in the business, um, that I've spent different time working on. You know, a big part of what we do is the complexity of leave means that software hasn't solved all of it. There's still a human service element of how do we have leave specialists that engage when there's questions that don't fit in the automatic flows of step 1, 2, 3, and you're done, but rather, hey, I've got kind of a special leave situation. We have people that are available to help. And so I've spent a lot of time working with, you know, other, other leaders and parts of the business to figure out how do we scale and optimize that.
Mm-hmm.
Uh, so I, I've had the opportunity to, uh, move around and focus on different parts of the business, mostly trying to enable, um, how do we understand what the sort of the future of that part of the business is for scale while staying true to our mission. Um, and then most of the time, like, I, like the, I'm not the long-term answer, so I, I really embrace, um, trying to cover the areas that need coverage while we then identify what does an amazing leader for this look like as we evolve and grow the business.
I was listening to a podcast this morning about, I guess, just the major hit that a lot of the SaaS companies are experiencing with AI. How have you guys seen AI impacting industry.
Yeah, it's exciting. I mean, one of the things that we did in 2025 that I'm really proud of, and our marketing team led by Brandon Salisbury, our CMO, did a superb job. We went out and said, and really planted the flag that Tilt is the AI leader in the leave HR tech space. There is lots of AI across HR tech. I would also say that a lot of it is driven by sort of like the big platforms trying to compete on how many AI features they have. And everyone's still— and this is not just true of HR tech— everyone's still trying to prove impact in outcomes of that versus just feature count. That said, because we are in a very compliant, compliance-driven portion of HR tech, there's a fair amount of hesitation from people to say like, okay, like, wait, you're doing AI? What, what does that mean? And so, uh, AI is everywhere. Um, we are trying to pull it forward in appropriate ways. Um, and that was really a big push in '25 was to say, what does responsible, compliant AI look like within leave management? And so You— I think you frame the question as the hit from AI. Fortunately for us, AGI hasn't arrived yet. The robots haven't taken over. And if you go ask ChatGPT some really complex leave questions in terms of compliance, it's going to get it wrong.
Hmm.
It's too situational. It's too context dependent with like complex legal analysis. And I'm not saying never. I mean, we're building the stuff that will actually give you the right answers in AI. But for us, it's more of an opportunity than a risk.
Hmm. How do you make sure that— because one of the things that they mentioned in this podcast episode was how many SaaS platforms are trying not to get left behind. So they're all trying to implement, you know, these models into their team. How do you make sure that you bring in the pieces, like you said, that are actually appropriate and helpful but still move at speed and not get like left behind? Because it sounds like you guys have done that if you are on the leading edge. So how have you maintained that with your team, like moving quickly but also making sure that you're bringing in the right things?
Yeah, I'm a big believer that identifying your first principles is one of the best ways to create acceleration in a business. So we spent time identifying what are our first principles when it comes to the use of AI in our domain. Uh, so we have 4 first principles, uh, that we hold up, whether it's us building AI into our product or, uh, for tools that we might, you can, you know, no company can build everything. That's the, the modern nature of a technology-driven business. So the, the 4 principles are, first of all, that is explainable AI. When I say do this thing, it's not a black box that it, you know, there is explainability there. The second is that it's auditable. So as much as everyone's worried about, are you using my data for training and those sorts of things, you need to parse those out that if you are using AI to deliver an outcome for a customer, you have to be using AI in a way where you can say, why did it do that? What did it do? So that's the second part. Why did it do it? Is it explainable? What did it do? Is auditable. The next is secure. HR is full of PII, personal identifiable information. Certain spaces get into HIPAA territory, like it, you know, it gets, you know, it gets into compliance acronym soup quickly. So you can't just be dumping PII into AI without knowing where it's going to go. What is your data sovereignty approach? So on and so forth. And so we really focus on security as that. And then, you know, the piece that I'll really highlight there is that we built an AI governance council to help wade through this and apply those first principles. So that was like a big part of it. And then the last— so the fourth pillar is compliance, which for us is highly specific, which is there's Department of Labor regulations on what you're allowed and not allowed to do with AI. There's, there's not really that much federal stuff, honestly. You know, there's lots of talk and we'll see how that evolves. The hard part, but also business security for us, is there's a bunch of state-level stuff emerging. There's California, Colorado, Utah have all shipped AI laws. Which no one's actually totally like— they haven't been tested in the courts very extensively. So no one— like, there's a bunch of people with hypotheses about what they mean. So, you know, to do this well, you have to bring all of that forward. And I know that's a lot of words, but if you don't have opinions on all of that, you're going to spend a lot of time just sort of like testing, iterating, building, and be like, oh, but that's not auditable. So like our customers would never be okay with that. Or That's really powerful, but it ain't secure. Do they have, you know, good old COO questions? Do they have their SOC 2, things like that? So what we did to speed up in that was establish that first principles approach.
What is the council that you mentioned?
Yeah, it's a group of the executives that represent the different functional pieces. So for us, it's our head of security, it's our CTO, it's our head of leave compliance, who's our legal expert on leave law. It's our, you know, general counsel and it's myself. And so that way, you know, and we've really tried to build a clear process, whether it's an internal, like we're building this AI feature or it's we're considering an AI tool, we've established there's service level agreements internally. If someone brings up, can I use this tool, we owe them a response in under 5 business days because we can't be slowing down AI adoption by just saying there's a bunch of red tape to push through. So it's this constant balance of what is enough governance for safety and alignment, but also efficiency so that people can move quickly.
That makes sense. Cool. Thank you for sharing all of that.
If you're the CEO of a company and you'd like to see how you stack up against the 8 core skills of other CEOs working as a second in command in their business, go to cooalliance.com/ai. /Downloads, grab a free copy of our scorecard where you can measure yourself against those 8 other areas, and we'll send you back a report showing you how you stack up, where you can improve, and where we may even be able to help you in your growth. Again, go to cooalliance.com/downloads.
Uh, I would love to talk about the dynamic with, you said, is it Jen? Yeah. Okay. Why do you think she chose you for this role, especially coming as an investor? What was it about you that stood out?
I think trust is the, the highest piece where we, uh, had a long established relationship, you know, having, uh, been, you know, she, she and the team were the ones building the company for many years before I joined on, on the operational level. Um, but I'd been there, uh, to support through ups and downs. And, uh, I think just being a thoughtful, uh, supporter Um, I think the other thing was intellectual honesty in the relationship. It's one of the things that I really focused on in my role as an investor, and I, I deeply appreciated that about working at Techstars at the earliest stage with founders is like, I, I built a reputation of, I'm gonna tell you what I honestly think. Um, and I'm also going to be clear about where I have significant data like, hey, I've done the thing you're talking about, so I, like, I'm not saying my solution's yours, but I actually know what I'm talking about, versus, uh, hey, I, I have some tangential data, but maybe it's further away. I really always tried to invest time to qualify those things, and I found that it led to deeper, more honest relationships, vulnerable relationships, where you're like, hey, I think you're, I think you're making the wrong choice here. It's your call. Like, I, I'm not the CEO, I'm not the founder. That foundation was what led to, I think, her interest in, in me, uh, joining to play this role at this time. Hmm.
What is your guys' dynamic like throughout the business now, kind of day to day?
Yeah. Uh, we, uh, it's, it's evolving is the answer. Um, and I think a lot of it is just trying to focus on What are the most important business needs? And then also, how can we be proactively thinking about the ideal alignment of our roles? Um, a little bit of a tangent, uh, but it applies to your question about our relationship is I don't think there's anything more fundamental to a company being able to perform well than role clarity. Uh, and that's true for a CEO and a COO or anyone in any role. Someone doesn't know what their job is and how they're going to be measured, how do they have any shot at getting anything done? And on top of that, if you don't tell them how they're going to be measured, like, how unfair is it to then, like, hold them to high expectations? You know, like, I want to be a part of high-performing teams that are striving to, like, do great things and then push even beyond it. And so if you don't spend the time to— like, this is one of those classic slow down to speed up things. And it doesn't have to be complex. It's a concept that I borrowed from some other management philosophy called roles, responsibilities, and expectations. It literally is a Google Doc with 3 sections and just write it down. I get— it drives me nuts the number of companies I've seen or been around where it's like, well, do you have a role description or something that helps someone understand what their job is? And they're like, well, we have the job description when we posted the role. I'm like, That's a marketing document that you use to attract talent to apply. That is not an internal alignment doc to figure out you do X, I do Y. So I have my own document for roles, responsibilities, expectations. She has hers. One of the things that I've installed across the company is that everyone has them. I'm— I think a lot of people have really appreciated it. It's still— you have to win hearts and minds on it. It's one of those like Any slowdown to speed up is never easy, right? Mm-hmm. And we're far from done rolling it out because they're only powerful if they're living documents. If you do it once and then it gathers dust, it was a worthless exercise. If it's the thing that you pull out when you're like, hey, we really screwed up for that customer. And then we sit down and as we're retroing, we're like, you know, I'll, I'll use the baseball analogy. The two outfielders stare at each other and the ball drops between the two of them. The way that we figure out who should call the ball next time so that we catch the ball and get the out in the outfield is we look at the RRNEs. We're like, oh, neither of us wrote down to do the thing. No wonder we dropped the ball. Right. Who's going to write down the thing?
Yeah.
And it doesn't have to be, you know, overly complex. Like literally the other week, Jenna and I were discussing who owns what part of investor relations, which is an interesting division of responsibilities between CEO and COO. And so we were working together to clarify if it's more of a strategic conversation. For example, we have investors that are also board members. She, as CEO, owns board member, board director relationship management. That's her portfolio. But you get a lot of— you have a lot more investors on the cap table than are on the board, and all of them appropriately want the update. How's the business doing? What's the quarterly or annual update on the financials? That flows through me. That is much more just a flow out of information from finance, operational updates, those sorts of things. And by me owning that, it helps us through this R&D discussion and clarity process that as much as we can bias her as CEO to be working on the business by taking the in-the-business stuff off of her plate, that's powerful. I think the COO needs to also explore what is their balance of working in the business and on the business. And I use my roles, responsibilities, and expectations doc as a place to also try to express that. What is my balance? Now, I am much more in the business versus on the business balance versus the CEO, and I think that's very appropriate. Mm-hmm.
I love that you brought this up. This is something that I actually just filled out for a team that I'm doing some fractional sales management for, which is a totally new. I mean, it helped build a sales recruiting company. We trained over 500 teams, but like sales management in itself, I've never been in that role. And I came in and this team has been established for quite some time, and it was just, yeah, it's really surprising to me that they didn't have what I call like a job scorecard. Like you said, like this is how you know you're winning in the position or not. Um, and one of the things that I like to have on there is competencies, which are like a little bit more expanded versions of core values. So it's like, I'll have like the core values, but then the competencies of that role. And like you said, there's something really great to come back to, not just like for yourself, but when you're a manager holding someone accountable. Like you said, if something— a ball is dropped, or someone's like, well, that's not a part of my role, or I didn't agree to that, it's like, well, when you came on board, we went over this. And every quarter, if you're going back to that and talking through how things are going and updating it. It's such a great way for the team member to actually know if they're winning, and then for managers to be able to have those conversations when there's clear things that you might be frustrated with. How is it always the manager's responsibility? Like extreme ownership of if someone didn't do something right on the team, where was it not properly communicated that they were responsible for that, or XYZ, whatever that piece was. So Very timely that you were bringing this up. And yeah, I'm a huge fan of— you said you call them RNEs, responsibilities.
Yep. Role, responsibility, and expectation. So role is just job title. Um, and then responsibilities is like the what, what are you doing? And then the expectations is the outcomes or how we measure it. Or I, I like the term that you used too, the scorecard or something of that nature. And, uh, what I think is really interesting is if you keep a very flexible framework like that, you can modulate based on different types of employees. Hopefully with, you know, employees that have more experience and are much more independent, you can just really beef up like what are the outcomes and then you give them space to figure out how they're going to go solve the problem, which is so much better than instead of like being like, here's the recipe and here's the 95-step process to do it. It's like give them the degrees of freedom to go be creative. Just tell them what they're responsible for. Versus, you know, sometimes you have whether it's an employee that has less experience, maybe earlier, whether it's early in their career or earlier in sort of a new job pathway. So they're just less familiar with it. Being more prescriptive could actually be the kind thing to do, or it could be a highly critical role. You know, a good example is like if you work on an assembly line and the part needs to be made within this millimeter sort of specification, like maybe 95 Steps manual is exactly the right choice. Other roles different. And like, that's the beauty is that can you as a company really say what is a framework that creates as much opportunity for each person's brilliance to emerge? And then also I'm a big believer in the concept that the people with the greatest proximity to the problem have the best, best shot at solving it. So the more that any of these frameworks, whatever language we want to use on it, can give that flexibility to be like, hey, the CEO or the COO or anyone top-down doesn't have all the answers. The most beautiful, creative, elegant solutions come bottom-up, uh, and they emerge from the person who sat with the problem for the longest and they're like, darn it, I know a better way. And what you need to do is like, how do you enable them? How do you give them agency to not be stuck with the solution and know where to go?
When you mentioned— I can't remember the term that you just used, but Ray Dalio, um, I believe it's Ray Dalio that has a chapter called Weighted Believability. And I had this exact— what was this, like maybe a year into my first executive position, and I was explaining why something was happening in this idea that I had, and the two other, uh, executives on the meeting that were not the owner started giving their feedback, and like very strongly, both of these guys are they were sales professionals turned executives, so very persuasive. And I remember feeling like, man, like, this is my department. I know the most about this, but like, I couldn't articulate my way through it. And I'm so grateful for the owner who taught me about weighted believability, where he really, like, he heard everyone out and he was like, you know, you guys have some really persuasive points, and Savannah has way more believability because she's so close to the problem that like I'm just going to trust her to go do what she thinks needs to happen. And I've been able to really bring that into future leadership situations because it's super important. So yeah, a little like side angle there, but I wanted to come back to side angle, sidetrack, rabbit trail.
I'm picking up what you're putting down.
Perfect. And coming back to that document, when you, if you have people that are maybe more experienced and you're like, hey, this is the outcome we don't really know what you're gonna do. We just know we need you to fix this. Do you have them go out and start playing around doing their thing and then you have them fill in that description on their own? Or do you guys have like a meeting set, you know, 90 days after your role, like we're gonna put in there what you're doing? Or how do you keep that updated?
Yeah, it's a great question. Um, uh, few things come to mind and just give, credit where credit is due. It's a concept that I borrowed from Principle-Based Management is the framework. And the, like the process of building the roles, responsibilities, and expectations, at least how I do it, it depends if it's an existing role or a new role. So if it's an existing role, then hopefully there's an architecture already there. Like if you, like, let's use software engineer. As an example, and let's say you have levels, software engineer 1, 2, 3, for lack of a better system. Um, it's probably mostly already defined, and that can be good, especially if you're outcome-focused in it versus being overly prescriptive. Now, maybe it's the first time that you're hiring a software engineer 2 that's focused on DevOps. Okay, now we should— we have an architecture to start with that we can then customize around Hey, this is our first DevOps hire. Let's make sure that it's queued up for that. And then that is a collaboration between your HR team, who is really your steward of the concept and figuring out how do you both maintain consistency, but have it applied in a custom way for every human in every role. The hiring or the hiring manager or the person that will manage them. And then the most important person is, is that the, the new person in the role. Because if it's a thing handed to you versus a thing that you felt some level of co-creation in, there's a totally different level of ownership and buy-in. So I think that creating that space is really critical. You have to do a lot of effort up front to get buy-in on the why. Like, I, I just want to write lines of— like, I— no software engineer says I want to write lines of code. That's a horrible, um, uh, description. They would say, I just want to go start solving problems, is what they would say, um, because that's why most software engineers that I know who are great at their trade love doing it. They love solving problems. And you— and so this is an opportunity where you need to say, cool, to solve problems, you're going to need to collaborate with your team. Having role clarity is going to allow you to do that more efficiently and effectively. In my experience, uh, software engineers are some of the best people at role definition.
Um, why is that?
They're generally— a lot of them, you know, there's, there's, you know, there's no one profile for software engineering, but generally speaking, they're problem solvers. They want to understand the why and they're system thinkers. So they—
It's how to make snacks.
Yeah, exactly. So usually once you get the space to explain the why, they're like, oh cool, this is going to make it so much clearer. And like, then they want to run with it and that's awesome. Like, let them go. So, so that's an example of this. If it's a new role, So let's say you've never had a partnerships manager before and you're doing that. I really like this as something that you do with whoever is the hiring manager hiring that N of 1 first person in role. It's like, yeah, let's write the job description to attract the candidates, but we also need to build the roles, responsibilities, and expectations because we effectively need to write a business case for why we're creating a new role. And this is your your underwriting for the case because it's like, well, why do we need a partnerships manager? Well, it's because we think we can drive new revenue through partnerships as a channel. Cool. You just described what the outcome in the, in the role's responsibility and expectation should be. How much revenue do you think they're going to generate over what period of time? Write it down.
Love that. Yeah. Which, speaking of partnership managers, do you guys have one?
We do. We have an amazing partnerships team. You cannot get very far in HR tech without partnerships because, you know, the HR tech stack is honestly messy and it's hard to like get all the pieces to play nice to each other or with each other. And that's one of the things that I think we've very effectively invested in is working on integrations with other parts of the HR tech stack. And because it's critical PII and other things like that, you have to build relationships between companies before everyone's, uh, comfortable to actually do the integration work. We have an amazing partnerships team and we've built strong partnerships with companies like Rippling, uh, Paycor, Paylocity, uh, all of the HR, um, systems out there. We have an integration with Workday. We're in their marketplace. Partnerships are at the center of our growth.
How do you guys go about originally like finding those you know, the ins, like getting in. My roommate has been talking a lot about partnerships, which is why I'm interested in it. Yeah. How do you go about initially starting that contact when there's a bunch of people vying for partnerships with some of these bigger brands?
Yeah, I mean, it's, it's a ladder that you keep climbing up over time to get enough credibility to be of interest to the larger partners. You know, HR tech is an interesting space. It's not that there's not new systems of record, but there hasn't been massive turnover. It's also a very fragmented market. Like no one has 50% market share or even close.
Mm-hmm.
So the truth is that like, it's a, it's a small world. So once you prove with customers that were willing to take a bet on you early that you have enough credibility, it's, it's pretty, It's pretty easy to navigate to all of the relevant players, in my opinion. The question is, how do you prioritize who the right ones are, especially in our space where there's a lot of dominant systems of record, but none of them own the majority of the market, but each one is sort of focused on a different part of the market? Are they focused on SMB? Like, are they HR tech for SMB, mid-market, enterprise? And so you start doing the three-dimensional chess of slicing, dicing, like where are you in the solution stack and for whom? And you get pretty— the list gets pretty short pretty quickly. And then it's a question of who's going to win the, you know, the dance card game, um, as, as all this stuff, uh, aligns pretty quickly.
Yeah, makes sense. Well, speaking of things that are going well, so your partnership management team is going great, love to hear it. Uh, what are you looking forward to? What are you hoping is also going to go great in next 6 months?
Yeah, uh, it's, it builds on the partnership point, and it's that we have some amazing existing relationship with partners and we're building new ones. Um, leave management doesn't stand on its own, right? Like, we, we have to integrate and play nice with multiple parts, like the HR systems, like the ones I described, um, payroll systems, Uh, all of this coming together, uh, currently, as I described, I would say the integration across the layers of the HR tech stack are messy. The question is, what if we made it actually work really well? Like, that's interesting. Uh, you know, that the payroll information is flowing well. Another layer to, you know, not put everyone to sleep too much, but, you know, the second you get into leave management, um, you quickly get into all of the insurance carriers that companies use. So if people are going on medical leave, I'll go back to the example that I was highlighting before. When someone gives birth in our country and they're like, I'm going to be out for some number of weeks, the main way that we as a nation have decided to underwrite that wage replacement period, so that person's not going to be at work and the company could be like, hey, do we just keep paying them or do we defer that risk to someone else? We have underwritten most of that through short-term disability. So literally when someone is giving birth, our main funding mechanism as a nation for that moment of employment journey is short-term disability. And that's not the fault of the insurance carriers or anyone else. Um, but it's an interesting choice that we've made. Um, and so you have another party, you have the company, you have your leave administrator, you have an insurance company, you might have a state paid family leave program. Like it's the definition of like, it's not rocket science. We're not putting, we're not putting, you know, um, anything on the moon here, but it ain't simple. And so the thing that gets me excited is, uh, all the hard work we are doing and we're going to do to take that which is complex and make it simple and approachable.
Hmm. I love that. The company that kept coming up, um, that I, I know this is a little bit of a weird comparison, but are you familiar with Deal? Deal.
Yeah. Oh yeah.
Yeah. I love Deal, just like how they were able to bring all the pieces. When I think of like compliance and regulations and all the different countries, uh, because I also helped scale an outsourcing company, um, last year and I just learned so much about that space. And yeah, anything that you can just bring all the pieces together and make it as seamless as possible for the end user, I am a huge fan of. Absolutely. Thank you for the, the work and the impact that you guys are doing. And I'm sure there are many happy moms and other people that have been impacted by the, the service that you guys provide.
Thank you. Yeah, no, it's, it's me. It's a meaningful mission. We really care about it.
Well, Taylor, thank you so much for your time. If anyone wants to reach out or connect with you, where would be the best place to do that?
Absolutely. I'm Taylor@OurTilt.com. Uh, so I, I, uh, am a self-proclaimed, uh, nerd on all things, both related to leave as we were talking about today, but also company scaling and building. Um, I just, you know, I have a passion for this. I think that entrepreneurship and building new companies is one of the greatest levers to change our world. Uh, I do not like— I deeply align with mission and impact. But profit is not evil. Profit is people voting with their dollars for great solutions. Um, and I believe there's, uh, you know, an impact-minded person in almost every company builder out there. And the more that they can connect why they're building what they're building and how they help customers vote with their dollars for a great solution is like, I, that's where I just get excited is people thinking that way. So anyone out there who wants to chat about that, I would love to meet them.
Amazing. Well, thank you so much. Appreciate your time.
Thanks for inviting me on. It was great to chat.
More from Cameron

Flutterwave Former Global Head of Operations Awa Kone | When Growth Outruns Operations (Podcast 611)

Optomi Professional Services COO Nick Murphy | The COO Can’t Know Everything (Podcast 607)








