Updated on 20 October 2026.
Semly Agency provides shared prompt and article resources that can be allocated across client projects. A useful allocation connects service scope, reserve capacity and ownership; client access and reporting permissions need separate decisions.
Define the shared resource and the project commitment
Semly's public agency offer describes shared prompt and article pools, client projects, project-level limits and team or client access. Projects can grow within available resources. Support for multiple brands does not mean unlimited questions or unlimited content.
Separate the agency agreement from each client commitment. The first establishes the purchased scope and terms. The second assigns resources to the work promised for a project. This makes it possible to check whether another client fits before the team starts generating material.
A prompt allowance should not be treated as the number of all answers or model calls. Counting depends on the offer and configuration. Confirm units, periods and change rules before using them in commercial calculations. The worksheet below is an operating proposal, rather than a Semly billing calculator.
Allocate against work the team can actually complete
For each client, identify market, language, buying needs and intended editorial work. A focused service business can need a different allocation from a broad store with an established editorial team. An equal split is convenient arithmetic, but it may be unrelated to the scope being delivered.
For article capacity, identify who can accept the output. If nobody can confirm specifications or implement revisions, a larger allocation can become a queue of unreviewed drafts. Agree a feasible scope instead of promising a publication count without an approval process.
A worked allocation ledger
Example data prepared only to explain the method, with no account information or brand results. Assume a planning pool of 180 prompts and 12 articles. These are worksheet assumptions, not a named plan, price quote or account allocation.
| Line | Prompts | Articles | Owner's responsibility |
|---|---|---|---|
| Project A | 50 | 4 | Agreed category coverage and revision acceptance |
| Project B | 60 | 3 | Market separation and offer confirmation |
| Project C | 40 | 2 | Buyer needs and implementation preparation |
| Agency reserve | 30 | 3 | Approval of additional work within scope |
| Total | 180 | 12 | Consistency of the complete allocation |
Project prompts total 50 + 60 + 40 = 150, leaving 180 - 150 = 30. Articles total 4 + 3 + 2 = 9, leaving 12 - 9 = 3. This check catches commitments exceeding the assumed capacity before work begins.
The reserve is a line in the agency's plan. It is not a claim about automatic resource transfers. Do not assume consumed capacity is refunded, carried forward or exceeded without charge. Those conditions must be confirmed in the current agreement and interface.
Handle a change as a recorded decision
Suppose Project C needs 20 more prompts and one more article. In this ledger it would receive 60 prompts and three articles; the reserve would become ten prompts and two articles. This is planning arithmetic. Whether the change can be executed depends on available resources and service terms.
Record the reason before changing the allocation: a new category, a distinct market or a confirmed unanswered buyer need. Check overlap with existing coverage. More capacity should buy a useful extension of scope, rather than additional versions of the same question.
Changing an allocation and changing monitored questions are separate actions. Adding or replacing questions changes what is observed. Later results should not be shown as an uninterrupted comparable series without explaining that change. Keep the decision date and reason internally, without copying private reports into public content.
Resource limits do not grant data access
Decide separately who may view a project, analyse information, prepare copy and approve its use. The public offer describes users and project-based access. Do not assume viewing a report grants every other permission; inspect the roles available in the current configuration.
Before inviting a client, check access to other projects. Before transferring material, remove information belonging to clients outside that scope. Confidentiality also applies to AI-generated drafts. Access to an analytical report is not permission to turn its contents into a public example.
Confirm the service before selling it
Establish counting units, the applicable period, model and market coverage, change conditions and behaviour when capacity is exhausted. Ask how the pool can be increased and which functions require separate scope. A panel screenshot or plan name cannot establish these commercial details.
Semly Agency describes white-label options and Google Data Studio reporting integration. Confirm the specific report format, data scope, branding and client access before committing. White label does not establish that every screen or document has identical configuration.
Keep resource promises distinct from outcome promises. The agency can define the analysis and editorial work it will deliver; it cannot guarantee that a particular publication count will cause AI recommendations. A content allowance is capacity to prepare material, rather than evidence of ranking improvement.
Keep one approved operating record
The completed record should contain allocation, reserve, owners and change rules. Keep planned capacity separate from actual use and approved publications. Accepting a task, generating a draft and releasing copy are different events. This prevents resource tracking from being mistaken for a visibility result.
After a change, compare the saved project state with the authorised decision and verify the remaining reserve. This guide prepares the decision; it does not invent undocumented button names or automatic billing behaviour. Consult the current interface or Semly support for the exact operation.
A smaller agency can keep this record in its normal work system. A larger team may assign an owner to review changes across projects. The essential requirement is the same: a client commitment should have an identified resource allocation and someone responsible for its acceptance.
Related guide on the blog
Organise AI monitoring across multiple client projects
