← Selected work 01 / SaddleSync

SaddleSyncBuilt with the people
who run the barn.

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.

My role
Founder, engineer & product designer
Practice
Forward-deployed engineering & creative technology
Scope
Discovery → design → build → support
Good Venture Farm’s workspace in motion. Scripted walkthrough with fictional identities and real financial amounts.

01 / Start with the work

The scheduling problem was a people problem, too.

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.

02 / Working alongside customers

The forward-deployed part.

Customer conversations become product decisions.

I own the loop between what a customer needs, what the system does, and what happens when people use it.

Discover

Understand the exception.

A family has multiple riders. A lesson moves to another week. A new customer needs to finish setup without booking immediately.

Implement

Follow it through the system.

Trace the change from interface to scheduling rules, account relationships, and billing behavior.

Support

Stay close after release.

Help customers through onboarding, investigate operational issues, and feed what they reveal back into the product.

03 / Engineering in practice

The useful work lives in the details.

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.

  • TypeScript
  • Next.js
  • PostgreSQL
  • Prisma
  • Stripe
  • Resend
  • Vercel

Decisions worked through with customers

01

Recurring availability

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.

02

Onboarding that fits the rider

Separate account and payment setup from booking. An occasional rider finishes onboarding without an unwanted recurring subscription.

03

Schedule and billing ownership

Recurring schedules stay connected to the enrollment or subscription that owns them, with deliberate effective dates.

04

Careful production changes

Investigate the current state, narrow the change to the intended records, verify the result. Support includes responsibility for the data.

04 / Creative technology in practice

Make the complexity feel manageable.

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.

SaddleSync
Identity in motion

The infinity ribbon becomes a continuous gold sweep in the app’s loading experience.

Good Venture Farm’s daily rides dashboard on a tablet, with fictional rider names
Daily operationsClose at hand. Tablet mockup using the current dashboard.

In the aisle. Between lessons.

The same product. A different rhythm.

SaddleSync mobile month calendar with colored session markers and the selected day’s lesson list SaddleSync Edit Session bottom sheet with class type, rider capacity, date, time, and appearance controls SaddleSync mobile billing summary with monthly amount due, items needing attention, open invoices, and client search
Current daily rides dashboard with fictional rider names
DashboardToday’s rides, horse assignments, and session actions.
Current billing workspace with fictional client names and email addresses
BillingStatus, recent payments, and open invoices.

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.

05 / What I bring

Ownership from the first conversation through real use.

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

Live with Good Venture Farm.

Another side of the practice

Global signals. A shared view.

Explore LabyrinthOS

Scroll to explore. Press Escape to close.