The Employer Health-Plan Proposal: When the CFO Reads the Premium First

The Split-Screen Audience Every Plan Has to Satisfy

There is no single buyer for an employer health-plan proposal. The deck lands on a table — sometimes physically, sometimes as a shared link — and the first person to open it is rarely the person who signs it. HR benefits managers scan for engagement features and employee experience signals. Finance directors flip to the premium summary and stop reading. The CFO, if the proposal makes it to that desk, checks the renewal variance from the incumbent carrier and the stop-loss attachment point. If any one of these readers hits a reason to stop, the deck is dead regardless of what the other two see. This is the core friction point of the employer health-plan pitch: the deck must be structured so that each constituency finds its own proof point within three slides, yet the narrative holds together as a single argument. Leading with network size or a wellness app feature is the fastest way to lose the financial reader. Leading with a premium discount is the fastest way to make HR suspicious that benefits are being cut. The opening slide must acknowledge the split-screen reality. A clear, upfront statement of total cost of coverage — from premium through expected out-of-pocket — gives every reader a shared reference frame. After that, the deck branches into the evidence each stakeholder needs, but it never asks them to wait past slide three for their core question to be addressed.

Why the Open-Enrollment Cycle Magnifies Every Mistake

Employer health-plan decisions operate on a fixed annual cycle. The RFP goes out in late summer. Proposals are due by October. Final selections are presented to the benefits committee in November. Open enrollment runs in December or January. That means there is no second-chance window for the deck’s mistakes. A confused benefits committee does not come back next week for a do-over; the plan is either selected or it is shelved until the next cycle, and the incumbent carrier almost always wins the default renewal. The regulatory layer here is the Employee Retirement Income Security Act of 1974 (ERISA), which governs how employer-sponsored plans are communicated to participants. Any slide that makes a coverage promise must match the Summary Plan Description language, or the employer’s legal risk spikes. The deck is being read through a compliance lens from the start, not just a financial one. The Affordable Care Act’s employer mandate, plus state-level requirements for network adequacy and essential health benefits, add additional layers of specificity. A proposal that hand-waves about ‘comprehensive coverage’ without naming the metal tier, the provider network type (EPO, HMO, PPO, POS), and the out-of-pocket maximum will be flagged by the benefits consultant in the room — and every employer of significant size has a benefits consultant on retainer. That consultant is not a friendly reader; they are a professional at comparing proposals. The deck’s credibility lives or dies on how well it preempts that comparison.

The Sequence That Survives Committee Review

The Business Case / Cost-Justification Arc dictates a specific sequence that does not follow the order of the carrier’s product brochure. Start with the baseline. The employer already has a current plan year’s claims experience, a current per-employee-per-month premium, and a current employee satisfaction score. Slide one states that baseline and names the problem — cost trend, access gaps, engagement deficits — that the proposal addresses. Do not name your solution first. The committee needs to agree on the problem before they can evaluate your fix. Slide two introduces the proposed plan structure: the metal tier, the premium, the deductible range, the out-of-pocket maximum, and the network type. This is the slide the CFO will interrogate. Keep it to one page, with a clear comparison table versus the current plan. Every number must have a source, and the source must be recognizable to the employer’s benefits team — CMS benchmark data, the carrier’s own rate filing, or a third-party actuarial report. Slide three addresses network adequacy. Show the employer’s primary service area, list every in-network hospital and the top five specialty groups by volume, and flag any gap with an honest explanation and a mitigation plan. This slide kills more proposals than any premium discussion because a missing pediatric endocrinologist or an out-of-network oncology center creates a member-experience risk the committee cannot accept. Slide four moves to employee engagement: wellness incentives, telehealth utilization projections, chronic disease management programs. HR reads this slide. Slide five is the financial model: the projected total cost of care for the employer’s population under the proposed plan versus the current plan, using their actual claims data. This appendix-level modeling must match how the employer’s actuary would run the numbers. If the deck projects savings without showing the assumptions — utilization trend, unit cost trend, risk adjustment — the deck goes back for ‘more analysis’ and dies in the cycle.

When the Proposal Needs Actuarial Depth Your Team Doesn't Have

Building a credible employer health-plan proposal requires two capabilities most insurance brokers and health-plan startups lack in-house: actuarial modeling and benefits-communication compliance. The deck’s financial slides need to reflect the employer’s specific demographic mix and claims experience, not a generic national benchmark. That means the team producing the deck has to either own or license an actuarial tool that can run the numbers at the group level, or partner with a third-party actuary who can validate the model. Presentation Gurus has structured these proposals for clients ranging from regional HMOs entering new employer markets to digital-health startups submitting their first self-funded plan design. The craft gap is not in slide design — it is in the translation of dense financial and regulatory material into a decision-ready narrative that every committee member can follow to their own conclusion. A work order for this deck type typically includes building the baseline problem statement, the comparative financial model, the network adequacy documentation, and the compliance-language alignment with ERISA and ACA requirements. The deck is submitted as a presentation deck with a separate financial appendix that the committee’s benefits consultant can pull into their own analysis tool. Without that appendix, the proposal gets treated as a marketing brochure, not a serious bid.

The Committee Does Not Read Linearly — The Arc Has to Account for That

The Business Case / Cost-Justification Arc for an employer health-plan proposal does not assume the audience sits through slide one through slide fifteen in order. The benefits director forwards the deck to the CFO with a note that says, ‘look at the premium page.’ The CFO skims to that page, checks the number, and either reads the rest or deletes the email. The narrative functions as an asynchronous decision tree. The first two slides must establish the problem and the solution so that anyone reading them can decide whether to invest the next twenty minutes. From there, each major section — network, engagement, financial model, implementation timeline — must be self-contained enough to be read in isolation if a committee member arrives late or skips ahead. The deck compresses a feasibility study, a regulatory filing, and a value proposition into an architecture designed for interruption. The most effective version of this arc starts with a one-slide executive summary that states the baseline cost, the proposed premium, the projected total cost of care savings, and the single most material coverage change. That slide is the only slide every committee member will read. Everything else is evidence, available on demand, structured so that any page can be the last page the reader sees without leaving a hanging question. The deck prompts the audience to verify a quantitative proposition directly against their plan data. Giving evaluators immediate control over that verification is what ultimately survives committee review.