Ricardo I. Cruz, MBA
Client Services and Customer Success Executive
Enterprise Retention & Expansion/Multi-Million-Dollar Portfolio Ownership/Global Matrixed Delivery
I steer enterprise client portfolios where the revenue is concentrated, the regulatory exposure is real, and the delivery organization doesn't report to me.
Remote, United States/317.674.3338/ricardo@workwithricardocruz.com/linkedin.com/in/ricardoicruz
What I am accountable for
Client services and customer success executive with 15+ years scaling enterprise recurring-revenue portfolios in financial services.
I steered a $6M Annual Recurring Revenue (ARR) book of strategic health and welfare clients serving 16,000+ end users, then took ownership of platform migration and implementation strategy across 10 enterprise engagements representing 275,000 employees. The delivery organization behind that work, 50 to 75 professionals across eight functions and two continents, has never reported to me directly. I direct it through strategic influence.
My work converts regulatory and technical complexity into retention and expansion: an average 90% reduction in client escalations, a 95% reduction in recurring operational defects, a five-point Net Promoter Score (NPS) lift on a single systems change, and 100% client adoption of Fidelity standards achieved through influence rather than refusal. I am a President's Circle recipient and a deliberate builder of leaders. Several of my mentees have won the same award.
Scale of responsibility
| Figure | Measure |
|---|---|
| 275,000 | Employees served across 10 enterprise migrations and implementations |
| $6M | Annual recurring revenue portfolio owned across four strategic clients at $1–2M each |
| 50–75 | Matrixed professionals directed across eight functions, United States and India |
| 16,000+ | End users under continuous portfolio management |
| 100% | Clients adopting Fidelity standards through influence and negotiation |
| 92% | Of proposed standards accepted, with the remaining 8% shaping the enterprise roadmap |
| 95% | Reduction in recurring funding and operational defects |
| 90% | Average reduction in client escalations across the portfolio |
| +5 | Net Promoter Score points gained from surfacing a retiree eligibility engine's output |
| 20% | Reduction in management reporting effort through executive frameworks |
Fifteen years, two directorships, one institution
Director, Platform Migrations, Enterprise Health & Welfare
- Led 5 strategic client migrations representing 100,000+ eligible employees and 5 platform implementations totaling 175,000 employees, covering 275,000 employees across 10 enterprise engagements.
- Guided 100% of clients onto Fidelity standards through influence and negotiation, with clients accepting 92% of proposed standards. The remaining 8% directed enterprise investment toward experience enhancements benefiting the entire book of business.
- Steer end-to-end migration strategy for enterprise health and welfare platforms, setting multi-year architectural direction from discovery through execution.
- Serve as executive advisor to C-suite client and vendor stakeholders, arbitrating high-stakes tradeoffs across regulatory exposure, platform capability, and client experience.
- Engineer 3–5 year capability-adoption roadmaps aligning client strategy to platform investment, converting migrations from cost events into expansion.
- Architect migration risk models spanning data integrity, operational readiness, and adoption, safeguarding retention at the highest-risk moment in the client lifecycle.
- Drive cross-functional alignment across Product, Engineering, Compliance, Operations, and Delivery, converting competing functional priorities into a single scalable roadmap.
Director, Client Services Manager
- Steered a $6M annual recurring revenue portfolio of four strategic health and welfare enterprise clients serving 16,000+ end users, owning full accountability for retention, satisfaction, and growth.
- Held revenue ownership of $1–2M ARR per strategic client, engineering account strategy that balanced service margin against expansion investment.
- Directed a 50-person matrixed organization spanning Analysts, Project Management, Configuration, Quality Assurance (QA), Case Management, and Specialty Services, approximately 75% India-based, leading entirely through strategic influence rather than direct authority.
- Surfaced and enabled platform-expansion opportunities mapped to client business strategy, driving adoption depth and incremental revenue within the existing book.
- Instituted portfolio-level analytics that surfaced service risk before it reached the client, converting reactive escalation management into proactive retention defense.
Selected impact
- Re-engineered funding and operational controls to eliminate 95% of recurring defects, stabilizing service delivery across 16,000+ end users.
- Established root-cause analysis and solution-design frameworks that cut client escalations by an average of 90% across the portfolio, replacing training-based remediation with structural fixes.
- Built executive reporting frameworks that cut management reporting effort 20% while measurably sharpening senior decision speed.
Standard as a growth strategy
No client was ever told no.
Every client adopted Fidelity standards. Through influence and negotiation rather than refusal, clients accepted 92% of the standards put forward while keeping support for the needs that genuinely made them different. Refusal costs you the relationship. Unlimited customization costs you the business. The work is finding the third path, and doing it without the client ever feeling denied.
The remaining 8% was not a concession. It was a roadmap. Those exceptions told the business precisely where to invest in experience enhancements, and those enhancements then benefited the entire book of business rather than only the client who asked. Deviation, read correctly, is product intelligence.
Containing custom build also changed what the organization could take on. Migrations that would have demanded bespoke engineering became repeatable, which meant the business could pursue larger migration clients it previously could not support. Standard adoption is a capacity strategy wearing a delivery metric's clothes.
Clients got the better end of it. Consistent integration and structure across the book means service interactions behave predictably, the same answer and the same flow every time, which is what actually moves NPS. The standard was never a constraint imposed on them. It was the reason their people had a better experience.
How I design an operating model
Four rules I apply before approving a solution. Each one came from watching the alternative fail first.
Put the decision where it belongs.
A process that depends on a person remembering to ask the right question at the right moment is not a process. It is a hope. When something fails repeatedly, I move the decision earlier and out of the conversation entirely, rather than stacking another layer of documentation behind it.
Fix the system before you fix the people.
Training, coaching, and performance plans are the expensive way to discover that the operating model is wrong. When the same error recurs across different people, the people are not the variable.
Make the system show its work.
Accuracy without visibility does not build trust. An answer nobody can trace is an answer they will re-check by hand, which means the automation saved no one anything. Every outcome should be auditable back to the rule that produced it.
Design for the worst day of someone's week.
Benefits decisions get made by people who are being laid off, retiring, or dealing with illness. The standard is not whether a trained representative can navigate the process. It is whether someone under stress gets it right the first time, without knowing they needed to.
The principles, applied
Moving a decision out of the call
A severance program with a single election at its center. An employee leaving the company had to choose: take severance, or transition to retiree healthcare if eligible. Choose severance, and a second question followed immediately. Did they want to continue coverage under the Consolidated Omnibus Budget Reconciliation Act (COBRA) for the remainder of the coverage period, at a stated cost?
One election. Three downstream outcomes. All of it riding on a single moment in a phone call.
The call center handled this conversation thousands of times. Most of the time the representative captured it correctly. Often enough, they did not, and the employee found out weeks later at the worst possible moment, when COBRA coverage had quietly lapsed or no one had confirmed the transition to retiree healthcare. The pattern was close to guaranteed. Severance ended. The phone rang.
Operational cost- Election captured verbally, mid-call, by a representative
- No reliable record of what was confirmed
- Coverage gaps discovered weeks later by the employee
- Remediated with training and performance plans
- Election made first, in a guided digital flow
- Every choice recorded at the moment it was made
- Coverage continuity confirmed before severance began
- Remediated by rebuilding where the decision lived
The organization's first instinct was to fix the people. Training was rebuilt, coaching increased, performance plans went out to representatives who kept missing the step. None of it moved the number. I stopped the remediation and reframed the problem: it was never the representative. It was an operating model that depended on a person remembering to ask a question correctly, every single time, leaving no record behind when they didn't.
Instead of asking how to make the call center more reliable, I asked where the decision should actually live. The answer wasn't later in the process with better documentation. It was earlier, and outside the call entirely.
The election moved to the first step. A guided digital flow walked the employee through the choice before severance began processing. It was available to the employee directly and to the representative, presented identically in both places, with the cost of each path stated plainly, and it required an answer before anything else moved forward.
The outcomeEscalations tied to this decision dropped 93%. Not because the people got better at their jobs, but because the system stopped depending on a human catching something it was never built to reliably catch.
Making an engine show its work
Eligibility and benefit amount depended on years of service, age bands, and date of hire. In combination, these produced roughly fifteen distinct outcomes for any given employee.
That complexity was not a plan sponsor's abstract problem. It showed up in real conversations, with real people, asking a real question at the worst possible time to get it wrong: what am I actually eligible for?
A representative on the phone in real time could not reliably work fifteen variable combinations and land on the right answer. Most cases escalated to a back-office research team, and even then the answer sometimes came back wrong. The complexity didn't disappear when a more senior person looked at it. It moved to a different desk.
Operational cost- Rules engine existed, but ran invisibly behind the scenes
- Staff cross-referenced variables by hand
- Errors persisted even after escalation to research
- No way to verify how an answer was reached
- Same engine, now surfacing a clear, presentable answer
- A single eligibility indicator visible on every tool
- Internal and client-facing tools showing an identical answer
- Every outcome auditable back to the underlying rule
The fix wasn't new technology. A rules engine capable of mapping all fifteen combinations was already in place before the engagement began. It ran quietly in the background, producing an answer no one downstream could see or use.
I directed the work at making the engine show its work. Rather than replacing the system, we rebuilt how its output reached the people who needed it, surfacing a clear eligibility indicator on internal tools and the client-facing portal alike. The same answer, in the same place, every time, whether a representative, a researcher, or the employee was asking.
Auditability mattered as much as accuracy. Every outcome traced back to the specific rule that produced it, because confidence in the answer was the goal rather than a faster lookup. A plan sponsor or a representative needed to trust the number enough to act on it without re-checking by hand, and trust requires seeing how a conclusion was reached.
Self-service followed naturally. Once the output was visible and reliable, the same logic became the backbone of a modeling tool that let employees explore their own eligibility scenarios with no representative involved at all.
The outcomeNet Promoter Score rose five points on this single change. Calls shifted from searching for an answer to confirming one. Plan sponsors gained confidence not because the technology was new, but because for the first time everyone was looking at the same answer and could see how it was reached.
Leading delivery I don't own
The organization behind my portfolio has been majority India-based for most of the last decade. This is not a global team as an org-chart footnote. I staffed, directed, and held the standard for an offshore-majority delivery organization across time zones and eight functions, without a single direct report.
Functions directed: Analysts / Project Management / Configuration / Quality Assurance / Case Management / Specialty Services / Migration & Implementation / Relationship Management
Four mentees at a time
Since 2015 I have kept a continuous mentoring practice of four concurrent mentees spanning client management, operations, and specialty functions. The focus is in-role development and moving people into the roles they actually wanted, anywhere in the enterprise rather than only within my own function.
Multiple mentees have gone on to win the President's Circle, the same award I received for client delivery. Developing people to the standard you were recognized against is the credential I am proudest of.
Capability and credentials
Where I operateRevenue & Portfolio
- Retention and expansion strategy
- Recurring-revenue ownership
- Executive client advisory
- Voice of the customer
Platform & Delivery
- Enterprise migration strategy
- Implementation leadership
- Operating model redesign
- Platform governance
Organization
- Matrixed and global team leadership
- Service Level Agreement (SLA) performance
- Risk and tradeoff analysis
- Leadership development