Sequenzyv1.6.0

A growth engineer uses Sequenzy to send a single transactional welcome email whenever a new user signs up. They check auth with `sequenzy whoami`, verify the recipient email, and send by template ID before logging delivery stats for the batch.

A marketing operations specialist lists current subscribers, removes hard-bounced or unsubscribed addresses, and adds newly opted-in contacts. They validate each subscriber ID and email before any mutation and use stats by sequence ID afterward to confirm engagement.

An e-commerce operations team triggers a transactional receipt email after a completed order using a raw HTML template. The agent first validates the order email and subject line, sends the email, then checks the stats overview to confirm successful delivery.

A platform administrator audits Sequenzy access by running `sequenzy whoami` with the current `SEQUENZY_API_KEY` and confirming identity before rolling the key. They explicitly avoid unsupported nouns like `account` and fall back to the dashboard for anything not wired in the CLI.

An agency analyst pulls stats overview and stats by campaign ID to build client reports on transactional email volume. Since campaign management commands are unsupported, they clearly note the limitation and use the dashboard for deeper campaign configuration.

Sequenzy sells tiered access to an email sending and subscriber management API, with the CLI as a first-class operational surface. Teams pay monthly based on contact volume and transactional send limits.

Revenue scales with the number of transactional emails delivered, charging per thousand sends or per active subscriber. The CLI enables low-friction automation that drives higher sustained usage.

Free access to core CLI workflows like login, whoami, subscribers, stats, and one transactional send drives adoption. Paid upgrades unlock higher limits, advanced workflows, and dedicated support.