What twelve attempts at sub-three taught me — and what actually gets a runner there.

My first marathon started at a blazing sub-three pace. Until mile 18. The wall. I finished in 4 hours, the hardest way possible.

I tried eleven more times. All failures. During those years I was at Adidas building miCoach, working alongside some of the top running coaches in the world. I was literally helping build the coaching tools while trying (and failing) to coach myself to a sub-three marathon.

On attempt #12, after a year of focused, honest training, I broke through. 2 hours, 58 minutes. What I learned across those attempts is what this app is built on.

The training structure is rooted in Jack Daniels' system — the VDOT-based framework that pairs pace prescriptions to a runner's current fitness rather than to their goal. Easy pace is defined. Threshold pace is defined. Marathon pace is derived. Every workout has a purpose and a physiological target.

The AI companion knows Daniels, uses Daniels, and translates Daniels into language a runner can actually feel. You don't have to read the book. You just have to have the conversation.

The most important thing I learned across 12 attempts: a plan is only as good as the runner's ability to hold it. Most training plans assume a healthy, undisturbed 16-week runway. Life doesn't work that way. Life gives you a lingering calf, a work trip, a bad week of sleep, a long tennis match Friday night.

A good coach asks “how are you feeling this week?” before writing the workout. That's not a nicety — it's the entire game. Project Sub Three is built around continuously gathering context and letting that context drive what happens next. The plan bends. The goal doesn't.

I've been the runner who broke in each of these ways. If you've tried and failed, one of these is probably yours too:

• •Going out too fast. You feel great in the corral. Your first 5K is 20 seconds ahead of pace. You don't notice. By mile 18, your legs do.
• •Not enough long-run volume. 20 miles once, three weeks out, isn't enough. You need repeated exposure to the fatigue of hours on your feet.
• •Skipping the marathon-pace work. Tempo and threshold matter — but marathon-pace long runs teach your body what 6:52/mile feels like for a very long time.
• •Under-fueling. A sub-three marathoner burns roughly 3,000 calories in the race. If you take in fewer than 60g of carbs an hour, the wall is a math problem, not a mental one.
• •Ignoring taper. The two hardest weeks of the plan are the two weeks before the race, when you have to do less than your training brain wants.

The magic of a coach isn't the workouts they give you. It's the ongoing relationship: someone who remembers what you did last week, notices the pattern, calls out the excuses, and adjusts on the fly. That's what I'm trying to build here — not with rules, but with a conversation that has memory and a plan that can move.

If it helps even one runner get to 2:59:59 in fewer than twelve attempts, it's worth every hour spent building it.