Automation audit
Where your hours go, what is worth automating, and what to leave alone.
We build automations for businesses in Quebec and across Canada that run on their own, stop for your approval where a decision is yours, and are built to alert a person when a step fails. AI does part of the work; a person reviews it and answers for what we deliver.
Routine steps run without anyone watching.
Steps that commit you (money, a promise, a message to a client) are set to wait for your approval. A step runs on its own only if you agree to it in writing.
Each system is built to alert a person when a step fails, instead of failing quietly.
Where your hours go, what is worth automating, and what to leave alone.
The recurring work nobody has time for, rebuilt to run on its own.
Claude set up on your own computer, with training until you run it alone.
For work that has to read, decide and act, with your approval on the actions we agree need it.
Monitoring, adjustments and re-tests when the model underneath changes.
A machine-readable layer that gives AI assistants accurate facts about you to work from.
You keep the workflow files, the prompts and your own accounts.
Product names are trademarks of their owners. Naming a tool means we use it, not that its vendor partners with or endorses us.
Every job is quoted in writing before work starts: a fixed price for the scope of a build or setup, an hourly rate for training, a flat monthly fee for ongoing care. Third-party accounts are yours and are listed in the quote.
Every inquiry is read by a person, and every deliverable is reviewed by a person before it goes out. AI research agents draft the field notes and help with parts of client work; they are named on this site. Ask, and we will tell you where they are used on your work.
Your AI provider account is yours. Any account we host or operate for you is named in the quote. Before a build starts, you get this sheet filled in for your system, to use in your own Law 25 records. It supports your privacy impact assessment; it does not replace it.
| Provider | What it processes | Where it is processed |
|---|---|---|
| AI model provider | The text a step sends it | Named in writing |
| Workflow platform | The records the workflow moves | Named in writing |
| Email sending | Messages the workflow sends | Named in writing |
No. Describe the task in writing. The first read, the scope and the quote all come back in writing. A call happens only if you ask for one.
You keep your own account with the AI provider, so the account, the billing and the provider's terms are yours. We use the smallest data that does the job and tell you in writing which providers process it and in which locations, so you can document it for your own privacy obligations. Some providers process data outside Quebec; we tell you which. Running a model on your own hardware is possible: it is a compliance choice, not a saving.
Yes, as set out in your agreement: the workflow definitions, prompts and documentation we write for you are yours, and we hand them over as files with handover notes. The third-party tools they run on (n8n, your AI provider, hosting) stay under their vendors' licences and accounts. Documented for handover: the notes are written so another team can pick the work up.
They change often, and instructions written for an old model can make a new one worse. On a retainer we re-test your setup when the model it runs on changes and adjust it. Without one, you keep the checks and the documentation.
Every engagement is quoted in writing before work starts: a fixed price for the scope in the quote on setup and builds, an hourly rate for training, a flat monthly fee for ongoing care. Scope changes are quoted before they are done. Third-party subscriptions (your AI provider and any tool accounts the build needs) are yours, billed to you directly, and listed in the quote.
Often, no. A form, a rule or a simple assistant handles most recurring work, costs less and fails less. We start with the simplest thing that works and move up only when the task needs judgment across several steps.
We build it to work from your documents rather than from the model's memory, and to mark missing facts instead of filling them in. Outputs are checked against a fixed test set when the build changes, and a person approves the steps we agree need it. This reduces invented content; it does not eliminate it, which is why the approval step stays.