Key Takeaways
A cycling coach can build his own coaching tools with AI and no code. Matt Hughes, British and Welsh National Masters Champion and a coach since this year, built an athlete availability page and a strength tracker on the Vekta API with Codex, describing what he wanted out loud instead of writing code.
An availability page can replace the Friday message to every athlete. Matt's page emails each athlete at 6pm on Friday, repeats twice a day until they reply, fills in a shift rota for them and writes next week's availability into Vekta as notes. He built it in "an hour tops".
A strength tracker can read Vekta load before the session starts. Matt's tracker shows his Vekta Load and Strain, asks how he feels, keeps or adjusts the session, and writes the finished session into Vekta as a weights workout, beside his rides.
One tool can teach the next, and both can become part of the offer. Matt built the availability page by telling Codex to reuse the strength tracker's method, and plans strength as a bolt-on to his coaching tiers, with each athlete given their own copy.
At 16:09 on Saturday 7 November, Josh filled in his week ahead: two day shifts, a couple of days' holiday, and an hour to ride most days. He pressed one button, and the page told him his week was now live in Vekta and that his coach, Matthew, had been notified.
His coach never sent him a message. He did not chase him on a Friday night, or copy a shift rota into a calendar on Sunday. Something he built did it for him.
Matt is the British and Welsh National Masters Champion, and races for NoPinz RT. He has never had a coach. For six or seven months he trained himself with Vekta and its AI tools, checking his numbers every day. It made him far more focused on the quality of each session, and taught him things about his own physiology he had missed or never known. It became his most successful season yet.
He saw that what had worked for him could work for other athletes. So this year, alongside his racing and a full-time job on shifts, he took on a third commitment: coaching, with Vekta. Something had to give. It was not going to be his athletes, or his racing. It was the admin. So he built the software around the way he works and the way he coaches, with the Vekta API and Codex, without writing a line of code.
What does a coach build when he writes the playbook himself?
The Message He Sent Every Friday
Every coach knows the question. What does next week look like? The plan depends on the answer, and the answer lives in the athlete's life, not in their power file: a shift rota, a holiday, an evening that will run late.
Matt's athletes have jobs too, and some work shifts like him. So every Thursday or Friday, Matt would text each of them. Then he waited. He can only plan around what he knows.
With a few athletes, the messages are a nuisance. At ten or more, they are an evening. Every week. Matt saw it coming before it arrived.
“Life happens. As long as I can see what an athlete's week looks like, I can build the plan around it. But I didn't want to spend every Friday asking athletes for the same basic information. So I automated it, and made it easier for them too.”
Matt Hughes
An Hour, Spoken Out Loud
So he built a page. At six o'clock every Friday evening it emails each athlete, and if they do not answer, it emails again, twice a day, until they do. Each day asks four things: the shift, whether they can train, when, and for how long. An athlete on shifts picks the first one, and the page fills in the rest.
When he submits, the week goes into Vekta as notes on the days ahead, and the page tells Matt.

The coach view of Matt's availability page. Built with the Vekta API
He did not type the instructions. He spoke them to Codex for about five minutes, just thinking out loud, and built the page in a couple of short sittings: an hour at most, by his own count.
It went out on a Friday with no explanation, and none was needed. The email arrived, the athletes followed it, and their weeks went straight into Vekta. A shift pattern fills itself in, so they zip through it in moments. For Matt, every athlete's week now lands in one view before the weekend, with no chasing. Across ten athletes, that is two to three hours back every week, to spend on the coaching.
“I'm not a developer. I described what I needed out loud, and with the Vekta API, it just works.”
Matt Hughes

The athlete's side of Matt's availability page.
It Started in the Gym
The method was not new to him. He had first built it for himself, in the gym.
Matt wanted his strength training in the same place as his riding, so he built his own tracker for it. Every session is laid out on his phone, each exercise with a video example to follow. For lifts he had not done before, he filmed himself and had the AI check his technique. When he finishes, the session goes into Vekta as a weights workout, beside his rides.
“I wanted my strength work in Vekta with my riding, so I can see what it's actually doing to me over a season. Now I can offer the same to my athletes.”
Matt Hughes

Matt's strength tracker built with the Vekta API
Then he took it a step further. The tracker opens on his Vekta Load and Strain, and before each session he rates how he feels. If he is tired, it asks whether to continue with the prescribed session or adjust it.
For a coach, that matters. Vekta's Load and Strain are built from the work done on the bike, and a gym session has no direct line into them. By pairing every session with how he felt, Matt is drawing that line himself. Over a season, it will show what his strength work is really doing to his riding.
From His Logbook to His Offer
The two tools are connected. When Matt built the availability page, he told Codex to use the same method as his strength tracker. Codex had learned how to talk to Vekta on the strength tracker, so the availability page came quicker.

Both now feed the business he is building. Matt is logging the time each athlete takes, from onboarding on, so he can price his coaching in tiers. Strength may become a bolt-on to those tiers. The next step is to give each athlete their own copy of the tracker, feeding his records and their Vekta. Richard, a lifelong friend he coaches, will test it first.
The work Matt cares about stays his: the plan, the conversation, the judgement. What he has removed is the work around it.
If you're interested in working with Matt, or in learning more about how he coaches, you can find him on here.
Write Your Own Playbook
Matt puts it simply.
“The only thing stopping you is yourself. The AI isn't the limit. The limit is how far you're willing to take it.”
For twenty years, the software wrote the playbook and coaches followed it. Matt is writing his own.
The Vekta API is free with every subscription. Generate your own key in Settings.
Connect Vekta to Codex, Claude Code or Gemini CLI · Start your 14-day free trial · Book a demo

Try Vekta free
Put the theory to work
Vekta is where coaches and athletes plan the work, see the numbers, and track what actually changes.

Brand Director


