Picking Up Where We Left Off

In Part 1, I used Claude to validate a SaaS idea: a cloud-based tool to overlay GPS telemetry onto cycling videos. Claude helped with competitive analysis, SWOT, market sizing, and a PRD — all in one session.

This time, I wanted to go deeper. Not more analysis — more perspective. I asked Claude to adopt three different roles and challenge me from angles I don't naturally think about as an engineer.

First: A Real Competitive Audit

A commenter on the first video made a great point: Claude can't browse the internet, so the competitive analysis was limited to what Claude already knew. The suggestion was to use a tool like Perplexity (which can search the web in real-time) to find actual competitors.

So I did. Perplexity surfaced a competitor I hadn't seen before: GPX Overlay, built by a solo developer in Poland. It takes a GPX file and generates transparent overlay frames that you then manually composite in your video editor.

The product works, but the user experience is brutal. You have to manually set frame rates, calculate time offsets, import hundreds of PNG frames into your editor, and pray the synchronization holds. The tutorial literally asks you to do math to match your video's frame rate to the overlay output.

Despite that friction, the creator had almost 1,000 YouTube views on the tutorial and was charging $49/year for the pro plan. Quick math: even with a modest 2% conversion rate on 3,000 monthly visitors, that's about 60 paying users — roughly $3,000/month from a side project with terrible UX.

The takeaway: if someone is making money with a painful workflow, there's room for a product that makes the same thing effortless.

Role 1: Claude as the Founder, Me as the VC

I asked Claude to pitch me on SportsSync as if it were the founder and I were a venture capitalist. The pitch was polished — maybe too polished. Claude invented metrics ("42% retention at 30 days in our private beta") that don't exist yet. But the structure was useful.

The interesting parts were the numbers Claude generated for the fundraising ask: $750,000 to fund 18 months of development and user acquisition, targeting 50,000 active users and 5,000 paying subscribers in year one.

I pushed back on the freemium model. Claude explained: the free tier gives full functionality but limits activity count (5/month). The constraint is volume, not features. Users who create more than 4 activities per month convert to paid at 3× the rate of casual users.

What I took away: the freemium gate should be on quantity, not capability. Let users experience the full product — then charge for more of it.

A Detour: The Two-Funnel Idea

While watching a video by Marlon (an indie hacker), I had an idea: what if SportsSync had two entry points?

Speed Overlay (free tool) — a simple, no-signup page where you upload a GPX file and a video, sync them, and see the overlay. You can view it but can't save or share it. This captures top-of-funnel traffic from people searching "speed overlay cycling video" or "GPX overlay tool."

SportsSync (the full platform) — where you save, share, customize, and export. The free tool becomes the funnel into the paid product.

Two domains, two funnels, one product underneath. The free tool does organic SEO work; the paid platform does the monetization.

Role 2: Claude as the Founder, Me as a Potential Customer

I asked Claude to sell me SportsSync as if I were a cyclist who just sat down next to them at a café. The conversation was natural and convincing. Three selling points stood out:

Ease of use — no desktop software, no manual editing, no frame rate calculations
Visual quality — attractive, customizable widgets that look professional
Community — sharing your ride with telemetry data is fundamentally different from sharing a raw video

Claude also demoed a hypothetical feature: route comparison. Ride the same route twice, and SportsSync shows you side-by-side telemetry — where you improved, where your heart rate spiked. Like Formula 1 timing overlays, but for your weekend ride.

Role 3: Claude as Product Manager

I asked Claude to build a roadmap and prioritize development phases. The proposed timeline was 16 weeks (4 months) with a team of 5-6 people. As a solo developer with AI tools, I think the MVP is closer to 2-3 weeks.

The disconnect is interesting: Claude was scoping for a traditional dev team. AI-assisted development compresses the timeline dramatically. The landing page alone — which Claude estimated at "week 1-4 of pre-production" — I built with Lovable in under 5 minutes during the same recording session.

The user acquisition strategy was more valuable than the timeline:

Reddit cycling communities (r/cycling, r/MTB)
Strava groups (150 initial users)
5 niche content creators as early ambassadors
Direct outreach to 20 tech-forward cycling clubs
A referral program where beta users can invite 5 friends

Total estimated cost for 550 beta users: ~€5,000. Customer acquisition cost: €8.70. With 14-month average retention at €10/month, the lifetime value ratio is 16:1.

Building the Landing Page with Lovable

To close the session, I asked Claude to write a prompt for Lovable (an AI UI builder) to generate the landing page. I pasted the prompt into Lovable, and in about 3 minutes it generated a complete landing page with:

Hero section with the "your video tells half the story" concept
How-it-works flow (connect → sync → share)
Feature showcase with telemetry widget mockups
Testimonials (fictional but well-written)
Pricing tiers
Email capture for the waitlist

It's not production-ready — the branding needs work, some sections need polish — but the structure is solid. What would have taken me two weeks of coding took 3 minutes of prompting.

What I Learned

Role-playing with AI reveals blind spots. As an engineer, I think about implementation. The VC conversation forced me to think about unit economics. The customer conversation forced me to think about the pitch. The PM conversation forced me to think about sequencing.

The competitive landscape is more nuanced than I expected. GPX Overlay proves there's demand even with terrible UX. Telemetry Overlay proves there's willingness to pay $183 for desktop software. Both validate the market from different angles.

AI compresses the pre-development phase to near-zero. Business plan, competitive analysis, PRD, roadmap, landing page — all done in two sessions totaling about 3 hours. The bottleneck is no longer planning; it's execution.

Next up: branding, the promotional video, and starting to build the actual product.

This is part 2 of the "Building SportsSync" developer journal — a series documenting the journey of building a SaaS product from idea to launch, using AI tools at every step. Follow the full series.

Using Claude as a VC, User Persona, and Product Manager