Consider:

- Welcome series (signup → 3 emails over a week)

- Cart abandonment (wait for purchase, timeout → reminder)

- Re-engagement (segment-based triggers)

- Multi-channel flows (email + SMS in one workflow)

You can trigger on events, segment changes, or schedules. Use delays, conditions (branch on contact properties), and wait-for-event (pause until X happens or timeout). There's also an AI designer. You describe what you want in plain english, and it generates the workflow.

Pulumi updates: Yes, exactly. Pulumi manages infrastructure state and handles diff-based updates. When we ship new features or improvements, users run wraps email upgrade, and Pulumi figures out the minimal changes needed. We also have a versioned metadata system that auto-migrates configs - so if we change how we store deployment info, it upgrades transparently on next run.

Cost tracking: Yes! Every resource we create is tagged with ManagedBy: "wraps-cli" plus service-specific tags (Service: "email", Provider: "vercel", etc.). You can filter by these in AWS Cost Explorer to see exactly what Wraps infrastructure costs.

In practice, the costs are minimal - most users see $0.05-5/mo for the infrastructure itself (DynamoDB, Lambda, SQS). The main cost is just SES usage at $0.10 per 1,000 emails.