Bring it in
Import a workout from the tools you already use, upload a screenshot or create it directly.
RepCord turns the workouts you already do into a living performance record. Import the session, log what happened, detect PRs automatically and understand what is actually improving.
Share from your current workflow or upload a workout image.
12 TTB · 10 DB Snatch · 200m Run
Fast enough to use while training. Your previous best stays in context.
Your Clean 3RM is up 9.7% across the last 12 weeks.
Whiteboards, screenshots, box apps, notes, spreadsheets and memory all hold pieces of the same story. RepCord turns those fragments into one usable performance history.
Import a workout from the tools you already use, upload a screenshot or create it directly.
RepCord detects blocks, movements, reps, loads and scoring so you do not rebuild the workout by hand.
Track sets live or enter results after class. RX, scaled, RPE, notes and context stay together.
PRs, trends and performance signals update automatically and become useful for you and your coach.
RepCord is designed to make the record useful. It keeps the context behind a result, compares it with your history and surfaces the change that matters.
“Your clean is trending up, but high-rep pulling volume drops when RPE stays above 9 for two sessions.”
Keep your history independent from memory and screenshots. See PRs, benchmarks, consistency and movement progress without turning training into admin.
Give independent athletes or your own roster a shared performance language. Review training history and make conversations more specific.
RepCord is designed to start alongside the tools a box already uses, while giving athletes and coaches a richer performance layer. It can also support independent coaching workflows.
RepCord can begin as the performance layer on top of the workflow you already have. Bring in a workout, train as usual, and let the record grow. For independent coaches and smaller teams, the same loop can work as the core training record.
Tell us how you train ↗Logging should not compete with training. The interface is built around fast inputs and familiar session context.
Boxes change. Coaches change. Programs change. Your athlete record should remain useful across all of them.
A time or weight alone is not the whole session. Version, RPE, notes and workout structure make comparison meaningful.
RepCord connects today’s work to previous sessions so improvements, plateaus and patterns are easier to see.
A workout should not disappear the moment the whiteboard is erased.
THE IDEA BEHIND REPCORDIt does not have to be. RepCord is being designed so athletes, coaches and boxes can start by using it alongside their current workflow. The focus is the performance record: importing training, logging reality and turning the history into useful progress information.
No. You can log between sets, after class, or come back later. The goal is to make recording easy enough that the data remains useful without distracting you from training.
The product direction includes structured workout parsing, movement matching, scoring context and automatic PR detection. The current prototype already demonstrates the complete flow, while production AI extraction is part of the build toward launch.
RepCord is designed first around functional fitness and the mixed structure of strength, skills, conditioning and benchmark work. That same performance-record approach can extend to adjacent training environments over time.
Yes. Independent coaches are an important use case: a coach can keep a clearer athlete history and use the same training record for more specific feedback, even without running a full gym.
RepCord is in early product development. Join the early-access list and tell us whether you are an athlete, coach or box so we can prioritize the right workflows for the first release.
Join the launch list and help shape RepCord around real training, real coaches and real boxes.
Tell us how your current workflow works and where performance data gets lost. Those conversations help shape what RepCord becomes next.