Services · AI
Claude for business, ChatGPT or Copilot.
Set up so the company is in control.
Your staff have probably already picked an AI tool, often on a personal account. We help you choose the business plan that fits, then set it up properly: admin console, single sign-on, data settings, connectors, policy and training. Vendor-neutral. You buy the plan direct; we resell nothing.
A Claude for business, ChatGPT or Microsoft 365 Copilot rollout from Pro IT NW, a Seattle-based, labor-only consultancy, puts your company in control of the AI tool staff use. We help owners and IT managers choose a plan, then configure admin settings, single sign-on, data retention, connectors, access, policy and training. You buy the plan directly from the vendor. We do not resell licenses or favor one vendor.
Start with what's already in use
Why not just let staff keep using the free version?
Because a personal account belongs to the person, not the company.
When someone pastes a client email into a personal AI account, the company has no admin view, no say in how long that data is kept, and nothing to switch off when that person leaves. Nobody did anything wrong; they found a tool that makes them faster.
The fix is not to ban AI. It is a business plan people would rather use, with the controls on and clear rules on what goes in it. If you want the discovery and policy work first, start with secure AI for business or our AI usage review.
What does a business AI rollout include?
Everything between buying the seats and staff using the tool well.
- Choosing the plan. Claude Team or Enterprise, ChatGPT Business or Enterprise, Copilot Chat or Microsoft 365 Copilot, matched to the controls you actually need.
- Admin console setup. Admins, workspace settings, features on or off.
- Single sign-on and identity. Staff sign in with their work account, so leaving the company ends access.
- Data and retention settings. What is kept, for how long, and who can see it.
- Connectors. Which business systems the AI may read, under whose permissions, and which stay off.
- Who gets access. Seats by role, not by who asked first.
- Policy. A short acceptable-use policy staff can follow, mapped to settings that enforce it.
- Onboarding and training. Hands-on sessions on your own work, not a generic demo.
- Measuring use. A look at what is actually used after a few weeks, and what to adjust.
Do the plans really differ on admin controls?
Yes, and the differences decide which tier you need.
One example from the vendor's own page: Claude's pricing page lists single sign-on on both Team and Enterprise, but user provisioning (SCIM) and audit logs on Enterprise only. ChatGPT's and Microsoft's plans draw their own lines. These details change, so we re-check the vendor pages at the start of every rollout.
Anthropic also announced Claude for Small Business in May 2026, which it describes as "a package of connectors and ready-to-run workflows that put Claude inside the tools small businesses depend on." Connecting accounting, CRM or email to an AI tool is a decision about data access, so we plan it with the rest of the setup.
For a plan-by-plan comparison, read Claude vs ChatGPT vs Copilot for business.
How it runs
How does a rollout run, step by step?
It is a scoped project with a start and an end, sized to your seat count and tools.
- Find out what is in use. Which AI tools staff use, on which accounts.
- Choose the tool and tier. Vendor-neutral, with the reasons written down.
- You buy the plan. Directly from the vendor, on your account.
- Configure. Admin console, single sign-on, data settings, connectors and access.
- Pilot. A small group first, so problems surface before everyone is on it.
- Train and onboard. Hands-on sessions, plus a plan for moving off personal accounts.
- Review. A few weeks in, check what is used and adjust.
What do we have at the end?
A working, documented setup your own people can run.
- The business plan configured, with admin access in your hands
- A written record of every setting and why it was chosen
- An acceptable-use policy and a one-page guide for staff
- Trained staff and a trained admin
- A short usage review with recommended next steps
What is this not?
The limits, stated plainly.
- Not a reseller: you hold the contract with the vendor
- Not tied to one vendor: Claude, ChatGPT and Copilot are all on the table
- Not legal advice on data protection or contracts
- Not a way to cut staff: AI makes skilled people more capable
- Not a custom build. If you need automations or agents built, that is AI automation and agents. For Copilot in Microsoft 365, see Copilot readiness for the permissions work first
Who is this for?
Owners, CFOs and practice managers who know staff are using AI and want it done properly, and IT managers asked to roll it out alongside everything else. You do not need to know which plan to ask for. That is part of the work.
Related: Secure AI for business · AI usage review · Copilot readiness · Staff using personal AI accounts
FAQ
Common questions about rolling out Claude, ChatGPT or Copilot.
Do you sell Claude, ChatGPT or Copilot licenses?
No. Pro IT NW resells nothing. You buy the business plan directly from Anthropic, OpenAI or Microsoft, on your own account and your own contract, and we do the setup work. That keeps the recommendation honest, because we earn nothing more from one tool than another.
Which is better for business: Claude, ChatGPT or Microsoft 365 Copilot?
It depends on what your staff already use, what data they handle, and which admin controls you need. A tool people will not use does not reduce risk. The bigger differences are in the business plans: single sign-on, user provisioning, audit logs and retention vary by vendor and tier. We help you choose, vendor-neutral.
What is Claude for Small Business?
Anthropic announced Claude for Small Business on May 13, 2026. Anthropic describes it as a package of connectors and ready-to-run workflows that run inside Claude Cowork and connect to tools such as QuickBooks, PayPal, HubSpot, Google Workspace and Microsoft 365, with the owner approving before anything sends, posts or pays. Connecting those tools is a data-access decision, so it belongs in the rollout plan.
Can we move staff off their personal AI accounts?
Usually, yes, but how much the vendor helps differs by plan. Some plans let you verify your domain and steer new sign-ups into the company workspace; pulling in existing personal accounts is more limited, and what is possible differs by vendor and tier. Part of the rollout is checking what your chosen plan actually supports and telling staff plainly what to move and what to delete.
Is this legal or compliance advice?
No. This is operational and technical work: plan selection, configuration, identity, data settings and training. It is not legal advice. If you handle regulated data such as health information, your counsel or compliance lead should confirm which vendor agreements you need before that data goes into any AI tool.
How is a rollout priced?
Scoped up front, on a call, by tool, seat count, existing identity setup, connectors and training needed. You get the scope in writing before work starts.
Free checks
Not ready to talk yet? Start with one of these.
Sample report
See a Copilot readiness report
A sanitized sample assessment: findings scorecard, readiness ratings and remediation roadmap, so you can see what you would get.
Open →
10 questions
Could you take back the keys?
Ten yes / no questions: could you remove your IT provider's access without their help and keep control? Admin accounts, domain, licenses, backups, contract dates.
Open →
Runs in your browser
Who controls your domain?
See who runs your domain's DNS, where your email goes, whether you publish DMARC, and whether on-prem Exchange is still visible. Nothing stored.
Open →
Pick the tool your team will actually use, and set it up properly.
Tell us roughly how many people, which AI tools they already use, and what systems you would want it connected to. We'll come back with a scope.