Tell your AI who to email. It sets up the rest.

Customer.lite is customer messaging you run from Claude Code. Your app sends us its users and what they do. Your AI assistant builds the workflows over MCP. We send the email from your domain, and check every message before it goes.

Request early accessRead the docs

In early access, not charged. When paid plans open, from $9 a month for 10k emails, with every feature. Pricing

When someone signs up, send our welcome email. Two days later, if has_project is still not set on them, send the setup guide.

customer-lite · workflows_upsert

welcome-and-setup v1: signed_up → email → wait 2 days → if has_project not set → email

customer-lite · workflows_activate

v1 waits for approval. A link was mailed to the workspace's approvers.

Saved. Open the approval link in your inbox and new signups start on v1. Both emails go out from your verified domain.

An example session in Claude Code. The tool names are the real MCP tools; your app sets has_project on the customer.

Email that reacts to what your users do

A newsletter tool sends an issue to a list. Customer.lite starts from your product: a signup, a trial about to end, a payment that failed, a feature nobody has tried yet. Each customer gets the message that fits where they are, when it fits.

And you set it up where you already work. The assistant that writes your app wires the events, drafts the emails, and builds the workflows, with the same actions, validation, and errors as the REST API.

What it does

Customer.lite is in early access. Here is what works today, what is being built for the first release, and what is planned after it.

Available now

  • Workflows your AI builds

    Describe the flow in Claude Code or any MCP client. It saves the workflow, with event triggers, delays, conditions, and emails, and asks to make it live. Today, during early access, a person on your team approves every sending version through a mailed link.

  • Customers and events from your product

    Your app records customers and what they do through the REST API. An event sent again with the same idempotency key is recorded once.

  • Every message accounted for

    Each message keeps its send state, delivery result, and a step log that says why it was or was not sent. Delivery, bounce, and complaint counts per project.

  • Unsubscribes honoured at send time

    Unsubscribes, bounces, and complaints are checked again just before each send, so a message queued yesterday is still skipped today.

In development

  • Webhooks in and out

    Turn Stripe or any service's webhooks into events, and call your own endpoints from a workflow with signed, retried requests.

  • Date and schedule triggers

    Start a workflow from a date on the customer, such as three days before a trial ends, on a schedule, or once at a time you pick, such as tomorrow at 9.

  • Click tracking

    Which links each customer clicked, with clicks by link scanners and bots kept out of the numbers.

Planned

  • Saved audiences and one-sentence sends

    Define a group once, such as trial users who have not invited a teammate, then ask your AI to “send this to that group tomorrow” without building a workflow first.

  • Analytics with opens

    Open and click rates per message, workflow, and audience.

  • A/B tests

    Try two subject lines or two versions of an email on part of an audience, then send the winner to the rest.

  • Connect without an API key

    Sign in from claude.ai, ChatGPT, or Claude Code and allow access, instead of copying a key.

  • Approval when you want it

    Approval becomes a setting per workspace: solo developers can go live without the mailed approval, with pause and rollback to undo a bad change, and teams can turn it on.

How it works

  1. Connect your assistant

    Add the MCP server to Claude Code, Cursor, Codex, or any MCP client, with a project API key. Making a workflow live needs a key with admin scope.

    claude mcp add --transport http customer-lite https://dev.customerlite.io/mcp \
      --header "Authorization: Bearer $CUSTOMER_LITE_API_KEY"
  2. Send customers and events

    Your app records customers and product events through the REST API. An event sent again with the same idempotency key is recorded once.

  3. Ask for the email you want

    Your assistant creates the workflow of triggers, delays, conditions, and emails, and asks to make it live. Today, during early access, a person on your team approves each version that sends email through a link mailed to them, and we set up your sending domain and approvers with you. Each change is a new version, and runs already started keep theirs.

  4. We send, and show our work

    Every message records its send state, its delivery result, and why it was or was not sent, so you and your assistant can check what happened.

Careful sending, even with an AI at the keyboard

The checks run on our servers, not in your assistant's prompt.

One plan, priced by the emails you send

Every feature and unlimited profiles under fair use, from $9 a month for 10k emails. You do not pay for customers who are not getting mail. When paid plans open, there are no overage charges. Events are capped at about 8 times the plan's emails, and at the email limit, sends wait until you upgrade or the next month starts; a send still waiting after 72 hours is skipped.

See every price step

Questions

Do I need Claude Code?

No. Any MCP client works, such as Cursor or Codex, and everything the MCP tools do is also a REST endpoint you can call yourself. The API reference lists both.

How is this different from a newsletter tool?

Newsletter tools are built around issues sent to a list. Customer.lite is built around your customers and the events your product records, so a message can follow a signup, a trial date, or a payment, one customer at a time.

What stops my assistant from sending email I did not mean to send?

Today, during early access, a new or changed workflow that sends email needs a person to approve that exact version, through a link mailed to the workspace's approvers and never returned to the API key. Mail goes out only from domains verified for your workspace, and unsubscribes, bounces, and complaints are checked again before every send. Approval covers the workflow, not the recipients: once live, it sends to whichever customers your API key records, so keep write keys in your app. Every message is logged with the reason it was sent.

Which email provider do you use?

Amazon SES, from your own domain with DKIM. Each workspace sends under its own reputation.

Is there a free tier or a trial?

Early access is not charged. When paid plans open, they start at $9 a month for 10k emails, with no free tier or trial.

Set up your first workflow in one sentence.

Request early accessGive your AI llms.txt