Most content about AMP for Email is written to sell you on it. This one is written to help you decide. If you run a DTC email agency, AMP is a real lever, but it is not a universal upgrade. It pays off cleanly for some clients and quietly loses money on others. Knowing the difference before you pitch it is the whole game.

The goal here is to give you the client profile that fits, a rough sense of the economics, and an honest list of the cases where you should leave AMP on the shelf. If a guide only ever tells you to say yes, it is a brochure, not a guide.

What AMP actually changes for a DTC program

AMP for Email lets the message do work that normally happens on a landing page. The subscriber can browse a product carousel, pick a size, leave a review, answer a one question survey, or reorder a staple, all without leaving the inbox. The action moves closer to the intent, and every step you remove between wanting and doing tends to lift conversion.

That is the upside in one sentence: fewer clicks between the email and the outcome. The rest of this guide is about when that upside is large enough to be worth the build, and when it is not.

The client profile that fits AMP

AMP rewards volume, repeat behavior, and a live catalog. The clients where it pays off tend to share most of these traits.

• A list above roughly 50,000 engaged subscribers. AMP has a fixed build cost, so it needs reach to earn back.
• Repeat purchase behavior. Replenishables, apparel, beauty, food and beverage. Reorders and restocks give AMP something to do every month.
• A product catalog that changes. New drops, restocks, seasonal lines. Live data inside the email is only worth it if the data moves.
• A team willing to whitelist. AMP only renders for approved senders, so the client has to commit to the Gmail and Yahoo application before a single interactive email ships.

The rough economics

Numbers vary by market and by how much you build in house, so treat these as a shape rather than a quote. The point is to show you how the math tends to work, not to set your rate card.

On the cost side you have three buckets. The one time setup, which is the whitelisting application plus the reusable AMP framework and fallback for the client. The per campaign build, since an AMP email is a designed asset with a live data source behind it, so it runs above a static build. And the maintenance, which is keeping the data feed and the fallback in sync as the catalog changes.

On the return side, the useful mental model is incremental revenue per send. AMP does not usually raise your open rate. It raises the rate at which an opener takes the action you wanted, because the action got easier. If a client sends to 80,000 people twice a week and an interactive flow lifts action rate by even a point or two on the sends where it fits, the incremental revenue compounds fast against a fixed build cost.

The honest version of the pitch is this. AMP is a fixed cost that buys a variable return, and the return scales with list size, send frequency, and how naturally the offer maps to an in email action. Big engaged list plus frequent sends plus a clear action equals a fast payback. Take any one of those away and the payback stretches.

When AMP is the wrong call

This is the part the brochures skip. There are clients where recommending AMP is the wrong move, and saying so is how you keep the account for years instead of months.

• ×Small or low frequency lists. If the client sends once a month to 8,000 people, the fixed build cost never gets enough sends to earn back.
• ×One time or considered purchases. Furniture, mattresses, high ticket electronics. When people buy once every few years, there is no repeat action for AMP to shorten.
• ×A broken foundation. If deliverability is shaky or the static program has never been optimized, fix that first. AMP on top of a weak base just adds cost to a leaky system.
• ×No appetite for whitelisting. If the client will not commit to the sender approval process, AMP will fall back to plain HTML for most of the inbox and you have paid for a feature nobody sees.

How to pitch it without overpromising

Lead with a single use case, not the whole category. Pick the one flow where the client's data and the in email action line up most cleanly, a reorder for a replenishable, a size and add to cart for apparel, a review request after delivery. Ship that, measure the incremental action rate against the static version, and let the number decide whether you expand.

This does two things. It keeps your first build small enough to prove out fast, and it trains the client to judge AMP on incremental revenue rather than novelty. A win you can point to is worth more than a deck full of what if.

Used this way, AMP stops being a shiny upsell and becomes what it should be for an agency: a sharper tool you reach for on the accounts that fit, and leave alone on the ones that do not. That judgment, applied honestly, is the thing that separates you from the agency that pitches the same feature to everyone.

If you want more breakdowns like this one, the kind that tell you where a tactic stops working as well as where it starts, subscribe to the Convertic.ai blog. We publish the parts most vendors leave out.