Lifecycle Marketing

For a long time, sending an email meant sending the same text to the whole list. One message went out whether the reader signed up yesterday or had been using the product for a year.

Pagedeck started that way. A note announcing the paid plan went to everyone, so customers already on the team plan wrote back to say they were already paying, and people who had signed up a day earlier and hadn't created a single document got a billing pitch as their first contact. Unsubscribes that week ran four times the usual rate.

The problem isn't that the writing was bad; it's that the position was wrong. The same sentence is useful guidance to someone weighing a purchase and a premature demand to someone who hasn't tried the product yet. One message leaves the sender, but it gets read from wherever each reader happens to be standing.

Lifecycle marketing starts by refusing to treat the list as one thing. People who only signed up, people trying it alone, people who have pulled their team in, people who pay, and people who stopped showing up each get something different. Deciding who is standing where comes before deciding what to send.

Split customers into stages by behaviour, pick the one thing each stage needs in order to reach the next one, and send only that.

1. Define stages by behaviour. Not by job title or company size, but by what someone has done inside the product. At Pagedeck the stages are signed up only, created one document, invited a teammate, started paying, and hasn't logged in for two weeks. Behaviour decides what to say next on its own; a job title doesn't. Knowing someone runs a design team says nothing about whether they need a nudge to open their first document or an invoice.
2. Pick one gate per stage. What a newly signed-up person needs is not a billing pitch but a first document. Onboarding, the work of helping a new user settle into the product, attaches here, and clearing activation — the point where someone first feels what the product is worth — becomes the goal for this stretch. Hang two gates on one stage and the messages point in two directions, blurring both.
3. Attach a mechanism and a timing to each gate. A triggered message fires the moment a behaviour happens, a drip campaign goes out on fixed intervals, and personalization fills different content in for different people. Right after someone creates their first document a trigger fits, because the message arrives while they are still in the product. For someone who has done nothing yet, a drip three days apart fits better, since there is no behaviour to fire on.
4. Read results as stage movement. Open rates tell you only whether the subject line worked. What percentage of people who signed up created a document, and what percentage of those invited a teammate, read stage by stage, shows which box people are stuck in.

It shows up most in products people start using for free and pay for later. The distance between signing up and paying is long, and there are several places a person passes through on the way, which is what makes splitting into stages worth the effort.

Five positions fall out at Pagedeck. Right after signup a note explains what to try first. Someone who has done nothing by day three gets a message asking them to create one document. Someone who has invited a teammate hears about the features built for shared work. Someone three days from the end of a trial sees how many documents they've made so far alongside the case for paying. And anyone quiet for two weeks moves into the dormant user group and hears about one feature added since they left.

What happens after someone leaves counts as a stage too. Winback covers customers who cancelled and are fully gone, and it sits apart from the dormant group because the two need different arguments. A quiet user is often won back by one feature they never tried; someone who already left won't return unless the reason they left is visibly fixed, which usually means naming the change rather than offering a discount.

There are cases where it doesn't fit. A product bought once has no stages to speak of, so the design spins in place. Early on, before enough behaviour has accumulated, there's no basis for five stages either — split into two, people who only signed up and people who have used it, and cut further once you can see where churn concentrates.

"Let's not blast this one. Send it only to people who haven't created a document yet."

Cutting the list by stage and mailing only the people in that stage.

"The billing push starts with activated users. Send it to sign-ups and all we get is unsubscribes."

Pushing a later gate's message at people who haven't cleared the earlier one backfires.

"Only 12 percent move on from this stage — let's fix this one first."

Reading stage-to-stage movement and starting with the most blocked stretch.

The week after that blast, Ravi split the Pagedeck list into five stages. He set the boundaries with Mia and took the activation definition the product team already used — one document created and shared — rather than writing a new one. Two definitions would have meant two different counts of activated users turning up in the same meeting.

Three months on, the unsubscribe rate was a third of what it had been, and what grew wasn't the number of sends but the number of sends that fit the reader. One blast disappeared and six stage-specific messages took its place.

People often read the stages as marketing's call to make. Marketing sends the messages, so drawing the boundaries looks like marketing's job too. But stage boundaries are set by in-product behaviour, and that behaviour follows the product team's definitions. Let both teams write their own and the number of activated users shows up twice in one meeting, and the time goes into arguing which figure to decide on.

The other common reading is that installing a message automation tool is lifecycle marketing. The tool draws stages and branches on screen, which makes the design look finished. The tool is plumbing; the design lives in how the stages are defined. Automate without splitting the stages and you have automated sending the same four messages three days apart to everyone, and the numbers land where they were during the blast era.