Really interesting thread. I’ve been lurking for a while and wanted to jump in because I’m building something that tries to solve exactly what you guys are talking about.
I’m working on a coaching app (iOS/Android/Web) that isn’t just another LLM chatbot spitting out generic advice. It’s a proper platform with structured workouts, zone calcs (Coggan, HR, CSS, etc.), and full load tracking (ATL/CTL/TSB). The AI coach works on approval—it proposes changes, tells you why, and you click yes or no. It doesn’t mess with your schedule without consent.
Under the hood, the coach has access to about 40 tools. It reads metrics, analyzes drift and power peaks, and has actual long-term memory. If you mention an injury or that you can never train on Tuesdays, it remembers that weeks later. I’ve already got integrations running with Strava, Intervals.icu (bi-directional), and Apple Health.
The point made earlier about plans failing when life gets messy really hit home. Generating a static plan is the easy part. The hard part is the daily grind—you slept 4 hours, you’re traveling, or you missed two sessions. That requires context, not just a recalculation.
The other issue I keep seeing is that AI coaches are too generic. They all pull from the same average internet knowledge. A TSB of -15 means “push” to one coach and “rest” to another. The AI shouldn’t be guessing; it should be following a specific philosophy.
That’s why I built a feature called Blueprints.
Think of it like a marketplace for coaching logic. Coaches or experienced athletes publish their methodology in a markdown format and you can select the blueprint for your training plan. It stops the AI from hallucinating generic advice and forces it to stick to that specific coach’s rules regarding periodization and recovery.
It also handles natural language notes. A Blueprint might say, “If the athlete misses a session, protect the Sunday long run at all costs.” So when your schedule blows up, the AI adapts exactly how that specific coach would, not how ChatGPT thinks it should.
The big plus of doing this as a marketplace is that you aren’t flying blind. You’ll be able to see ratings and popularity for each Blueprint, so you know which methods are actually working for other people before you commit to one.
A Maffetone Blueprint and a Daniels Blueprint will give you totally different advice on the same data, which is how it should be. It gives the AI a consistent voice.
Happy to show more if anyone is interested. Does the “Blueprint” concept sound like something you’d actually use, or am I overcomplicating it?
The results of my work are here: https://mytrainpal.app
Obviously still in early development days so please forgive if you find bugs, appreciate your feedback though.