Separate client sending, one slot at a time

Thursday afternoon, two client send lists sit in the same folder and one lead has no owner. That is the week you start shopping. With Software Programmer you write the brief, and the build comes back as a working app with its data, logins and payments already part of it, so each client's sending sits inside its own tool rather than a shared box somebody forgets to filter.

You hand over the written brief as your client campaign description reads: who receives, which fields are captured, which payments are taken. The app that returns holds contact records, sign-in for the people who need access, and payment handling inside the same product. Because it is an app rather than an open inbox, a lead's path stays visible to the client whose campaign produced it.

The lifetime you buy is counted in apps, not in months. The store where every deal is run sells what you hold, and that store's rules sit alongside whatever you buy. For an agency, the unit of purchase is therefore the number of separate builds you can run, which maps closely to the number of clients you insist on keeping apart.

Three tiers are published on the site: one app lifetime, three apps lifetime, and ten apps lifetime. They differ in count alone. Nothing in the brief suggests the purchased app changes with the tier, so the question for a seven-client desk is arithmetic: how many separate tools does each client genuinely need before a single build can serve two of them?

Count first, then buy. If four clients need nothing more than a form that records a lead and confirms a payment, four slots cover them and the tier question is settled. If each client insists on its own sign-in and its own data view, add them up honestly before choosing. The published lifetime tiers are the only price structure in play.

A useful habit is to list every client against the apps you would build on day one, not the apps you might want later. A tier that leaves spare slots is spare capacity for the next retainer you sign. A tier that exactly fits may leave you short when a client asks for a second tool, and that slot would need to be bought separately.

Your objection is that one shared inbox mixes clients together. The brief covers separate apps rather than a single shared workspace, and a separate app is the mechanism by which client A's leads stay out of client B's list. The build itself does not merge records across the tools you hold. What you give up is the convenience of one login for everything.

That trade is worth pricing in hours rather than in feelings. A mixed inbox costs you a misdirected outreach, an awkward client call and a rebuild of the list. Separate apps cost you a little more switching and slightly more setup when a client joins. The choice is between a recurring risk and a fixed amount of housekeeping that you control.

Doubt also attaches to the selling channel. The store sells every deal you run, and its rules apply. Read them before you brief anything, because they govern what you are buying and how the app reaches you. Once that is clear, the remaining decision is the count, and the count is a client list rather than a leap of faith.

Take the three-app lifetime first, on an agency with three retained clients that each need a lead capture form, a login for the client contact, and payment on a signed proposal. One slot per client, written briefs for each, and three separate tools. The fourth client, when signed, sits outside the tier until you buy another slot or move up.

Now take the ten-app lifetime on the same agency. Seven clients could each hold a tool, with three slots spare for a client needing two separate apps, perhaps outreach on one and onboarding on another. This is the tier that gives room to keep every client apart without asking whether two could reasonably share. The published lifetime tiers are the sole price basis.

What decides between them is your client list rather than the feature list. Move the number of clients you expect to hold over the next few years against the apps each needs alone, then match that to a tier. Reading the store rules before you commit is the last step, and it belongs before you pay rather than after.