A team meeting turned into a product pressure test. We walked in arguing about features. We walked out with a sharper product thesis than we started with.
We were on a group call, the four of us — Ryan, Kai, Joaquin, and me. I was supposed to brief everyone on where the youth sports wearables market was heading and walk the team through the v1.6 feature set we had been building toward for weeks.
I opened with what I thought were our strongest features: the Session Load Score that compresses athletic exertion into a single number, and the jump counter that tracks vertical and explosive efforts session over session. These were the features I expected the team to rally around.
Instead, Ryan cut in first. "Why couldn't coaches just use the eye test for this?" Then Kai followed up with something sharper. "Why not a laser?" He was not proposing a product alternative. He was saying that our feature set could be replicated with a cheap measuring tool and a stopwatch — which is a very different kind of critique than "change the algorithm." It is a co-founder asking whether the category needs a dedicated device at all.
Kai kept going. Catapult already ships parent-facing PDFs. STATSports has the enterprise dashboard. Any coach with a CSV export and a free ChatGPT account can produce a parent summary in under a minute. What were we actually adding to the space?
The research was not thin. I had been running on a real thesis: Catapult's enterprise pricing and STATSports's D1 focus leave an empty price band below $150, and the youth and private-training market lives in that band with no product built for them. The data backed it.
What I had not done was translate that business thesis into a language two engineers would find compelling. To Ryan and Kai, a "market gap" is not a feature. Hardware that is intentionally simple at v1 — a clean Session Load Score, a jump counter, a clear parent-facing summary — sounds underbuilt if you have not yet connected it to the business reason simplicity is the right call.
So instead of walking away from the call, I pulled up the research I already had.
Simple is the point, not a limitation
I walked the team through what the research was actually saying — not just that the gap existed, but why it existed, and why a simple product was the right answer to it.
The pattern that mattered was retention. Private trainers lose clients between months three and six, and the reason is almost always the same: parents stop seeing their child's progress. Not that there is no progress — that the progress is not visible. No product at our price point makes a child's development into a weekly, parent-facing artifact.
Simple is the point of v1, not a limitation of it. A trainer running fifteen clients a day does not want a dashboard with forty metrics. A parent paying $1,200 a month does not want a CSV. What a trainer needs is one number that a parent can understand without explanation. What a parent needs is a weekly summary they can show their kid and believe in.
v1.6's feature set was not the problem. Session Load Score, jump count, movement zones — these are the right features because they are the simplest features that answer the retention problem. Complexity is a v2 conversation. You earn complexity by first proving the simple version works.
When I framed it that way, the conversation changed. The same features that sounded underbuilt fifteen minutes earlier became the obvious starting point once the business reason was on the table. v1.6 stayed. The features stayed. The sentence that sells the product got sharper.
Ryan and Kai asked the right question, and they asked it early enough to matter. That is exactly what co-founders are supposed to do — and the reason the product came out of that call stronger than it went in.