
Validate the useful measurements
Define training measures and feedback together. Wrist and upper-arm fit, skin contact and signal quality need separate validation.

Case study
Members and followers, but no hardware team. Define a screenless training band for your own brand.
Talk to us
Fitness creators & gym owners
The owner wants their training approach to carry into a band: fewer phone checks in class, useful feedback for coaches, and eventually a product followers could use too. What to measure and how much software the first version needs are still open questions.
Custom screenless module · Screenless
This project starts with a US gym-chain owner who also creates fitness content. They have members, followers and coaches who understand how people train. They do not have hardware engineers or a finished product specification. The starting material may be a few ideas and products they have tried.
They want a band under their own brand that fits their courses. Members should not need another screen during training, and coaches should receive useful feedback. The first version would serve classes in the gyms; a version for online followers could be considered later.

Define training measures and feedback together. Wrist and upper-arm fit, skin contact and signal quality need separate validation.

Member-owned bands and shared gym devices need different account, strap, cleaning and charging arrangements.

Agree the roles of coach software, member software and existing apps. Audio feedback and earphone connections are assessed for the project.
Together, we would work through who wears it, how it is issued, what is worth measuring and when feedback helps. The owner and coaches shape the training experience; we help turn it into choices about hardware, wearing and software. We would also agree accounts, data access and how the parts connect.
The screenless module collects agreed, validated data. Coach and member software provides the course context and feedback. We would define the connections between the band, phone, earphones and backend around the first version’s actual needs.
Define the use case. Build the prototype.
Try it with the team. Refine the first batch.

Together, we would work through who wears it, how it is issued, what is worth measuring and when feedback helps. The owner and coaches shape the training experience; we help turn it into choices about hardware, wearing and software. We would also agree accounts, data access and how the parts connect.

After prototype validation, a first batch could be tried in one gym with one type of class. The agreed package could include complete bands, charging arrangements and basic software. Staff would try the whole routine, from issuing a band to taking it back, while we review comfort, useful feedback and the work required to manage it.

Trial feedback would guide changes before the next batch. A member-owned product and a shared gym device need different straps, packaging, charging and account arrangements. Once the product and gym routine are ready, the owner can decide on repeat orders, more locations or a version for their online community.
Pilot devices, wearing carriers and charging arrangements based on the agreed version, so staff can try the full class routine.
Basic interfaces and data connections within the agreed scope, with clear access rules and a defined place for feedback.
Issuing, returns, cleaning, device identification and repeat orders, informed by the first trial before further production is agreed.
Work with the owner and coaches on useful measurements, feedback and the way members will use the band.
Check fit, signal quality and habits during real movements before agreeing the pilot version.
Test issuing, use, cleaning, charging and returns before planning further orders or locations.
The first trial should help the owner and coaches decide whether members will keep wearing it, whether the feedback helps their classes and whether staff can manage the devices. Those answers guide changes, repeat orders and wider use.
Functions, suitability and delivery scope are defined and validated for each project.