· AI Automation Services

AI Automation for Quebec City Businesses

n8n and Claude workflows for Quebec City tourism, Saint-Roch tech and Sainte-Foy SMEs — delivered async, bilingual-aware, Law 25 friendly.

Serving: Vieux-Quebec · Saint-Roch · Sainte-Foy · Limoilou
Waseem Nasir, AI automation engineer serving

Industries I automate in

  • Tourism & hospitality
  • Insurance & financial services
  • Software & SaaS (Saint-Roch)
  • Public-sector suppliers

Where teams lose time

1

Vieux-Quebec tourism operators answer the same FR/EN questions thousands of times a season

2

Quebec City insurers are constrained by Law 25 and cannot use generic US AI tools out of the box

3

Saint-Roch software firms compete with Montreal and Toronto on smaller ops teams

Waseem Nasir, remote AI automation engineer

Client snapshot

What this looks like in practice

Worked with a Vieux-Quebec tourism operator on a bilingual concierge workflow. Web chat and email land in n8n, Claude answers standard FR and EN questions using their policy and availability data, and edge cases route to a human with full context. Summer inbox load dropped around 65% and the hotel stopped losing bookings to slow off-hours replies.

Who builds it: Waseem Nasir — AI automation engineer, digital nomad from Pakistan, based in Bali/ASEAN, serving global clients.

Frequently asked questions for clients

Can your AI workflows respect Law 25 for Quebec City clients?

Yes. I minimise personal data before any model call, document consent and retention at each step, and keep everything auditable. Your privacy officer gets a simple one-page summary per workflow that explains what happens, where, and for how long.

Can Claude handle bilingual tourism comms for Vieux-Quebec?

Yes. I tune it against your brand's FR and EN voice, add a Quebec-specific glossary for place names and terminology, and keep a bilingual reviewer on sensitive messaging. Guests get answers fast, in the right language, without the copy sounding machine-translated.

Do you work with Quebec City insurers on AI?

Yes, almost entirely as decision support. Claims triage, underwriting note drafting and customer comms are the most common use cases. The insurer always owns the decision; AI just does the reading, summarising and formatting that eats junior underwriter hours.

How do you run a bilingual project remotely from Bali?

Weekly syncs switch freely between English and French based on your team's preference. Deliverables ship in both languages where relevant. For anything especially nuanced in Quebecois French I keep a bilingual human reviewer in the loop so nothing ships that does not read naturally.

Book a Quebec City automation audit

30-minute discovery call. No pitch deck. I map your current workflow, identify the highest-leverage automation targets, and tell you whether it makes sense to work together.