The short answer.
Not every employee needs an AI licence on day one. A role gets a paid seat on your company’s assistant when your plan gives that role a workflow to run, and then every person in that role gets one. Count seats from the plan, role by role, never from the headcount, and the seat count rises each time the plan gives another role its first workflow.
Deciding seats is part of planning your use of AI, the first of three steps: plan it, develop the workflows, deploy them. What AI are we already paying for? lists the seats you have today, and Should we standardize on one AI assistant? settles which assistant they are on. This piece decides who gets the next seat, and why.
The seat rule: a workflow to run means a seat.
The seat rule is one line: a role gets a seat when the plan names a workflow that role runs, what the workflow starts from, and who checks what it prepares. A seat bought before that workflow exists is a seat waiting for work. A seat bought with the workflow is used from the first day, because the person in the role has a named piece of their own week to run in it.
The rule settles the three arguments every leader hears about seats.
- “Give everyone a seat and see what happens.”Experimenting was the right way to start, and a company that experimented has learned what its people reach for. The next seat goes where the plan has put a workflow.
- “Only give seats to the people who ask.”The people who ask are often the keenest, not the roles with the most repeating work. The plan names the roles; asking is not the test.
- “Seats for managers first.”A seat goes to the role that runs the workflow. Often that is the person who does the work every day, and the manager is the person who checks it.
Who waits for a seat, and what they do meanwhile.
A role with no workflow on the plan waits for its paid seat, and the wait has a date. Every role on the plan carries one of three marks: has a workflow, has a workflow being developed, or not yet. A role marked “being developed” gets its seats the week its workflow is ready for testing, so the people who will run it test it on real cases.
Waiting is not the same as being left out. The company’s default assistant stays available for the things people already do with it, under the company’s rules, and nobody uses a personal account for company work. How do we plan AI by role? covers writing each role’s first two or three workflows, which is how a waiting role moves up the list.
Seats belong to roles, not to people.
An AI seat belongs to a role on the plan, so when a person changes role or leaves, the seat follows the role, not the person. The person who takes over the role inherits the seat and the role’s workflows on the first day. The person who moves to a role without a workflow hands the seat back.
Holding seats by role keeps the seat list honest. Each seat on the list points at a role, and each role points at the workflows it runs. When a seat sits unused for a month, the question is about the workflow: whether it fits the work, whether its inputs arrive, whether the person in the role was shown it. How to run a monthly AI review puts that question on the agenda every month.
A seat list to copy.
Copy these headings onto one page, one row per role. Fill it in from the plan, not from the payroll.
- Team and role.The team, then the role inside it, named for the work.
- People in the role.How many people hold the role today.
- Workflow the role runs.The named workflow, or “none yet”.
- Status.In daily use, being developed, or not yet.
- Who checks the output.One name. That person reads what the workflow prepares and decides.
- Seats.The number of people in the role if the status is “in daily use” or “being developed”. Zero if “not yet”.
- Seats held today.From the list you made when you took stock.
- The change.Add, keep or hand back, with the date it happens.
The total of row six is your seat count. The difference between row six and row seven, role by role, is your buying decision.
A brokerage counts its seats from the plan.
Take a 65-person insurance brokerage with five teams: commercial lines, personal lines, claims advocacy, producers and finance. Some staff already held seats on the company assistant, bought for whoever asked, and the rest used it without a seat or not at all. The operations director built the seat list from the plan.
Illustrative example.
- Commercial lines account managers.The plan gives them a renewal summary workflow that starts from the policy and claims export in the agency management system and prepares a renewal brief for each account. The commercial lines manager reads each brief before it reaches a producer. Status: in daily use. Every account manager gets a seat.
- Personal lines service.A workflow that drafts the reply to a policy change request, from the request and the current policy, is being developed. The service lead checks every draft. Every person in the role gets a seat the week testing starts.
- Claims advocacy.The plan gives the claims advocates a workflow that turns a client’s first report of a loss into a claim summary for the carrier. Status: being developed. Seats with testing.
- Producers.Several producers held seats because they asked first. The plan has no producer workflow yet; the prospect research workflow is scheduled for next quarter. Status: not yet. The producers keep the default assistant for what they do today, and their paid seats move to the claims advocates.
- Finance.Commission reconciliation is on the plan for later in the year. Status: not yet. No seats this quarter.
The brokerage bought seats for the roles with workflows and moved the seats it already held, instead of buying one for every employee. The renewal summary started from a free workflow template in the Workflows Directory, adapted to the brokerage’s own renewal brief and tested on last season’s renewals before any producer saw one.
What is different in a company of under 200 people.
In a company of under 200 people, you decide seats role by role, by name, in one sitting. A large company buys seats in blocks through a procurement cycle and works out who uses them afterwards. You know every role and who holds it, so the seat list and the plan are the same page.
- One person can be a whole role.A single office manager or bookkeeper is a role on the plan. When that role has a workflow, that one seat carries a whole function.
- Moving a seat is quick.The admin page of your assistant is one screen, and the operations lead who keeps the plan can move a seat the day a role changes.
- Every seat is visible.With a few dozen seats, each one points at a role and a workflow you can name. That is the whole case for each seat, written down.
Start the seat list from the plan. FullyPowered Planner is where the plan lives: you set out your teams, their roles and the work between them, choose what to build first, and your colleagues add their own teams. The roles with workflows are your seat list. How organizations plan their use of AI covers the rest of the method.