Does every employee need a paid AI account?

Start with the people doing the task

Your headcount alone does not tell you how many paid AI accounts to buy. A person asking an assistant to prepare work has a different role from a colleague reviewing the finished document in an existing business tool. Start by mapping those roles, then have the provider confirm the licences required for each. Neither a small pilot nor a custom automation automatically removes licensing obligations. The useful question is which people need which capabilities to finish one agreed task.

Make a simple access worksheet

Use one row per role, with these fields: task, tool opened, feature used, source information needed, output received and account requirement to verify. In a fictional eight-person service business, the coordinator drafts job summaries, the owner reviews them and six field staff read approved updates in the job system. If only the coordinator opens the assistant, that is one direct AI user to investigate. If the owner also asks the assistant questions, there are two. The six readers still need whatever access and licensing their job system and the proposed workflow require.

Check the feature, not just the product name

Microsoft documents Copilot Chat access with eligible Microsoft 365 subscriptions, while its work-based chat requires a Microsoft Copilot licence. It also describes assigning Copilot licences to users and checking the underlying subscription. A chat box appearing in an account therefore does not establish that the particular work feature you want is included. Ask the provider to demonstrate the proposed task while signed in as the intended staff member, using the actual plan. Other suppliers have different entitlements; do not transfer this Microsoft example to them.

Current primary documentation checked October 15, 2026. Supports the stated Microsoft-specific chat, user-assignment and prerequisite distinctions. Exact chosen-plan entitlements remain a separate check. Microsoft: Copilot licence options and user requirements

Distinguish an assistant from a connected service

If every employee will ask their own questions, prepare documents or work inside AI-enabled applications, review each intended user. If one configured workflow prepares a draft in a shared work queue, list the people building, running, approving and receiving that draft separately. Ask which user licences, process charges, connection fees or usage charges apply to those roles. Receiving a result is not evidence of a free entitlement. A provider should explain the chosen arrangement in plain language before including it in a quote.

Try the handoff with the actual roles

For the fictional office, use harmless sample notes and ask the coordinator to produce one draft. Have the owner check it through the agreed review route, then let a field colleague open the approved update. Record any extra login, missing permission, unexpected upgrade request or manual copying. If the reviewer cannot reach the source notes, solve that access problem before treating the trial as successful. Keep named access and business account ownership clear instead of planning around one password passed between staff. This exercise tests the proposed handoff; it does not prove every future case will work.

Budget for useful access and continuing work

Request a cost sheet naming each role, required plan, minimum purchase or commitment, recurring fee and any usage allowance. Include training, maintaining shared instructions and reviewing outputs. Check the current currency and billing terms rather than relying on an old screenshot. Compare whole-task staff time before and during the trial, including colleagues who return to their usual method. Any released time is capacity, not automatic payroll savings or revenue. The related adoption guide helps distinguish a missing account from a tool that staff can open but do not find useful.

Related Exovara guide: suitable tasks, attempts and accepted uses are different measures. The eight-person access worksheet and role demonstration above are original proposed exercises. Find out why staff are not using an AI tool

Expand after the first team can finish the job

A focused starting group can reveal what the rest of the business actually needs. Keep a list of roles deferred from the first version and what would justify adding them. Some may need direct AI help; others may benefit from clearer approved updates without changing how they work. Exovara can map those roles, check the proposed tools and scope a small setup with staff practice and a usable handover. You can start with an ordinary task and your current software, without arriving with a technical specification.

Related Exovara buying guide: agree the delivered work, dependencies, checks and ongoing costs before approval. Check what an AI setup quote includes

Want help putting this to work?

This guide applies across Canada. We provide remote AI consulting for businesses in Abbotsford; it does not describe a local client or a staffed office.

AI help in Abbotsford · See how we can help · View pricing and scope