Case StudiesTyme Wear
Tyme Wear: a software team that learns the physiology first.
Tyme Wear set out to bring the insight an athlete gets in a laboratory out into the field. As a young company it had built its software to work and moved on to the next thing. When it was time to prepare for scale, its founders looked for a way to raise the level of that software. Our engineers now work on it with them.
- Company
- Tyme Wear
- Based in
- Massachusetts, United States
- Sector
- Sports and performance technology
- Co-founder and CEO
- Arnar Lárusson
- What we bring
- 2X Software Engineering & Tech Excellence
In the founder’s words
They’re not just there to follow a prescription. They’re really there to solve unique problems and solve them thoroughly, and really get their hands dirty.
The company
The question behind Tyme Wear: how do you develop a technology that gets as close as possible to the sophisticated insight gained in a laboratory, and bring it out into the field?
Its product, VitalPro, is a breathing sensor that brings laboratory-grade insight to every workout, for athletes at every level.
That makes its software unusual. A feature only makes sense to someone who understands the physiology and the human performance behind it.
Where things stood
- Built fast, as a start-up builds.The team made things work as well as it could and moved on to the next thing.
- Speed came first.Documentation and process had come second up to that point.
- Scale was coming.The company had reached the point where it had to prepare for, and manage, much more scale.
What we did
The software
- Developers from our global teams work on Tyme Wear’s software and the technology under it.
- Time on site together, so the engineers see how the product works from Tyme Wear’s side and why each feature exists.
- The software prepared for scale, with the documentation and process a growing product needs.
- Issues are dealt with quickly when they come up.
How we work together
The work is not a list of tasks handed over and checked a week later. The engineers are expected to understand the problem in depth. When something unexpected comes up on the way, they solve that too and carry on.
We’re super happy with the team. They’re great people, but also really talented developers.
We feel very supported, from the top management all the way down to the team that we’re working with.
Next step: a two-hour workshop.
Book the intro call and we fix the workshop date on it.