Pricing an agency platform by apps, not seats

Money here buys finished apps, and the tiers are labelled by how many you get: one, three or ten across a lifetime. Look at your client list and count the separate tools you genuinely need, because that count, not the number of months you have been trading, decides which tier suits you.

Separation matters more than volume for your desk. Each client needs its own build so sending and lead records stay apart, which means a shared tool is not the answer to your objection. Count the clients who need their own app and let that number pick the tier.

Nothing in the published tiers is charged per month or per person, so the cost question becomes a build question. Read the tiers on softwareprogrammer.app against your brief list and note which clients already have a tool and which are still waiting.

Each tier hands you a set of lifetime slots, and a slot covers one app built from a written brief. Data, logins and payments come included in that build, so a client campaign that needs a sign-in and a checkout does not require a second purchase elsewhere.

The work starts from your brief rather than from a template you assemble. You describe what the client needs, and the build follows that description. For an agency running outreach, this is the point where a client-specific lead tool stops being a spreadsheet and starts being something you can hand over.

Lifetime is counted in apps, so a slot does not expire while it waits. That suits an agency whose client roster changes through the year: you can hold a slot until a brief is ready rather than buying access you may not use in a given month.

Your fear is a shared inbox that blends one client's leads into another's, and the tier structure speaks to that directly. Because a slot covers a single app, each client build stands on its own, and the separation you want is a matter of how many slots you hold, not a setting you hope behaves.

The store where every deal is sold sits alongside the tiers, so the purchase route is the same one used for each deal you run. That keeps the commercial side in one place rather than spread across separate contracts for each client tool you commission.

Where the doubt has weight is scope. A brief that describes something involved may need review before work begins, so the separation you plan should be paired with a realistic view of how detailed each client build is.

Set the tiers beside the alternatives you already use: separate accounts per client, a shared tool with filters, or a developer hired per project. The tier comparison is really a comparison of how many independent builds you end up paying for, so write down the per-client tools you need before you judge any option.

For six or seven clients, the middle and top tiers are the ones worth weighing, since a single slot will not cover a roster that size. Compare the number of slots against the number of clients who need their own build, and leave the remaining clients on whatever you use now.

Weigh the review step too. If several client briefs are detailed, the wait before work begins becomes part of your plan, and a tier with more slots does not shorten it. Price the tier against the builds you can actually brief in the coming months.