Book a call →

Systems · Operations · Network · Automation

You shouldn't still be
doing this by hand.

Every business has work that eats hours and produces nothing — retyping data, sorting inquiries, chasing follow-ups, moving files between systems. SONA builds custom automation that takes that work off your team permanently, using the tools you already run on.

Book a 15-minute call → Build a workflow now
Based in
Montréal · EN / FR
Typical build
2 weeks to live
Runs on
Your existing tools
Commitment
Month to month

§ 01 Workflow composer

Describe the annoying part.
Watch the system build itself.

This is a working preview, not a video. Type the task that wastes your team's time and the composer assembles the pipeline that would replace it — the same structure I'd build for you, just generalized.

sona · composer idle

Plain language works best. English or French.

Common:

Pipeline

—

—

Est. recovered
— hrs/wk

Range, not a promise. Confirmed on the call.

This is the skeleton. Yours gets shaped around your actual software, your exceptions, and the edge cases that break generic tools.

Get this built →

§ 02 What the name means

Four commitments, one per letter.

The name isn't decoration. Each letter is a standard the work is held to.

S

Systems

Built, not bought

No template, no seat licence, no platform to migrate into. Your workflow is designed around how your business actually runs — including the exceptions that break off-the-shelf tools.

O

Operations

Where the hours go

I start with the operational middle nobody has time to fix: intake, handoffs, follow-up, reporting. Unglamorous work that quietly consumes a day a week.

N

Network

Your tools, connected

Your inbox, CRM, booking system and accounting software already hold the data. I make them talk to each other so nobody has to be the messenger between them.

A

Automation

Unsupervised by design

Monitored, error-handled and maintained. If something breaks at 2am, an alert reaches me before it reaches you — and the fix lands the same day.

§ 03 Systems already built

Four systems. Four problems worth solving.

Each of these is built and tested end to end — not a concept. They're the patterns I reach for most often. Yours will differ, because your bottleneck is yours.

SYSTEM 01 — DENTAL & MANUFACTURING LABS

3D print production routing

A lab receives STL files from clients all day. Someone opens each one, orients it, arranges the print bed, queues the job and updates the client. This system does all of it and only asks for a human when something looks wrong.

Operational win
~8 hrs/week returned
IN
File arrivesemail attachment or client upload portal
02
Model analysedpart type · orientation · support requirements
03
Bed arranged automaticallydensity packing across available printers
04
Job queuedsliced, named, pushed to printer fleet
OUT
Everyone notifiedclient, lab tech, production board

SYSTEM 02 — ANY BUSINESS TAKING INQUIRIES

Inquiry qualification & routing

Serious buyers sit in the same inbox as spam, students and time-wasters. By the time someone sorts through it, the good lead has called a competitor. This scores every inquiry the moment it lands and escalates the ones worth dropping everything for.

Operational win
Minutes, not hours, to first contact
IN
Inquiry capturedweb form · ads · DM · phone transcript · email
02
Context enrichedcompany, size, and fit signals attached automatically
03
Scored against your ideal clientrules you define, applied consistently every time
04
Noise filteredspam logged separately — never silently deleted
OUT
Priority alert firedSMS or chat to whoever can act fastest

SYSTEM 03 — CLIENT-FACING TEAMS

Email operations assistant

If your inbox decides how your day goes, the inbox is the bottleneck. Every message gets read, classified and answered in draft — so you approve replies instead of writing them, and only see what genuinely needs you.

Operational win
Most replies become one click
IN
Message receivedGmail, Outlook, or shared team inbox
02
Classifiedsales · support · billing · supplier · noise
03
Urgency assessedflagged against rules you set, not guesswork
04
Reply drafted in your voicebilingual EN/FR, matched to past correspondence
OUT
Routed or held for approvalnothing sends without a human saying yes

SYSTEM 04 — ADMIN-HEAVY OPERATIONS

Document & invoice processing

Invoices, receipts, purchase orders, intake forms, signed PDFs. The paperwork of running a business, currently being retyped by someone who has better things to do. This reads them, pulls what matters, and files it where it belongs.

Operational win
Data entry becomes review
IN
Document landsemail, upload, scanner, or phone photo
02
Read and understoodhandles scans and handwriting, not just clean PDFs
03
Fields extractedvendor · date · totals · tax · line items
04
Checked before it countsanomalies and duplicates flagged for a human
OUT
Filed into your systemaccounting, spreadsheet, or database — plus an archive

§ 04 How an engagement runs

Scoped like a build.
Not sold like software.

Most automation projects fail because they're treated as a product rollout. This is a build with a date on it: scoped, tested against your real data, deployed, then maintained.

Day 1 · 30 minutes

Show me the problem

You walk me through the task on a screen share. I map what can be automated and say plainly what can't. If the honest answer is that it isn't worth automating, you'll hear that.

Days 2–10

The build

Wired into your actual tools and your actual exceptions. You get a short Friday update showing what works so far — no silence until launch day.

Days 11–14

Tested on your data

Fifty-plus runs against your real historical records before anything touches live operations. Monitoring, error alerts and a fallback path are part of the build, not an add-on.

Ongoing

Kept alive

Software changes, processes drift, edge cases appear. Maintenance keeps the system working — and adapts it as the business moves. Month to month, cancel whenever.

§ 05 The questions people actually ask

Straight answers.

Including the uncomfortable one.

How many clients have you done this for?
SONA is early. The four systems on this page are built and tested, and the technical work behind them is real — but I'm not going to show you a wall of logos I don't have. What that means for you: you get direct attention from the person actually building it, pricing that reflects being early, and month-to-month terms so you're not trapped if it doesn't earn its keep. If a long client list is what you need to feel safe, I'd rather you find that elsewhere than oversell you here.
What if it breaks?
Every system ships with monitoring and error alerts, so failures reach me before they reach you. Fixes land same-day during the week. Every workflow also has a defined fallback — if the automation can't handle something, it routes to a human instead of failing silently. Silent failure is the real risk in automation, and it's designed against from the start.
Do we have to change the software we use?
No. That's the point. The system connects to what you already run — your inbox, your CRM, your booking platform, your accounting software. Nobody on your team learns a new interface, and there's no data migration. If a tool genuinely can't connect, I'll tell you before you pay anything.
Is our data safe?
Your system runs on isolated infrastructure — not shared with other clients, not on a home machine. I get user-level access to your tools, never passwords, and access can be revoked by you at any moment. For work where data can't leave your building at all, a fully local setup is possible; it costs more and takes longer, and I'll say so honestly on the call.
What does it cost?
A build fee, then a monthly fee for maintenance and monitoring. The build fee depends on how many systems the workflow touches and how many exceptions it has to handle — which is why I quote after the call rather than putting a number here that's wrong for you. You'll get a fixed price in writing before any work starts. No hourly billing, no scope surprises.
Can you work in French?
Yes — natively, both languages. Calls, documentation, contracts and the systems themselves. Bilingual handling is built into the workflows too: an email assistant that reads and drafts in French as fluently as English, which most automation tools do badly or not at all.
What if we want to take it in-house later?
Then you should. Everything is built on open, standard tooling rather than something proprietary you'd be locked into. There's a transfer option that hands you the system and its documentation outright. It costs more upfront and ends the monthly fee — a fair trade, and it's on the table from day one.

§ 06 Built on

n8n · orchestration Claude · reasoning OpenAI · extraction Ollama · local inference Airtable · structured data Postgres · persistence Hetzner · isolated hosting Cloudflare · edge & security Stripe · billing

§ 07 Next step

Tell me the part of your week
you'd pay to never do again.

Fifteen minutes, no deck. You describe the task, I tell you whether automating it is actually worth your money — and if it isn't, I'll say so. If it is, a fixed-price scope lands in your inbox within 24 hours.

Book a 15-minute call → Try the composer first

hello@sonaautomations.ca · Montréal, QC · EN / FR · Remote across Canada