Industries · Sports & Lifestyle
Clubs, leagues, gyms, studios and outdoor brands live by their sign up windows. We build membership, scheduling and ticketing systems that hold up on registration night, plus member apps and campaigns people actually keep using.
You own the code and IP Weekly demos Reply within one business day
Good morning
Your account at a glance
Balance
12,480
OlDevs is a full-stack technology studio in Vancouver that builds membership, booking and event software for clubs, leagues, gyms, studios and outdoor brands.We handle registration and renewal flows, class and facility scheduling, waivers and payments through your chosen provider, member apps for iOS and Android, and the campaigns that fill each intake. Every build is accessible to WCAG 2.2 AA, can ship bilingually in English and French, and is owned outright by the client, code, designs and accounts included. Request a quote to scope your next season.
Key facts
Sports & Lifestyle
The problems we are asked to solve most often — and how.
A season opens and a term of demand lands in ten minutes. Shared hosting and a single payment queue buckle, families lose the spot they waited up for, and your inbox fills by morning. That load has to be designed for, not hoped for.
One parent registers three children across two programs, pays once, and expects every schedule in one place. Systems built around a single account per person turn that into four logins, four carts and a support call you have to answer on a Sunday.
Youth programs need guardian consent, signed waivers, medical notes and photo permissions, each tied to the right child and kept private. Paper binders and inbox PDFs do not survive an audit, a coach change or a mid season transfer.
Ice time shifts, a field floods, an instructor calls in sick. Every change has to reach the right members within minutes, update the calendar, release the space for rebooking and never notify the group it does not concern.
Memberships pause over summer, lapse in December and come back in January. Without holds, renewals and a clear record of who left and why, you rebuild the roster from scratch each intake instead of bringing familiar people back.
The person managing your rosters may be a parent volunteer with twenty minutes on a Sunday. Admin tools written for full time staff get abandoned, and the data quietly drifts back into spreadsheets nobody else can read.
Process
Season map
A short discovery with the people who run intake: program structure, key dates, current tools, the reports you need and the failure you fear most. We leave with a scope and a launch date pinned to your calendar.
Prototype
Clickable registration, booking and admin flows tested with real staff, coaches and a handful of members. Cheap to change now, expensive to change later, so we settle the hard decisions here.
Build in weekly demos
One accountable team ships a working demo every week against your priority order. You see progress in the product, not in a status report, and you can reorder scope at any point.
Load rehearsal and launch
We simulate registration night well above expected peak, fix what breaks, agree a fallback plan and go live with staff trained and someone watching the dashboards on the night itself.
Season support
After launch we track what members and staff actually do, fix friction in the first weeks, then plan the next release around renewals, off season retention and the following intake.
How we work
Intake dates, program structure, pricing tiers, blackout weeks and the moments your staff dread. The calendar drives the roadmap, so the first release lands before a sign up window rather than after it.
Household accounts, multi child carts, prerequisites, waitlists and prorating, all rehearsed under load. Payments run through the provider you already use, with retries and receipts that reconcile cleanly.
Facilities, instructors, teams and classes share a single calendar, so a cancelled session frees the space, notifies only the affected members and updates the app, the website and the front desk together.
Native apps for booking, check in, schedules, digital membership cards and push notifications, built on the same API as the web so members never see two versions of the truth.
Tiered tickets, member pricing, transfers, refunds and offline capable scanning, with volunteer friendly screens for the people working the gate on a cold night.
Paid social, search, email and community content scheduled around intakes and renewals, with tracking wired into the registration funnel so you can see which channel filled which program.
Recommended
Weekly
working demo through every build
WCAG 2.2 AA
accessibility standard we build to
Since 2014
one accountable team, EN and FR
FAQ
Yes. We treat registration night as its own engineering problem: cached catalogue pages, a queue in front of checkout, idempotent payment handling and rehearsals at several times your expected peak before the date. We also agree a fallback plan with you, so a slow payment provider does not take the whole intake down with it.
Not always. If your current platform holds member records and payments well enough, we build the missing pieces around it and connect through its API, so you keep the system of record and gain the booking, app or event flows you lack. Where the platform is the bottleneck, we plan a migration season by season rather than all at once.
Yes. Booking is usually the feature members touch most, so we build it for one handed use: live availability, waitlists, a clear cancellation window, calendar sync and a receipt that matches what the front desk sees. Staff get the same view with override rights, so the desk and the app never disagree.
Carefully, and with your own counsel involved. We separate guardian and participant records, capture consent as a dated event rather than a tick box, restrict who can see medical notes and photo permissions, and keep an audit trail. Canadian privacy law such as PIPEDA and its provincial equivalents shapes the design, though nothing here is legal advice.
It depends on how often members act between visits. Booking, check in, live schedules and push notifications earn a native app; a sign up that happens twice a year rarely does. We often start with a strong responsive web experience and add iOS and Android once the usage pattern is clear and the demand is real.
Yes. We run paid social, search and lifecycle email against your intake dates, so spend rises before a sign up window opens and pauses once programs fill. Because the same team builds the platform, campaign tracking and the registration funnel are measured as one system instead of two that blame each other.
Most club, gym and studio platforms begin with a short discovery, a working prototype within weeks and a first release aimed at your next intake rather than a distant launch date. You see a working demo every week, so scope changes stay cheap and visible. Tell us your season dates and what breaks today, then request a quote.
Let’s connect
We’ll reply within one business day with next steps and a tailored quote — no obligation.