From the diagnostic to a team reflex.

AI consultancies often talk strategy, models, and “transformation.” We take care of what actually moves an organization: the people, the tasks, and how the work is organized once the tool is open.

This page is consulting and training. Diagnostic, workshops, work guides, adoption, Law 25 ops frame, tool choice. Not a menu of robots.

For a visible fixed-scope install — lead response, Google review asks, receptionist, SOP bot — see Tools.

Thirty minutes. No 40-page proposal.

Scope

What this page is — and isn’t.

On this page

  • A diagnostic and roadmap (90 days, then 12 months)
  • Role-based training on your files
  • Processes and work guides (human / AI / review)
  • Adoption support until it holds without us
  • Responsible use and Law 25 — plain-language ops frame (we are not counsel or RPRP)
  • Tool choice and setup for what you already have (ChatGPT, Copilot, Claude, Gemini…)

Not here

  • The five installed tools with fixed scope → /en/tools
  • An agent factory or custom-model lab (not the main offer)
  • A public price grid — we talk price on the call; numbers in the contract

Also

Visible proof first?

Sometimes the mandate starts with a simple automation: a lead that gets an ack at night, a review ask without faking, a number that answers after hours, an SOP that answers in Slack with citations.

That lives on Tools — fixed scope, human gates, then we expand into enablement if it makes sense. We do not mash the two here. Consulting on one side. Tools on the other. People stay in the middle either way.

Go to Tools →

The path

A diagnostic. Then a format.

We don’t ask you to pick six products. We start with a map. The format follows: 30 days, 90 days, or the year — sized to the work.

Framing

Diagnostic and roadmap

An honest read of where you really are: tools already in place, real usage, risks, skills, and how hungry leadership is. Out comes a prioritized plan — what unblocks fast first, bigger projects after.

  • Targeted interviews (leadership, IT, the business)
  • Use-case map by impact and feasibility
  • Tool recommendations, without a pointless catalogue
  • A 90-day plan, then 12 months

Then a format

Short

30-day sprint

A short diagnostic, one team workshop, one process written down. Ideal for an SME that wants to stop circling the topic.

  • Framing and one workshop
  • One process written down

Several teams

Year-round support

For organizations rolling this out across several teams: governance, a training calendar, a quarterly review, useful watch.

  • Governance and Law 25
  • Quarterly review
Book a call

Thirty minutes. No 40-page proposal.

If the mandate opens it

Training, process, adoption, Law 25, tools. The diagnostic says which. Not a menu to tick before the call.

Team training Skills

Not a tour of “50 prompts of the moment.” Workshops built on your documents, emails, reports, and client objections. People practise. They leave with a routine, not just inspiration.

  • Leadership briefing (2 to 3 hours)
  • Role-based workshops (half day or full day)
  • Multi-cohort programs for larger teams
  • Materials you can reuse internally
Processes and work guides Method

This is often where the real gain sits. We write how AI enters an existing process: a proposal, a file summary, a ticket, a contract review, a shift plan.

  • Task by task: human / AI / review
  • Work guides with examples from your context
  • Quality criteria and checkpoints
  • A versioned internal library of instructions (prompts)
Adoption support Anchoring

Training alone almost never holds. We stay in the picture until the use becomes ordinary: internal leads, short reviews, unblocking friction, adjusting the process after the first tries.

  • Naming and coaching champions
  • 30-minute rituals (weekly or biweekly)
  • Simple measure of usage and time recovered
  • A handoff so you no longer need us
Responsible use and Law 25 Frame

A frame that’s too heavy and nobody uses it. Too loose, and you take risks with personal information and trade secrets. We write the version your teams can pin next to the screen.

  • Usage policy in plain language
  • Classification: public, internal, confidential, forbidden
  • Alignment with Law 25 and sound retention practice
  • Roles: who decides, who reviews, who trains newcomers
Tool choice and setup Tools

We have no allegiance to a platform. We look at what you already have (Microsoft 365, Google, Slack), how sensitive the data is, and how comfortable the teams actually are.

  • A sober comparison: ChatGPT, Copilot, Claude, Gemini, line-of-business tools
  • Workspace settings, sharing, retention
  • Avoiding the second (or third) subscription
  • When an agent or automation is worth it — and when it isn’t

Common questions

Before you write.

Do you build custom agents or models?

That’s not the main offer. If a simple automation becomes obvious during the work, we’ll say so — and point you to Tools or to who builds it. Our job is that your teams know how to use it.

We don’t have a tool yet. Is it too early?

No. It’s often simpler: we avoid buying three licences “just to see.” The diagnostic is exactly how you pick a reasonable first step.

Do you work in English?

Yes. Workshops, work guides, and policies can be delivered in English or in Quebec French. Mixed teams are common; we adapt.

Do you only work in Montreal?

We’re based in Quebec. Workshops happen in person in Montreal and in the regions when the trip is worth it, or remotely when that’s more effective.

What does it cost?

It depends on the number of teams and the length of the work. A framing sprint is not an annual rollout. We give you a sense of price on the first call, before any written proposal. No public price grid.

Law 25: do you act as counsel or RPRP?

No. We draft management docs (inventory, classification, ops pause triggers) that the client’s RPRP or counsel can adopt. We are not lawyers and we do not act as RPRP. Counsel / RPRP decide.

Where are the installs — lead response, receptionist, and so on?

On Tools. This page is consulting and training.

Are the Fiverr @notaissue packs the same thing?

No. On Fiverr, some packs stay files only. Live installs and enablement are on notaissue.ca — different product, different responsibility. Detail on Tools.

Tell us where it sticks.

Thirty minutes to see where you are. You talk to the person who would do the work, not a salesperson. We talk price on the first call.

If you want a visible fixed-scope proof first → Tools. If you want the method so it holds as a team → you’re in the right place.

Not an issue.