AI automation and plain automation
AI automation takes on the work that fixed rules stall on. Most small businesses already run some plain automation: a nightly backup job, or a reminder that goes out on the first of the month. Those tools repeat the same steps and stop as soon as the input looks different.
Your staff spend their hours on the input that looks different. A client email asks three questions and mentions a deadline in passing. A supplier sends a quote as a scanned PDF. An AI model can read input like that, work out what it means and suggest the next step.
Some jobs need no AI. If the steps never change and the input arrives clean, a plain rule costs less and is easier to audit. We'll say so when that's the case.
AI for small businesses: where agents fit
An AI agent is a model with a goal and access to tools. It can open files, use software and work through several steps on its own, then hand the finished work back for review.
For years, a handwritten update script and a lot of practice kept our 100+ client websites updated. We rebuilt those tools with AI, so each update checks its own work and safety checks run before anything touches a live site. Setting up a new client site used to take two to three hours across four dashboards. Now one command plans the domain, hosting, security certificate, a safe home for the site's code, publishing the site and email, and the setup takes about five minutes.
We run agents on office work too. One reads our project threads and client requests, then sends a daily digest of the tasks waiting on a reply and the deadlines coming up. Another hunts missing receipts, and specs out and shops for hardware. Our people still do the work, and the digest shows them what's waiting.
The work that suits agents has a common shape:
- It repeats weekly or monthly, so the time saved adds up.
- A person could write the rules down, even when the inputs arrive messy.
- Someone can check the result before a mistake costs anything.
- Your staff dread it: software updates, status chasing, digging for paperwork.
Some work suits agents poorly. One-off decisions and work built on relationships belong with your people, and so does anything where one mistake costs more than a year of saved hours. Most AI for business pays off on a dull, recurring task that eats hours each week, so start there.
How we keep AI agents safe
An agent that is allowed to change things can make a wrong change to a live website or to the systems your office runs on. We build three controls into client AI work.
Permission boundaries
An agent gets the access its task needs and no more. Our office admin agent has a machine of its own, kept apart from the passwords and logins it doesn't need. If you gave an agent your website updates, it would need to reach the sites it maintains. It would have no reason to hold the login for your bank or your payroll system. Give each agent its own account, and you can switch one off without touching anything else.
Audit trails
An audit trail is a record of what an agent did and who approved it. If a setting on a website looks wrong months later, someone can trace it back to the step that changed it. We build that record in from the start. Before you trust any AI tool with your systems, ask the vendor to show you that record for a single change.
Human approval gates
The agent pauses before a consequential step, and a person approves it. If a check fails or the agent can't decide, it stops and leaves the item for a person to handle. Our own site setup tool has a gate like this: it lays out what it plans to create for a new client site and waits for our approval before it touches anything.
Local AI models for private data
Most AI tools send your data to a provider's servers for processing. For a lot of tasks that's acceptable. For patient charts or legal files, a professional obligation or a client contract may rule it out. In Alberta, the Health Information Act sets rules for health information held by custodians such as clinics, and the Personal Information Protection Act (PIPA) sets rules for personal information held by private-sector organizations. Depending on the data and your contracts, keeping it in-house can be the simplest way to meet them.
For data like that, we can run the model on a machine in your office or server room. Your staff reach it over your own network, so those documents don't have to go to an outside AI provider.
A model small enough for one office machine gives up some capability for that privacy. It can pull invoice numbers and dates from a stack of scanned forms, or sort incoming documents into the right folders. Summarizing a long contract or reasoning across a year of correspondence still goes better on a large cloud model, where the data allows it.
AI automation services in Edmonton: where to start
Our AI consulting starts by asking where your team's hours go. We ask which tasks repeat every week and which ones stall when the one person who knows them is away.
Bring real examples to that first conversation, such as the checklist someone works through every month or the email thread where a request got lost. Real samples show us where the input is messy and where a fixed rule would do the job.
A good first project for AI workflow automation comes with a clear test for a right answer. For a website update, the test is whether the site still works afterward: the pages load, the contact form sends and the store still takes orders. For document sorting, the test is whether each file lands in the right place. For a follow-up digest, you check whether a promised task ever drops off the list.
Brown Walrus is an independent Edmonton IT company, founded in 2011, with a team that has worked in IT since 2001. The same company handles managed IT, web development and cybersecurity, and a person picks up when you call during support hours.