Triathlon coaching
Coaching for athletes who already do the work.
Structured training blocks, analyzed against your power and heart-rate data, for triathletes who want to get faster — not to be reminded to train.
The premise
Most coaching sells availability. This sells analysis.
Constant contact, same-day replies, a text back within the hour. That model is built for athletes who need someone to keep them going.
This isn't that. You get a plan built on your data, reviewed in depth every three weeks, and adjusted every week against what you actually did. Messages get a considered answer inside 48 hours instead of a reflexive one in ten minutes.
The structure is the point. It's what makes room for real analysis instead of constant shallow contact.
If you're already training consistently and want someone to make the analytical calls — which sessions matter, where your limiter actually is, what the data is telling you that you can't see from inside it — that's what this is.
What you get
Five things, done properly.
A plan built on your check-in
Written or adjusted in TrainingPeaks, driven by what you report each Saturday. No check-in, and the plan holds as written.
Block review
A recorded video walkthrough of your data — fitness and fatigue trend, the two or three sessions that tell the story, what's working, what's changing and why — plus a written summary. This is the artifact you're actually paying for.
A 45-minute call
Scheduled, one every three months. For the conversations that don't fit in writing.
Swim video analysis
Filmed and annotated breakdown of your stroke. Swimming is the discipline I actually came from, and the one where technique returns the most time for the least training load.
Async messaging
Questions and updates whenever they come up, answered within 48 hours.
Same-day availability
Deliberately. Every response window I guarantee is one I'd have to fill with a reflex instead of a read of your data.
What's required from you
Three things, non-negotiable.
A power meter and a heart-rate monitor
The coaching is built on the data. Without it I'm guessing, and you're paying for guesses.
A check-in every Saturday
Five questions, a few minutes. It's what drives the next week's plan.
Honesty in it
What you skipped and why is more useful to me than a clean-looking week. Compliance data only works if it's true.
Fit
Who this works for — and who it doesn't.
This works if
- You follow a plan and flag problems, rather than checking in to confirm you're doing it right
- A week that goes sideways means you salvage the key sessions, not that the week is lost
- You want someone making the calls on how to get faster with the hours you already train
- You're chasing a specific outcome — a time, a placing, a distance you haven't done
This doesn't work if
- You need same-day responses or real-time accountability
- You want a coach who rebuilds your week every time a session slips
- You're looking for someone to get you to show up
None of that is a character flaw — it's a different service. If it's what you need, better to know now than three weeks in, and I'd rather point you somewhere else than take your money for a bad fit.
How it works
Four steps to a first block.
Apply
An intake questionnaire — background, goals, equipment, and how you actually operate as an athlete. It's built to test fit in both directions.
Initial call
We confirm the fit is real. Either of us can say no.
First block
Built around wherever you are right now and delivered before your next training week starts.
Saturday check-in
The weekly cycle starts, and the three-week review cycle runs on top of it.
Pricing
One tier. No upsell.
- Weekly plan in TrainingPeaks, driven by your check-in
- Block review every three weeks — video plus written summary
- Quarterly 45-minute call
- Swim video analysis twice a year
- Async messaging, 48-hour response window
Three-month minimum, billed monthly. That minimum isn't a lock-in tactic — it's the shortest window in which a training block, its review, and the adjustment that follows can actually show you anything.
The progression · 2024 → 2026
One run a week, and it hurt. Then a 3:31 marathon.
I came into this as a swimmer. Years of competitive swimming through the D1 level — one discipline trained properly, and two I had never trained at all.
In 2024 I ran 0.92 times per week. Forty-eight runs, 219 miles for the entire year, and most of them hurt. That is the honest starting point: not a lapsed runner coming back, but someone whose body had never been asked to run and pushed back every time it was.
Two years later I ran a 3:31 marathon off a 4:32 Ironman bike split. Not by running more — I still average under two runs a week. By running the right ones, pacing them against data instead of feel, and fixing the fueling that was quietly capping every long effort.
On the same 70.3 course that took me 59th in my age group in 2024, I finished 12th in 2026. At the full distance, first attempt, 5th — an age-group podium.
Two minutes and one second per mile off the same 13.1, all of it run on tired legs. The first point is my first 70.3, four months into ever running seriously. The steepest section — April to November 2025 — contains a nine-week stretch where I did not run at all.
The part that isn't a straight line
A knee injury in May 2025 took running away entirely. June 11 to August 14 — nine weeks, zero runs. The comeback was a two-mile jog, and it was not comfortable.
Eleven weeks after that two-mile jog I ran 6:48/mi off the bike at the 70.3 World Championship. That isn't a story about toughness. It's what a rebuild looks like when the sequencing is right and the ego stays out of the first four weeks — which is exactly the call I'd be making for you.
Same course, three years
Oceanside is the control. Same 70.3, same roads, three consecutive years — the cleanest read available on whether anything is actually changing.
| Oceanside 70.3 | 2024 | 2025 | 2026 | 24 → 26 |
|---|---|---|---|---|
| Swim — 1.2 mi | 28:34 | 26:11 | 26:50 | −1:44 |
| T1 | 7:42 | — | — | — |
| Bike — 56 mi | 2:57:23 | 2:31:25 | 2:19:00 | −38:23 |
| T2 | 3:30 | — | — | — |
| Run — 13.1 mi | 1:58:07 | 1:38:03 | 1:31:48 | −26:19 |
| Run pace | 9:01/mi | 7:29/mi | 7:00/mi | −2:01/mi |
| Age group | 59th | 12th | 12th | 47 places |
2024 is official race timing (total 5:35:16). 2025 and 2026 are device splits with transitions excluded, so the leg times are directionally right but not yet apples-to-apples.
Pacing
The run got faster because the bike got more disciplined, not less. Over two years at Oceanside the bike came down 38 minutes and the run came down 26 — the opposite of the usual trade, where a faster bike is paid for by a slower run. At Texas the same discipline held for four and a half hours:
A variability index of 1.024 means the power almost never spiked. Decoupling under 2% means the engine never drifted. And a 3:31 marathon averaging 130 bpm means the bike was ridden to set the run up, not to post a bike split. That is the whole discipline in three numbers, and it's the read I'd bring to your files.
Fueling
This is the part I got most wrong for longest, and the part that moved the most once it was fixed. In 2024 I carried gels and Honey Stingers and ate when I felt like it. No plan, no target, and no gut training — which meant the ceiling wasn't my fitness, it was how much fuel I could actually absorb while using it.
2024
- Gels and Honey Stingers, taken on feel
- No carb target
- No sodium or fluid plan
- No gut training at all
Now
- Bike carbs 110–150 g/hr
- Run carbs 50–60 g/hr
- Fluid 1 L/hr
- Sodium 1500 mg/L
A hundred and ten to a hundred and fifty grams an hour is not something you can just decide to do. Try it off the back of a season eating gels on feel and you will spend the run walking to portable toilets. The gut is trainable the same way the aerobic system is — progressively, in sessions built for it, over months. That's the work almost nobody does, and it's why the marathon at Texas held 8:04/mi to the finish instead of unravelling at mile 18.
Most athletes I talk to are leaving more time here than anywhere else in their training. It's also the cheapest to fix: it costs nothing in extra hours, and it's a plan rather than a sacrifice.
Where it ended up
| Swim — 2.4 miThe one I was given | 55:57 |
|---|---|
| T1 | 3:41 |
| Bike — 112 miBuilt | 4:32:4124.6 mph |
| T2 | 3:28 |
| Run — 26.2 miBuilt | 3:31:198:04 / mi |
| Total | 9:07:06 |
| Age group | 5th — podium |
The interesting part isn't the total — it's which legs held up. The two disciplines I had to build are the two that did their job: a bike paced at IF 0.70 to set up the run, and a 3:31 marathon off it in 85–93°F heat.
Getting fast in a sport you didn't grow up in is a training-design problem, not a talent problem. It's the problem I spent years solving on myself, and it's the one I'm most useful to you on.
The whole arc
-
Through college
Competitive swimming, D1
One sport, trained seriously. Two never trained at all.
-
January 2024
First run of the build — 2 miles at 10:46/mi
The actual starting line.
-
April 2024
First 70.3 — Oceanside, 5:35:16
Run 1:58:07 — 9:01/mi, 59th in age group. Four months after the first two-mile jog.
-
October 2024
Half marathon — 1:33:27
7:08/mi, standalone and fresh.
-
December 2024
Indian Wells 70.3 — 4:44:40
Run 1:38:26, 7:31/mi off the bike, 14th in age group. Twenty-three seconds a mile slower than fresh two months earlier — the durability gap, measured.
-
April 2025
Oceanside — run 1:38:03
7:29/mi. 12th in age group, up from 59th the year before.
-
Jun – Aug 2025
Knee injury — nine weeks, zero runs
Back with a two-mile jog on August 14.
-
November 2025
70.3 World Championship — run 1:29:02
6:48/mi off the bike, eleven weeks after a two-mile comeback jog. 83rd in age group in a qualifiers-only field.
-
March 2026
Oceanside — run 1:31:48
7:00/mi, 12th in age group, and 38 minutes faster on the bike than the same course in 2024.
-
April 2026
IRONMAN Texas — 9:07:06
First full distance. Marathon in 3:31:19. 5th in age group — podium.
Questions
Before you apply.
Why 48 hours and not sooner?
Because a considered answer is worth more than a fast one, and guaranteeing speed means guaranteeing shallowness. If something is genuinely urgent — an injury, a race-week decision — say so and it moves to the front.
What if I miss a check-in?
The plan holds as written for that week. That's policy, not a penalty — it's what protects the depth of everything else.
Do I need TrainingPeaks?
Yes — your plan lives there, and it's where your data and my analysis meet.
What distances do you coach?
Full- and half-distance triathlon.
Can I start mid-season?
Yes. The first block is built around wherever you are, not around a calendar that assumes you started in January.
What happens after three months?
It continues month to month, or it doesn't. The minimum exists so the work has time to show something, not to keep you past the point where it's useful.
Next step
Apply for coaching.
The questionnaire takes about fifteen minutes. Answer it honestly — it decides fit in both directions, and a bad fit costs us both more than a no does.