The Customer.io Builder Plan: Start on Real Infrastructure, Not a Tool You'll Outgrow
Most early-stage teams reach for the same thing when they need to send email: whatever's quickest to wire up. A transactional API from a side tool, a free tier on a basic sender, something that gets the password resets going by Friday. It works, right up until you need segments, or a second channel, or behavioural triggers... and you're staring down a migration to a grown-up platform.
The Builder plan is Customer.io's answer to that. It's the same messaging infrastructure the platform runs on, available to a solo developer or an AI coding agent from the first line of code. You build and test for free, send across every channel, and pay only when you actually ship messages to customers. No subscription, no trial clock, no migration waiting for you later.
This post covers what the Builder plan gives you, what it deliberately holds back, and the maths for when to move up to Essentials. It also flags the option that gets qualifying startups a year of the full platform free. By the end you'll be able to place yourself on a simple decision line in about two minutes.
Builder is Customer.io as infrastructure, not a starter tier
The Builder plan is the same Customer.io messaging engine bigger brands run on, repackaged so you can adopt it like any other developer tool. It's not a watered-down trial. Customer.io's Builder plan documentation, updated on 17 June 2026, describes it as messaging infrastructure for early-stage builders, transactional senders and AI coding agents. You sign up without payment details, set up your channels, verify a domain, and build your content before you owe anything.
That last group is the tell. Builder runs from the Customer.io CLI and MCP server, not just the web app. An AI coding agent can wire up messaging for your project the same way it adds any other dependency. You don't need a GUI, and you don't need a plan meeting first.
If you've spent time comparing Customer.io against Braze, Klaviyo, Iterable and HubSpot, the barrier to trying it was rarely the product. It was having to commit before you'd built anything. Builder removes that.
What $10 buys, and what it doesn't
Ten dollars buys roughly 25,000 sends. At $0.40 per 1,000 messages, that's the floor, and the rate is flat across every channel Builder supports. But Builder is deliberately not the whole platform, and the gap is the entire point of the plan.
What's included: transactional, broadcasts, and every channel
Builder is built for transactional messaging: the receipts, password resets, shipping updates and two-factor codes your product sends because a customer did something, not because you scheduled a campaign. You can send those through the CLI, the MCP server or the web app. One-time broadcasts (newsletters) and API-triggered broadcasts are in too.
The channels are the full set: email, push notifications, in-app messages and webhooks, plus SMS and WhatsApp if you connect Twilio. The $0.40 per 1,000 rate is the same whichever you use. You also get unlimited people profiles, up to two sending domains, and up to ten verified recipients you can email free while you're still testing.
Once you're sending receipts and shipping updates at volume, there's a real case to turn those transactional emails into a revenue engine. They get opened far more than marketing mail, and Builder lets you start sending them for $10.
One honest detail: funds are prepaid and don't expire, but when they run out, sending stops until you top up. Customer.io emails your account admins when you're low, so it shouldn't catch you out.
What's not included: campaigns, segments, objects, integrations
Builder leaves out the automation. There are no behavioural campaigns, no dynamic data-driven segments, no custom objects, and none of the native integrations with tools like Salesforce or HubSpot. Customer.io's own guidance is blunt: if you need behavioural workflows, audience segmentation or multi-channel automation, start with Essentials.
The lack of custom objects matters more than it looks. If you're not sure whether your data belongs on a person profile or somewhere else, the difference between collections and custom objects is worth understanding before you build. Builder gives you neither; Essentials gives you both.
The break-even maths
Builder is cheaper than Essentials right up to about 250,000 messages a month. Past that, it flips. Here's the working, because it's worth seeing.
At $0.40 per 1,000 messages, Builder works out to $0.0004 a message. Essentials starts at $100 a month and includes 5,000 profiles and one million emails, per Customer.io's pricing page. Divide that $100 floor by Builder's rate ($100 ÷ $0.40 per 1,000) and you get 250,000 messages. So $100 spent on Builder buys you 250,000 sends. The same $100 on Essentials buys up to a million emails, plus segments, workflows and objects.
Below roughly 250,000 messages a month, Builder costs less. Above it, Essentials is both cheaper per message and more capable: you get the whole platform, not just message delivery. At the Essentials floor an email costs $0.0001, four times cheaper than Builder's rate, and additional emails run $0.12 per 1,000.
Volume isn't the only axis, though. Builder gives you unlimited profiles and charges per message; Essentials includes 5,000 profiles and then charges $0.009 for each one beyond that. A product with a large list but a low send rate can still come out ahead on Builder. The flat Builder rate also covers every channel, whereas the Essentials million is emails specifically. (Push and in-app are unlimited on Essentials anyway.) For mixed-channel sending, run the sum on your total message count.
If you do move to Essentials, plan for your AI-credit spend once the free bundle runs out the same way you plan for sends: predictable, but a line item.
The option most founders miss: up to 12 months free
If you've raised under $10 million, there's a third door, and it beats both Builder and paid Essentials. Customer.io's Startup Program gives eligible companies up to 12 months free, and not a stripped-down version. You get the full Essentials feature set, up to 30,000 profiles, billed monthly.
Eligibility comes down to three things. Your company has raised less than $10 million in total funding. Your contact lists were obtained legitimately, not purchased. And you've never been a Customer.io customer before. Meet all three and you apply, with no charge while you're enrolled.
This is the part worth pausing on. The Startup Program isn't Builder. It's the automation platform, free, so if you qualify, the build-versus-automation trade-off that Builder forces simply goes away for a year. The catch is that it's time-boxed and you have to apply, but for an early-stage team it's the cheapest way onto the full product by a distance.
A decision line you can apply in two minutes
Put yourself on one line.
Building, testing, or sending low-volume transactional messages with no automation? Use Builder. It's free to set up, $10 to go live, and the cheapest option under about 250,000 messages a month, provided you don't need campaigns or segments.
Raised under $10 million, with legitimate lists, and new to Customer.io? Apply to the Startup Program. It gives you the full Essentials platform free for up to a year, which beats both Builder and paid Essentials on price and capability.
Need behavioural workflows, dynamic segments, custom objects or native integrations, or sending more than 250,000 messages a month? You're on Essentials. That's where the automation lives: visual workflows, segmentation, and LLM actions that make runtime decisions inside a journey.
Moving up is painless. Customer.io carries over your channels, profiles and content with no migration, and you email their team to upgrade. So the right first move for most early teams isn't to wait until they can justify $100 a month. It's to build on Builder for nothing, go live for $10, and switch when the maths or the feature list says so.
Frequently asked questions
How much does the Customer.io Builder plan cost?
Setting up is free. To send to real customers you add funds starting at $10, and pay $0.40 per 1,000 messages, a flat rate across email, push, in-app, webhooks and SMS or WhatsApp through Twilio. There's no subscription and no monthly fee.
What's the difference between the Builder plan and Essentials?
Builder is pay-as-you-go infrastructure for transactional and low-volume sending, with no automation. Essentials is a subscription from $100 a month that adds campaigns, dynamic segments, custom objects, native integrations and a million emails. Builder is a different product, not a cheaper Essentials.
Can I run marketing campaigns on the Builder plan?
No. Behavioural campaigns, audience segmentation and multi-channel automation all require Essentials or higher. Builder covers transactional messages, one-time newsletters and API-triggered broadcasts: the things you send because of an event, not a schedule.
Do Builder plan funds expire?
No. Funds you add don't expire. They're prepaid, with a $10 minimum and a $1,000 maximum per purchase, and sending pauses if you run out until you top up. Customer.io emails your account admins when you're running low.
Does Customer.io have a free plan for startups?
Yes, with conditions. The Startup Program gives qualifying companies up to 12 months of Essentials free, including up to 30,000 profiles. You need to have raised under $10 million, used legitimately obtained lists, and never been a Customer.io customer. Builder is also free to build and test on, at any stage.
Can I upgrade from Builder to Essentials without losing my setup?
Yes. Your message channels, profiles and content all carry over, and no migration is required. You upgrade by contacting Customer.io's team rather than self-serving in the app.
How many messages does $10 buy on the Builder plan?
About 25,000. At $0.40 per 1,000 messages, the $10 minimum works out to roughly 25,000 sends, and the rate is the same across every channel Builder supports.
At what volume does Essentials become cheaper than Builder?
Around 250,000 messages a month. That $100 buys 250,000 Builder sends but up to a million emails on Essentials, so below 250,000 messages Builder costs less and above it Essentials wins, on price and on features.
Does the Builder plan include segments or custom objects?
No. Builder doesn't include dynamic, data-driven segments or custom objects, both of which are Essentials features. Builder gives you unlimited people profiles, but no objects and no behavioural segmentation.
How many sending domains and test recipients does the Builder plan allow?
Up to two sending domains per workspace, and up to ten verified recipients. Verified recipients are test users who've opted in, so you can check how your emails look before you add funds and go live.
Do I need a credit card to start on the Builder plan?
No. You can sign up without payment information and set up your channels and integrations straight away. You only enter payment details when you add funds to start sending to customers.
Which channels can I send on the Builder plan?
Email, push notifications, in-app messages and webhooks, plus SMS and WhatsApp through a Twilio integration. The $0.40 per 1,000 rate is flat across all of them, so the channel you pick doesn't change the cost.
Sources
- Builder plan: pay-as-you-go. Customer.io Docs. 17 June 2026.
- Pricing + Plans. Customer.io. Accessed 19 June 2026.
- Customer.io for Startups. Customer.io. Accessed 19 June 2026.
