— AI for small business / Rollout & training

Your team is already using AI. Make it the safe, useful kind.

Most staff have tried a chatbot at work, usually a free one, usually with client information in it. We pick the assistant that fits how your business works, set it up on a business plan with the data controls switched on, write the rules in one page, and train people on the jobs they actually do.

What changes in a normal week.

Today With it in place
Staff paste contracts and client emails into personal chatbot accounts you cannot see or close. Everyone signs in to one approved assistant with their work account, and a leaver’s access ends with their email.
Two people use AI daily, most tried it once, and nobody shares what works. Each role has a short set of workflows that save real time, and the team swaps new ones monthly.
You are paying for Copilot seats that mostly go unused. Licences go to the people who use them, and the rest of the team is on the tool that suits their work.

What the rollout covers.

  • Choosing the assistant

    Microsoft 365 Copilot, ChatGPT, Claude, or Gemini, based on where your files live and what the work is. Often one main tool for everyone and a second for a few heavy users.

  • Business plans, set up properly

    Team or enterprise plans whose terms keep your data out of model training, single sign-on with your Microsoft or Google accounts, retention settings, and the admin console configured.

  • Fixing what AI would expose

    Copilot can read whatever a user can open. We find and fix the over-shared SharePoint sites, Teams, and drives before it starts summarizing the HR folder for the wrong person.

  • A one-page AI use policy

    What can go in, what never can, which tools are approved, and who to ask. Written in plain English so people read it, not pasted from a template.

  • Training on real jobs

    Hands-on sessions by role, built from your own documents and tasks: the estimator drafts a quote, the office manager cleans up a policy, the owner summarizes a contract.

  • A 30-day check-in

    Seat usage, what people use it for, what went wrong, and which licences to cut or add. Then a short refresher on the workflows that stuck.

How the rollout runs.

About a month from first conversation to a trained team, with a pilot group before anyone buys seats for everyone.

  1. Audit what is in use

    A quick, no-blame survey of which AI tools people already use and for what, plus a look at your Microsoft 365 or Google permissions.

  2. Pick and pilot

    Three to five people trial the shortlisted tool on real tasks for two weeks. Their results decide the purchase, not a demo.

  3. Set up and lock down

    Business plan, sign-on, data controls, and the permission fixes. The policy goes out before the licences do.

  4. Train by role

    Short live sessions per team, recorded, with a one-page sheet of prompts and workflows for each role.

  5. Measure and adjust

    At 30 days we review usage and feedback, reassign seats, and add the workflows people asked for.

Safe by default, not by memo.

A policy alone does not stop someone pasting a client file into a free chatbot at 11pm. Settings do. We switch on the controls that make the safe path the easy one.

  • Business or enterprise plans only, with terms that exclude your data from model training.
  • Sign-in through your existing Microsoft or Google accounts, so leavers lose access the day they leave.
  • Over-shared files and sites fixed before Copilot or any connected assistant goes live.
  • Retention and history settings chosen deliberately, not left at the default.
  • A short list of data that never goes into any AI tool, such as health records and card numbers.
  • Personal and free AI accounts discouraged in policy and, on managed devices, blocked where you want them blocked.

Is it for you?

A good fit when

  • You have between five and two hundred people who work at a computer.
  • Some staff already use AI tools, approved or not.
  • You are on Microsoft 365 or Google Workspace, or about to be.
  • You want people to be good at it, not just licensed for it.

Probably not yet when

  • You want AI to replace a role outright. That is a different conversation, and usually a workflow automation project.
  • Your files and permissions are in a state you are not ready to look at. We can fix that first, but it is a separate piece of work.
  • You need a custom model trained on your data. We do not train models.

What it costs.

The rollout is a fixed-price engagement: audit, setup, policy, and training. The assistant licences are billed by the vendor per user per month, and we show you the total for your team before you commit, including which people do not need a seat.

What moves the number

  • Number of people and roles to train.
  • How much permission clean-up your Microsoft 365 or Google tenant needs.
  • One assistant for everyone, or a mix.
  • In-person sessions in Halifax or remote training elsewhere.
  • Whether you want quarterly refreshers as the tools change.

— Questions

Before you write.

Copilot, ChatGPT, or Claude: which is best?

It depends where your work lives. Copilot’s strength is working inside Outlook, Word, Excel, and Teams on your own files. ChatGPT and Claude are often stronger for drafting and analysing long documents, and they connect to Microsoft and Google files too. Many small teams use one main tool and give a second to a few heavy users. The pilot decides, with your real tasks.

Is it safe to put client information into these tools?

On business plans with the right settings, the major vendors state that your inputs are not used to train their models, and you control retention. On free or personal accounts that is often not true. That difference is the main reason to roll out a business plan properly instead of hoping people use the right account.

Can our data stay in Canada?

Some plans offer Canadian or regional data residency for stored content, and some do not. Processing may still happen elsewhere. We tell you, per tool and per plan, what stays in Canada and what does not, so you can decide with the facts.

Do you train people in person?

In Halifax and nearby, yes, if you want it. Elsewhere we train live over video in short sessions by role, record them, and leave a one-page sheet per role. Most teams prefer short sessions over a single long workshop.

We already bought Copilot licences. Can you still help?

Yes, and this is common. We check who is using their seat, fix the permission problems that make people nervous about it, and train the team on the workflows where Copilot is strongest. Often the answer is fewer seats, used well.

— Engage

How many of your people are using AI right now?

Tell us your team size, whether you are on Microsoft 365 or Google Workspace, and what you already pay for. We reply in writing within one business day with a recommended tool, a rollout plan, and a fixed price.

Esc