The Seedling Model for Going Multi-Product

Core principles

• 01Give new fires air to grow — keep seedlings organizationally separate from mature products so their roadmaps aren't crowded out
• 02Treat each new product as a seed-stage company: dedicated squad, angel-investor mindset, periodic reinvestment decisions
• 03Expand into adjacencies just beyond the core — a new product line for an adjacent segment, not just another feature
• 04Prefer bets you can de-risk with existing traction and where you hold a distribution advantage
• 05Build products people love and let revenue be the byproduct; don't revenue-optimize at launch
• 06Anchor customer obsession back to the business — a want that can't sustain a viable business isn't a product

How to run it

1. 1

   Separate seedlings into their own org

   Create a distinct expansion org so new product areas aren't structurally close to core banking/payments, whose maintenance and higher-impact work would otherwise always trump the seedling's roadmap.

   Pro tip Run the new teams on a different cadence — two-week sprints and weekly check-ins instead of the core's monthly cycles — to stay nimble and learn-iterate-repeat.

   Watch out Keeping new bets inside the mature org lets the 'gravitational force' of the mature product starve them of prioritization and space.

2. 2

   Staff each bet like a seed company

   Give it a full cross-functional squad (eng, design, product, data science), borrowing central teams (CS, risk, ops) unless dedicated support is needed. Size to the opportunity — a whole new personal-banking market got ~3x the engineers of an invoicing bet built atop existing banking.

   Pro tip Give teams 'just enough' resources but make them stretch.

   Watch out Trying too many things at once and understaffing each is a classic misstep — the seedling never gets enough hands to survive.

3. 3

   Select products by adjacency, de-risk signal, and distribution

   Look for an adjacent customer segment wanting a fuller product (not a mere feature), evidence of existing demand you can point to, and a distribution advantage where you can reach users inside your current product without a full go-to-market.

   Pro tip Surface the new product inside the natural flow of the existing one (e.g. highlight Bill Pay when a user sends a complex vendor payment).

4. 4

   Reinvest on a quarterly/half-yearly review

   Every quarter or half, decide whether to keep investing. Set goals and financial projections, but weight learnings heavily like an angel investment — if a goal is missed, ask what key learning still points toward success in the next six months. There's no forced return to the core until the line becomes a 'Series C' business in its own right.

   Watch out Don't kill a bet purely for missing a number early — but do demand a clear learning that keeps it pointed at success.

5. 5

   Give it away free, then monetize complexity

   After launch, don't jump to revenue optimization. Give the second/third product away free to drive usage, engagement and retention; keep core money movement and basic functionality always free. Charge only when the customer needs real added complexity, and only for the ICP at the complex end of the scale.

   Pro tip Run a real willingness-to-pay process and put a genuine price in front of the ICP — a price is itself a test of product value and fit.

   Watch out Slapping a paywall on at launch ('now you have to pay us') breaks trust; monetize when the customer journey reaches genuine complexity (often 6–18 months into a business).

In the wild

Common mistakes

Is it for you?

From the transcript