Available · 2 projects · Q4 2026Independent practice · Montreal

Process automation · Quebec SMBs

The tasks your team redoes every week can run on their own.

Copying an order from an email into the software. Rebuilding the same report every Monday. Chasing the same customers by hand. One by one, they’re small irritants; added up, they’re often a part-time position. I automate these processes end to end, connected to your current tools — and I add AI only where text needs to be read or written.

Gabriel Nadon, independent consultant in Montreal. You talk to the person who builds it.

What we automate most often
  • Double data entry between email, Excel and the accounting software.
  • Weekly reports put together by hand from three exports.
  • Follow-ups: unanswered quotes, overdue invoices, missing documents.
  • Routing a customer request to the right file and the right person.

The signs

If someone “bridges the gap” between two pieces of software, it can be automated.

The most reliable symptom: a person whose job partly consists of moving information from one place to another. That’s paid time that creates nothing.

  • The same data is typed twice, into two different systems.
  • A spreadsheet serves as a database, and only one person knows how to keep it up to date.
  • Reports arrive late because they have to be rebuilt every time.
  • Follow-ups fall through the cracks when someone is on vacation.
  • You already pay for Microsoft 365, Zapier or an ERP without using their automations.

How I work

You don’t automate a messy process. You simplify it, put a number on it, then hand it to the machine.

The tool comes last. Make, n8n, Power Automate, Zapier or a few lines of code: we choose based on your software, your volumes and the long-term subscription cost — not my preferences. When a step requires understanding an email or a PDF, an AI model handles it, with control rules and human approval.

  • The math first

    Hours per week × people × hourly rate × 50 weeks: if the number doesn’t justify automating, I’ll tell you.

  • Monitored, not forgotten

    Every automation reports its own errors. If a supplier changes its format, you know the same day.

  • Documented for you

    You know what runs, where, and how to stop it. No black box that depends on a single person.

How it works, in five steps

  1. Price the chore

    We measure what the process really costs today — in hours, errors and delays.

  2. Map the process

    Who does what, in which tool, with which exceptions. That’s often where half the work already gets simplified.

  3. Build

    The connections between your tools, the control rules and, if needed, the AI step that reads or drafts.

  4. Run in parallel

    The automation runs alongside the current method for a few days. We compare, fix, and earn the team’s trust.

  5. Go live

    The old method is retired, monitoring is in place, and we look at the next process.

Real results

Updating supplier prices at an independent grocery store took the equivalent of a part-time position — close to $56,000 a year. Automated end to end and connected to the existing point-of-sale system, it now happens without manual data entry — the team only approves — and the business buys at the best price on every order. Read the full case study →

Pricing

Automation sprint: from $4,500, fixed scope, 2 to 3 weeks. In Quebec, published prices range from about $2,500 to $10,000 for a first process. Price ranges and grants in detail →

Questions I often get

Make, n8n, Power Automate or Zapier: which one should we choose?

If the whole company is on Microsoft 365, Power Automate is often the natural choice. Make and Zapier are quick to set up for connecting web apps. n8n can be hosted on your own infrastructure, useful when data control matters. I recommend based on your tools and your volumes.

Which process should we start with?

The one that combines three things: it comes back every week, it always follows the same steps and it costs the most hours. The free calculator on this site gives you a first number in 30 seconds.

What happens if an automation breaks?

It warns you. Every flow has its alerts and a recovery procedure. Format changes at a supplier or in a piece of software are the most frequent cause — and the simplest to fix.

Do we need a technical employee in-house?

No. Your team knows the process; I handle the technical side. A sprint usually takes a few hours of your time, mostly at the start, to validate the rules.

Where does AI come into an automation?

Wherever text needs to be understood: reading an order received by email, extracting the fields from an invoice, classifying a request, drafting a reply. The rest is classic automation, more reliable and less costly.

Free review

What task does your team redo every week?

Describe it in two lines. I’ll reply within 24 hours with what can be automated, and at what price — whether or not we end up working together.

Or book your 20 minutes now

Reply within 24 hours. Or book 20 minutes directly.