Movement AI
AI that measures movement, for health and sports products
Pose, reps, form, gait and body signals from a phone camera or a wearable. Six steps from a free verdict to a model in production. Each step ends with a result you can use, and you can stop after any of them.
Pick your step
Most teams start with the free assessment. If your model is already live, start where you are.
- 01Entry
Free assessment
One working daySend a spec and a few recordings. An engineer replies in writing within a day: can it be measured, and what will break it.
Start here - 02Research
Technical research
Two weeksTwo or three candidate models run on your recordings. Measured accuracy, a list of failure cases and a go or no-go.
Open - 03Proof
Proof of concept
6 to 12 weeksA model trained on your data and a demo your pilots can use. Accuracy measured before and after.
Open - 04MVP
First product version
8 to 16 weeksYour first app version in users’ hands: capture flow, on-device model, results screens and a test build.
Open - 05Product
Product build
Scoped per releaseYour model in your next release, on both platforms, built in your repositories alongside your developers.
Open - 06After launch
Model care
MonthlyThe model keeps its accuracy as users, phones and OS versions change. A one-page accuracy report every month.
Open
Find your stage
Hover a stage to see where to start.
Can it be measured?
Will a phone camera or a sensor even catch this?
Vendor or SDK failed
Months in, the model still does not work.
Raising / pause
We are raising. Development has to wait.
Launch
The feature has to work in the app, on the phone.
Accuracy complaints
Reviews say it counts wrong.
Expansion
A new sport, a new test, a version for clinics.
Free verdict in one working day
Free feasibility check for your AI feature
Describe what the AI should measure. Within one working day an engineer tells you in writing whether it can be done, what is likely to break it, and what to do next.
- 1You describe the feature
A sentence or two, and a link to recordings if you have them.
- 2An engineer reviews it
The CTO or a domain expert, not a sales team.
- 3You get a written verdict
Within one working day: can it be measured, the risks, the next step.