COLUMN
One department succeeded.
Don’t make it the case for a company-wide rollout
The pilot worked. “Roll out company-wide” goes on the scaling deck. What you decide first isn’t the headcount — it’s which departments can state the same who / for what / how often as the pilot. Only those get the copy. The ones that can’t don’t get folded into the success story. No plan document needed.
Before scaling, carve out the departments not to copy to →We start by separating the one department that succeeded from the ones not to copy to yet. No plan document, no sales deck after the call
Before the scaling meeting — a pilot success is not a company-wide case
One department is generating proposal drafts every week. “It worked, so let’s go company-wide” lands on the scaling deck. IT adds the seats. A quarter later, the departments that don’t use it can still be sitting in the same “rolled out.”
Which department goes first is covered in rollout order. This article is about what comes after the success — not using it as the case for rolling out everywhere. It is also different from the PoC that never reaches production. Here, the premise is that one department is already using it well.
None of this dismisses the department that succeeded. It is a way of not folding departments that can’t copy the result into the same “success” — a split that fits your own approval and rollout rules. We don’t make that decision on your behalf.
What tends to remain a quarter after adding the success to everyone
| How the scaling started | What tends to remain a quarter later |
|---|---|
| The success story went into an all-hands email and seats were added | Departments that don’t use it sit in the same “rolled out” |
| The same prompts were distributed to every department | The work is different. Neither frequency nor quality lines up |
| Company-wide seat count was derived from the pilot department’s headcount ratio | Seats for departments that can’t state usage stay on next year’s amount line |
The third one weighs the most. Multiply the pilot’s headcount across the company and next year’s budget turns back into a conversation about seat counts.
Before scaling, carve out the departments not to copy to →No plan document, no sales deck after the call
How to cut the departments you copy to
| Scaling target | Condition for inclusion |
|---|---|
| Departments to copy to | Can state the same who / for what / how often as the pilot on the spot. Add seats here only |
| Departments not to copy to yet | The work is different, or the frequency can’t be stated. Don’t mix them into the success story |
| Departments to look at after the numbers | Review once the pilot department’s logs are in. Don’t add them at the same time |
Don’t push the pilot through by rewriting its task name onto another department. The moment you rewrite it, the frequency is blank.
For the scaling meeting, three lines are enough: the department that succeeded / the departments to copy to / the ones not yet. Tool name and headcount come after.
How to measure is in the three metrics; next year’s amount line is in lines to keep and lines to cut. This article is about deciding, before either of those, whether the success may be copied at all.
If you bring in an external assessment, “only the departments to copy to” is easier to run than “the whole company” (our Metamon works on the same premise). A first conversation starts from cutting the scaling scope. 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 scaling meeting — not a plan document
| Department | Copy / Not yet / After the numbers | The one line for the scaling meeting |
|---|---|---|
| Sales Planning (the pilot) | — | Generates proposal drafts weekly. Can state the count. This is the source |
| Sales Operations | Copy | Same proposal drafts, same weekly cadence. Can state who / for what / how often |
| Accounting | Not yet | Different work. Not counted in the success story’s headcount |
You don’t need a company-wide rollout plan. These three columns are what you can write in-house before the scaling 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 the pilot department’s feedback notes first. What the scaling meeting wants is the list of departments to copy to.
Before scaling, decide only which departments not to copy to
Before one department’s success becomes the company-wide case, we split the departments. No plan document needed. We don’t send a sales deck. Individual rollout, approval, and contract decisions follow your own internal rules.
Before scaling, carve out the departments not to copy to →
References
The first department: Company-wide rollout starts with one department
Next year’s budget: Decide by lines to keep and lines to cut
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.