The WhatsApp Reply That Reshaped the Product

The Message I Wasn't Ready For

I'd been trying to get a reel in front of Edu Talavera for a while. Edu runs @edutalfer, a cycling coaching account with 32K followers on Instagram. He's exactly the profile I'd been optimizing for: active creator, cyclist, technical, vocal about the tools he uses. If SportsSync resonated with him, I'd learn something useful. If it didn't, I'd also learn something useful.

I sent him a recent SportsSync short and asked what he thought.

His reply came back fast:

"Hola David, perdona, voy a tope, no me ha dado tiempo ni a mirarlo. Sin haberlo visto todavía, solo este último reel que me has pasado, a ver, cuando grabo onboard ya siempre grabo con la Insta360 Go Ultra y trae esto de manera nativa, tienes que luchar contra eso jajjaja"

Translated: "Sorry David, I'm slammed, haven't had time to look at it. Without having seen it yet, just from this last reel — when I record onboard I always use the Insta360 Go Ultra and it has this natively, you've got to fight against that."

He hadn't even opened the product. He'd just looked at the reel, recognized what it does, and pointed at a competitor I hadn't taken seriously enough: the camera itself.

That message did something to me. Not defensiveness — the concrete feeling that some assumption underneath the whole project had just been stress-tested and I didn't know how it held up.

What Is Insta360 Stats Dashboard

I'd known Insta360 cameras had overlay features. I hadn't understood how good the feature had become, or how deeply integrated.

Here's what the Insta360 Stats Dashboard actually does in 2026:

• Works natively inside the Insta360 app on mobile. No desktop software. No post-production pipeline. No file transfers to a laptop.
• Supports GPS, speed, heart rate, elevation, cadence, and more, overlaid on video captured by any recent Insta360 camera (X-series, Ace Pro 2, GO 3S, Go Ultra).
• Pulls data from Garmin Connect directly, Apple Health (since early 2025), and Strava (since late 2025).
• Exports vertical video for Reels and TikTok.
• Costs zero extra — it's included with the camera.

The user journey is: finish ride, sync Strava, open Insta360 app on phone, tap Stats, select Strava as source, authorize once, overlay appears, trim clip, export, post. Maybe four minutes from ride end to Instagram.

My user journey is: finish ride, open SportsSync on phone or desktop, upload video, wait for upload, connect Strava, select clip, generate short, export or publish. Rough parity in outcome, more friction in flow, and the user had to find SportsSync in the first place.

For anyone who owns an Insta360, SportsSync was not obviously better. In several respects, it was worse.

Then I Checked DJI

After Insta360, I checked DJI. Because if one action camera vendor had solved this, others likely had too.

DJI ships the Osmo Action GPS Bluetooth Remote — a wrist or handlebar remote with GPS that connects to Osmo Action 4, 5 Pro, 6, and the Osmo 360. It records location data that the DJI Mimo app overlays on video with speed, elevation, direction, route. The hardware is £69. The app is free.

Same story as Insta360, with a hardware add-on instead of built-in GPS, but functionally the same solution: action camera vendor ships overlay flow native to their ecosystem.

Two vendors, both with large cycling and action-sports audiences, both offering data overlay natively, both on mobile, both for free or near-free.

I was sitting on my couch realizing that the "gap in the market" I'd been building toward for a year was more like a gap that had closed while I wasn't looking. Or more accurately — a gap that had never been a gap for the people who bought these cameras.

The Wahoo Rabbit Hole

One more check before deciding what to do. I asked: does this cover every camera + GPS combination, or are there holes?

I ride with a Wahoo. Insta360 doesn't have direct Wahoo integration. But Insta360 supports Strava as a data source. And Wahoo syncs to Strava automatically. So the flow exists, just not as a first-party integration:

1. Wahoo records the ride
2. Wahoo syncs to Strava
3. Insta360 app pulls data from Strava
4. Overlay appears on Insta360 video

This works for any Strava-connected device: Wahoo, Polar, Coros, Bryton, Apple Watch, Garmin. The Strava integration is the universal adapter.

Insta360 had effectively absorbed the entire GPS-device ecosystem through one integration. DJI had a similar story with Garmin Connect. The "camera-agnostic GPS overlay" positioning I'd been building wasn't differentiated for anyone who owned an Insta360 or a DJI Osmo.

At this point I closed the laptop and sat with it for a while.

What Edu Said Next

The next day I replied to Edu with something like: "Makes sense. I guess the competition is real. I hope not everyone has an Insta360 — and not every camera has GPS."

He wrote back:

"Ya… hay competencia. Espero que no todos tengan una insta 360. No todas las cámaras llevan GPS 🤞🏻"

"Yeah... there's competition. I hope not everyone has an Insta360. Not every camera has GPS 🤞🏻"

Okay. Not everyone has one. That's true but thin.

Then I mentioned it was a pity because I thought the target audience would have been creators like him. His response changed the project:

"jajaja tienes el nicho en los que graban con el móvil"

"Ha, you've got the niche of people who record with their phone."

One line. No elaboration. He moved on to something else in the conversation.

But that line did what no amount of independent market analysis had done. It named the segment that was actually uncovered.

Who Actually Records Video of Their Rides

This is the question I should have asked harder in episode 1.

If you record onboard cycling video with the intent to post on social media, you fall into one of these buckets:

1. You have an Insta360 or a DJI Osmo. You use their native flow. SportsSync is not compelling.
2. You have a GoPro. GPS overlay options exist but are weaker than Insta360's, and the GoPro Quik mobile app has been improving. SportsSync is marginally compelling.
3. You record with your phone. Nothing is easy for you. You have a cycling app that tracks GPS (Strava, Wahoo, Garmin Connect), you have a phone that shoots good video, and you have no tool that connects the two.

The first bucket is the one I'd been marketing to, and Edu is in it. He doesn't need SportsSync.

The third bucket is larger than I'd been treating it. Most cyclists don't own an action camera. They own a phone. The phone shoots good enough video for social. The phone is already in their jersey pocket or mounted on the bars. The barrier to entry is zero — no €400 hardware investment, no accessory to remember to charge.

These users have no native solution. Their Strava syncs have rich data. Their phone camera rolls have rich video. Nothing stitches them together.

That's the niche.

Santi Was the Signal, I Just Didn't Read It

Here's the thing that makes me feel slow: Santi, my first real user research subject from episode 13, records with his phone. In portrait mode, for Instagram Stories, because that's what his generation does.

I noted that as a product gap at the time — vertical video support needed — but I didn't recognize it as a positioning signal. Santi wasn't a GoPro user who happened to also record with his phone. He was a phone user, period. Him being my first voluntary user said more about who the market is than I let it say.

The data was in my user research notes from October. Edu's message in April was just the moment I finally read it.

What Actually Changed

Here's the uncomfortable, and also kind of liberating, thing: none of the product needed to change technically. SportsSync already accepts any video file. It already syncs with Strava. It already outputs 9:16 vertical. It already has Instagram direct publish. The product was already a phone-user tool. I'd just been describing it to the wrong audience.

What changed was positioning, not code:

• Primary user in every piece of copy is now the phone-recording athlete. Action camera support is secondary, described as "works with your GoPro or Insta360 too" rather than leading with it.
• Landing page visuals need to show phones mounted on handlebars, not GoPros on helmets. That's a shoot I haven't done yet.
• The pitch changed from "better GPS overlay for your cycling videos" to "turn your phone recording into a shareable short with real data from your ride."
• Insta360 and DJI aren't competitors to beat. They're competitors who serve a different segment well. The honest statement is: if you already own an Insta360 or DJI Osmo, use their native flow. If you don't, here's SportsSync.

The business case also got cleaner. Instead of trying to win against well-resourced hardware vendors with excellent software, I'm serving the much larger segment of athletes who never bought one of those cameras. That segment is structurally invisible to Insta360 and DJI because those companies make money from hardware sales — they have no reason to build an app that works without their cameras.

What I'd Tell Past Me

If I could send episode 1 a message: the camera you use is the camera you default to when designing the product. Stop doing that.

I have a GoPro. I built the mental model of the product around GoPro users. Most of my target users don't have one. Most athletes with a phone and a Strava account are the actual market.

This is a specific version of a general founder mistake: you build for users who look like you. Unless you look like most of your users — which is rare — that's going to bias positioning in a way that eats into your addressable market without you noticing.

The fix isn't to have better intuition. The fix is to get your product in front of people who don't look like you, fast, and listen when their behavior contradicts your assumptions.

Santi recorded with his phone in October. I didn't fully hear it until April.

What Happens Next

A few things that matter from here:

The retention loop. SportsSync doesn't yet automatically notify users when they have a new ride to edit. Strava sends webhook events for every new activity, and SportsSync currently discards them. Hooking that up — webhook arrives, email fires ("your Saturday ride is ready to edit, open SportsSync") — is one to two weeks of work and is probably the single highest-leverage piece of work pending. For a tool used 1-4 times per month, retention depends on the product actively re-inserting itself into the user's workflow. Without that loop, users forget they're subscribed.

Overlay quality polish. This hasn't changed. The default template needs to reach a broadcast-quality standard before I put SportsSync in front of more ambassadors. One great overlay is worth more than five decent ones.

Mobile scrubber UX. Currently the scrubber on mobile is functional but not visually usable — it has fine-tuning buttons but no draggable timeline with preview. For the phone-recording ICP, the primary input device is a finger on a phone. This is not polish, it's table stakes.

Talking to more users. Santi was one session. Marc Figueras (@elsellociclista, cycling journalist, 116K combined IG + YouTube) got a message from me last week and hasn't replied yet. There will be others. The pattern I'm trying to set for myself: for every assumption I make about who the user is, put the product in front of two people who fit that profile and see what breaks.

The Meta-Lesson

Thirteen episodes of careful product development. One WhatsApp message reshaped the positioning more than any of them.

Not because the message contained new information — I could have researched Insta360 myself at any point. It's that the message came from someone whose opinion I'd already decided to weight heavily, at a moment when I was paying attention because I'd asked. Unweighted information on the internet is infinite. Weighted information from someone you respect, arriving when you're listening, is scarce and high signal.

This is the argument for ambassador conversations over market research reports. A spreadsheet comparing SportsSync to Insta360 across 20 features would have told me the same thing. But it would have been abstract. Edu's one-liner was personal. I heard it.

Build slow if you have to. Listen fast.

The next phase of SportsSync is about serving the segment that actually has the problem. See you there.