Great HR platform projects stall one level below the people who'd fund them
A post about software sales got me thinking about our own pitch.
The argument went like this: in enterprise software, deals don't die in the demo. They die later, quietly, because the seller only ever talked to users and middle management. The champions are sold. The platform team is sold. Then the proposal reaches the C-suite, where nobody recognizes the language being used, and it never quite turns into a yes.
I read it and winced a little. Because that's not only a sales problem. It's a customization problem too – and one I watch our clients run into all the time.
When you set out to make Cornerstone yours – branded, intuitive, built around how your people actually work – you're usually doing it for the right reasons. Better experience. Higher adoption. Less confusion. All true. But "better experience" is an adjective, and adjectives don't get funded. Numbers do.
I had exactly this conversation last week. An HR team was browsing for AI-enhanced features to save everyone time – a genuinely good idea, championed from inside HR. But the project manager was honest about what came next: "Our leadership is very number-driven. Being able to measure it will be the first question." Could they justify the spend against the time it would save? That question – not the quality of the idea – decides whether it happens.
The same project, three different conversations
Here's the part worth borrowing from the sales world: the exact same project sounds completely different depending on who's in the room.
On the floor, customization is about functionality. Can I find my training? Does this page make sense? Will I actually use it?
For managers, it's about productivity. Fewer support tickets. Faster onboarding. Less time lost to a tool nobody understands.
In the boardroom, it's about cashflow, margins, and competitive advantage. Is this money well spent? What do we get back? What does it protect us from?
Most of us – and I'll happily include Octily here – tell the first two stories beautifully and forget the third. We talk craft and adoption to people who already believe in craft and adoption. The person who signs off on the bigger number never hears a story in their own language.
Turning adoption into a number a CFO will defend
The good news is that the third story is already true. It just needs translating. A few angles we've seen land in the room that matters:
License waste. You pay for Cornerstone per seat, whether someone logs in or not. If half your people quietly avoid the platform because it feels generic or confusing, you've bought a tool for twice the people who actually use it. Customization usually costs a fraction of your annual license fees – so closing that adoption gap pays for itself before it does anything else. And if you want the actual number, Cornerstone MicroApps can surface exactly who is and isn't engaging.
Time to competence. Every week a new hire spends lost in an unfamiliar interface is a week they're not yet productive. Multiply that across thousands of joiners a year, and a clearer welcome page stops being a design detail and becomes a line on the P&L.
Retention and employer brand. People judge a company by the tools it hands them on day one. A talent experience that feels considered isn't a nicety – it's part of why good people stay, and part of why they pick you over the competitor down the road. That's the competitive-advantage story a CEO actually leans in for.
Risk. Compliance completion, data accuracy, clean audit trails – all of it improves when people can find what they need. A boardroom understands reduced risk even when it never thinks about UX.
None of this asks you to drop the experience story. It asks you to put a number next to it.
The honest part
Not every customization needs a board meeting, and pretending otherwise would be its own kind of overselling. A single branded login page or a tidier learner home is an HR-leader decision, made with a budget you already control. Chasing the CFO for that would be silly.
But the bigger moves – a multi-year platform strategy, a shift to something always-on, a rollout across every region – those do reach the people who think in margins. The mistake was never talking to the C-suite. It's only knowing how to talk to everyone else. So know which conversation you're actually in, and bring the right story to it.
Build the case before someone asks for it
If you're planning anything ambitious with Cornerstone this year, write the business case early – before someone upstream requests it. Put the experience reasons and the financial reasons on the same page. Name the license spend you're protecting, the hours you're handing back, the people you're keeping.
That's the part we can help with, by the way – not just the design, but the case for it. We've helped make the impossible possible for nearly a hundred organizations, and the projects that truly fly are almost always the ones where someone took the time to tell the boardroom story too.
And if you'd rather talk it through than build the case alone, you know where to find us: https://octily.com/meet
