Why we built CoachLogik's Copilot the way we did
COPILOTAug 28, 2026

Why we built CoachLogik's Copilot the way we did

We built CoachLogik's Copilot to execute a coach's thinking, not to replace it. It builds full blocks and multi-week progressions, analyzes an athlete's training history, and makes edits across your calendar on command. What it does not do is make your coaching decisions for you, because that is the part of the job athletes are actually paying for. Here is the thinking behind what we built, and what we deliberately said no to.

Where this started

When I started thinking about what I wanted CoachLogik to be, I was struggling.

I was managing my team of athletes at the gym while trying to deliver the best possible experience to remote athletes across the world. And the limitation was not time, capacity, or the will to coach. It was that there was no real weightlifting coaching software built for what I needed, and the tools I had could not deliver the experience I wanted or track what I wanted. Sheets and TrueCoach were not cutting it anymore.

My workflow was a patchwork. I would use spreadsheets to calculate the data, then go into TrueCoach to implement the program, then do my video reviews somewhere else. And even then, simple things were impossible. If a lifter was jumping forward in the snatch, I wanted to draw on the screen and show them with a diagram instead of saying it over and over again. There was no way to do it.

So when we built this thing, we knew we wanted the features other apps were missing. But it was about more than features. We were entering the AI wave, and I did not want coaches to get left behind by AI slop from larger companies, tools built by teams where nobody has actually coached and nobody knows what we as coaches truly need.

Related: How the Best Coaches Use AI to Deliver Better Programs →

What we wanted CoachLogik Copilot to be

From the very beginning, I wanted to build a real AI assistant. A system that could flag what needs attention, run analysis, and take a question from me like: go do a deep dive into this athlete's training and tell me what it sees from a data standpoint. Then I make the decision about what to change.

I wanted a place to pressure test my ideas. My hypotheses about what to change next cycle. A way to compare cycle to cycle that goes deeper than looking at charts, which is also why we added the yearly planner in CoachLogik. I wanted more than the visual. I wanted the story behind the visual.

Because as the years go by, it is so easy to forget what you did three years ago that may or may not have worked. A copilot that can go look at that history, pull the information, and bring it back into view while you are programming the next block is a real advantage, not a novelty.

The problem was never ideation. It was sets and cells.

Here is the thing about programming that non-coaches building coaching software never understand.

When you are looking at a lifter's block and building the next cycle, you already know what you want to give them. You know the dosing. If training is the medicine and progress is what we are solving for, you already know what medicine is needed. That part is fast, because that part is coaching.

What took forever was the creation. Sitting there typing cell to cell, day to day. Copying and pasting a week, filling in the blanks, adding an RPE, adding an intensity, adding a percentage. I have done that thousands and thousands of times. And honestly, I felt like I was falling out of love with coaching, because coaching had become adding sets and reps. Not being creative. Not being able to ideate.

A lot of coaches make this mistake without realizing it. They cannot be as creative as they want with programming because the job of just getting it onto paper eats everything. It becomes a volume play.

So we built Copilot to take that entire layer of the job away. You spend your time on the iteration and the ideation. You stop worrying about how long the writing will take, because the writing was never the coaching.

Now I find myself spending more time thoughtfully thinking about the training cycle, what we are trying to accomplish, and how to build it, without the implementation tax hanging over every idea.

What it does

Copilot builds full blocks and multi-week progressions. It analyzes your athlete's history. It makes edits directly on your calendar. You tell it what you want the way you would explain it to another coach, and it types the whole thing out for you.

Two real situations, because this is where it earns its keep.

Client goes out of town
Tell Copilot what equipment they have available and what you want changed. It is done.
An old knee injury flares up
Tell Copilot what you want: convert squatting to tempo work at 3-0-1, drop squat percentages to RPE 7 for weeks six, eight, and nine, swap plyo for steady state on the bike. You tell it. It does it.

No more rewriting a block by hand because life happened to your athlete. Life always happens to your athletes. Now the adjustment takes a sentence instead of an evening.

Paste in a block and ask Copilot to change one thing.

Start Your Free Trial →

What we refused to build

The refusals mattered as much as the features, because they are what keep the coach in the middle of the coaching.

We refused to let the AI make the decisions.
Copilot flags, analyzes, and answers questions about the data. It does not decide what changes to make. The judgment stays with the coach, always, because the judgment is the product.
We refused to automate the ideation.
Copilot removes the sets-and-cells labor, not the thinking. It will not invent your training philosophy for you.
We refused to build a generic chatbot with a coaching label on it.
A generic model with no coaching knowledge behind it looks like help and is not. Copilot is built with a coaching and training knowledge base, by people who have actually coached.

The pattern across all three: use AI on the labor, never on the judgment or the relationship. The moment an AI tool starts doing the parts of coaching that make you a coach, it is not saving you time. It is taking your job.

The point

We built Copilot so that the time you used to lose to typing goes back into the thing you got into this for: thinking about training, watching your athletes, and building the blocks you always wanted to build.

If you want to feel the difference, start a free trial, paste in a block, and ask Copilot to change something. The first time an adjustment that used to cost you an evening takes one sentence, you will understand why we built it this way.

Tell it what you want. It does the typing.

Paste a block in. Ask for a change. See the sentence replace the week.

Start Your Free Trial Today →

Frequently asked questions

Does Copilot decide what changes to make to my program?
No. Copilot flags patterns, analyzes an athlete's training history, and answers questions about the data. It does not decide what to change. A coach reviews what Copilot surfaces and makes the actual call.
Will Copilot invent programming for me if I don't tell it what I want?
No. Copilot builds and edits based on what you tell it, the way you'd explain it to another coach. It does not generate training philosophy or invent a program from nothing.
Is CoachLogik's Copilot just a general AI chatbot with a coaching skin?
No. Many "AI" features in fitness software are a direct integration with a general model and nothing else. Copilot is built with a coaching and training knowledge base specifically, by people who have coached.
Can Copilot handle a mid-block change, like an injury or a schedule conflict?
Yes. Describe the change in plain language, and Copilot applies it across the relevant weeks. What used to take an evening of manual rewriting takes a sentence.
Why does CoachLogik keep the coach in the decision-making loop instead of automating more of it?
Because judgment and the coach-athlete relationship are what a client is actually paying for. Automating programming labor gives a coach their time back without taking away the part of the job that makes someone a coach.

About the author

Max Aita is the co-founder of CoachLogik and has spent his career coaching weightlifting and strength athletes at the highest levels. He built CoachLogik to be the weightlifting coaching software he always wished he had.