Build a nurture around one segment: the journey and the exit that stops it, the drafts, the experiment that decides whether it worked, the pre-send checks, and the incremental readout afterwards.
The English summary is being prepared. Showing the original description.
Run score Not tested
See how to installReview the instructions the agent will receive before you install.
Use this when someone wants a sequence, a lifecycle journey or a re-engagement series for a specific segment. If a lifecycle map already says which emails should exist, build inside it; if none exists, name the stages you are assuming in one line so the owner can correct them before anything is written.
Name the stage this segment sits in, the one action that moves them out of it, and the touches that earn it:
Then name the exit in one line: what stops the sequence for someone who converts. A sequence with no exit does not ship.
One sequence per segment and stage. A blast wearing a nurture costume is still a blast. Write who is in and who is out, one line each, and say how you know which is which.
One goal, one ask, a subject under 50 characters, a first line that does real work. Every claim carries a number or a source or it gets cut. Missing facts stay marked in the draft rather than getting filled in.
Decide this first. An experiment designed after the results is a story.
Links, names, dates, the unsubscribe line and the reply-to address. Read every draft back once looking for the segment's name in the wrong place. Then the domain side: Sender Policy Framework (SPF), DomainKeys Identified Mail (DKIM) and Domain-based Message Authentication (DMARC) all passing, spam-score and rendering previews clean, and bounce and complaint watch switched on before the first send rather than after it.
Delivered, bounced, clicked, replied, converted, meetings booked, and the lift against the holdout or the prior baseline. Opens are a deliverability health check only — mail privacy features preload images and inflate them, so nothing gets scored on opens. Judge rates against benchmarks for the send type: cold, warm and customer sends never share a target. Name the send time and frequency behind each touch. Label every line FACT, INFERENCE or UNKNOWN.
Never send, schedule or upload a list without a yes. Never invent an open rate, a click rate or a conversion to fill a readout. Never re-send to an address that has bounced twice — suppress it.
No reviews yet. Tell others what you thought.
No login needed. Share how it worked for you, ask a question, or note where it did not run.
No comments yet. Be the first to write one.
Use when a support account wobbles or a quarterly business review looms: read the health signals, run the success plan, and prep the review from evidence.
The English summary is being prepared. Showing the original description.
Reconcile accounts by comparing GL balances to subledgers, bank statements, or third-party data. Use when performing bank reconciliations, GL-to-subledger recs, intercompany reconciliations, or identifying and categorizing reconciling items.
The English summary is being prepared. Showing the original description.
Review open receivables and draft factual, staged payment follow-ups without inventing status or contacting a customer.
The English summary is being prepared. Showing the original description.
Write ad variants that each test one idea, within platform limits and supported claims.
The English summary is being prepared. Showing the original description.
Use on the first conversation with Alex, or whenever their memory has no product preferences yet: learn what the user is building and who for, where specs, roadmap and numbers live, who decides dates and scope, and get them to a first real product deliverable.
The English summary is being prepared. Showing the original description.
Use when a strategic alliance needs joint selling governance: operating model, joint targeting, steering prep, and milestone accountability.
The English summary is being prepared. Showing the original description.