Rick Ramos is the founder and CEO of Benefits Studio, which helps insurance brokers and HR teams launch employee benefits portals in minutes. Every portal includes Benny, an AI assistant that answers employee questions straight from the plan documents and cites the page each answer comes from. Pricing starts at $49 a month with no per-employee fees, which puts real benefits help within reach of the SMB and mid-market employers that bigger vendors tend to overlook.
Before Benefits Studio, Rick was a founding team member and CMO at HealthJoy, where he helped scale the benefits navigation company to a $500 million valuation. Earlier in his career he held leadership roles in adtech at Adknowledge, the 6th most acquisitive company on the internet. He’s also the author of several books, including Transform Your Marketing and Content Marketing.
Company: Benefits Studio
We are thrilled to have you join us today, welcome to ValiantCEO Magazine’s exclusive interview! Let’s start off with a little introduction. Tell our readers a bit about yourself and your company.
Rick Ramos: I’m Rick Ramos, founder and CEO of Benefits Studio. I’ve spent most of my career in marketing, and the stretch that shaped me most was my time as a founding team member and CMO at HealthJoy. We helped employees make sense of their health benefits, and the company grew to a $500 million valuation.
The idea for Benefits Studio came out of a conversation with a nonprofit. They asked about my background, I told them about HealthJoy, and they loved the concept. Then the reality set in. They had no budget for something like that, and they weren’t convinced the ROI was there. I walked away thinking about how many employers are stuck in that exact spot.
Most benefits navigation vendors charge per employee per month and go after the largest employers. A 200-person company usually ends up with a PDF on a shared drive and an HR person answering the same questions all year long.
Benefits Studio gives those companies a better option. Brokers and HR teams can launch a benefits portal in about five minutes, starting at $49 a month with no per-employee pricing. Every portal comes with Benny, our AI assistant. Employees ask him questions in plain English, and he answers from the actual plan documents and shows the page number so they can check it themselves.
We launched this year and we are part of the Anthropic’s Claude for Startups program, so it’s been a good year.
What was the moment you realized that complexity was holding your company back, and how did that shift your approach to product, operations, or strategy?
Rick Ramos: The moment came early, when the team was still very small. Every process we added seemed to route back through me, and bandwidth became the thing I worried about most. That’s when I realized complexity wasn’t only a product problem. It was an operating problem, and for a lean team it would sink us faster than any competitor could.
So we put AI at the center of how the company runs. Today I work with a team of part-time people in customer success and product testing, plus SDRs handling outbound to brokerages. Nobody is full time, so every process has to be simple enough to pick up midweek and fast enough that nobody sits around waiting on me.
The rule we follow is that AI does the heavy lifting and a person makes the call. Content is a good example. We plan topics together, AI writes a full draft every week and runs it through an editing pass, and nothing publishes until a human has reviewed it. Customer communication works the same way. Emails go out automatically based on what someone actually does in the product, like signing up without building a portal or building one and not publishing it yet. That frees our customer success people to spend their time on real conversations instead of reminder emails.
The same principle runs through the product. When a broker uploads a plan document, AI pulls out the details, but the broker approves everything before it goes live.
The biggest shift was in how I judge new ideas. Before we add anything, I ask who’s going to carry the complexity. If the answer is a part-time teammate or a customer, we redesign it until the system carries it instead.
Can you share one specific example of something you simplified (a product feature, process, pricing model, or customer experience) that delivered outsized results?
Rick Ramos: Pricing. Almost everything in benefits navigation is sold per employee per month. That sounds simple until you try to buy it. The price moves every time headcount moves, the broker needs a spreadsheet to quote it, and a 200-person company can end up paying $7,200 a year or more before anyone knows if it works.
We threw that model out. Benefits Studio is priced per portal at a flat monthly rate, and headcount never enters the math. Our Professional plan comes to $1,188 a year whether the employer has 60 people or 1,000.
The effect on sales conversations was bigger than I expected. A broker can quote it on the spot without a calculator, and an HR leader can often approve it without kicking off a procurement process. It takes the budget debate out of the conversation, which is usually where deals like this stall. They dont need to get finance involved, since a simple credit card charge of $99 a month is a simple ask.
The result I didn’t see coming was that some brokers stopped passing the cost along at all. They just absorb it and give the portal to their clients as part of their service. When the price is low and predictable enough, it stops being a line item to negotiate and becomes a way for a broker to show up with more value than the competition. For us, that means the broker becomes the buyer and the champion at the same time.
How do you systematically identify and eliminate complexity across the organization without oversimplifying in ways that hurt quality or value?
Rick Ramos: For anything new, whether it’s a feature, a process or an email sequence, we start with one question: who’s going to carry the complexity? If it lands on a customer or a part-time teammate, that’s our signal to redesign it so the system carries it instead.
The harder part is knowing where to stop. My line is accuracy. Anything that affects whether an employee gets the right answer about their benefits doesn’t get simplified, even if it slows us down. That’s why Benny only answers from the plan documents a broker uploaded and cites the page every time. It’s also why AI pulls the details out of those documents, but the broker has to approve them before anything goes live. Skipping that step would make setup faster, and it would also be the quickest way to lose a customer’s trust.
Below that line, we build for the common case and handle the rare one honestly. Plan-year rollovers are a good example. Roughly 95% of employers switch their whole benefits program over on a single date, so that’s what we built. The small group that staggers rollovers across employee groups gets a clear explanation in our FAQ instead of a setup screen everyone else would have to wade through.
We’ve also gotten it wrong in the other direction, and that taught us just as much. Early on I was firm that portals would be public with no logins, because it kept things simple for employees and for us. Then I got enough feedback from people in the industry, and saw research showing only around 10 to 15 percent of companies publish benefits information publicly, to realize that was a dealbreaker for a lot of HR teams. So we added an optional shared password for each site. It’s off by default, there are no employee accounts, and no personal data is involved. HR gets something to point to when the CEO or legal asks about it, and we kept the simplicity that actually mattered.
What’s the biggest resistance you’ve faced when pushing for radical simplicity, and how did you overcome it?
Rick Ramos: The biggest resistance isn’t from any one person. It’s an assumption built into the benefits industry that if something matters, it has to be complicated and expensive. Benefits navigation has been sold for years with per-employee pricing and long implementations, so a lot of buyers have learned to read complexity as a sign of quality. When you show up with something that takes minutes to set up and starts at $49 a month, the first reaction is often skepticism. People wonder what’s missing.
I stopped trying to argue with that and started letting people see it. In a demo, I pull up a real plan document and have Benny answer a question from it, page number and all. That does more than any slide about our philosophy. We also let brokers and HR teams build their entire portal before they pay anything, so they can judge it with their own plans instead of taking my word for it.
The other piece was being clear about what we don’t do. We aren’t trying to replace a broker’s expertise or HR’s judgment. The portal gives employees one clear place to find answers, and the harder questions still go to people. Being upfront about that makes the simplicity easier to trust.
For other CEOs who struggle with feature bloat, process overload, or confusing customer journeys, what’s the most important principle or first step you would recommend they take?
Rick Ramos: Sign up for your own product as a brand-new customer, and do it often. Monthly isn’t too much.
Make a fresh account with a new email. Don’t skip the steps you know by heart, and don’t use your admin shortcuts. Go through it exactly the way a customer would on day one. It’s uncomfortable, because you’ll find things you built that annoy you.
The problem is that founders and teams go nose blind. You’ve seen the same screens so many times that you stop noticing the extra form field, the confusing label or the email that shows up at the wrong time. Your customers notice all of it, and most of them won’t tell you. They just leave.
While you’re going through it, question everything. Why is this step here? Why do we ask for this now instead of later? Who is this screen actually for? A surprising amount of complexity exists because “that’s how we built it” or because it made something easier for the company, not the customer. Those answers are what you cut first.
For us, the moment that matters is when Benny answers a real question from a real plan document and shows the page the answer came from. Everything between signup and that moment is friction, so that’s the stretch we keep testing hardest.
