Preview for review. Not live, not indexed, and the form doesn't send anything yet.
Palo Alto Networks is buying Applied Compute for $4.5BWhat it means for you →

A 30-day AI rollout plan for your company

The plan we use for clients, written out so you can run it yourself. It works for ChatGPT Business, ChatGPT Enterprise and Claude's business plans.

Short answer: spend the first three days on setup and data settings, the next week building two or three workflows per team on their real documents, the second week training each team on those workflows, and then measure usage and time saved at day 30. Most rollouts that fail skip the workflows and the training.

Before day 1

Days 1 to 3: setup

TaskWhy it matters
Create the workspace and admin rolesOne owner, one backup. Avoid personal accounts.
Turn on single sign-on if your plan has itPeople leave; access should leave with them.
Set data retention and sharing rulesDecide what can be shared across the company and what stays private.
Choose which connectors are allowedDrive, email and CRM connectors are powerful. Turn on what each team needs.
Write a one-page usage policyWhat not to paste in, who to ask, how to report a problem.

Days 4 to 10: workflows per team

Build two or three reusable setups per team, each for a task from the list above. Load each one with real examples: past proposals, the price list, the support policy, the month-end checklist. Typical first workflows:

Sales

Proposal drafts from call notes, follow-up emails, account research before meetings.

Support

Reply drafts that follow your policies, ticket summaries, help-article updates.

Finance and ops

Invoice and contract summaries, spreadsheet clean-up, month-end checklists.

Days 11 to 17: training

Days 18 to 30: use, fix, measure

Questions

How long does it take to roll out ChatGPT to a company?

Setup takes a day or two. Getting people to actually change how they work takes two to four weeks of workflows and training.

Who should own the AI rollout internally?

Someone who understands how the teams work day to day, with IT involved for setup and security. It works badly as a side project for IT alone.