In Vernon, the local small-business organization has been asking a calmer question than most of the AI marketing that lands in your inbox. Not "how do we transform the company?" Just: how do you make a practical plan, and what do you do when the hype is louder than the work?
On December 4, 2025, Community Futures North Okanagan held a free workshop at its office at 3105 33 Street called AI Your Way: A Practical Plan for Your Business. The invitation opened with a line a lot of people in this town would recognize: "Feeling overwhelmed by all the AI hype? You're not alone." The session, led by Amber Wetherill of Your Friendly Dev, was offered as "a simple, practical plan for your business or non-profit," covering a strategy that works for "the curious innovator" and "the careful skeptic," the difference between AI and automation, a "safety kit" for data and clients, and a basic framework you can actually write down. It also asked people to bring their questions.
That is the right starting point for a Vernon contractor, a trade outfit, or a small shop. It was not a construction-only event, and it should not be dressed up as one. It was a local workshop, held here, for local businesses. The question still fits the work.
I should be plain about my own place in this. I live and work in Vernon. That does not make every contractor in the North Okanagan a client, and it does not make the Okanagan my whole market. This post is about the question asked at Community Futures, applied carefully to the kind of firms that already do this work here. It is not a claim about results.
Where the question came from, and the limits of the sources
A workshop agenda is not a survey. It tells you what Community Futures thought North Okanagan businesses needed, not how many contractors have tried a tool, or what happened when they did. The facilitator teaches this material for a living, so she has an interest in people making a plan. No public transcript of the questions asked in the room was found, so this post does not invent any.
The same office has run other practical sessions. In March 2025, Community Futures hosted AI-Powered Websites & Workflows for Small Businesses downtown, on website content, automating client processes, and documenting or summarizing meetings. It has also listed a session on AI tools for small-business revenue and growth. Those are useful supporting events. They are still small-business workshops, not trade-association research.
A search of public forums did not turn up a usable Vernon-specific Reddit or community-board thread in which a local contractor asked how to get started with AI. The strongest local questions are the ones Community Futures put on the calendar. That is a real source. It is also a limit, and it is better to say so than to pretend a job-site survey exists.
Why a practical plan matters here
BuildForce Canada's 2026 to 2035 outlook now includes a Thompson-Okanagan sub-market, and Vernon is named in it, alongside Kelowna, Kamloops, Penticton, Salmon Arm, Golden and Revelstoke. In that region, residential construction employment is projected to fall 11% from 2025 levels by 2035, while non-residential employment is projected to rise 6% on the back of ICI buildings and maintenance work. Province-wide, B.C. still faces a large retirement wave and a possible shortfall of 7,400 construction workers by 2035.
For a smaller centre, that usually means the same people are already wearing several hats. The estimator is also the PM. The owner is also writing the quotes. A tool that takes a real bite out of repetitive writing can help. A tool that needs a full-time owner, or that creates a second set of records to maintain, will not. The regional adoption story, including the gap with the Lower Mainland, is already covered in Why the Okanagan Lags Vancouver. The question here is narrower: if you are in Vernon and the hype feels noisy, what does a practical plan actually contain?
First, separate AI from automation
The Vernon workshop put this on the agenda for a reason: "What's the real difference? (And which one do you actually need?)"
They are not the same thing. Automation is a rule you can write down: if an invoice is 14 days overdue, send the reminder you already approved. AI is a draft you have to check: turn these site notes into a client update in your usual tone. A lot of firms need the first one more than they need the second. If your problem is missed follow-ups, a simple reminder in the system you already use may be the whole plan. You do not have to buy a "platform" to get that done.
AI is worth considering when the work is writing, summarizing or sorting, and you can review the result before it goes out. It is a poor fit when the work is a decision, a number you will be held to, or a process that is already unreliable on paper. If you want a general version of where to begin, the site already has Okay, So Where Do You Actually Start? and Five Minutes and a Free Account. The Vernon version is simpler still: name one job, decide whether it needs a rule or a draft, and do not mix the two up.
Build a small safety kit before you paste anything
The same workshop promised an "AI Safety Kit," with "practical steps to protect your data, your clients, and understand your responsibilities." You do not need a legal department to start that list.
Write down what never goes into a third-party tool: client drawings you do not have permission to share, personal information, incident details, and your own pricing, labour rates and margins. If a document would make you uncomfortable sitting on a coffee-shop table, it does not belong in a public chat window.
Then write down what "review" means. Every draft gets a name on it before it is sent. Every number, date and promise gets checked. The BC Construction Association's AI Hub says the same thing in different words: review what AI creates, and do not paste your cost breakdown or documents that are not yours to share. The habit of catching a confident wrong answer is in Don't Believe Everything the Robot Says.
A practical plan that skips this step is not practical. It is just faster.
The plan is not a list of tools. It is a short written decision about one job, one review step, and what you will not share.
If you cannot get that onto one page, you are still in the overwhelmed stage, which the workshop already said is common. That is fine. It is not a reason to sign up for five products.
Make a plan that works for skeptics and enthusiasts
Most small firms in this area do not have an "AI team." They have one person who wants to try everything and one person who does not trust any of it. The Vernon session named that split directly: a strategy that works for both.
The way through is not to convert anyone. It is to pick a low-risk task and agree, in advance, on what would count as success. One person tries a first draft of a weekly update or a meeting summary for two weeks. The skeptic reviews the output. If it saved time and the review caught the mistakes, you keep it. If it created cleanup work, you stop. Nobody has to win an argument about the future of the industry.
Keep the first task inside the office. Quotes, follow-ups, meeting notes and closeout checklists are enough. Leave pricing, safety calls and customer commitments with the people who already own them. A plan that starts on the highest-stakes work is not bold. It is careless.
The workshop also flagged "keeping your brand's authentic voice." That matters more in a smaller city than it first sounds. Most of the work here still comes from people who know you, or who were sent by someone who does. A letter that sounds like a generic marketing page, or a proposal that no longer sounds like your firm, is not a time saver. If you use a tool to draft, give it two of your own examples and tell it to stay in that voice. If the result still sounds like someone else, the draft is not ready, no matter how fast it arrived.
The same honesty applies to what this town is not. Vernon is not Vancouver, and a practical plan should not pretend otherwise. You do not need an enterprise platform to start. You need one task, one review, and a way to stop if it is not helping.
What to do with this
Write a one-page plan this week. Give it four headings: the task, whether it needs a rule or a draft, what must never be pasted into a tool, and who reviews the output. Use a job you already do every week, not a process you have been meaning to invent.
Try it on real work for two weeks. Time the drafting and the review. Then decide, in writing, to keep it, change it, or drop it. If you keep it, only then consider a second task.
That is the whole method. It will not make Vernon a technology hub, and it does not need to. It will tell you whether a tool helps your operation, which is the only question the hype never quite answers.
