Real businesses, built to ship.
A sample of what I’ve designed and shipped, from a full operating platform down to a marketing site. Different sizes, same standard: real software in production, owned by the people who run it.
Inside CSC+.
The full build.
A coaching practice partnered with a licensed clinical group for prescription peptide therapy, with no platform tying them together. I built the marketing site, the member app, and the coach surface. One codebase. Twenty-three tables. Live in production.
Same practice. A completely different way to operate.
- ×Inbound went to email; nothing routed or tracked
- ×Programs lived in spreadsheets and DMs
- ×No client app: no workouts, check-ins, messaging
- ×Intakes tracked by hand; peptide orders too
- ×Partnership existed; no system connected it
- ×Compliance language scattered across docs
- ×No scheduling, no payment flow
- +Structured intakes captured straight to the database
- +Member app: workouts, nutrition, check-ins, messaging
- +Coach app: roster, dashboard, intakes, orders
- +Role-aware boundary enforces who sees what
- +Branded scheduling embedded inline
- +Compliance consolidated; single source of truth
- +Forms double-write for redundancy
From zero to live, end to end.
One operator, one codebase, eleven weeks. No agency, no platform stitched from off-the-shelf parts. Every screen and every table designed for this business.
Design + schema
Stakeholder interviews, role model, full schema with row-level security, brand system, design tokens.
FOUNDATIONMarketing site
17 surfaces: home, coaching, peptide library, intake flows, scheduling, legal, journal.
ACQUISITIONMember + coach apps
Training, nutrition, check-ins, messaging, coach dashboard, intakes pipeline, orders, reviews.
OPERATING SYSTEMPolish + ship
QA, copy pass, image work, deploy, domain cutover. Live on campanaroplus.com.
PRODUCTIONPerformance, prescribed.
Seventeen marketing surfaces: home, coaching, how-it-works, peptide library, waitlist, contact, FAQ, journal, book a call, legal, audience splits. All locked to the same brand system.
One operator. Two surfaces.
The same auth entry routes a client to their training app and a coach to the operating console. A role-aware boundary enforces who sees what, scoped per coach.
TODAY · PUSH A
Bench, OHP, dips.
~58 min · Tempo focus on the bench. Hit the press hard.
- Barbell bench press4 × 6185 lbRPE 7
- Standing OHP4 × 8115 lbRPE 8
- Weighted dip3 × 10BW + 25RPE 8
- DB lateral raise3 × 1220 lbRPE 7
Got it. Appetite low: protein hit 140g vs target 200.
Sleep was light midweek. Strength still good.
Skin clearer this week. Energy way up.
Three back-to-back deep-work blocks today.
THIS WEEK
REVIEWS DONE
NEEDS REVIEW · 05
- 2D OVERDUEM. ReyesCUT · WK 08
- 1DJ. WaltonBUILD · WK 05
- TODAYS. DavisGLOW · WK 03
- TODAYE. KovacELITE · WK 04
- TODAYD. KingRECOVER · WK 02
A business that runs.
Not features for their own sake. What the platform lets the practice actually do, on day one.
FOR THE OWNER
- Take inbound from a structured intake, routed by stage
- Run an active roster from a single screen
- Place and track peptide orders to delivery
- Brand site that converts without ad spend
- Compliance language consolidated in one source
FOR THE CLIENT
- Train from a coach-assigned plan on their phone
- Log workouts with RPE + set-by-set tracking
- Weekly check-ins with form-video uploads
- Message the coach in-app: no Slack, no SMS
- See body composition + strength trend over weeks
FOR THE COACH
- Per-coach scoped roster, no cross-talk
- Weekly review queue surfaces overdue clients
- Intake pipeline with stage progression
- Live inbox, per-thread unread state
- Exercise + meal + workout libraries to compose from
Foundations that scale.
The platform isn’t a feature list. It’s a load-bearing foundation. What it can absorb without rewrites:
Multi-coach roster, at any scale
The codebase scopes per-coach by default. Add coach #2, coach #50:no schema changes, no migrations.
A second clinical partner
Intake routing is partner-aware. Add another licensed prescriber, route inbound by state or specialty.
Real-time, on every surface
Messaging, presence, intake stage progression, order status: the data layer already streams. The UI just listens.
AI-drafted coach replies
Model-agnostic interface, drafts pulled from each client’s logged history. Swap providers without touching the app.
Push notifications, ready to flip
Wired in at the data layer. Toggle on: clients get pings on new assignments, coaches get pings on reviews due.
Subscription + per-cycle billing
Payment state lives next to the client record. Subscription tier, last paid, dunning state: already modeled.
Direct partner-clinic handshake
Replace the manual intake forward with a programmatic write into the partner’s portal. Endpoint already mapped.
Composable coach toolkit
Workout templates, meal plans, exercise + peptide libraries: coaches compose new protocols without engineering.
The website was the door. The platform is what’s behind it.
The founder can onboard clients through a flow he controls. The coach can manage an active roster from one screen. Every inbound lead lands in the database the moment a visitor hits submit. Orders to the compounding pharmacy are tracked from placed to delivered, with full state history.
The compliance disclaimers, the peptide library, the intake form, the check-in cadence, every regulated and recurring piece of the business, lives in one codebase he can ship to in minutes.
Not a website with a CRM bolted on. A business built as software.
Build notes / AuteraNext, on demand
Inside Apex.
Golf fitness, shipped.
A golf-specific training app built with PGA-tested coaches Gabe Williams and Nick Campanaro. I designed the brand, built the iOS app, wired 500+ coaching videos to structured programs, and launched the marketing site. One system, live on the App Store.
A binder of workouts, rebuilt as an app golfers use.
- ×Programs lived in PDFs, spreadsheets, and DMs
- ×Exercise demos scattered across random video links
- ×No read on whether a golfer was ready to train
- ×Progress tracked on paper, if at all
- ×No brand, no store presence, no funnel
- ×Coaching couldn't scale past the room
- ×Warm-ups and recovery left to chance
- +15 structured programs, coach-built, in one app
- +500+ exercise videos wired to every movement
- +Daily Apex Score reads readiness from a 10-second check-in
- +Set-by-set weight logging with per-exercise history
- +Full brand + marketing site, live on the App Store
- +The coaches' method, in every golfer's pocket
- +Guided warm-up and recovery routines built in
From a coach’s method to the App Store.
One operator: brand, app, and a 600-video content pipeline — designed and built around how golf coaches actually program.
Brand + system
Compass mark, red-and-navy system, condensed type, design tokens, and the App Store identity.
FOUNDATIONThe app
Home, programs, guided workout player, exercise library, daily check-in, and the Apex Score — built in React Native / Expo.
PRODUCTContent pipeline
600+ exercise videos edited, hosted on Vimeo, and mapped to every movement in every program, with an alias system for renames.
CONTENTShip
Marketing site, App Store submission and review, launch on apexgolfperform.com and the App Store.
PRODUCTIONSwing with purpose.
A brand with a point of view: a compass mark for direction, red-and-navy for intensity, condensed type and target-reticle motifs for focus. The same system runs from the app icon to the App Store creative.
The coach, in your pocket.
Every golfer gets a program matched to their goals, guided workouts with video for every movement, set-by-set weight logging, and a daily Apex Score that tells them how ready they are to train.
What it actually does.
Not a feature list. What the app lets each side actually do.
FOR THE GOLFER
- Get a program matched to your goals and level
- Follow guided workouts with video for every move
- Log weights set-by-set and watch your history build
- Check in daily for an Apex Score readiness read
- Warm up and recover with built-in routines
FOR THE COACHES
- Their PGA-tested method, delivered at scale
- 15 programs across every golf goal
- A swap system for coach-approved alternates
- New programs added quarterly, no rebuild
- Every movement demonstrated on video
FOR THE BUSINESS
- Live on the App Store, subscription-ready
- A brand and marketing site that convert
- One codebase for iOS and web
- A content library that compounds
- A daily engagement loop, analytics-ready
Foundations that scale.
The app isn’t a screen deck. It’s a system built to keep growing without rewrites.
600-video content pipeline
Every clip hosted on Vimeo, mapped name-to-ID, with an alias layer so renames never break a program.
Data-driven program engine
A program is data, not code. Add one — weeks, days, sections, progressions — without touching the app.
The Apex Score model
A weighted read of Recovery, Readiness, and Consistency from a five-signal daily check-in.
Supabase backend
Auth, profiles, and row-level security in place — ready for cross-device sync and cloud history.
Subscription billing
RevenueCat + StoreKit 2 wired for a monthly membership with a free trial.
Custom Workout of the Day
A generator that builds a fresh session each day from the golfer's goals and level.
One codebase, two platforms
React Native / Expo ships the same product to iOS and the web.
Quarterly content drops
New programs and videos land as data updates — no app rebuild required.
A workout binder became a product on the App Store.
Two coaches had a method that worked and no way to scale it. Now it’s an app: fifteen programs, five hundred coaching videos, a daily readiness score, and guided workouts a golfer can run in the gym — live on the App Store and sold from a marketing site that matches.
The brand, the app, the video library, and the funnel are one system — one codebase I can ship to in an afternoon, with room to add Android, wearables, and a coach dashboard on the same foundation.
Not a fitness PDF with a login. A coaching method, built as software.
Build notes / AuteraNext, on demand
Herlong Sports PT.
[CLIENT: one or two sentences on Herlong Sports PT: what they do and what they needed.]
Scope
- [CLIENT: what you built: e.g. site + intake/scheduling]
- [CLIENT: key pages or features]
- [CLIENT: any systems or automations]
- [CLIENT: the outcome for the practice]
Want something like this