If you have just received a one-time website build from a studio or a freelancer, the next question is the one most people did not ask in the contract: how do you actually run the thing you now own? The honest answer is that running it is not a second project. It is a cadence. Two minutes a week, about half an hour a month, and half a day once a year — roughly one hour a month in total, spent mostly looking rather than building.
That is the whole pitch, and it is good news. A one-time build hands you a working website, not a second job. The failure mode we see most often is not that the work is hard; it is that nobody ever put the rhythm on a calendar, so six months later the contact form has quietly stopped arriving, the certificate has expired, and the owner assumes the website is somehow broken. It usually is not broken. It was simply not looked at.
The short answer, before the long one: the discipline is the cadence, not the work. The work is small. The cadence is what keeps it small.
If you have not been handed the site yet, start with what you actually own when you pay for a website, so you know which accounts should end up in your name. If you are still deciding between the two models, the managed vs one-time comparison is the trade-off, and how much a small-business website costs in Canada is the budget context. This guide is the part in between: the operating rhythm that turns a clean handoff into a site that keeps earning its keep.
What handoff actually includes
A clean handoff gives you three things: access, files, and documentation. Access is the important one, and it is the one most commonly botched.
Access means working logins to every service the site depends on. The domain registrar is one. The hosting account is another. The site admin is a third. The business email account that sends from your domain is a fourth. The analytics account is a fifth. A clean handoff gives you a list of every account, the role you hold on each, and the recovery options for each one. A messy handoff gives you a single email from the studio containing a single password that works for half of them — and a support relationship that ends the same week.
If the accounts are still in the studio's name, you do not own them yet, no matter what the invoice says. Getting the domain and hosting into accounts you control is the single most important thing in this entire guide, and it is also the step most often deferred. What you actually own when you pay for a website walks through the specific wording to look for in a contract or proposal.
Files means the design files, the source code, and any exported content. If the studio used a content-managed platform — WordPress, Webflow, or a builder — the design and code largely live on that platform, and what you receive is the export. If the studio built something custom, you receive the source files in a folder. Either way, the files should be yours, in a format you can open, stored somewhere you control.
Documentation is the part most studios skip. A good handoff includes a short document covering the site structure, the account list, the backup arrangement, and a named contact at the studio if something goes wrong. A better one includes a short screen recording of how to edit the site, made for your site rather than generic.
The test is simple: could a competent friend take over tomorrow afternoon using only what you received? If the answer is no, the gap is worth closing now, while the studio still wants the project to end well.
The first 30 days
The first month after handoff is when sites quietly drift. The studio stops touching it; you have not yet built the habit of touching it. Three things, in this order.
Verify every login. Open every account on the day of handoff. Change the password to something only you know. Turn on two-factor authentication wherever it is offered. Add a recovery email and a recovery phone that are not on the same device as the primary login. Store the credentials in a password manager — not a sticky note, not a browser autofill profile tied to someone else's machine. If you do not use a password manager yet, this is the week to start one.
Confirm the backup plan. A site that backs up to the same provider that hosts it is not meaningfully backed up. Ask where backups are stored, how often they run, and — the question that actually matters — how to restore one. If the answer is "we have it," ask to see the backup list and one example of a restore. The point is to know the answer before you need it.
Put the cadence on the calendar. Pick a recurring slot — Friday afternoon, Sunday morning, whenever you will actually do it — and name it after the activity, not after the vague intention. "Check the website" gets skipped. "Friday 4pm: two-minute site check" gets done. This is the single highest-value thing you set in the first month, and the four sections below are built around it.
The first 30 days are also the right window to fix whatever the studio missed — a broken link, a missing image description, a phone number that reads "text only" by accident. Studios are most responsive in the first month. Six months later the same request costs you a new invoice.
The weekly maintenance rhythm
The weekly check is two minutes and looks the same every week. Open the site on your phone. Tap the main call to action. Submit the contact form. Confirm the email arrives. If the site books appointments, book a test slot and cancel it. If it sells something, add a test item to the cart and remove it.
That is the whole thing. The point is not to fix anything; the point is to notice anything that needs fixing. A weekly check that repairs a broken link is good. A weekly check that flags it and books the fix for the weekend is better. A weekly check that never happens, because it felt like too much, is the actual failure mode.
Checking on a phone is not optional. Google indexes and ranks the mobile version of a page, and most of your customers will see the site on a phone first — Google's page experience documentation sets out the mobile-first principle in more detail. The desktop view is convenient for editing; the phone view is the one that matters to a customer.
While you are there, check the address bar. If the padlock is missing or the browser warns that the connection is not secure, the SSL certificate has expired. Most hosts renew it automatically, but the renewal still fails silently when the card on file has expired — which is a bookkeeping problem disguised as a technical one.
The monthly and yearly reviews
The monthly review is about half an hour. Log in to the site admin and apply any outstanding updates to the platform, theme, and plugins. Read the host's security log. Read the admin access log and look for sign-ins you do not recognise. Look at analytics for the past four weeks and flag any sudden drop. Check Search Console for new errors on the pages customers actually land on.
The yearly review is half a day, and it is where a Canadian business earns its keep:
- Renew the
.cadomain. It renews annually, your registrar bills it in CAD, and the price you see today is not guaranteed to be the price you pay next year — registrars pass through CIRA's wholesale changes as they happen. Confirm the renewal is on, and confirm the card on file is still valid. - Renew hosting and confirm SSL is auto-renewing. Then check it actually renewed rather than assuming.
- Check your tax treatment. If you hire anyone for ongoing help, remember this is a provincial question: HST applies in Ontario, GST plus PST in British Columbia, GST plus QST in Quebec, and GST alone in Alberta and most of the territories. It affects the real cost of a maintenance retainer.
- Refresh the season-specific material. Outdated hours, a photo of a team that no longer works there, a service you stopped offering. This is the highest-return hour you will spend all year.
- Revisit your privacy page. Confirm it still describes what the site does — particularly the contact form. If you are a Quebec business, check your obligations under Law 25 as well as PIPEDA.
The yearly review is also the moment to ask the bigger question honestly: is the design still current, is the navigation still what your customers need, is the copy still accurate? The answer is usually "mostly", and mostly needs a tweak. The trap is the reflex answer, "we need a full redesign", which turns into a year-long project nobody finishes. A small annual fix and a real redesign every four to five years is a healthier plan than a redesign triggered by a feeling.
The five things that quietly break
The same handful of problems recur on small-business sites. Knowing them in advance saves a Saturday.
An update introduces a conflict. This is the most common cause of a genuinely broken site. Update on a quiet week, never in the week of a campaign or a launch, and know where the last backup is before you press the button. If an update does break something, the recovery path is a restore, then a temporary hold on that update until the next stable release.
The SSL certificate expires. Covered above — mostly a renewal and card-expiry problem, not a technical one, and entirely preventable in the yearly review.
DNS records get edited by accident. The registrar's DNS panel is easy to change and hard to undo, and a single deleted record can take a live business offline. Set the records once, screenshot them, store the screenshots with your other documentation, and treat the panel as something you do not touch without a reason.
The contact form starts sending to a closed or full mailbox. The form is fine; the destination is not. Log into the receiving mailbox once a month and confirm the flow still works. Two Canadian rules apply to what that mailbox does next. Commercial email falls under CASL, which sets consent, identification, and unsubscribe requirements for messages you send. And the personal information the form collects is your responsibility as a business under PIPEDA, regardless of who hosts the site.
The site slows down as it grows. A site that started with a dozen pages and now carries several hundred is asking more of the same host. The weekly check is where you notice; the monthly review is where you decide between a cleanup and a hosting upgrade.
None of these are hard. None of them require a developer. Every one of them requires someone to notice, and the only way to notice is to look. Our observations on common problems with Canadian small-business websites cover the same ground from the review side.
When to call the studio that built it
In the first 30 days, the studio should be available for reasonable follow-up. After that, it depends on the question.
Some studios offer a maintenance retainer; some do not. At Seaway Sites, a one-time build includes a 30-day bug-fix window and then no recurring fee from us — if you later decide you would rather not hold the rhythm yourself, the same conversation that produced the one-time build can be reopened as a managed plan. The managed vs one-time comparison is the right document to have in your hand when you have that conversation, because it makes the trade-off explicit rather than emotional.
Two situations are genuinely specialist work.
A security incident — a compromised login, a defaced page, a domain that has gone black — is not a weekend-clever problem. The right studio has a runbook: contain, restore from a known-good backup, rotate every credential, then write down what happened so it does not happen again. Slow down and pay for this one.
A design system question — adding a page that has to match everything else — belongs to the studio that built it, because the design system lives in their files and, more often, in their head.
For everything else, the rhythm above is enough. You are not hiring a developer to run a website. You are scheduling twenty minutes a month to confirm the thing you paid for is still doing its job. If that discipline is not something you want to own, a managed plan exists precisely so you do not have to — but either way, it should be your choice, made deliberately rather than defaulted into.
