Mission, Vision and Team Members
We Bring Parking and Security Together
OperationsCommander didn’t start as a grand vision. It started with a phone call.
Twenty years ago, a university parking director named Brian Billings needed to move his department’s permit management off a desktop application and onto the web. At the time, online payments were still primitive — staff would take card details over the phone and manually process them through a POS terminal. It wasn’t elegant, but it was a start. And it worked.
What happened next was less planned than it was inevitable. Other universities saw what Carleton had built and wanted it. Lockers went online. A handheld enforcement app followed — first on Windows CE, scanning plates and issuing violations in the field. Then appeals. Then dispatch. Then incident tracking. Then LPR. Then fixed cameras. Then mobile patrol vehicles. Then a full analytics layer connecting everything.
Each addition came from a client who needed something that didn’t yet exist. We built it, refined it with their feedback, and made it available to everyone. That’s still how we work today.
What we didn’t fully appreciate at the time — because we were too focused on keeping the lights on and delivering for the next client — was that we were building something the industry genuinely needed. It took standing at a tradeshow, being compared to enterprise competitors with ten times our headcount, and realizing we matched them function for function, to understand what we had actually built.
What We Built — and Why It Works the Way It Does
The architecture of OperationsCommander reflects how the platform actually grew: organically, from real operational problems, with a relentless focus on making disconnected things work together.
From the beginning, the instinct was to put everything in one place. Permits connected to enforcement. Enforcement connected to payments. Payments connected to appeals. Incidents connected to vehicles. LPR connected to all of it. Not because we had a whiteboard strategy that said “build a unified platform” — but because every time a client ran into a problem caused by two systems not talking to each other, we fixed it by connecting them.
The result, twenty years later, is a platform where one database drives everything. When a permit is purchased, enforcement officers see it in real time. When a plate is scanned on patrol, it’s checked against permits, violations, and security watchlists simultaneously. When an incident involves a vehicle, its full parking history is immediately available. That’s not a marketing claim — it’s the technical consequence of twenty years of building connections rather than silos.
In the past few years, we paid off significant technical debt — migrating our enforcement and user portal applications to Ionic, making the platform fully device-agnostic across iOS and Android. That work wasn’t visible to clients, but it matters enormously for what comes next.
How We Work With Clients
We are a bootstrapped company. There were never investors writing cheques, never a safety net. For years, the business survived on the strength of client relationships and the quality of what we built — because those were the only things we could fully control.
That constraint shaped how we think about client relationships. When you don’t have the luxury of losing clients, you develop a different relationship with them. You answer support tickets the same day. You call to check in. You ask what’s frustrating them, and then you actually fix it. You build features that come from real conversations rather than product roadmaps designed by people who have never run a parking office.
The testimonials on this site aren’t marketing copy. They’re from people who have been using the platform for years — in some cases, for a decade or more. Brian Billings at Carleton University, our very first client, remains one of our strongest advocates. That kind of longevity doesn’t happen by accident.
We run the company the way we’d want to be treated as a client. That means being heard, getting responses, and working with a team that genuinely understands the operational context of what you’re trying to do. It’s not a customer service philosophy. It’s just how we think business should work.
Where We Are Today
OperationsCommander is a team of 12 specialists in development, support, implementation, and operations. We serve universities, colleges, municipalities, healthcare campuses, airports, private parking operators, and mixed-use developments across Canada and the United States.
The clients who shaped the platform in its early years — Carleton, Cambrian, Lakehead, Trent — are still with us. So are organizations that joined more recently and immediately understood what a connected platform makes possible: the Town of Perth achieving a 91% ticket collection rate, Cambrian College cutting operating costs by 37%, Taylor University meeting 100% of their needs at a price point that worked for them.
After twenty years of building, the technical foundation is solid. The platform is mature. The client library is diverse and growing. And for the first time, the focus is shifting — from keeping up with what clients need, to actively going out and finding the organizations that need what we’ve built.
We know what we have. It took us a while to see the forest through the trees, but we see it clearly now.
Our Mission
To provide parking and security teams with the most capable and easiest-to-use operations platform available — and to back it with the kind of support and responsiveness that makes the relationship worth having for the long term.
Our Vision
A single platform where every aspect of parking and security management — permits, enforcement, LPR, incidents, analytics, and payments — operates from one connected database, giving organizations the visibility and control they need to run their operations with confidence.
A Canadian Company. A North American Platform.
OperationsCommander is proudly Canadian — founded, built, and operated in Canada, serving organizations across North America. Our understanding of Canadian regulatory environments, provincial privacy legislation, and the specific operational requirements of Canadian universities and municipalities runs deep. At the same time, the platform is fully deployed and actively used across the United States, from health sciences universities in Texas to police departments in Ohio to mixed-use developments in Pennsylvania.
We understand both markets because we’ve been operating in both for years.
Ready to See What We’ve Built?
The best way to understand OperationsCommander is to see it in action — in the context of your operation, your workflows, and your specific challenges.
Request a Demo and we’ll show you exactly what a connected parking and security platform looks like for an organization like yours.
Or explore what our clients have achieved:
- Carleton University — our first client, still with us twenty years later
- Town of Perth — 91% ticket collection rate in Year 1
- Cambrian College — 37% annual budget savings
- View all client case studies
