My name is Kris Treytl. I have spent 25 years in HR and I have exactly zero regrets — except maybe the years I spent avoiding HRBPs because I thought they were kind of useless. (Turns out that was projection. More on that in a minute.)
I built HRBS.ai because I got tired of watching the same preventable disasters play out over and over. Manager makes a mistake. Manager makes a worse mistake trying to fix it. Company ends up in a legal situation that any decent HRBP could have helped them sidestep in fifteen minutes. Rinse, repeat.
The problem was never the managers. The problem was access. And honestly? A lot of the time the problem was also HR.
Where I Started (And What I Was Avoiding)
Right out of graduate school, I went straight into the kind of HR work that gets called "strategic" — leadership development, executive coaching, employee engagement, career development frameworks, recognition programs. The big stuff, done globally, for companies like Oracle and Gap Inc. I loved it.
What I was quietly avoiding was the HRBP role. HRBPs, in my early career experience, seemed to be the people who existed to say no, to complicate things, to introduce process where common sense would have served perfectly well. I was going to stay as far from that as possible.
And honestly? I wasn't wrong about the stereotype. Most leaders I eventually worked with had the same story. They'd had a bad experience with HR. They saw HR as the people who showed up with a twenty-page form when you needed a five-minute conversation. The ones who said "we need to loop in legal" when what you really needed was someone to say "here's what to do, here's how to do it, and here's how to not get sued while you're at it." They'd stopped asking HR for help because the help was worse than figuring it out alone.
“I spent years judging HRBPs from afar. Then I became one. Turns out the job is genuinely hard — and genuinely important — and there are never enough of us to go around.”
After a stint at a startup and some time in survey consulting, I eventually caved. I became an HRBP. And here is what surprised me: I was good at it. Not because I had some gift for politics or bureaucracy — in fact, the opposite. I was good at it because I had zero patience for the parts of HR that don't actually help anyone. The pointless forms. The CYA processes. The "let me get back to you after I check with three people" stalling that makes leaders want to throw their laptop.
What I had instead was judgment. Good judgment, developed over years of actually sitting in rooms where decisions got made and watching what happened when those decisions were right and when they were wrong. I understood the business. Not "I've read about business strategy" understood it — I understood what the VP of Engineering was actually stressed about at 2am, what the sales leader needed to hear versus what HR thought they needed to hear, and where the gap was between what a policy said and what the situation actually required.
She Just Gets It
That phrase followed me everywhere. Different companies, different leaders, same feedback. "Kris just gets it." Not as a compliment about being smart — as relief. Relief that they finally had an HR person who didn't make them feel like they were talking to a compliance robot.
What "gets it" actually meant, when you unpacked it: I understood what the business needed and I figured out how to make it happen, even when that meant going around the bureaucracy that HR itself had created. If a leader needed to move fast on a hire and the standard process was going to take six weeks, I didn't lecture them about process. I found the path that got them what they needed while keeping the company out of trouble. That's judgment — knowing when the process serves the outcome and when the process is the problem.
My partners loved the irreverence. They loved that I'd walk into a meeting and say "that's a terrible idea and here's why, but here's a better one." They loved that I didn't hide behind HR-speak. They loved that I had a sense of humor about a job that can feel deadly serious. Because it turns out that when you're helping someone navigate a termination or a harassment complaint or a team that's falling apart, the last thing they need is someone who sounds like they're reading from a manual. They need someone who's done this before and can talk to them like a human being.
“Most people expect HR to hand them a process. I'd rather hand them an answer — and a joke, if they look like they need one.”
The Employee Side
Here's the thing nobody talks about: employees hate HR too. Not for the same reasons leaders do — leaders see HR as blockers who slow them down. Employees see HR as management's enforcer. They assume HR exists to protect the company, not to help them. And in a lot of organizations, they're not wrong.
Every employee I worked with closely would tell you something different about me. I listened. I actually cared about what was happening to them. I didn't treat their concerns like a liability to be managed — I treated them like a person who needed someone in their corner. When an employee came to me with a problem, I didn't immediately calculate the company's exposure. I tried to understand what they actually needed and then figured out how to get it for them.
Sometimes that meant advocating for them in rooms they'd never be invited to. Sometimes it meant having an uncomfortable conversation with their manager. Sometimes it meant telling them something they didn't want to hear, but doing it in a way that left them knowing I was on their side. That's the part most HR people get wrong — they think advocacy and honesty are opposites. They're not. People can handle hard truths from someone they trust. They can't handle soft truths from someone they don't.
Good HR isn't about knowing the policies. Anyone can look up a policy. Good HR is about reading a room, understanding what someone actually needs versus what they're asking for, having the judgment to know the difference, and having the guts to act on it — even when the "process" says otherwise.
Silicon Valley, Fortune 100 to Unicorn
I've spent my career in the Bay Area, which means I've had a front-row seat to something most HR people only read about. I've worked inside the rooms where heads of AI are shaping what the technology will and won't do. I've talked to VCs who are thinking hard about what AI means for knowledge work. I've watched tech companies hire brilliant engineers and then hand them fifty direct reports and a "good luck."
Working across those worlds gave me a specific kind of credibility. I know what enterprise HR looks like when it's well-resourced. I know what startup HR looks like when it's one person trying to hold back a flood with a Post-it note. I know the delta between those two realities. And I know that delta is killing companies — quietly, in the form of preventable turnover, legal exposure, and managers who never got the support they needed to become the leaders they were capable of being.
The Unicorn That Changed Everything
A couple of years ago I joined a genuine unicorn startup. Fifteen employees when they started. Growing to 150 in a year. The energy was electric and the people challenges were extraordinary.
Engineers who had been coding the core product six months earlier were suddenly VPs of Engineering. Managers who had never managed before were running teams of fifteen across multiple time zones. Executives who had only ever worked with tactical HR people had no idea what a strategic HRBP could even do for them — so they didn't ask.
I was the only HRBP supporting five business units, fifty managers, and over 300 employees. The math didn't work. It never works. That's the dirty secret of startup HR: the ratio is always wrong, and the consequences land on the managers who are just trying to figure it out as they go.
One HRBP. Five business units. Fifty managers. Over 300 employees. And the problems compound as the company grows — because managers who got lucky in year one start making the same mistakes at scale in year three.
I watched genuinely talented people make entirely avoidable mistakes. Not because they were careless, but because they didn't know what they didn't know. A California leave request that got handled informally. A performance issue that should have been documented six months ago. A team conflict that had a clear resolution sitting right there, if anyone had known to name it.
I couldn't clone myself. But I started thinking about what it would mean if every manager had access to the kind of guidance I could give — not a policy document, not an FAQ, but an actual conversation with someone who understood the situation, understood the context, and could help them figure out the right move.
The Honest Startup Struggle
Building HRBS.ai has been the hardest thing I've ever done. I'm going to tell you that directly, because I think founders who pretend otherwise are doing everyone a disservice.
I found a technical co-founder who was brilliant and genuinely excited about the problem. Then he went quiet. Then he was gone. I spent months in that limbo that founders don't talk about, where you have a real idea and a real market and a technical gap you can't close on your own.
Meanwhile, the technology was moving. Every quarter, the models got better. The things that seemed impossible in the first version of my roadmap became possible. The things I thought would take two years took six months. Keeping up with that pace while also learning to be a CEO for the first time, while also being the chief practitioner for a product that requires genuine domain expertise to build correctly — it was a lot.
“I've made every first-time CEO mistake in the book. I've hired wrong, trusted the wrong people, moved too slow when I should have moved fast and too fast when I should have slowed down. I'm still here because the problem is real and somebody needs to solve it.”
The thing that kept me going was the clarity of the problem. Every week I talked to managers and HR leaders who described exactly the same situation I had lived. The access gap was real. The consequences were real. And the technology — finally — was real enough to actually address it.
The Turning Point: The Expert Gets to Build
Here's what shifted. For most of the history of HR technology, the way software got built was: software engineers talked to HR people, tried to translate what they heard into product requirements, and built something that kind of worked but missed about forty percent of the nuance that matters in an actual HR situation.
The reason is simple: the engineer doesn't know what they don't know. They can build a competency framework tool without knowing how competency frameworks actually get used in organizations. They can build a performance review workflow without understanding what happens when you hand a manager a blank text box and tell them to describe "areas of improvement." The tool ships. The friction persists.
What changed with modern AI is that the domain expert can now build. Not in the sense of writing code — though the tools have gotten good enough for that too — but in the sense that the practitioner's knowledge is the product. Lisa works because every response pattern, every discovery question, every escalation trigger was designed by someone who has had hundreds of these conversations with real managers in real situations.
Lisa's seven-category evaluation rubric — Risk & Compliance, Manager-Centric Communication, Contextual Awareness, Insightful Discovery, Practical Solution Quality, Proactive & Strategic Coaching, Evidence-Grounded Advice — was built by an HR practitioner, not a software team guessing at what good HR looks like.
Lisa Is Me
I want to be direct about this, because I think it's actually the most important thing to understand about why Lisa is different from other AI HR tools.
Lisa is modeled after me. Not in a vanity sense — not as a "digital twin" or an avatar. In a specific, structural sense: the way Lisa approaches a manager situation, the questions she asks before giving advice, the things she flags as risks, the judgment calls she makes about when to coach and when to escalate — all of that reflects how I would approach the same situation.
I spent more than a year building and testing Lisa before I was willing to put her in front of real managers. We ran 3,400+ simulated HR scenarios. We tested across jurisdictions, across difficulty levels, across manager archetypes. The median score across all evaluated simulations is 94 out of 100. On crisis-level scenarios, she maintains that standard.
That rigor isn't a software team's instinct for quality control. It's an HR practitioner's instinct for what happens when someone gives a manager bad advice. The stakes are different when you've seen the outcome.