S
Systems
Built, not bought
No template, no seat licence, no platform to migrate into. Designed around how your business actually runs — including the exceptions that break off-the-shelf tools.
Work goes in messy.
It comes out handled.
Every business runs on tasks that consume hours and create nothing — retyping data, sorting inquiries, chasing follow-ups, moving files between systems. SONA builds the system that absorbs that work, using the tools you already have.
- Based in
- Montréal — EN / FR
- Typical build
- Two weeks to live
- Runs on
- Your existing tools
- Commitment
- Month to month
What the name means
Four letters. Four promises.
The name isn't decoration. Each letter is a standard the work gets held to.
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 eats 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, maintained. If something breaks at 2am, the alert reaches me before it reaches you — and the fix lands the same day.
Systems already built
Four problems worth solving.
Each of these is built and tested end to end — not a concept slide. They're the patterns I reach for most. Yours will differ, because your bottleneck is yours.
Dental & manufacturing labs
3D print production routing
A lab receives model files all day. Someone opens each one, orients it, arranges the print bed, queues the job, updates the client. This does all of it — and only asks for a human when something looks wrong.
- Operational win
- ~8 hrs a week back
File arrivesEmail attachment or client upload portal
Model analysedPart type, orientation, support requirements
Bed arranged automaticallyDensity packing across available printers
Job queuedSliced, named, pushed to the printer fleet
Everyone notifiedClient, lab tech, production board
Any business taking inquiries
Inquiry qualification & routing
Serious buyers sit in the same inbox as spam and time-wasters. By the time someone sorts it, the good lead already called a competitor. This scores every inquiry the second it lands.
- Operational win
- Minutes to first contact
Inquiry capturedWeb form, ads, DM, phone transcript, email
Context enrichedCompany, size and fit signals attached automatically
Scored against your ideal clientYour rules, applied the same way every time
Noise filteredSpam logged separately — never silently deleted
Priority alert firedText or chat to whoever can act fastest
Client-facing teams
Email operations assistant
If your inbox decides how your day goes, the inbox is the bottleneck. Every message read, classified and answered in draft — so you approve replies instead of writing them.
- Operational win
- Most replies become one click
Message receivedGmail, Outlook, or a shared team inbox
ClassifiedSales, support, billing, supplier, noise
Urgency assessedAgainst rules you set, not guesswork
Reply drafted in your voiceBilingual EN/FR, matched to past correspondence
Routed or held for approvalNothing sends without a human saying yes
Admin-heavy operations
Document & invoice processing
Invoices, receipts, purchase orders, intake forms. The paperwork of running a business, currently being retyped by someone with better things to do. This reads them and files the result.
- Operational win
- Data entry becomes review
Document landsEmail, upload, scanner, or a photo from a phone
Read and understoodHandles scans and handwriting, not just clean PDFs
Fields extractedVendor, date, totals, tax, line items
Checked before it countsAnomalies and duplicates flagged for a human
Filed into your systemAccounting, spreadsheet, or database — plus an archive
Workflow composer
Describe the annoying part.
Watch it get solved.
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.
Plain language works best. English or French.
Pipeline
—
—
- Est. recovered
- —
A 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 →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, maintained.
I
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 it isn't worth automating, you'll hear that.
II
Days 2–10
The build
Wired into your actual tools and your actual exceptions. A short Friday update shows what works so far — no silence until launch day.
III
Days 11–14
Tested on your data
Fifty-plus runs against your real historical records before anything touches live operations. Monitoring, alerts and a fallback path are part of the build.
IV
Ongoing
Kept alive
Software changes, processes drift, edge cases appear. Maintenance keeps it working and adapts it as the business moves. Month to month, cancel whenever.
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: 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 quietly. 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 learns a new interface, and there's no 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 you can revoke it 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 handles — which is why I quote after the call rather than posting a number here that's wrong for you. You 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.
Built on
n8n orchestration
Claude reasoning
OpenAI extraction
Ollama local inference
Airtable structured data
Postgres persistence
Hetzner isolated hosting
Cloudflare edge & security
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.
hello@sonaautomations.ca · Montréal, QC · EN / FR