Guideline as Retirement Operating System

This points to Guideline becoming a retirement operating system, not just a 401(k) vendor. Once payroll data, participant balances, and rollover flows already run through Guideline, adding IRA, SEP IRA, and HSA products is mostly an extension of the same money movement and compliance stack. The common thread is that these accounts can be offered without paying a state or other required intermediary that would eat the economics.

• The IRA is especially strategic because it lets Guideline keep the customer relationship when a worker leaves a job. A former employee can park old 401(k) money in a Guideline IRA, keep it invested, and later roll it back into a new Guideline 401(k), which extends revenue beyond the original employer plan.
  2 sacra
• SEP IRA and HSA fit the same core workflow. They are still tax advantaged contribution accounts funded by employer or employee dollars, and Guideline already handles payroll linked contributions, investing, compliance logic, and participant UX. HSA is also tied to a real pain point, because healthcare is a major driver of hardship withdrawals from retirement accounts.
  2 sacra 4 sacra
• The boundary is where regulation inserts a toll collector. In 529 plans, state sponsorship means a provider like Guideline would have to share 25 to 50 basis points with each state, which makes the unit economics much worse than in IRA, SEP, and HSA, where the company can own more of the product and fee stream directly.
  1 sacra 5 sacra

From here, the product suite should widen around the same pre tax and tax advantaged money flows. The more Guideline can keep savers inside one stack across 401(k), IRA, HSA, and emergency savings, the more it looks less like a point solution for employers and more like the default account system for long term household savings.