One-off website build vs subscription platform for Canadian clubs

Canada edition. This guide is written for volunteer-run clubs in Canada. Where rules differ — grants, tax, incorporation, safeguarding — follow the Canada-specific pointers below or check with your national body.

The quote lands in the club inbox on a Tuesday night, and it is genuinely a good quote. A local developer — or a member's daughter who does this for a living — will build the club a proper website. Custom design, the crest reproduced properly, a fixtures page, a gallery, a contact form. One number, paid once, and then it is yours.

Set against a subscription that renews for as long as the club exists, "paid once" sounds like the responsible option, and it is the sentence that wins the vote at most committee meetings where this comes up. It is also the sentence that hides nearly everything expensive about a website, because very little of what a website costs over its life is the building of it. The build is the cheap, visible, exciting part. The invisible part is the four years afterwards, when the design is fine but the software underneath it has moved on twice, the person who built it has a new job in another city, and nobody on the current committee knows who the hosting account belongs to.

This guide is for the committee holding that quote. It sets out what each option genuinely includes, models three years of cost both ways with line items you can argue with, works through who is responsible for patching, hosting and backups once the invoice is paid, and shows you how to keep ownership of your content, domain and member data whichever way the vote goes. There is no universal answer. There is one answer for a club with a working developer on the committee and a very different one for a club whose most technical volunteer is the person who set up the group chat.

What you are actually choosing between

The two options are not "custom" versus "template". They are two completely different ways of buying software, with different failure modes.

A one-off build is a project. Someone is paid to produce a thing, and when the thing is delivered the relationship ends unless you buy an ongoing arrangement separately. What you receive is a set of files running on a server, usually on top of a content management system with a stack of third-party extensions bolted on for the club-specific parts — a form, a payment button, a photo gallery, a calendar. Every one of those pieces is maintained by a different party, on a different schedule, and none of them know your club exists.

A subscription platform is a service. You are not buying files, you are renting the operation of a working system: hosting, updates, security patching, backups and new features arrive whether you ask for them or not, and the price is a line in your budget that repeats. What you lose is total control of the underlying code. What you gain is that no single volunteer's departure can take the site down.

A third path sits between them — a general-purpose website builder, which is a subscription for the site but leaves memberships, fees and fixtures to you. We have compared that route separately in club website builder vs general website builder; the argument below applies mostly to the custom-build end of the market.

The three-year ledger

Committees compare a build quote against one year of subscription. That is the mistake. Compare three years of everything, because three years is roughly one full committee turnover and about as far ahead as a volunteer organisation can honestly plan.

The table below is an illustrative model, not a price list. The figures are in your own currency and deliberately round; the point is the shape, not the total. Substitute your actual quotes and your own volunteer time before you take it to a meeting.

Three things in that table do the real work, and they are the three committees leave out.

The maintenance arrangement. A build quote covers building. Keeping the thing patched, updated and working is a separate agreement, and if you decline it the cost does not disappear — it converts into risk, which lands as a bigger bill later. In the volunteer column above, declining maintenance is exactly why years two and three carry a repair and a rebuild.

The major version event. Every few years the software underneath a custom site has a version change that breaks extensions. Somebody has to do that work. On a subscription platform it happens without you hearing about it; on your own build it arrives as an unbudgeted invoice, usually at the worst possible moment in the season.

Volunteer hours. Hours are not free, they are just unbilled. If the treasurer spends two evenings a month re-typing fixtures into a page because the site cannot pull them from anywhere, that is the most expensive line in the ledger and it never appears in a single quote. Our guide to how much a club website costs breaks down the pricing side in more detail.

For a rough local calibration — illustrative only — a small custom build from a freelancer commonly starts in the low thousands of dollars and an agency build with online registration runs into five figures. Hosting sits at a couple of hundred dollars a year and a maintenance retainer at several hundred upwards. Clubs in Canada that need any French-language content should price translation and bilingual page maintenance into the quote from the start rather than as a later change request.

Who patches it, hosts it and holds the backups

This is the section that decides the argument, and it almost never gets discussed, because it is not exciting and nobody in the room feels qualified to raise it.

A website that takes registrations holds names, dates of birth, contact details, emergency contacts and sometimes medical notes about children. It is a system holding sensitive data about your members, and it needs the same discipline as the club's cash. Whichever option you choose, someone must own each of these jobs by name:

• Core software updates. Security fixes for the underlying platform, applied promptly rather than "when we next get someone in".
• Extension and plugin updates. Every add-on is a separate supplier with its own patch schedule, and abandoned extensions are the most common way a small site is compromised.
• Server and runtime updates. The language version and operating system under your site both go out of support on published timetables.
• Certificate renewal. Modern certificates auto-renew until the day the automation breaks, and then the browser puts a warning in front of every visitor.
• Backups that have actually been restored. A backup nobody has tested is a belief, not a backup. Restore one to a test address once a year.
• A monitored inbox for security notices. Not a volunteer's personal address that stops being read when they step down.
• A record of who has administrator access, reviewed whenever the committee changes.

On a subscription platform, every one of those lines is the provider's job and comes with the price. That is most of what you are paying for. ClubHelix runs managed backups and keeps an audit log of admin actions so a new committee can see what changed and who changed it, and our security page sets out how the platform is built. On a one-off build, every one of those lines is yours — which is entirely workable if you have the person, and a slow-motion problem if you assume someone else is doing it.

Because the site holds member data, PIPEDA and any provincial privacy legislation that applies to your organisation are the frame to work within, and some provinces add their own requirements about where personal information may be stored. Ask where the server sits, who else can log in, and what happens to backups when the arrangement ends. Treat this as general information and confirm your obligations with an adviser in Canada.

The bus factor — one person, one password, one credit card

The most common way a club website dies has nothing to do with code. It goes like this. The site was built by someone helpful. The domain was registered on their personal account, using their card, because it was easier than waiting for the treasurer. The hosting is on their reseller account for the same reason. Three years later they move away, or fall out with the committee, or simply stop answering, and the club discovers it cannot change a training time, cannot renew the domain, and cannot prove to anybody that the domain was ever theirs.

There is a fix, and it is administrative rather than technical:

1. The domain is registered in the club's legal name, with the club's own email address as the contact, and billing on a club card or account.
2. Every account has a shared club address on it, not a personal one — web@yourclub.org style, forwarded to two committee members.
3. Credentials live in the club's password manager, with at least two office bearers holding access.
4. One page in the handover pack lists every account, what it costs, when it renews and who to contact. Add it to your committee handover checklist.
5. Auto-renew is on, with a card that will not expire the same week as your busiest registration night.

None of that stops you commissioning a custom build. It stops the custom build from quietly becoming someone's personal property. If you are registering a domain now, how to buy a domain for a club covers the ownership details properly.

Local domain names in Canada carry a presence requirement, which most incorporated clubs meet through the organisation itself — but that only works if the registrant is the club rather than a member. Record which registrar holds the name, keep the contact on a club address, and check the transfer process before you need it in a hurry.

Owning your content, whichever way you go

Assume that in five years you will move. Not because anything went wrong — committees change, needs change, providers change. The question to ask of both options is not "will this last forever" but "what do I walk away with".

Put these in writing before you pay anyone, and ask the same questions of any subscription provider:

• Copyright in the design and content transfers to the club on final payment, in a sentence you can point at.
• The club can export its member list, registrations and payment records in a common file format, on demand, without asking permission.
• Photos and page content can be downloaded in bulk, not retrieved one page at a time by a volunteer with a right-click.
• You hold the domain and its DNS, so pointing the name at something new is a decision you can make alone.
• Nothing critical depends on a licence in the developer's name — a paid theme or extension bought on their account leaves with them.
• You have a copy of the database and the files, or a stated way to get one.
• Written notice applies both ways if either side wants to end the arrangement.

The uncomfortable version of this question for a subscription platform is "what happens if you shut down". The honest answer any provider should give is that your data is exportable at any time and your domain is yours, so the worst case is a migration rather than a loss. If a provider cannot answer that plainly, that is the answer.

When a one-off build is genuinely the right call

Being fair to the other side, there are clubs for which a custom build is clearly correct:

• You have an unusual requirement no platform covers — a bespoke handicapping system, an integration with an industry tool, a public data feed that only your sport uses.
• The look is the product. A club whose brand is genuinely part of its commercial offer, with the budget to keep a designer engaged.
• You employ someone technical. Not a helpful member, an actual role with a salary and a successor plan.
• You are funded for it and the funder wants an asset. Some capital grants will fund a build and not a subscription, which changes the maths entirely.
• Your governing body supplies nothing and your competition data lives somewhere you must pull from.

And one honest note on the other side: if your reason is "we want it to look like us", that is not a build reason any more. A modern platform theme with your colours, crest and photography will look like your club to every visitor who is not a designer. Our themes and branding and canvas page editor exist precisely so that argument stops costing clubs five figures.

Before you commit either way, check whether funding will cover it. Clubs in Canada can look at municipal community grants, provincial sport organisation development funding and local community foundations. Many of these fund projects rather than operating costs, so a build can look artificially attractive — be clear with the funder about what happens in year three when the project money is gone.

Seven things to put in writing before you accept any quote

Copy this into your reply. A good developer will answer all seven in a paragraph each and think better of you for asking; anyone who bristles has told you something useful.

1. What exactly is included in the price, and what counts as a change request.
2. What software the site runs on, and which paid extensions it depends on.
3. Who applies security updates after handover, how often, and at what cost.
4. Where the site is hosted, in whose account, and in whose name is it billed.
5. What happens if you are unavailable for a month.
6. What a typical small change costs and how the process works.
7. What the site will cost the club in each of the next three years, in total.

Ask the same seven of any subscription provider. The answers should be shorter, and if they are not, keep looking.

Putting the website money where it keeps working

The reason we build a platform rather than sell builds is the fourth year. Everything in the ledger above — patching, hosting, certificates, backups, the major version event, the volunteer who left — is absorbed by a subscription, and what the committee is left with is the part it can actually do: writing pages, publishing results, taking registrations. ClubHelix gives you a branded site on your own domain, a drag-and-drop page editor any committee member can use without training, and themes that carry your colours and crest, with memberships, events, fixtures and email in the same place.

The fair way to settle the argument is to build both. Put your real content into a free site over a weekend, then hold it next to the quote at the next meeting and compare like with like. There is a free tier that costs nothing to try, published pricing rather than a quote you have to chase, and you can create your club site between now and Thursday. If the custom build still wins after that, at least the committee has chosen it with the whole ledger in front of them.

Frequently asked questions

Is a one-off website build cheaper than a subscription?

In year one, usually yes if a volunteer builds it and sometimes no if an agency does. Across three or four years it is rarely cheaper, because a build does not include hosting, security updates, extension licences, the periodic major version repair, or anyone to make changes. Model the full period with every line item before you compare the two numbers.

What happens to a custom club website when the developer moves on?

Whatever the club has prepared for. If the domain, hosting and administrator accounts are in the club's name and the passwords are in a shared vault, you hire someone else and carry on. If they are on a personal account with a personal card, the club may lose the ability to update, renew or even prove ownership of its own site — which is the single most common way a club website ends.

Who is responsible for security updates on a club website?

On a subscription platform, the provider — it is a core part of what the fee buys. On a one-off build, the club, unless you have paid separately for a maintenance arrangement and it names the specific work. Assign it to a person by name, including who reads the security notices and who tests that a backup can actually be restored.

Can we move our content off a club platform later?

You should be able to, and it is a fair question to ask before you sign up. Look for exports of members, registrations and payment records in a standard file format, a way to download your pages and images in bulk, and a domain that you own and control. If you hold your own domain, moving is a migration and a redirect rather than starting again.

Do we still need a designer if we use a platform?

Only if you want one. A platform theme with your colours, crest and decent photographs looks like your club to a normal visitor. Where a designer earns their fee is the logo, the photography and the tone of your words — assets that keep their value regardless of what software you run the site on.

Keep reading — how much does a club website cost puts numbers on the options, and how to build a sports club website walks through the build itself.