Contents
The challenge: Drive meaningful employee engagement My 300x ROI app The surprise wasn't the app. It was the collaboration. The takeaway: vibe coding is meaningless unless it's tied to a real business need

A year ago, the sentence “I just deployed an app on GitHub” wouldn’t have made sense coming from me. I’m the VP of People at CloudZero; code deployments and I were not close friends.

That’s changed. In this AI era, non-engineers are building, and I think that’s a genuinely good thing. But only if it’s tied to something that matters.

The challenge: Drive meaningful employee engagement

One of CloudZero’s company objectives is to be a place where exceptional people thrive. That’s easy to put on a wall and hard to operationalize. When you actually dig into what drives it, a lot of it comes down to one thing: whether employees have meaningful, continuous developmental conversations with their managers. Not the archaic once-a-year review-cycle version. The everyday version: real-time recognition, coaching, and feedback woven into how people actually work, with the employee at the center.

We know what’s at stake when that breaks down. Two of the top reasons employees leave are poor relationships with their manager and a lack of growth. Turnover isn’t cheap: for small- to mid-sized organizations, the cost of a single departure runs anywhere from $150K to $300K and up, once you account for recruiting, ramp time, and lost momentum.

So I didn’t set out to build an app. I set out to address that problem, and an app was the form the solution took, a form AI made newly available to me.

My 300x ROI app

The result is a five-module app that supports exactly those developmental conversations, amplifying the behaviors that create a workplace rich in feedback, high performance, and accountability. It took less than 10 hours of build time and under $1,000 in total AI spend.

I want to focus on those two numbers for a second, because they’re the whole argument. Spending under $1,000 to directly address a problem that costs $150K to $300K per occurrence, while building new skills and strengthening collaboration along the way, isn’t a cost. It’s one of the cleanest AI ROI examples I’ve seen. The math only works, though, because the spend was pointed at something that mattered. Cheap effort aimed at the wrong problem is still waste.

The surprise wasn’t the app. It was the collaboration.

Here’s the part I didn’t see coming.

The People team I lead partners with employees across the org every single day around core objectives: coaching, talent management, people operations, recruiting, and organizational strategy. This was different. Building this app meant working with Security, IT, and Revenue Engineering on code reviews, architecture decisions, and deployment.

Same people I regularly partner with, but an entirely new dimension of working together. I learned how they think about problems I’d never had to consider, and they got pulled into a People-team objective they wouldn’t normally touch. That cross-functional muscle, the one that rarely gets exercised, got a real workout because we were building something together. And honestly, it was a lot of fun.

That’s worth naming as its own outcome. The app addresses a retention problem. But the process of building it created exactly the kind of cross-team partnership that makes a company a place where people want to stay, and thrive. The medium turned out to be part of the message.

The takeaway: vibe coding is meaningless unless it’s tied to a real business need

The app is still early. There’s more to learn and more to build, and I’m treating this as a first iteration, not a finished product.

But if I had one thing to share with anyone exploring AI right now, it’s this: Vibe coding is meaningless if it isn’t tied to a real business need.

The tool doesn’t matter. The model doesn’t matter. The thing that’s easiest to obsess over (which platform, which model, which workflow) is the thing that matters least. What matters is whether your AI spend is aligned directly to your company’s objectives, and whether it opens new pathways of learning and partnership along the way.

This is the same discipline we talk about with customers every day, just pointed inward. It’s what cost intelligence actually means in practice: not “how much did we spend,” but “what did we spend it on, and was it worth it?” That’s the real AI ROI question, and it doesn’t change whether you’re a Fortune 500 finance team or a People leader shipping her first app.

The question is never “can we build it?” The answer to that is increasingly yes, for almost anyone. The real question is “should we, and toward what end?” AI makes the cost of building collapse. It does not make the cost of building the wrong thing collapse. That bill still comes due, in time, attention, and trust.

So spend. Build. Ship. Let non-engineers get their hands on the tools. But anchor every dollar of that spend to an objective you actually care about. If it’s aligned, if it’s solving a problem that matters and creating new ways for your people to work together, then keep going. Spend responsibly.

That’s what it’s all about.