Guideline · Strategy · Senior · 45 to 60 minutes

How should Guideline launch its first 401(k)?

Guideline is a startup building retirement plans for small and midsize businesses, starting with 401(k) plans. Answer this product management case and get it graded line by line against a weighted rubric.

Strategic thinking
Product judgment
Sequencing
Business modeling
Risk management

The situation

It is 2015. Kevin Busque has left TaskRabbit after spending nearly two years researching why small business 401(k) plans are costly and hard to use. He asks you, the first senior product leader, to help define Guideline's initial product strategy before the team commits its seed capital and engineering time. The signal is strong: TaskRabbit's own plan had only 36% participation despite costing the company more than $20,000 a year, and founders in Kevin's network react strongly to hidden fees, confusing enrollment, and payroll data that still has to be checked after every pay run. But the path is unclear. Guideline could start as a broader benefits platform or focus tightly on 401(k). It could move faster by putting modern software on top of legacy record keepers and plan administrators, or build much more of the stack itself to remove middlemen and reduce ongoing admin work. A few prospective customers want a solution soon. Assume the team has enough funding for one major strategic path, not several parallel bets, and the product must operate in a heavily regulated category.

What to produce

Write a 1 to 2 page product strategy memo for Guideline's founders.

Your answer must

State the core strategic decision and recommend Guideline's initial market scope, including whether to focus only on 401(k) or start broader.
Compare at least two viable product stack approaches, including a lighter partner dependent model and a deeper in house model, across customer value, speed, economics, and compliance implications.
Propose a sequenced 12 month plan that shows what Guideline should build first, what can be manual or outsourced at the start, and what capabilities must be owned early.
Define the target customer and early go to market motion, including how design partners or early customers would be used to validate demand.
Specify 3 to 5 success metrics and the biggest risks, with mitigation steps for each.

Constraints

The category is regulated, so plan administration, filings, and payroll handling cannot be treated as an informal beta.
Small business buyers have little time for repeated manual validation every pay period, so employer admin burden matters as much as participant UX.
Hidden and asset based fees are a central source of customer pain, so any approach that adds middlemen affects both pricing and trust.
The team is small and newly funded, so strategy must balance time to first customer with the risk of building the wrong foundation.

Format

Use clear sections: decision, options, recommendation, 12 month sequence, metrics, risks. A simple comparison table is encouraged.

How Guideline actually played it

Co-founder recounts how a small-business retirement plan startup chose to build its own payroll integrations and productize a manual process, plus the pivots on the way to being acquired. Shows how operational pain turned into product advantage.

Bringing a manual process into software can become the moat
Integrations with partners were a distribution and product decision at once

Built from Guideline's Path to Product-Market Fit: The Early Decisions That Powered Its Acquisition by Gusto by First Round Review.