Understand the exception.
A family has multiple riders. A lesson moves to another week. A new customer needs to finish setup without booking immediately.
What started as a barn owner’s scheduling problem became a software business. I work directly with the people using it, translating daily operational needs into the product and staying involved after it ships.
The starting point was a barn owner coordinating lessons through text messages, a paper calendar, and a shared spreadsheet. Every change meant keeping instructors, riders, and parents in sync.
My job was to understand those connections, then turn them into software that fit the way the barn actually operated.
A calendar alone solves part of it
Each change on one side has to show up correctly on the other.
I own the loop between what a customer needs, what the system does, and what happens when people use it.
A family has multiple riders. A lesson moves to another week. A new customer needs to finish setup without booking immediately.
Trace the change from interface to scheduling rules, account relationships, and billing behavior.
Help customers through onboarding, investigate operational issues, and feed what they reveal back into the product.
A booking interface is the visible part. The engineering underneath has to account for time, capacity, ownership, payments, and the people affected by a change.
Decisions worked through with customers
An open slot this week does not guarantee one every week. Evaluate the future series, including bookings, holds, and blocked time, before offering a recurring schedule.
Separate account and payment setup from booking. An occasional rider finishes onboarding without an unwanted recurring subscription.
Recurring schedules stay connected to the enrollment or subscription that owns them, with deliberate effective dates.
Investigate the current state, narrow the change to the intended records, verify the result. Support includes responsibility for the data.
I design the navigation, information hierarchy, and interaction patterns alongside the underlying workflows. For barn staff, that means finding the right lesson from a phone. For an owner, it means seeing what needs attention without assembling the answer from separate tools.
The infinity ribbon becomes a continuous gold sweep in the app’s loading experience.
In the aisle. Between lessons.
Presentation images adapted from the September 2026 app. Personal names and contact details are fictional; financial amounts are retained. Platform administration controls are omitted. Device scenes are generated mockups.
With SaddleSync, I’m responsible for understanding the customer’s problem, designing the experience, building the application, and supporting the people who rely on it.
That is how I approach forward-deployed engineering: close customer collaboration, hands-on implementation, and design judgment carried all the way through.
See it running
Another side of the practice