Back to blog
Engineering

The 7-minute lifecycle stack: what changed in 2026

What used to be a quarterly project is now a coffee-break install. Here's the new minimum-viable lifecycle setup for a PLG founder.

Aiko Tanaka
Head of Growth, Foldspace
· 4 min read
Engineering4 min read
#stack#dx#plg

The old stack

A 2022-era lifecycle program looked like this:

  • A warehouse (1–2 weeks to set up)
  • A CDP to model identity (1 week, plus integrations)
  • An ESP for sending (3 days, plus deliverability)
  • A prompt or template library (forever)
  • A growth engineer to glue it all together

Total: ~6 weeks before the first useful email went out.

The new stack

The new stack is a single loop with three jobs:

  1. 1Capture — events, identities, product context (one SDK)
  2. 2Decide — score intent and pick the next-best message (one model)
  3. 3Deliver — send and learn from the response (one channel for now)

That's it. No warehouse, no CDP layer, no template editor.

A reasonable 7-minute install

npm i @vibefollow/sdk
import { vf } from "@vibefollow/sdk"

vf.identify(user.id, { email: user.email, plan: "trial" })
vf.track("connected_data_source", { type: "postgres" })

You're done. Voice-note your positioning, and the next email reflects it.

Why this matters

The cost of running a thoughtful lifecycle program collapsed by ~95% this year. That doesn't mean lifecycle is solved — it means the bottleneck moved from infrastructure to taste.

The teams that win the next 12 months will be the ones who use that newly-freed time to actually talk to customers and update positioning weekly, not quarterly.

Tagged#stack#dx#plg
Aiko Tanaka
Head of Growth, Foldspace

Writes about lifecycle, intent, and what changes when AI gets the keys to the funnel.

Keep reading

All posts