BlackRock's tailored 401(k) default moves the income call earlier

BlackRock is developing customizable funds for corporate 401(k) plans that could combine public stocks and bonds with private assets and annuities written to provide guaranteed retirement income, AdvisorHub reported in its market brief. The design breaks with the conventional starting point of putting every participant into the same target-date glide path; instead, BlackRock would work with individual employers to tailor portfolios around employee demographics, wages and retirement behavior.

Advisors should read that as a plan-menu story, because most of them touch defined contribution twice: once on the way in, when they sit across from a participant or a sponsor, and once on the way out, when the balance rolls to an IRA and becomes billable. It is the second touch this puts in question, because if a worker's default already carries a guaranteed income component, the rollover conversation no longer opens with how to build an income floor but with what the floor does not cover.

That is a narrower opening than advisors are used to, and it arrives earlier than the client expects: a retiree who has spent thirty years never logging into the recordkeeper's website reaches sixty-five with an income stream already running, an asset allocation somebody else set, and no invoice attached to either. The advisory work does not disappear at that point; it changes shape, and the advisor who shows up at the rollover without an answer for the gaps will be re-litigating a decision the plan already made.

Customization by workforce is a different product philosophy from a glide path, which is one answer for an entire population; the brief names the inputs BlackRock would use, and demographics, wages and retirement behavior are all properties of a single employer's headcount rather than a national average. A sponsor weighing a default like this is comparing assumptions about its own workforce, which likely pushes the diligence upstream into employment data and away from a quarterly fund scorecard. That is a place many advisory practices are not staffed to stand.

The private sleeve drags in the questions advisors already ask in client accounts, and AdvisorHub frames the capital consequence plainly: strategies previously concentrated in pensions and institutional portfolios would reach millions of workers if the approach is widely adopted, becoming a potentially enormous new source of capital for private markets. What the brief does not say is what vehicle would hold the private assets, what the all-in cost would be, or how it would be valued. Those are the same questions that sit at the center of advisor due diligence since August's launch cycle, when wrapper and fee disclosure moved to the front of the packet. Put a private sleeve inside a retirement default and the audience for that answer stops being a due-diligence committee and becomes every participant who never reads a prospectus.

Tailoring at the plan level also follows a habit RIAs built in their own books this year, letting outside managers into a provider's own models instead of accepting a single house answer. Vanguard's August decision to open four model portfolios to outside fund choices showed how far the habit had spread on the advisory side. A plan default is the same idea with more force behind it, because a default is the option a participant lands in by doing nothing, and the workers least likely to seek advice are precisely the ones whose income floor would be set by someone else's model.

The last mile of retirement is an income, health-cost and benefit-claiming problem rather than a savings problem, and a guaranteed sleeve inside the default sharpens that position instead of softening it. The easy half of the decumulation case, buying the participant an income floor, becomes something a plan can hand over at zero decision cost. What remains is the harder half, and it stays advisor work: when to claim Social Security, what a survivor needs, how health costs land against a fixed payment stream, and how to sequence withdrawals around a floor that no longer has to be manufactured.

The initiative does not shrink the advisory opportunity; it relocates it, and there is a real argument that the relocation is good for clients and awkward for practices that priced themselves on the floor. A guaranteed income component inside the 401(k) sits below the level at which most advisory fees are charged, which means the fee has to be justified by planning above and around it rather than by an insurance decision the plan got to first. Practices that build decumulation and protected-income budgets are positioned for that shift, while practices whose retirement offering is a rollover and a model portfolio are about to be compared against a default that costs the client nothing extra to keep.

The strategic bet underneath all of it is worth pricing honestly, because an offering built on employer-specific tailoring concentrates the distribution burden on plan sponsor relationships rather than participant adoption, and the prize being contested is the default slot itself, where assets sit untouched for decades. That is a business that will be won in a small number of sponsor conversations, not on a fund platform. It also means the initiative's reach depends on a fact the brief does not provide, which is how many employers want a default built around their own workforce rather than a familiar glide path with a decade of committee minutes behind it.

For advisors, the near-term move is unglamorous: ask the sponsors you work with whether they have been approached, and be ready to compare a tailored default against the target-date option they run today on the two axes that decide defaults: what it costs and what the participant does in a bad quarter. The participant-side work is to find out what is already sitting in a client's plan before building the retirement income plan, because the floor may already exist and the sequencing question has moved to the front of the file.

Watch for the first sponsor that asks to see its own headcount modeled against the default it runs today. That request is the one that tells you the menu has stopped being a menu.