About
A product company, built in Canada.
We build association management software that fits the association.
The problem we kept seeing
Associations do specific, often unusual work. A regulator's registration process is not a trade association's membership renewal. A certifying body's continuing-education audit is not a chamber of commerce's event calendar. And yet they are all offered variations of the same software, and all asked to adapt to it.
The result is familiar to anyone who has worked in this sector: capable organizations spending real staff time working around the tool that was supposed to save them time. Workarounds calcify into policy. Institutional knowledge becomes "ask Susan, she knows how to make the system do that."
We started Hopkee because that trade-off no longer needs to exist.
What we believe
Three things, and everything else follows.
The end of one-size-fits-all AMS.
Software built for everyone in general serves no one in particular. Associations shouldn't have to compromise on how they operate to satisfy a product roadmap written for a market average.
An AMS built for the way you work.
The fitting is our job, not your staff's. You describe how your association runs; we make the system match, and we keep it matching as you change.
The economics of custom software have changed.
Building and maintaining tailored software used to be expensive enough that standardization was the only responsible answer. That is no longer true, and the category hasn't caught up.
A product company, not an agency
One platform. Many associations. Each one fitted.
This distinction matters enough that we'll be blunt about it. We are not a development shop that will build you a system, hand you the keys and move on to the next client.
Hopkee is a product. Every customer runs on the same platform, and that platform improves for everyone at once. What we tailor is the layer that should be tailored: your workflows, your rules, your language, your member experience.
That means you get software shaped around your organization without inheriting the risks that usually come with custom software — the single developer who understands it, the framework that stops being maintained, the rebuild that arrives five years later.
Canadian by design
Canadian, on purpose.
Hopkee is Canadian-owned and built in Canada, focused on Canadian associations, regulators and member-based organizations.
That isn't only a statement about where our desks are. Canadian associations have requirements that international platforms tend to treat as edge cases: genuine operation in both official languages, provincial regulatory structures that differ from one another, Canadian payment and tax handling, and real expectations about where member data lives.
Building for that from the beginning produces a different system than adapting to it afterwards.
What that means in practice
- Canadian-owned and built in Canada
- English and French treated as two official languages across staff tools and the member experience — not a translation layer added at the end
- Member data hosted in Canada
- Built around Canadian association and regulatory structures
Where we are
Hopkee is early, and we would rather say so plainly than imply otherwise. We are working closely with a small number of founding associations, building the platform around real organizations with real requirements rather than assumptions about what the market wants.
If you're evaluating AMS options right now, that's worth knowing in both directions. It means you would have unusual influence over how this product develops. It also means we will be straightforward with you about what exists today and what we would be building alongside you.
We think that's a better conversation than a polished demo of features you'll never use.
Tell us how your association works.
We'd like to hear about your processes, your structure and the things your current system can't hold. It costs you a conversation.
Start a conversation