Hire an AI post-purchase, delivery-email and repeat-order test planner

Everything it can hand back

Your task sets the actual outputs. The specialist picks the methods that cover them.

• A post-purchase flow with a trigger, a split by order count and six email outlines with subject lines
• A delivery date rule, a four-message update flow and a tracking page plan
• A map of your flows by new, returning and loyal buyer, with a build order
• A ranked test queue with sample sizes and a rule for calling each result

How it does the job well

• Write for one named audience and one action. Each asset has a single job.
• Use the customer's own words from reviews, calls or surveys before inventing language.
• Every claim needs proof the business can show. Leave unproven claims out or mark them.
• Judge results against the business goal, such as profit or qualified leads, not clicks alone.

Mistakes it avoids

• Generic copy that could fit any brand.
• Comparing periods or campaigns that are not comparable, such as different dates, budgets or tracking.
• Calling a test winner before there is enough data.

What a good result looks like

An example, not your task: Your only email after an order is the receipt, and nothing brings buyers back.

• STEP 1: Post-purchase flow builder. The trigger, a split by order count, six email outlines with subject lines, and timing.
• STEP 2: Delivery update flow builder. A delivery date rule, four update messages, a tracking page plan and a late parcel script.
• STEP 3: Customer stage flow mapper. Your flows by new, returning and loyal buyer, with goal, tone, offer rule and a build order.
• STEP 4: Email test planner. A ranked test queue with hypothesis, sample size, winning metric and tests to skip.
• HAND-BACK SUMMARY. Each step's file, any step not run, and every MISSING line in one list.

How the work is checked

• Each step passed its own checks, or the run stopped at the step that failed and says why.
• The steps ran in order, and each one used the result of the one before.
• Nothing was invented to fill a gap. Every gap is a MISSING: line.
• Nothing was sent, published or paid for without a clear yes.
• States which checks passed, failed or could not run, and names missing inputs.

These checks have not been run against a model yet. Your AI uses them to check its own work.

Capabilities

• Post-purchase flow builder. Builds the emails after a first order. It starts with a plain founder note, then adds more products, a shipping update and how to get the most from what they bought.
• Delivery update flow builder. Rates your order-status tickets and delivery accuracy, sets a delivery date rule, and writes four update messages. It reuses the post-purchase flow so nothing goes out twice.
• Customer stage flow mapper. Puts a new, returning and loyal branch at the top of each flow, with a goal, tone and offer rule for each, so a buyer is in one place at a time.
• Email test planner. Ranks the tests on your mapped flows, with a hypothesis, a sample size and a winning metric for each. It skips tests your volume cannot read.

How the role works

1. Checks your task, context and available tools.
2. Picks the methods needed and prepares a work plan.
3. Carries out supported tasks, with each method's limits and review gates.
4. Checks the real deliverables and corrects supported faults.
5. Hands back files, evidence and unresolved gaps.

Your specialist's working setup

Download the base specialist without a task form or account. README.md and SETUP.md explain how to use the folder. SOUL.md defines its scope. INTAKE.md asks missing questions inside your AI. PLAYBOOK.md, SKILLS.md, BEST_PRACTICES.md, CHECKS.md and HANDOFF.md guide the work and its checked deliverables.

Complete associated skills, supporting files and licences are included. Choose only the methods needed for the actual task. Keep context, working files and accepted feedback in your AI project.

Use this specialist through MCP or the API

Call prepare_specialist with role_id turn-the-first-weeks-after-an-order-into-repeat-buyers only. No task is required to load it. Your AI asks what job you need done, what you want back and which relevant context it can use.

For task-led hiring, call find_specialist, explain the suggested specialists and let the user accept or change the team.

Complete ZIP: Download base specialist. API: GET /api/v1/specialists/turn-the-first-weeks-after-an-order-into-repeat-buyers/pack. The host AI supplies its own model, tools and execution; a pack does not connect accounts or run a task.

Inputs and helpful context

The specialist starts from the task brief. Only active methods require their inputs.

For the primary method, when used

• Your products, and what pairs well with each
• Your delivery times, and how many order-status tickets you get a month
• Your email results, such as flow revenue and recipients per month
• Your current flows, with their triggers and delays
• Your brand file and offer rules (optional)

Tools and access

• Klaviyo: Placed-order triggers, order-count splits and flow filters fit the steps.
• Shopify: Order, shipping and cancelled-order data drive the filters.
• Any good chat AI: Any current chat AI can run the skill from your pasted product facts.
• Any good chat AI: Any current chat AI can do the sums and write the messages. Paste real numbers.
• Klaviyo: Paid service with an account. It sends the update flow by email and SMS from your order events.
• AfterShip: Paid service with an account. It hosts a tracking page and sends delivery updates. Check the current price against your order volume.
• Gorgias: Paid service with an account. A helpdesk that can tag order-status tickets, so your WISMO count is real and not a guess.
• Klaviyo: Flow filters and conditional splits let you build each branch, and predictive fields show expected next order dates.
• Shopify: Order counts, spend and subscription status define the stages.
• Any good chat AI: Any current chat AI can draw the map from your pasted flow list.
• Klaviyo: Paid service with an account. Its A/B tests show win probability and placed order rate, and flows can split into paths for timing tests. Check that your plan includes A/B testing.
• Google Sheets: A test log with one row per test keeps hypothesis, sample, result and the next step in one place.

Functions and deliverables

• Post-purchase, delivery-email and repeat-order test planner: Share products, orders and current emails. Get drafts for after an order and during delivery, rules for each buyer stage and a test plan.
  • A post-purchase flow with a trigger, a split by order count and six email outlines with subject lines
  • A delivery date rule, a four-message update flow and a tracking page plan
  • A map of your flows by new, returning and loyal buyer, with a build order
  • A ranked test queue with sample sizes and a rule for calling each result
• Post-purchase flow builder: Plan the six emails sent after an order. Get the trigger, an order-count split, outlines and subject ideas for each email.
  • A flow spec with the trigger, filters and a split by number of past orders
  • Six email outlines with subject line ideas
  • An opening line for first, second, third and later orders
  • Timing for each email and a rule for when to move it
  • A list of campaign winners to copy into the flow later
• Delivery update flow builder: Share shipping data and order-status contacts. Get a date rule, four updates, a tracking-page plan and a reply for late parcels.
  • Your WISMO rate and delivery accuracy, each rated against a limit
  • A delivery date rule that pads your real times
  • A four-message update flow with timing and copy
  • A tracking page plan and a script for delayed parcels
• Customer email journey planner: Split your cart and post-purchase flows by customer stage. Get new, returning and loyal paths, each with a goal, tone and offer rule.
  • A flow map with a new, returning and loyal branch at the top of each flow
  • The goal, tone and incentive rule for each branch
  • A list of flows to build or merge, in order of the biggest bottleneck
  • A flow spec the email writer skills can fill in
• Email test planner: Plan email and popup A/B tests that can finish. Get a ranked test queue with sample sizes, run times and rules for calling a winner.
  • A ranked test queue, each test with a hypothesis
  • A sample size and run time for every test
  • Set-up notes, the winning metric and the rule for calling a result
  • A skip list of tests your volume can't support, with the reason
  • A test cadence and what to record after each result
• Brand profile builder: Share your website. Get a reusable profile covering your products, customers, voice and approved claims, with sources.
  • A folder of eight plain files, from a start file for your AI to a claims list and a change log
  • A tag on every fact, and every claim marked approved, pending or banned
  • A two-sentence diagnosis of your biggest gap, and a list of what's missing and who can answer it
  • A short slice for your next step, if you name one

Tasks you can use it for

• Your only email after an order is the receipt, and nothing brings buyers back.
• Customers write to ask where their parcel is, and you want to answer before they ask.
• You have several flows, and some buyers get emails from two of them at once.

Limits to check before starting

• You get under about 50 orders a month, so test results will be too thin: send one plain receipt and shipping email by hand instead.
• You want to win back buyers who went quiet months ago: use a win-back workflow instead.
• You only need delivery messages: use the Delivery update flow builder.

Best way to use this role

Give it one clear outcome, the actual files and a definition of done. Keep the work in one AI project so it can reuse checked context and earlier files.

• Download the handoff pack. It's a zip with HANDOFF.md and every skill file this workflow uses.
• Give the folder to Claude (in Claude Code, or as files in a Claude Project) and say "Follow HANDOFF.md".
• Paste your product list, delivery times and email results. Add how you define a new, returning and loyal buyer.
• Build the flows in your email tool in the order the map gives.
• Run the first test it ranks, and read the result only when the sample size is reached.

Read it as data

Read the complete role setup as JSON. Connect your AI to the AI Blocks MCP library and read aiblocks://roles/turn-the-first-weeks-after-an-order-into-repeat-buyers for its role instructions and pinned sources.

This is a prepared AI role. No task has run. Your AI carries out authorized work using its available tools and reports the actual deliverables and checks.