One shared AI account for the whole agency: terms, seats and bills

This happens in almost every small agency. Someone tries an AI tool on a free plan, likes it, and upgrades on their own card. A month later a second person does the same. By the third month you have five subscriptions, two of them for the same tool, and a client asks how much the AI work cost. Nobody can answer.

This page is about the buying side: who holds the account, what a team plan really gives you, and how to see the spend. It is not about which tool makes the best clips. For that, see the agency tool guide. I use Higgsfield as the main example because its terms and team help page are public, and I compare it with other tools on the same points.

This page may contain affiliate links from which Blur Studio earns commissions.

The problem: many cards, no visibility

Personal accounts cause four separate problems, and it helps to name them before you pick a fix.

• Cost you cannot see. Charges sit on staff expense reports under different names, so no one adds them up.
• Credits wasted. A credit is a unit of spend that the tool charges for each image or video. Subscription credits usually reset each month, so five half-used accounts waste more than one fully used account.
• Client work in personal accounts. When someone leaves, their account, their files and their history leave with them.
• Confidentiality. Any promise you made a client about how their material is handled cannot cover a personal login you do not control. I cover that in the page on keeping client work out of AI training.

Cheapest fix first: one producer account and a one page rule

You do not need a team plan to solve the first three problems. You need an owner and a rule. Once that is settled, see how to train your agency team on AI creative tools in a week.

Pick one paid individual account, owned by one named person. Call that person the producer. Everyone else sends a short brief (what the clip is for, the reference images, the size, the deadline) and the producer runs the generation. The company card pays. One bill, one place to look, one person who knows the cost per approved clip.

Write the rule on one page:

1. Work for clients is made only in the company account.
2. Personal experiments stay on personal free accounts and never use client material.
3. The producer keeps a sheet with date, client, tool, plan, credits used and whether the result was approved.
4. Finished files are saved to company storage, not left in the tool.
5. The budget owner checks the sheet every Friday.

This works well for one generator. It starts to hurt when the producer becomes a bottleneck, which is the signal to read the next sections.

Check the terms before you share anything

Many people reach for the simplest fix: one login that the whole team uses. For some tools that is fine. For Higgsfield it is not. Section 2.4 of its terms (last updated 23 October 2026) says you may not share your account or login credentials with anyone. I would read that sentence as written and not as a grey area.

The same terms, in section 2.5, describe the proper route. They cover organizations and workspaces. The workspace owner or administrator is responsible for paying the fees for the workspace and its members. So the tool expects you to add people as members of a workspace, not to hand out one password.

Rules differ by vendor. Before you suggest a shared login anywhere, search the terms page for the words "share" and "credentials", and check that tool's team plan page. A shared login also hides who did what, which defeats the point of this page.

When a real team plan is worth it: a headcount rule

Count the people who press Generate in a normal week, not the people who work at the agency. A designer who only reviews does not need a seat.

People generating each week	What I would do
1	One individual plan owned by the company. Producer model above.
2 to 4	Price a team plan with pooled credits against two or three individual plans. Choose on the seat math below.
5 or more, or a client contract needs controls	Talk to the vendor about Scale or Enterprise tiers and ask the questions in the vendor list below.

Two people generating once a month is still a one plan job. A team plan costs more per seat than an individual plan, so it needs to earn that difference.

What Higgsfield offers for teams

From Higgsfield's own help center (dated 2 August 2026) and its pricing page, as of 3 November 2026:

• Team covers 2 to 9 seats. The pricing page showed Team from $65 per seat. It has no single sign-on (SSO, one company login that staff use to enter all tools) and no member spend controls.
• Scale covers 5 to 15 seats. It adds SSO and the ability to pause a member's spend.
• Enterprise is custom and sold by quote. It adds per-user spend caps, roles and groups, usage export, and a written promise that your content is not used to train its models. SOC 2 (an independent security audit report) and legal indemnification (the vendor covering certain legal claims) are Enterprise only.

Three details matter for a small agency. First, if the real pain is "who spent what", Team alone does not solve it, because member spend controls start at Scale. The Usage page for each member under Manage Account is the fallback to check. Second, the help center says you cannot lower the seat count yourself in the middle of a cycle. You contact support and the next renewal starts with fewer seats. Third, VAT or a tax ID can be added on Team, Scale and Enterprise, which helps your accounts team.

Seat credits per plan are not something I will quote here. The numbers on the pricing page change, and some promotions on it end soon. Read the pricing explainer for the structure, and the credits guide for how to measure spend per approved result. Then confirm on higgsfield.ai/pricing.

How other tools handle teams

Here is what the vendors' own pages say as of 3 November 2026. Prices change, so confirm before you rely on them.

• Runway, an AI video tool aimed at creative teams, publishes its Team plan: $69 per seat per month, or $55 per seat per month billed yearly, starting at 2 seats. Each seat adds 6,900 credits a month to one shared balance, and unused credits roll over for one month. It lists comments tied to exact frames and up to 100 shared projects. Its individual plans are Free (125 one-time credits), Standard $15 ($12 yearly), Pro $35 ($28 yearly) and Max $95 ($76 yearly). Enterprise lists no training on your data and SSO.
• Luma, an AI video generator, lists Plus at $30 a month with commercial use and guest collaborators who can edit. Its Team plan says "contact us", with shared team credits, usage analytics and SSO.
• HeyGen, a tool that turns scripts into videos of talking avatars, lists Free (3 watermarked videos a month), Creator $29, Pro $49, and Business $149 plus $20 per seat per month (a line in its FAQ). Its page does not show in readable form which plans include a team workspace or role controls, so ask HeyGen before you count on them.

Runway is the honest winner on one point: you can budget before talking to anyone, because the Team price, seat range and pooling rule are public. With Higgsfield you read the Team price from the pricing tab, and Scale and Enterprise need a conversation. For a side by side on output rather than billing, see Higgsfield vs Runway.

Pooled credits: the saving and the trap

Pooled credits mean every seat draws from one shared balance. That helps when one person has a heavy week and another has a quiet one. Nothing is stranded on a single login.

The trap is that one heavy week from one person can empty the pool for everyone. Because subscription credits usually reset each cycle, an empty pool on day 12 means either waiting or buying a top-up. So pooling needs a weekly check, not only a monthly bill. Ask each vendor three things in writing: do credits pool, what rolls over, and can an admin cap a member? Higgsfield says every Team and Scale seat brings its own monthly credit allowance that pools into one shared balance, but Team has no member spend controls, and Runway's Team page does not list a member cap either.

Illustrative seat math for a three person agency

These numbers are made up to show the method, using Runway's published prices because they are the only team prices with a public source. Swap in your own vendor and your own numbers.

Option	Monthly cost	Credits	What you gain
Three individual Pro plans at $35	$105	6,750 total (2,250 each)	Cheapest. Three bills, no pooling, no shared projects.
One Pro plan, producer model	$35	2,250	Cheapest of all. One person is the bottleneck.
Runway Team, three seats at $69	$207	20,700 pooled	One bill, pooled balance, shared projects, frame comments.

The team plan costs roughly double the three individual plans but gives about three times the credits. It is only worth it if you use that extra capacity or the shared projects. If your three people used 5,000 credits last month, the individual route is cheaper. If they hit the limit by day 18 and bought top-ups twice, the team plan may be cheaper in the end. Look at what you actually spent, not what the plan offers.

Billing owner, alerts and a reserve

Guides on sharing AI credits keep returning to the same few habits, and they apply here too. Credits are not always transferable, so find out first what unit you are sharing: a monthly allowance, a purchased top-up, or per-seat credits.

• Name one billing owner. Only that person can buy top-ups or change the plan. Everyone else asks.
• Set an alert before the cap. If the tool lets you, alert at about 70 percent of the monthly balance. If it does not, put the check in the Friday review.
• Keep a reserve. Hold back roughly 10 to 15 percent of credits for reruns and urgent client fixes, so a heavy week does not leave you with nothing on delivery day.
• Tag spend by client in your sheet. Most tools do not tag for you, so the sheet carries a client column.
• Judge cost against approved work. Fewer credits used means little if the clips needed many reruns. Track credits per approved asset, not raw credits.
• Write down the plan and the date you decided. Billing rules change, and the note tells you when to look again.

The percentages above are my rules of thumb, not vendor figures. Adjust them after your first 30 days.

A 30 day test with pass and fail numbers

A plan you can run before you commit to a year:

1. Week 1. Producer account only. Log every generation in the sheet.
2. Week 2. Add one more person, on a monthly plan if the vendor offers it. Do not add seats you will pay for through the cycle unless you accept that cost.
3. Weeks 3 and 4. Keep logging. Calculate credits per approved asset.

Pass if you can state spend per approved asset for each client, at least 80 percent of credits are used, and the pool lasts to day 25. Fail if the pool runs dry before day 20 twice, or if nobody can say who spent a given block of credits. A fail means a plan with spend controls, a different vendor, or going back to the producer model.

Offboarding and staff privacy

When someone leaves, do these in order: remove the seat, confirm the shared assets stayed in the workspace, download client deliverables to company storage, and rotate any API or connector credentials that person created. Higgsfield's help center says assets stay in the workspace, and the person who made them loses sight of that project after leaving. Still, keep your own copies.

Also tell staff something many do not expect. Under Higgsfield's section 2.5, workspace administrators can access, manage and reassign members' content, and members should expect no privacy against administrators. Put one sentence in the written rule: personal experiments do not belong in the work workspace.

Who should skip a team plan

• One person generates. An individual plan is cheaper on every vendor.
• Your use is a few clips a month. Pay for a single month when you need it.
• You need per-user caps or an audit trail today and the tool you like only offers them through a quote you cannot get before a deadline. Use the producer model meanwhile.
• A client contract requires no training on their material. Team and Scale on Higgsfield do not carry that promise. Read the safety and legitimacy check and the training page linked above first.

How I'd approach this

I would start with the producer model this week. Name the owner, move the card, write the one page rule and start the sheet. That alone fixes most of the pain for the price of one subscription. After 30 days, the sheet tells you whether a team plan is worth it, and which one.

If Higgsfield is on your shortlist, I would price Team against your real headcount and confirm what you get on the Higgsfield pricing page, then ask support in writing about seats, credits and what happens if you remove a member. If you want to compare the all-in-one route with using separate tools, that comparison shows the cost logic.

If the sheet and the Friday check become a chore, that is the part worth automating. Blur Studio builds the repeatable workflow, approval portal or shared asset library around these tools, so the spend sits in one place. You can read more at our business page, with no hard sell.