Start with the customer's situation
A shop sends its new collection to everyone on the mailing list each Friday. Later, it begins treating a new subscriber, a recent buyer and a long-absent customer differently. The channel is still email. The planning has changed.
Email marketing is the work of using that channel: collecting subscriptions, creating messages, maintaining deliverability and reviewing response. CRM marketing uses information about the customer's relationship with the business to decide who needs a communication, when and for what purpose. Email can be one part of that work.
Lifecycle marketing and retention marketing overlap with this approach, but the labels are less useful than the practical question: what should happen for this customer now?
Software does not write the strategy
A CRM can store customer records, orders and conversations. Some products can send messages and run automated workflows. None of that, on its own, tells a business which relationship to develop or which customer problem to solve.
A lost enquiry from a messenger suggests a process or integration problem. A customer who buys once and never returns calls for a different investigation. Product experience, purchase frequency and communication may all be involved. Buying the same category of software will not settle both questions.
Write one scenario before building ten
Choose an observable action, such as helping a new subscriber place a first order. Then describe the minimum scenario in plain language.
- Who enters the audience, and which data establishes that?
- What event starts the communication?
- What useful action can the customer take?
- What should cancel or stop the message?
- Who checks that the scenario is still working?
Consider a replenishment reminder. The business needs the purchase date and product, an interval supported by the product and purchase history, and rules to exclude people who already reordered, returned the product or unsubscribed. A universal number of days is not a strategy.
Writing these rules exposes missing information early. If a storefront sends only an order total, a product-specific reminder may not yet be possible.
Measure the behaviour you wanted to change
Delivery and clicks help diagnose the message. The business question is usually about purchases, repeat use, enquiries or another meaningful action. Review unsubscribes and complaints alongside those outcomes.
Revenue associated with an email is not necessarily revenue caused by it. A person may already have planned to buy. Where the audience is large enough, a randomly assigned group that does not receive the experimental message can help estimate the difference. Compare results per eligible customer over the same period, not raw totals from groups of different sizes.
Small audiences produce noisy results. A few purchases can move the average considerably. Record what the data can support, allow enough observation time and avoid turning one successful send into a permanent rule.
Adapted from the FIRSTOV business library. Russian original