1. Certification, membership, directory, marketplace subscription payment, and physical goods commerce
The brand needed a WordPress property that handled certification enrollment, subscription checkout, authentication code redemption, coaching notes, a dynamic trainer directory where every certified trainer had a public profile at a stable URL, and a physical goods store carrying training cones, props, merchandise, and other equipment used in skill development. Players had to be able to find trainers geographically by state, by zip code, and by name.
The subscription commerce model was a marketplace. Every player subscription and product purchase in the subscription surface had to split at the point of transaction between the certified trainer earning the training relationship and I'm Possible Training taking the platform share. In the era when this engineering ran, marketplace payment infrastructure did not yet exist as turnkey SaaS. The split had to be engineered end to end on top of standard commerce primitives.
Physical goods commerce carried a separate operational shape with shipping, inventory, and order fulfillment, all running through the same WooCommerce backbone. This surface faced the customer directly and had to stay reliable under the checkout and login traffic that funded the business.
2. Structured skill training and video delivery
Video content was heavy. A single trainer subscription carried access to hours of course video, and the catalog kept expanding. Serving that content required a system that could hold the video files on infrastructure the client controlled, encode them for cross device playback, present them through lightbox and course page surfaces, drive quiz progression logic for certification, and stay responsive as trainers and players streamed sessions from 6 continents.
3. Checklist workout system and coaching workflows
Trainers needed to build checklists of drills for individual players, assign them, track completion, and add coaching notes tied to specific player profiles. Players needed a mobile experience for consuming assigned checklists on court. Workout logs required sport specific fields such as Moving Right, Moving Left, and Spot drill categories that captured the way basketball skill training was actually structured. Trainer and player views needed distinct permissions, distinct navigation, and distinct data access boundaries.
4. Camps, events, and the growing facilities network
As the business scaled from a single Skill Lab HQ to a network of Skill Lab facilities, the platform had to support facility pages, camp signup workflows, events calendar templates, and cloneable campaign pages for each new camp launch.
The integration demand across all four
Two distinct web properties needed to feel like 1 product to the end user. Account creation on 1 surface had to automatically provision access on the other, credentials had to mirror, notifications had to fire at the right transition points, video traffic on the training side had to not destabilize checkout on the profile side, the mobile application had to sync with web based session state, deliver video from the Online Training System, and carry the same trainer and player role boundaries the web enforced, and the whole system had to stay operable across a client team that scaled its trainer and player base year over year.
DM Us
