Paying for an agent that prepares your client lists

Your fee covers the hours before a send, not the send itself. The agent plans a campaign, assembles the list and drafts the writing, which is the part of your contract where a client asks for a source on every row. You then read the prepared work and decide whether it leaves your desk.

Clients pay you for rows they can defend in a meeting. A prepared campaign gives you templates and a contact set to inspect before anything reaches an inbox, so you can attach a source to a row before the client sees it. That review step is the part of the job the agent does not remove.

The managed sending mailbox also falls inside what you are buying. It removes the setup work of wiring a sender to a campaign, which matters when you run several client lists in a month. What it does not do is make a poor list good, and it does not answer for the rows you approve.

Compare Starter, Growth and BYO-SMTP by the scope of work each includes, using the lifetime table published on softwareprogrammer.app as your reference. The names describe how much preparation and sending setup you receive, not a ranking of output quality. Read each row against the size of the lists you actually deliver.

The BYO-SMTP tier is the one to examine if you already run sending infrastructure for clients. It places the mailbox on your side, so your existing reputation carries the campaign. Starter and Growth sit closer to a managed setup, where the included mailbox is part of what you receive rather than something you supply.

Interface language is worth checking as well, since English and Spanish are supported. If your client base reads in either language, that affects which tier and workflow you choose. Set the tiers side by side, mark the scope you need for the lists you hand over, and let that mark decide the purchase.

Unverifiable rows are the fear, and it is a fair one for anyone whose name sits on a delivered list. The agent prepares contacts and writing, but it does not certify that a row is current or reachable. Your review before launch is where that risk is managed, so build the check into your own process rather than assume it.

Ask what a client does when a row bounces or a contact is wrong. If the answer is a difficult conversation, then the agent's role is to speed the preparation while your sign-off protects the relationship. The confirmation step exists for exactly this reason and should be treated as part of delivery, not as friction.

Sending reputation is the second doubt. Delivery depends on how the sending domain is regarded, and a managed mailbox is a starting condition rather than a promise. If you cannot explain that to a client, you are not ready to hand over a campaign, whichever tier you buy.

Take a contractor delivering a small list each month to a single client. A managed tier covers campaign planning, list assembly, drafting and the mailbox, so the contractor spends the saved hours on checking rows and citing sources. Confirmation before launch keeps the client relationship in the contractor's hands.

Now take a contractor with existing sending infrastructure and several clients. The BYO-SMTP tier keeps the mailbox on the contractor's side, so reputation stays under their control and each client list can be reviewed before it goes out. The trade is more setup responsibility in exchange for a sending path they already understand.

Neither worked example tells you which to buy. Write down the lists you deliver in a month, the languages your clients read, and who owns the sending domain. Where those answers point, the tier follows. A purchase made against that short note is easier to defend than one made against a feature comparison.