Buying a mailbox account when your client wants sources

Pricing here is a one-time tier figure rather than a monthly subscription, and the tier is chosen by mailbox count. Read the published table on softwareprogrammer.app as a capacity decision: Starter at five mailboxes, Studio at fifteen, Floor at fifty. Nothing in the tier scales with list size, client count or sending volume, so match the number to your sending plan.

Because the purchase is lifetime, the question shifts from what a month costs to what the tier actually contains. You are paying for standard SMTP and IMAP mailboxes plus browser webmail, with warm-up and authentication checks around setup. That is infrastructure for sending, and it sits beside your list work rather than replacing any part of it.

Compare the tier figure against what your client engagement can absorb as a fixed setup cost, then check whether anything you need falls outside the mailbox count. Extras are priced separately, so the headline tier is not automatically the whole bill. A contractor delivering lists should read the table twice: once for mailboxes, once for what the tier leaves out.

Across every tier the contents are the same shape: mailboxes you can configure over standard SMTP and IMAP, browser webmail for whoever signs in, and warm-up and authentication checks alongside setup. What changes between Starter, Studio and Floor is only how many mailboxes you receive. No tier adds contacts, sources or verification of its own.

For a contractor, that means the tier decision is arithmetic. Five mailboxes suits a single small engagement where you send from a handful of addresses. Fifteen fits several client domains running at once. Fifty covers heavier parallel work. Work out how many separate sending identities your current clients need, then pick the smallest tier that covers it.

Tier by tier, the useful mental model is one mailbox per sending identity rather than one mailbox per campaign. Warm-up and authentication checks apply to the mailboxes you hold, so spreading identities across the larger tiers keeps each client's sending separate. Write that mapping down before you buy, because the tier is fixed once purchased.

The hesitation a lead-generation contractor feels is rarely about mailboxes. It is about the handover: a client who finds an unverifiable row blames the list, and the relationship takes the damage. That fear is well placed and it points at your process, not at the mailbox account. The account cannot introduce or check a row, so it can neither cause nor cure that problem.

Read the objection as a boundary marker. Anything a client will audit, meaning the contact, the role, the company and where each came from, belongs to your own verification workflow. The mailbox only carries the message once you have decided the row is sound. Separating those two jobs makes the hesitation manageable rather than a reason to avoid buying.

Once the split is clear, the purchase becomes ordinary. You are buying sending capacity with a known count, and you are keeping verification under your own control. If a client asks how a row was sourced, the answer comes from your records. If a client asks where the mail was sent from, the answer comes from the tier you bought.

Anything beyond the mailbox count is priced apart from the lifetime tiers, so the published table is worth reading to the end before you commit. If your work needs something the tier does not list, expect a separate charge for it. Budget for that separately from the mailbox figure rather than assuming the tier covers everything you will eventually want.

There is also a cost that never appears on the LocalSMTP table: the research and verification hours you spend building and checking rows. That is your own work and no tier reduces it. A contractor quoting a client should price sourcing and checking as labour, and price the mailbox account as a fixed setup cost carried across engagements.

The clean split is to treat the tier as one line and extras as another, then keep both visible in your own client quotes. Where a client asks what the mailbox spend buys, the honest answer is sending capacity and webmail access, with warm-up and authentication checks. It does not buy rows, sources or a promise about where a message lands.