Most marketing tools charge per seat. You add a user, you pay more. Add five users, pay five times more. The seat was the right unit when the software was a workspace and the work was done by the people inside it. The seat measured the thing that actually did the work.
Agentic marketing breaks that assumption. The work is done by the system. The human steers. Two people steering one engine produce the same output as one person steering it, or zero people steering it on a quiet week. Paying per seat for a product where seats are not what produces the output is the wrong shape.
bbuddy bills in BBT: bbuddy-token. This post explains what BBT is, why we picked it, and what the design means for you as a user.
What BBT is
BBT is a unit of capacity. Every action your bbuddy engine performs costs BBT: drafting a post, generating an image, running an automation, replying to a chat, classifying a feed item. You start the month with a fresh grant of BBT. You use it as the engine works for you. When the period renews, the grant resets.
Concretely, on the Pro plan today: a single BBT grant comfortably covers a daily multi-channel posting cadence, regular image generation, ongoing automations, and day-to-day chat with bbuddy. Most accounts finish the month with headroom.
Why a capacity unit, not seats
Three structural reasons.
One: the engine is the worker. An agency steering bbuddy on twelve client accounts produces twelve accounts' worth of work. A solo creator steering bbuddy on one channel produces one channel's worth of work. The seat count is the same. The work is not. Capacity is the unit that scales with what you actually get.
Two: seats lock out collaboration. Per-seat pricing punishes the right behaviour. The founder, the head of brand, the freelance writer, the rotating intern, the account manager, all of these people should be in the workspace, leaving edits, approving drafts, watching the rotation. Per-seat pricing forces you to triage who gets in. Capacity pricing does not.
Three: capacity matches the value. A quiet month uses less. A launch week uses more. You pay for what the engine did, not for how many people happened to log in.
The hard-cap design
BBT has a single guardrail that we think matters: when your grant runs out, AI features pause. They do not overflow into a surprise invoice. Posts already scheduled keep going. New generations wait until the period renews or you top up.
We picked this shape on purpose. The standard usage-billed SaaS pattern is to let you run over and bill the difference. That keeps the engine running but it also turns billing into a horror movie for any team that ever forgets to check a dashboard. We would rather pause the engine than send you a bill you did not see coming.
What this means in practice
Five concrete things change with capacity billing.
You can invite everyone. Bring the team in. Bring the freelance writer. Bring the client. Workspaces are shared, the brief is shared, the queue is shared. Seats are not the unit of cost.
You can experiment without fear. Try a new rotation. Spin up a campaign mid-month. Throw an extra channel into the mix. The engine will use a bit more capacity. You will see the burn in your usage panel before anything else changes.
Quiet months are honest. If you do not ship for two weeks, you do not consume capacity for two weeks. Your unused grant resets at renewal, just like a fresh slate.
Launch weeks are predictable. A heavier week uses more capacity. The Pro grant has enough headroom for monthly launch cycles. We size it that way deliberately.
Cost stops correlating with team size.Whether you are a one-person creator or an eight-person agency, you are running the same engine. The agency uses more capacity because they have more accounts. The creator uses less. The price reflects the work, not the org chart.
Why we called it BBT
Capacity tokens have appeared in plenty of AI products. Most of them are anonymous numbers in a dashboard. BBT is named on purpose. It is bbuddy-token. It is the unit of work the engine performs for you. Naming it makes it a concrete thing you can think about: "this campaign cost about a third of my month", "this automation runs nightly and barely moves the needle", "I have plenty of room for the launch next week".
The unit needs a name because the unit is going to matter. Inbound marketing had MQLs. Agentic marketing has BBT.
What changes next
As bbuddy expands beyond social into email, paid, landing pages, and lifecycle, the same unit covers everything. You do not add a new line item for the new surface. The engine does more work, the capacity covers more surfaces, the grant scales with the plan you are on. One unit, one engine, every marketing surface.
The motion this fits is laid out in the agentic marketing manifesto. BBT is the billing shape that motion needed.