COLUMN
Generative AI starts with one department.
Don’t decide the company-wide rollout first
Before the all-hands email and the rollout meeting, what you decide isn’t the headcount but the one department that can answer who / for what / how often (for example: Sales Planning | proposal drafts | weekly). Teams that can’t answer don’t get mixed into a company-wide “in progress.” No plan document needed.
Before the rollout meeting, carve out one department →We start by separating the first department from the ones not to distribute to yet. No plan document, no sales deck after the call
Before the rollout meeting — don’t start with company-wide distribution
“Distribute to all employees” goes on the rollout deck first. IT issues the seats. The floor replies “we’re using it.” A quarter later, the teams that don’t use it can still be sitting in the same “in progress.”
This article is about not starting the rollout with company-wide distribution. This year’s renewal target is a separate matter; next year’s amount line is another. This is only about the order of distribution.
What you decide first isn’t a discount or a tool choice. It is the first department that can answer who / for what / how often — a way of splitting that fits your own approval and rollout rules. We don’t make that decision on your behalf.
What tends to remain a quarter after starting company-wide
| How the rollout started | What tends to remain a quarter later |
|---|---|
| Seats issued to all employees and called “rollout complete” | Teams that don’t use it sit in the same “in progress.” No end in sight |
| Interviews run across every department first | Impressions come in. Who / for what / how often doesn’t |
| “Pick the department once we have a success story” | No target gets picked. The company-wide blank comes first |
The first one weighs the most. “In progress” is a way of deferring the decision to stop distributing.
Before the rollout meeting, carve out one department →No plan document, no sales deck after the call
How to cut the first department
| Distribution target | Condition for inclusion |
|---|---|
| The one department to distribute to first | Can answer who / for what / how often on the spot. Issue seats here only |
| Departments not to distribute to yet | Can’t answer. Don’t mix them into the same “company-wide rollout” headcount |
| Departments to distribute to once the numbers are in | Look at them after the first department’s logs are in. Don’t distribute at the same time |
Don’t start from the biggest department. Headcount comes after distribution.
For the rollout meeting, write department / one task / frequency. Example: Sales Planning | proposal drafts | weekly. Tool name and headcount come after.
How to measure is in the three metrics; sending outside the scope you can’t produce in-house is in the scope of an external assessment. This year’s renewal is the renewal case; next year’s amount line is lines to keep and lines to cut. This article is about deciding, before all of that, the order of the departments you distribute to.
If you bring in an external assessment, “the first department” is easier to run than “the whole company” (our Metamon works on the same premise). A first conversation starts from cutting the rollout order. Whether to order an assessment or sign anything can wait until you have seen the result of the cut. If you only measure in-house, the cut is the same.
The note you can write in-house before the rollout meeting — not a plan document
| Department | First / Not yet / After the numbers | The one line for the rollout meeting |
|---|---|---|
| Sales Planning | First | Generates proposals weekly. Can state the count from day one |
| Accounting | Not yet | Not in the all-employee distribution. Don’t start with interviews |
| IT | After the numbers | Add seats after seeing the first department’s logs |
You don’t need a company-wide rollout plan. These three columns are what you can write in-house before the rollout meeting. When you contact us, no plan document or internal material is needed either. If you know things like the license unit price, the free-text field on the form is enough (leave it blank if not).
No need to hand over a company-wide sheet of impressions first. What the rollout meeting wants is the one department to distribute to first.
Before the rollout meeting, decide only the one department that can answer
Before distributing to all employees, we separate the first department from the ones not to distribute to yet. No plan document needed. We don’t send a sales deck. Individual rollout, approval, and contract decisions follow your own internal rules.
Before the rollout meeting, carve out one department →
References
This year’s renewal: A renewal case with no usage number
Next year’s budget: Decide by lines to keep and lines to cut
External assessment scope: Scope it to teams you can’t measure in-house
How to measure: The three generative-AI adoption metrics
Our service: Metamon (generative-AI usage diagnostic)
This article is a general framing, not legal, regulatory, or contractual advice. Decisions on renewals, budgets, and contracts follow your own internal rules.