Mailboxes for client lists, priced by count

What you pay for is a working mailbox you sign into, not a pile of rows. Each tier hands you standard SMTP and IMAP mailboxes, and browser webmail is included for anyone who would rather not configure a mail client. Warm-up and authentication checks sit alongside setup, so your first sends from a client domain start from a sensible place.

Picture the contractor workflow: you agree a campaign with a client, set up a sending identity, and write from it. The tier decides how many identities you can hold at once before you need another purchase. Five mailboxes suits one or two clients running side by side, with a spare for testing.

Nothing in the purchase supplies the contacts themselves. Your verified rows, with a source recorded against each one, stay in your own working files. The mailbox is the pipe you send through, and the sourcing discipline that protects the client relationship remains entirely your own work.

Moving up a tier changes one headline number and very little else. Starter holds five mailboxes, Studio holds fifteen, and Floor holds fifty. Each is a lifetime tier, so the decision is about capacity you expect to keep using, not a monthly commitment that lapses when a quiet quarter arrives.

Capacity matters when you run several client campaigns at once. Studio gives you enough identities to separate each client's sending, which keeps replies and complaints attributable to the right account. Floor suits an operation that routinely carries several clients plus test mailboxes without reshuffling logins every week.

Every tier still delivers the same core: standard SMTP and IMAP, browser webmail, and the warm-up and authentication checks. What you buy with the larger tiers is headroom. Read the published table on softwareprogrammer.app to confirm exactly what each level includes before you commit, and note anything outside the mailbox count.

The doubt a contractor brings is usually about proof. A client asks where a row came from, and an unverifiable row damages the relationship faster than a missed quota. Since the tier supplies no recipients, the proof has to come from your own sourcing records, kept alongside the mailbox that sends the campaign.

Read that honestly: the purchase solves sending identity, not attribution. You still need a source recorded against every row you hand over, and warm-up checks passing does not certify the data behind an address. Separate the two jobs in your own process so the client sees which part you control.

The other honest note is that delivery is not assured. A message can clear authentication and still miss the inbox, so a client reporting silence is not automatically a data failure. Agree with your client upfront how you will both read a low reply rate.

Start with a count, not a feeling. List the sending identities your next few engagements genuinely need and add one for testing. If that lands at five, Starter is the fit. If separating three or four clients matters to how you report replies, Studio at fifteen gives you room without spreading a single identity thin.

Ask whether you expect to add clients. A contractor who takes on work steadily will outgrow five mailboxes before the tier feels settled, while one running a small number of long engagements will not. Choose the tier that matches the work you already have, not a hoped-for pipeline.

Whichever you pick, confirm the published contents and any separately priced extras on softwareprogrammer.app first. Then set your sourcing records up before the first send, so the first campaign you hand over already carries the proof your client expects.