How Much to Charge for Email Automation (Method)

How much to charge for email automation comes down to a floor and a ceiling you can calculate. The floor is your estimated hours times your rate. The ceiling is what the automation is worth to the client in its first year, using their own list, order and time numbers. Your quote sits between the two, and the job is usually a welcome series, an abandoned cart flow, a lead follow-up sequence or a win-back campaign for a store, a coach or a service business.

I am not giving you a market dollar figure here, because the range between a three-email welcome series and a fully segmented store setup is too wide for one number to mean anything. Your rate and their numbers will get you closer than any figure I could print.

Claude Code drafts the emails, writes the logic and connects the systems fast. That is why pricing by the hour undersells you. The slow part is everything else: a list nobody has cleaned, a store that does not send the right data, a sending domain that was never set up properly, and an owner who rewrites every subject line.

Run this before you write a number on anything. It takes a few minutes once you have the answers from your first call, and every input is yours or the client's.

If the floor is above the ceiling, the job does not pay for itself. Say so and offer a smaller version, because a client who cannot get their money back will not stay happy. If the ceiling is far above the floor, you have room to price on value. How far you move toward the ceiling is your call, based on how solid their numbers are and how much of the result you can actually influence.

Do not quote from the number of emails. Ask five questions in the first call: how big the list is and how it was collected, what they send today and who sends it, what a customer is worth to them, what tool holds their contacts and orders, and whether their own domain has sending authentication set up. Those answers shape the price more than the writing does.

If nobody can tell you who is on the list or where it came from, sell a paid audit first and quote the build after. Paid discovery for AI projects covers how to sell that, and client discovery questions before you quote has more questions to ask.

The flow map is your anchor line. Claude Code can draft ten emails quickly, but the question of who should get them, and when they must stop, is what separates useful automation from a customer getting a discount offer the day after paying full price. Quote it as its own line and say why.

Deliverability gets its own line because automated email that lands in spam is worth nothing. Gmail's rules are public. Anyone sending to Gmail accounts needs SPF or DKIM on their domain and must keep spam rates below 0.3 percent, with below 0.10 percent as the recommended target. Anyone sending more than 5,000 messages a day to Gmail accounts needs SPF, DKIM and DMARC, plus one-click unsubscribe on marketing messages. Check where the client stands before you commit to a launch date, because the fix depends on whoever controls their DNS.

Email automation sends in the client's name to real people, so put ownership in the proposal. The sending account, the domain and the contact list stay in the client's name, and they pay the platform directly. You are added as a user with access that ends on an agreed date. That way a growing list raises their bill, not your costs.

Then write down the rules. In the US, the CAN-SPAM law requires a valid physical postal address in each commercial email and a clear way to opt out, and opt-outs must be honored within 10 business days. Hiring someone else does not remove the business's responsibility, and both the business being promoted and whoever actually sends can be held liable. Other countries have their own rules, and some need consent up front. Whether their list and copy comply is a decision for the client and their legal adviser, so name that in the proposal. Your job is to make sure the unsubscribe and address parts of the setup work.

Finally, define done: which flows are live, what starts and stops each one, who signed off the copy, and which test contacts passed through every path. Once that is signed, a new flow or a new audience is a change request. If you are connecting to a store or CRM that has no ready-made integration, how much to charge for an API integration covers that line.

Email automation only shows its results after real people receive it. A subject line nobody opens, a flow that fires too soon, or a segment that turns out to be empty all appear after launch. If you have not quoted for that, you fix them for free while the owner decides automation does not work for their business.

Put a fixed tuning window in the first proposal, next to the build price. Say what it covers: reviewing results, adjusting subject lines and timing, and fixing rules that do not behave. Say what it does not cover: new flows, new audiences and monthly campaigns. If they want ongoing work after that, offer a retainer. How to price a maintenance retainer covers the structure.

And skip hourly on the invoice, even though hours set your floor. Claude Code makes the drafting and wiring fast, so billing by the hour turns that speed into a pay cut. Why I stopped charging hourly for AI builds covers why. If the emails are part of a store build, see how much to charge for an ecommerce website, and for paid content businesses see how much to charge for a membership website.