Owner-operator case study, 2026
Over five months I redesigned the systems behind Sierra Nevada Off Road Academy and the other work I manage. The point was not to build an impressive AI demo. It was to return owner time, make complex client work repeatable, preserve what the organization knows, and make the next useful idea less expensive to test.
The work so far
These numbers describe different parts of the work. They are not one combined "hours saved" claim, and the administration estimate still needs prospective time tracking.
The pile, every week
SNVORA's work crosses bookings, payments, waivers, reminders, rosters, customer communication, calendars, curriculum, and financial follow-up. Generic applications handle individual pieces, but the owner still has to move information among them and remember the rules.
I estimate that routine administration was taking about 15 hours each week. A personalized post-event follow-up could consume another 90 minutes, plus 20 minutes to create and connect a photo album. Scheduling through several short emails took 10 to 20 minutes. Cleaning up, filing, and later finding meeting notes took 15 to 30 minutes per meeting.
None of those tasks looks catastrophic alone. Together, they decide whether the owner spends the week teaching, selling, creating, and being with family, or maintaining the machinery around the work.
The system prepares the routine work and keeps a record of what it did. Sending, commitments, money, safety, customer exceptions, and other decisions that matter stay with a person.
Booking, payment, waivers, customer and class records, rosters, communications, calendars, finance checks, backups, and exceptions run through one connected system. Business-specific rules no longer have to live only in the owner's head.
The system screens multiple inboxes, prepares response drafts, assembles event follow-up, provides self-service booking against real calendars, processes meeting transcripts, and makes prior decisions easier to retrieve.
Research, client context, curriculum structure, vehicle-specific imagery, human review, slide placement, instructor notes, and final verification move through a traceable process. A separate review workflow screens outside sources and proposes controlled changes instead of silently rewriting the system.
Produced in real organizations
The flagship system
Routine owner administration is moving from an estimated 15 hours a week toward 45 minutes. The goal is not zero oversight. It is to spend owner attention on exceptions and relationships instead of shuffling the same information between tools.
Visit SNVORAAt least 275 hours of deck and curriculum production, including a roughly 200-hour first deeply customized institutional program and about 150 client-specific images, are becoming a repeatable workflow with human review over safety and teaching.
A hard-to-use fire-department and off-road incident resource became a searchable database for research, safety review, and curriculum development. A dependable way to use information the organization already has.
fireincidentlibrary.orgSelf-guided event information and structured intake reduce repeated explanation and scattered volunteer coordination. Small products built around a real, repeated communication burden.
barc-event-guide.netlify.appReusable website, communication, intake, scheduling, and monitoring patterns cut the setup to launch a local tape-digitization business. It still has to prove demand. This time, testing the idea did not mean starting from zero.
campbellvideo.comThe immediate priority is using these systems to grow SNVORA and improve the organizations they already support. I am also exploring whether specific problems repeat strongly enough to support a separate offer: owner-workflow diagnostics, specialized booking and event operations, searchable organizational knowledge, or customized curriculum-production systems.
These are not packaged software products today. Product-market fit requires owner interviews, paid pilots, clear implementation boundaries, workable support economics, and evidence that the outcome transfers beyond my own operation.
You run a training, certification, outdoor, event, cohort, or field-service business.
You spend five or more hours a week moving information among scheduling, forms, payments, email, and internal records.
Your business has operating rules that generic software repeatedly gets wrong.
Your organization has valuable knowledge trapped in spreadsheets, PDFs, inboxes, or one person's memory.
You produce expensive customized client work and keep rebuilding the same production steps.
I'm talking with a handful of owner-operators right now to see which of these problems show up outside my own businesses. No pitch, just comparing notes.
Tell me about your workflow