Skip to main content
Sapt bills at the project level — but a project can have sub-projects, and they don’t pay separately. One parent project owns the plan and the credit pool; its sub-projects (typically your clients) draw from that same pool. You subscribe once, top up once, and pay from one card, no matter how many client workspaces you run.

​
Two kinds of project

A sub-project is just a project with a parent. The relationship is single-level: a sub-project can’t have its own sub-projects.
Sub-projects share billing identity, not data. Each project’s CRM records, content, workflows, integrations, and team membership are still its own — being a member of the parent does not automatically grant access to a sub-project. Only the plan and credit pool are shared.

​
Credits are one shared pool

The parent project holds the credit balance. Whenever any project — the parent or one of its sub-projects — uses a credit-consuming feature (AI generation, agents, enrichment, …), the cost is drawn from that single parent pool. There is no separate balance per sub-project. Usage is still attributed per sub-project, so you can see how much each client consumed — but every charge draws down the same parent balance, and the monthly refill replenishes that one pool on the parent’s billing cycle.
Because it’s one shared pool, there is no per-sub-project spending cap today. Per-client usage is reporting, not a budget — a busy client draws from the same pool as everyone else. Plan for the parent’s total, not per client.

​
Plan & entitlements are inherited

A sub-project runs on the parent’s plan. Upgrade the parent to Pro and every sub-project immediately gets Pro entitlements and the larger monthly credit allotment; there’s nothing to upgrade on the children. The same is true for custom plans — the parent’s entitlements apply across all of its sub-projects.

​
Where to manage it

Everything billing lives on the parent (top-level) project: the subscription and plan, the payment method, invoices, credit balance, top-ups, and the per-client usage breakdown. Open the parent project and go to Billing. Sub-projects have no billing screen — the dashboard sends you to the parent with a note that “billing is managed by the parent project.” This is the whole point of the model: one place to manage money, however many client workspaces you operate.

​
Good to know

  • Single level only. A sub-project can’t have sub-projects.
  • Deleting a sub-project doesn’t lose any credits — it never held a balance. Its past usage stays on the parent’s history (shown as a deleted client) so your records stay intact.
  • You can’t delete a parent while it still has sub-projects — remove or reassign the children first.
  • Spinning up clients. Creating a sub-project (and configuring it from a template) over the API automatically attaches it to the parent’s billing — see Building a client onboarding funnel.