Accelerate
Your
Training
Periodization built for sprint and track, not borrowed from the gym.
Built for coaches who demand precision with ease.
Sprint, hurdles, jumps, relay, gym, track.
An open beta — built with coaches.
One person building it, with a coach shaping it.
That is the whole team. It is the reason the fields match the sport, and the reason a bug you report gets looked at the same week.
- The build
One person writes the software
No team, no investors, no roadmap written by someone who has never run a session.
- The check
A sprint coach shapes it
Every decision about what a session holds gets argued with someone who coaches for a living.
- The result
The fields follow the sport
A sprint asks for distance and time, a lift for reps and load. That came from coaching, not from a spec.
Let me set it up with you.
Free, and with the person who writes it. Tell me about your squad and I'll email you to find a time. We put your athletes, your groups and your first block in together, live. Right now the walkthrough is the product.
Isn't one person a risk?
Yes, and it is the honest trade. What you get for it is that nothing on this page was written by a marketing team, every claim traces to code that runs, and the person who reads your email is the person who fixes it. What you give up is the reassurance of a large company behind it. If that trade is wrong for you, it is genuinely wrong for you.
From the session you wrote to what came back
Paste a session — AI extracts it.
A scripted walkthrough on example data — not a live account.
Prescribed in metres and seconds, not kilos and reps.
A sprint asks for a distance and a time. A bench triple asks for load. Each movement shows the few fields it needs, the rest are a menu away, and the ones that make no sense never appear. No kilos on a flying 30.
Do I have to get the whole squad on first?
No. Each athlete signs in with their own account and you invite them as they come. Put next Tuesday in first, then add whoever turns up to it. An athlete added after you published still gets that session. Leave the twelve-year-olds on paper until you're ready.
Sprint: Flying 30m. Fields — distance, time, rest, effort.
Distance and time, because that is what a sprint is measured in.
Example session — the numbers are made up. The row itself is the app's own, and the fields it shows are chosen by the app's own rules. Type in it if you like.
Is VBT a fourth kind of exercise?
No. VBT is a column set, not a category. That tab is the same gym lift as the Gym tab with one optional field switched on, which is why its fields come back as distance, time, rest, effort rather than something new. Nothing gets created to track bar speed.
Never enter the same week twice.
Two of these will become your habit. The other four are why a week you were too busy to enter still ends up in the record. A week that never got entered is a week the comparison can't use.
Write the session for the group
Publish it. Everyone on that group's roster opens it on the day, with the video if you attached one.
Copy the week forward
Take one week onto up to twelve later weeks, then change only what's different about each.
And four for the weeks that get away from you
Photograph what you wrote
Ten photos of a written session, back as sets you edit.
Give a subgroup different work
Tag exercises to a subgroup. One session, different work per athlete.
Save a session as a template
Keep one you run often. Drop it into any later day.
Lay the block out first
Name a program, give it two dates. Blocks and empty weeks appear.
Flying 30m
Build through the run-in, hit top speed by 20m, hold your shape through the zone. Walk back.
Example session, as one athlete opens it. The rows are the app's own — put a time in and tick a set.
Your coaching goes in the same place.
The record holds what your athletes did. It also holds what you know. Your own articles, in your own categories, open beside whatever session you're editing.
What do coaches actually put in there?
Your warm-up standards. The cues you always give on a fly. Why GPP2 changes what it changes. The things you re-explain every September, or keep in a notebook only you can read.
Reading it uses no AI. If you do use the assistants, they can search and read those articles when you ask. Separately, you can tell an assistant a preference once and it keeps it.
- Warm-upTrack warm-up, wet days
- SpeedFly 30: cues that work
- BlocksGPP1 to GPP2: what changes
- GymTraining max, how I set it
Fly 30: cues that work
Build through the run-in. Top speed by 20m. Hold shape through the zone, then walk back. Don't chase the clock on rep 1.
Yours · written once, open beside every session
Example articles. The panel opens beside the session you're editing, and beside a template.
Is anyone actually getting faster?
Every rep an athlete logs sits on one page, in order, next to the ones before it. That is the question the record exists to answer.
| Session | Rep 1 | Rep 2 | Δ best |
|---|---|---|---|
| 20 May | 3.61 | 3.58 | no earlier session in this window |
| 3 Jun | 3.62 | 3.55 | −0.03faster |
| 17 Jun | 3.57 | 3.50 | −0.05faster |
| 1 Jul | 3.53 | 3.56 | +0.03slower |
| 15 Jul | 3.48 | 3.51 | −0.05faster |
| 29 Jul | 3.45 | 3.47 | −0.03faster |
| Best rep, first session to last | −0.13faster | ||
Example data. Times come from the reps the athlete logged.
How long before it tells me anything?
About six weeks. The squad comparison runs on a rolling ninety days and splits it down the middle, so it needs one comparable value either side before a difference means anything. It does not line up with your block boundaries.
Top lifts and completion rates are there from the first week. Sprint times only reach that squad table when they arrived as timing-gate data, so if you type times in, that column stays empty. Per athlete, the reps you logged are readable straight away.
If you can photograph your sheet, you can start.
Take a picture of last Tuesday, in your own handwriting and your own shorthand. It comes back as a session you edit before you send it. If it reads something the wrong way, write the rule down once and it keeps it.
- Flying 30m4 × 30 m1234
- Wickets6 × 30 m
- Back squat3 × 3
- Depth jump3 × 5
- Flying 30mMS2 × 30 m12
Illustrative animation — the real parse returns the whole session at once. The rows are the review screen's own, and every value in them is editable before you send it.
The lab in your pocket.
Sprinter turns the phone already in your pocket into trackside measurement gear — neural readiness, reaction, stride mechanics, sprint splits. Seven tools. One phone. Feeding the same training system.
Sprinter measures: CNS tap test, reaction time, block start, plyometric RSI, stride analysis, distance, and sprint timing.
The AI half waits to be asked.
It never runs on its own and it never interrupts. Every one of the three things it does starts with you deciding to do it.
- You click
Ask about the group
Pick a group and a window. It writes up what their logged work shows.
- You upload
It reads your handwriting
Your sheet comes back as a session, shorthand and margin notes included. Write your rules once; it keeps them.
- You ask
Ask about an athlete
Ask in plain language. Answers come from that athlete's logged sessions, and it says when data is missing.
Anything I should look at before I write GPP2?
Three of the five logged every session. R. K. has missed four Tuesdays, and his flying 30 has not moved since the second week. The other four are all quicker over the same window.
Every answer is built from logged sessions. If it isn't in the record, it doesn't answer.
An example question and answer, not a live account.
Is this part for me?
Some coaches want the record and nothing else. Others already run a spreadsheet, time everything, and want a second opinion. If that's you, this part is for you. If it isn't, ignore all of it and nothing changes.
Built for both sides of the stopwatch
Athletes log and see progress. Coaches plan and see everything.
I'm an Athlete
- Track every rep effortlessly
- See your progress after every session
- Beat your personal bests
- Get AI coaching suggestions
I'm a Coach
- Build periodized plans visually
- Monitor your entire roster at once
- Make data-driven training decisions
- Send each session straight to their phones
Four reasons to not start yet.
We would rather you came back in October than started this week and found the thing you needed missing.
You want your gate exports read automatically.
Velocity is a real field on the set, and split data already in the record drives the sprint charts. But nothing reads a Freelap, Brower or Dashr file on its own, and there is no screen to type splits into. While we are this small, send us the file and we will bring it in by hand.
You want it to tell you the programme is too aggressive.
It answers when you ask it. Nothing reviews your block and warns you off it, and nothing compiles your week for you. Both are on the list. If that is the reason you would sign up, wait for it.
You are mid-block and don't want anything to move.
Start at your next block instead. Nothing here needs your season backfilled, so there is no advantage to starting in the middle of one.
You want it to tell you whether the block worked, this block.
The squad comparison runs on a rolling 90 days: the last six weeks against the six before them. It needs about six weeks of logged sessions before a difference means anything, and it does not line up with your block boundaries. Top lifts and completion rates are there; sprint times only feed it when they arrived as timing-gate data, so that column stays empty if you type times in. If you would sign up for a verdict on the block you are writing now, that is not what this does yet.
Either way, one thing holds: the numbers you'll wish you had in March are the ones somebody wrote down in September. That is as true in a notebook as it is here.
Frequently asked questions
Sprinting uses AI to help you build and modify training plans through natural conversation. During a workout, you can chat with the AI assistant to add exercises, swap movements, or adjust sets and reps. The AI understands training principles and adapts suggestions to your context.
Yes. Sprinting supports coach-athlete relationships natively. Your coach can create training programs, assign them to you, and monitor your progress. Athletes log workouts and the data flows back to the coach. Both roles work within the same platform.
Sprinting supports strength training, running, sprinting, and general athletic training. Sprint work is logged in distance and time per rep, with velocity on flying runs where you record it, alongside periodized training blocks for structured programs and a comprehensive exercise library. The platform is designed to handle any training that involves sets, reps, or timed efforts.
Yes. All data is encrypted in transit and at rest. We use Supabase for our backend infrastructure with row-level security policies. Your training data is private by default — coaches can only see data from athletes who have explicitly connected with them.
Sprinting is a web application that works on any modern browser — desktop, tablet, or mobile. It is built as a progressive web app (PWA), so you can install it on your home screen for a native app-like experience on iOS and Android.
Free during open beta — the whole product, no card. Paid coach plans begin when billing launches; the prices are already published on the pricing page so there is no surprise. Your feedback during the beta is what we are optimising for.
Start at your next block.
One upcoming session and two athletes is enough to begin. You'll still be writing wherever you write now.
- 00:00You bring next Tuesday
- 00:15Two athletes, invited
- 00:30It's on their phones
No card during the open beta · Priced per coach, not per athlete · No seat cap