Owned-Channel Lifecycle Officer
Owns the owned channel as a share of revenue. The Lifecycle Officer FTE plans the email and SMS program — the calendar, the campaigns, the holdouts and the frequency budget across everything the list receives — and reports owned-channel revenue against a printed attribution window with a holdout behind every claim. It works beside the Retention FTE, which runs the behaviour-triggered flows: one role owns the program and its number, the other owns the flows. Every campaign waits for your approval and stays inside the cap.
Accountable for
Owned-channel share of revenue, every send approved, every claim with a holdout
Judged on · Owned-channel share of revenue
What it does not do · It does not send without approval, cannot exceed the frequency cap or message the suppression list, and does not claim revenue it cannot show against a holdout.
It proposes · you approve · every claim carries its evidence
Workspace · Lifecycle Officer FTE
Lifecycle Officer FTE
Owned-Channel Lifecycle Officer
Waiting on you · Campaign · needs your approval
Proposed · inside the frequency budgetMid-season edit · Thursday · 48k recipients after cap and suppression
Preview per device · segment · cap applied · holdout size · attribution window printed
Yesterday: 1 campaign sent on approval, holdout results posted for last month's two campaigns.
A whole job function, not a task queue. Lifecycle Officer holds the role, the targets and the budget you set, and reports to you on the numbers below.
Owns
Reports on
Needs from you
It reports in first, does the work, hands it over for approval, and measures what happened. You review it the way you review a direct report.
Campaigns, flows and holdouts on one calendar with the frequency budget applied.
Previewed per device, segment size after cap and suppression, holdout size, window printed.
Warnings turned into cautious proposals, never silent.
Owned-channel revenue as a share of the total, against the printed window, with holdout results.
Lifecycle Officer reports into a workspace built for a manager, not an operator. Four of its tabs, drawn as they work.
Today
What is waiting on you comes first, then yesterday, what it noticed, and spend against budget. Read it in a minute.
Workspace · Lifecycle Officer FTE · Today
Morning brief · Monday 08:00
Yesterday: 1 campaign sent on approval, holdout results posted for last month's two campaigns.
Waiting on you
2 to reviewApprovals
Every publish, send or spend waits here with its verdict, its reasons and its evidence. Approve, or send it back with a note.
Workspace · Lifecycle Officer FTE · Approvals
Approvals
1 waiting on you
Lifecycle Officer FTE · Campaign · needs your approval
Proposed · inside the frequency budgetMid-season edit · Thursday · 48k recipients after cap and suppression
Preview per device · segment · cap applied · holdout size · attribution window printed
Performance
KPIs are measured, never estimated. Anything not connected yet is shown as unmeasured, not filled in.
Workspace · Lifecycle Officer FTE · Performance
Owned-channel share · 12 weeks
Measured, not estimated
Targets
Each target carries a status and its evidence. It can propose new targets; they wait for your approval.
Workspace · Lifecycle Officer FTE · Targets
Owned-channel share of revenue above 30%
31% · window printed
Every campaign inside the frequency budget
6,200 held to Saturday · 0 breaches
A holdout behind every revenue claim
3 running · 1 campaign without one
Add a holdout to the welcome campaign
FTE-suggested · awaiting your approval
Illustrative workspace frames · the tabs, verdicts and statuses are real product surfaces; the figures are samples.
Owns the owned channel as a share of revenue. The Lifecycle Officer FTE plans the email and SMS program — the calendar, the campaigns, the holdouts and the frequency budget across everything the list receives — and reports owned-channel revenue against a printed attribution window with a holdout behind every claim. It works beside the Retention FTE, which runs the behaviour-triggered flows: one role owns the program and its number, the other owns the flows. Every campaign waits for your approval and stays inside the cap.
The whole program on one calendar with the frequency budget applied, so flows and campaigns never collide
A holdout behind every revenue claim, and the attribution window printed on every report
Works beside the Retention FTE: it owns the program and the number; the Retention FTE owns the flows
Skills
Beyond the weekly routine, you give it missions: a goal, a scope, a deadline, and progress you can see. Three modes, all of them bounded.
A bounded calendar with the frequency budget, holdouts and the Retention FTE's flows accounted for.
Ranked causes: list erosion, deliverability, a paused flow, a campaign that collided.
Share by cohort and category with the program changes it proposes.
Diagnoses arrive as ranked hypotheses with evidence, never as certainties.
Lifecycle Officer connects to the systems below with the permissions you grant, per organization and per property, and nothing more. Connections can be revoked at any time.
Email and SMS
Store platform
Where you review its work
It starts at Level 0 and earns autonomy one step at a time. You grant each level when the evidence says so, and you can take it back at any time.
Proposes only
Every draft, launch, send or spend waits in Approvals. This is where every FTE starts.
Low-risk on its own
You allow routine actions you have approved many times: refreshes, reply drafts, reconciliations that match exactly.
Acts inside caps
It may pause losers, scale winners or publish scheduled work, always inside the budget and rules you set.
Runs the week
Scheduled production runs; you review the brief, the exceptions and the numbers. Any level can be taken back at any time.
Approvals
1 waiting on you
Lifecycle Officer FTE · Campaign · needs your approval
Proposed · inside the frequency budgetMid-season edit · Thursday · 48k recipients after cap and suppression
Preview per device · segment · cap applied · holdout size · attribution window printed
Illustrative approvals queue · budget and spend are always visible beside it.
Instant onboarding: it is on your team the same day you sign up.
Create your organization. Lifecycle Officer is added to your workforce from the link below.
Grant the tools it needs and confirm the targets it proposes. It never asks for what the platform already knows.
Its first brief and first proposals land in Approvals the same day.
Short answers. The docs have the long ones.
The Retention FTE runs the behaviour-triggered flows. The Lifecycle Officer owns the whole owned-channel program, its calendar, its holdouts and its share-of-revenue number.
Nothing that leaves your company. Lifecycle Officer proposes first: every publish, send or spend waits in Approvals with its reasons and evidence. You can grant more autonomy step by step and take it back at any time. Every action is logged.
Plans are token-metered blocks of work, not seats. Every FTE in your organization draws from one wallet whose balance is always visible in the workspace. At zero the FTEs pause; they never overdraw.
Sign up, connect the tools the role needs, and confirm the targets it proposes. Roles marked instant onboarding are working the same day; roles marked custom onboarding are scoped with our team first.
Your data stays scoped to your organization and, where it applies, to the specific property the FTE works on. Integration credentials are encrypted at rest and can be revoked at any time.
Every role holds its own targets and budget; hire one or several, they share one wallet and one workspace.
Customer Intelligence Officer · E-commerce
Instant onboarding
Loyalty Program Officer · E-commerce
Instant onboarding
Lifecycle & Retention Marketer · E-commerce
Instant onboarding
Post-Purchase Support Specialist · E-commerce
Instant onboarding
Sign up, connect the tools it needs, and review its first proposals this week.
