A benefits communication budget is a build-versus-buy choice. Build means headcount: writers, channel operations, and someone who can measure what happened. Buy means a platform and a partner who keep a calendar when your team is in open enrollment or out on leave. Compare the paths on reach, continuity, and proof. This post does not include a price table. Invented dollars would be fiction. Use the questions below to price either path in your own market.
The tool difference is laid out in portal versus communication platform. Proof standards are in how to measure communication ROI. The program you are funding should match a real benefits communication strategy, with a calendar and an owner. Product detail for a buy path sits on the solution page and the cost conversation continues at ROI.
What build actually includes
Build means people. Someone who can write a deductible sentence an employee will finish. Someone who can run email, text, and print without dropping consent rules. Someone who can pull completion by segment and put it on one page. Someone who can update the library when a network changes on a Thursday.
Those jobs can live in one person at a small employer and in a team at a large one. Either way, write them down. A budget that funds a design tool and assumes HR generalists will "fit communication in" has funded a template. The March send still needs a person. Generalists will do the urgent notice and skip March. March is where continuity dies.
Build also includes the boring stack. A place to store approved copy. A list of personal emails and SMS consent. A no-login page. A way to see which site was not on the send. If you already own pieces of that stack, count only the gaps. If you own none of it, the headcount estimate should include the first year of setup and the steady state. Setup is when programs stall.
The risk unique to build is concentration. When the person who knows the calendar leaves, the program leaves with them. Budget a backup: documented templates, a shared calendar, and a second approver. If you will not fund the backup, you are renting the program from one employee. Say that in the proposal so leadership hears the continuity risk before it happens.
What buy actually includes
Buy is a platform plus a partner who will run a cadence. LinQed Online is that kind of system: discovery, a 12-month blueprint, approved messages, and delivery to the channels your workforce actually uses. You still own plan facts, eligibility, and approvals. You should not be staffing a newsroom.
Ask what is in the fee and what is a project. The annual calendar. The no-login pages. Language support. Manager cards. Reporting by segment. A human who reviews the file with you. Implementation help. If a line is extra, you want to know before renewal season, when every extra feels mandatory. A low headline fee with every send priced as a change order is a different purchase from a cadence that is in the scope.
Buy fails when the client disappears. Approvals that sit for weeks, eligibility files that never arrive, and goals that change every call will stall a partner the same way they stall an employee. Budget the internal time to approve. It is smaller than building the whole engine. Put a number of hours on that line. Name the approver in the same document as the purchase request.
Compare reach, continuity, and proof
Reach: which path can put an important message in front of frontline employees and households inside 48 hours? A build that is an email platform will reproduce the email-only problem with internal staff. A buy that only posts to a portal will do the same. Ask both paths to describe the deskless and household route. Score both paths on Reach Equity™: a fair chance for every group to see the message.
Continuity: which path still sends in April if the benefits manager is in open-enrollment recovery or has left the company? Build needs a second person and a calendar that is not in someone's head. Buy needs a partner whose job is the calendar and a client approver who can answer. Score both honestly. A partner with no approver is not continuous. An employee with no backup is not continuous.
Proof: which path will put completion by segment and a reach gap on one page twice a year? If build, who has the skill and the hour? If buy, is the report in the scope, and does it match the way you talk to the CFO? A path that ends in open rates has not finished the job. Read the ROI post before you write the requirement, so the vendor response and the internal proposal aim at the same evidence.
Questions to price either path
How many audiences do we have that email does not cover? What does it cost to collect and maintain consent and personal contact data? Who writes, and what happens when they are out? Who approves a number about cost, and how fast? What do we need on paper for a required notice versus an ordinary reminder? Which report will we hand the CFO in November?
For build, price salary, benefits load, tools, and the backup. For buy, price the annual scope, implementation, and the internal hours for approvals. Put the two totals next to each other with the three comparisons. Leave industry benchmarks out unless you can source them. Your finance partner can smell a fake table. They can also fund a clear one.
Decide for a year, with a review at the second CFO page. If build cannot show reach beyond email by then, the headcount is writing for the people you already reach. If buy cannot show a cadence and a segment report, you bought a login. Either result is useful. The budget conversation is how you avoid discovering it by accident. When you want the buy side explained against your segments, start at solution and ROI, then talk with us.
Key takeaways
- Build funds writers, channel operations, measurement, and a backup so the program survives turnover.
- Buy funds a platform and a partner with a calendar. You still approve facts.
- Compare reach, continuity, and proof. Skip a fake dollar table.
- An email tool with internal staff can still miss the floor and the household.
- Price internal approval time on the buy path. It is smaller than a newsroom and it is not zero.
- Review the choice when the second leadership report is due.
Frequently asked questions
Is build always more expensive?
Price headcount, tools, and backup on one side and scope plus approval time on the other. Then compare reach, continuity, and proof. A path that only hits inboxes is a different product from a path that reaches the floor and the household. There is no universal price in this post.
Can we build now and buy later?
Yes, if you are honest about continuity. Document the calendar, the library, and the consent list so they are not trapped with one employee. Many teams buy when they see that April goes silent every time enrollment ends.
What should we refuse to pay for?
A portal login described as a communication program. A report that only shows opens. A scope that charges every ordinary monthly note as a custom project. Pay for reach beyond the desk, a cadence, and proof a CFO can read.
Who has to be in the budget meeting?
Benefits, the person who will approve copy, and finance. If frontline reach is the reason for the request, bring one operator who can describe how a message gets to a shift. A meeting of brand stakeholders will fund a look. Bring an operator if you need a path to the shift.
Compare build and buy on reach, continuity, and proof. Price both paths with the same questions.
A co-founder of Touchpoints with two decades of experience in employee benefits communication. He partners hands-on with benefits firms and employers nationwide to build strategies that deliver real outcomes.
