What should a small startup expect to pay for SMTP mailboxes?

Money here goes towards mailboxes your team can sign into, configure and send from, not towards a sending platform that keeps your identity. The tier sizes are counted in mailboxes, and the published table on softwareprogrammer.app lists them as lifetime entries rather than annual renewals. For a small team that means you can budget once and stop paying again for the same tier.

Because the count is mailboxes, the arithmetic is simple. Work out how many people will actually send during the test, add nothing for vanity, and choose the tier that covers that number. Standard SMTP and IMAP mailboxes plus browser webmail mean a founder, a marketer and whoever answers replies can each work in the tool they prefer without a second purchase.

Warm-up and authentication checks come alongside setup, which is the part that takes time rather than money. None of this supplies recipients, so the cost of finding addresses sits outside the tier and stays your own work. Treat the tier as the mailbox budget, and treat your research time as the rest of the outreach budget.

Three lifetime tiers are published, named Starter, Studio and Floor, and each is sized by how many mailboxes you get. A startup running a first test usually sits at the bottom of that ladder, because the number of people sending is small. The higher tiers exist for teams that have already proved replies arrive and now need more sign-ins for more people.

What the mailbox actually gives you is ordinary: standard SMTP and IMAP so a client like any other can connect, browser webmail for whoever will not install anything, and warm-up plus authentication checks while you set things up. You write the messages yourself and you source the addresses yourself. Nothing in the tier behaves like a contact list or a sending volume allowance.

Where the tiers divide is mailbox count and nothing more dramatic. If two founders send the first batch, a small tier covers it. If a marketer and an operations person join afterwards, the count changes and so does the tier. Read the published table against your headcount before you commit, because the difference between tiers is scale, not extra sending features.

Will you be tied into an annual contract before a single reply lands? The tiers are published as lifetime entries on softwareprogrammer.app, so the commitment is a one-off purchase of mailboxes rather than a subscription that renews while you are still waiting for the first response. That is the point worth checking on the page itself before you pay.

The second doubt is whether the mailboxes will place your messages in the inbox. Warm-up and authentication checks help setup, but placement is not guaranteed, so an honest test should expect some sends to be filtered. Judge the test on replies received, not on a promise that every message reaches the main folder, and keep the batch small enough that filtering does not waste your effort.

The third doubt is hidden cost. Anything beyond the mailbox count, whether extra services or additional capacity, is priced separately, so read the published table in full rather than assuming a tier includes everything you saw during setup. If you need something the tier does not list, ask before paying and get the answer in writing.

Compare tiers on the number of mailboxes against the number of people who will genuinely send in the next month. A team of two testing a short sequence needs only the smallest tier that gives both a mailbox and a way to read replies. A team that expects to grow during the test should look at the next count up, but only if the extra sign-ins are already planned.

Compare on access as well. All tiers rest on standard SMTP and IMAP plus browser webmail, so a founder on a mail client and a marketer in the browser are served the same way. What changes between tiers is how many such people you can bring in, not how the mailbox behaves once it exists.

Finally, compare the tier price against the work you are doing outside it. Recipient research, message writing and follow-up are yours whatever tier you pick, and no tier reduces that effort. If the smallest tier covers your sending headcount, the honest comparison usually favours starting there and moving up after replies arrive, not before.