Can one licence keep six or seven clients apart

Behind the purchase is a way to turn a client's legal problem into something you can act on: an action plan, a document draft, a deadline calendar and the list of agencies and steps that apply. That structure is what an agency needs when outreach work runs alongside a client's compliance question.

The deadline and evidence checklists matter more than the draft itself. When you are handling several clients at once, the risk is a missed date or a missing document rather than a badly written paragraph. A checklist you can hand to a client shows where the matter stands and what still needs to arrive.

Escalation routes are mapped in the output, which helps you tell a client when a question has moved past drafting and needs a lawyer. Tiers are split by usage or by bringing your own key, so the choice is about how much drafting volume you expect across those client accounts.

The lower tier is built around a single user's drafting volume, and the gap usually shows in how much work you can push through in a month. If six or seven clients each need an action plan, the cheaper allowance runs out before the month does, and you are back to rationing output.

Bringing your own key is the other route, and it shifts the cost of model usage to your own account. That suits an agency that already pays for a model provider, but it adds a setup step and a dependency you need to manage. The published tiers on softwareprogrammer.app set out which option fits which usage.

Neither tier adds client separation as a feature you can point at. The tiers change volume and key handling, not the way matters are kept apart, so the discipline of keeping one client's file out of another's stays with you and your team.

Your objection is the shared inbox that mixes clients together, and it is a fair one. A single workspace where drafts, deadlines and evidence lists from different clients sit side by side invites the wrong document into the wrong thread. The product organises a matter, not a client roster.

The practical answer is procedural. Start a fresh matter for each client, name it after the client and the issue, and keep the exported draft and checklist in that client's own folder. That way the tool supports your separation rather than replacing it, and an audit trail stays readable.

Ask yourself whether your team will actually follow that naming rule under deadline pressure. If the answer is uncertain, treat the licence as a drafting aid for one matter at a time and keep client records in your existing system of record.

Compare the three lifetime options on one question: how many matters will your client roster generate in a busy month. If the count is low and steady, the entry tier covers it. If outreach work brings a rush of questions, the higher usage tier or the bring-your-own-key route keeps the work moving.

Second, weigh the bring-your-own-key option against your existing provider arrangements. It can suit an agency already paying for model access, but only if someone owns the setup and the billing. Without that owner, the simpler tier is the cleaner choice.

Third, decide what you will do about separation before you pay, not after. Write the naming rule, pick the folder structure and tell the team. The comparison then comes down to volume and key handling rather than to a feature that solves the shared inbox for you.