Engineer, CRM Systems & Management

Lifecycle Turns a first order into a second

You own retention as a number: the flows, the segments, and the experiments that turn a first order into a second. A technical role that's growth-led.

Most commerce growth hides in retention, and it's technical enough that a marketer can't own it alone. That system needs one owner, end to end. That's this role.

• Build and ship the flows, segments, and experiments across the lifecycle stack, yourself.
• Model the customer's life after checkout: what actually predicts a second order, where the flows leak, what a segment is worth.
• Read the data underneath Klaviyo and the rest, and trust it only after you've checked it.
• Run retention experiments against a baseline, and kill the ones that don't move it.
• Treat lifecycle as one system, not a folder of automations.
• Report retention as a number the founder can act on, not a send report.

Retention, as a number. The flows, the segments, and the experiments across the lifecycle stack, built and shipped by you. You're technical, but the job is growth‑led: the question is never how many messages went out, it's whether more customers came back.

• You've built lifecycle or CRM systems and got hooked on the experiment results more than the tooling.
• You write real automation and you read your own data.
• You'd rather move a retention curve than launch a campaign.

If you measure the job in sends, campaigns, or how elaborate the flow diagram looks, we'll disagree about how done means. Volume isn’t the point here.

Retention moved, against a baseline. Not messages sent.

Not a resume. One thing you made or moved that speaks to this role. We read every one, and we write back either way.