Skip to content
PA

In development

TRACKBORN

Own product · Founder & Product Manager · 2026 – present

Illustrative mock-up in TRACKBORN's black and yellow brand: a desktop app and a phone showing the teaser with the starting lights. Not a final product.

Side project

Role
Founder & Product Manager
Team
Solo
Period
2026 – present
Tools
LovableReactTypeScriptSupabaseClaude

In short

Problem

A real problem in the racing hobby community, studied first-hand.

What I did

Research, product definition, design and an AI-assisted build, working solo.

Result

A first version tested against real data, now in round two: deeper research and an MVP to take to market.

There isn't much I can share yet: TRACKBORN is still being built. What I can say is that it's grounded in deep research and design work, around a real problem I've studied first-hand.

I spotted the problem, ran an initial discovery, defined a hypothesis and built a first, small version. Early validation against real-world data showed the idea held up, so I'm now running deeper research, refining the product and shaping an MVP to take to market. I'm building it with AI and no-code tools, and the goal is a product that makes a real difference for hobby communities.

Progress

Round 1 · Testing the idea

  1. Problem

    spotted

    done

  2. Discovery

    initial

    done

  3. Hypothesis

    defined

    done

  4. First build

    small scope

    done

  5. Early validation

    with real data

    done

Round 2 · Building the MVP

  1. Deeper research

    & refinement

    in progress

  2. MVP

    to market

    next

My role

Founder and Product Manager, working solo: discovery, positioning, product definition, UX, data model and the build itself, with AI-assisted development.

What I've done so far

Competitive analysis to position the product against existing tools; a functional specification with a versioned data schema and test cases with acceptance criteria; two role-based experiences, one mobile-first and one desktop-first; privacy by design, with access rules on every table to meet GDPR; and automated in-app notifications. Every product decision is documented with its reasoning, so the vision stays consistent as the product grows.

How I'm approaching it

  • Saying no early

    I removed an early feature that competed with established tools, to focus the product where it could really stand out.

  • Validating before scaling

    The core logic is already validated against real-world data, with an exact match.

  • AI with judgement

    AI does what it does well, reading messy inputs; deterministic logic does what must be exact.

Brand

Built from the culture, not the logo

Before designing a single screen, I defined what TRACKBORN should feel like: the tension of the starting lights, the pride in a driver's history, the community that gathers around the track. The name carries that idea, and a personal tribute too.

That concept drives every choice: Race Black, Pit Yellow and Bodywork Silver, taken from the paddock; Anton for the energy of a race poster, DM Mono for the precision of a timing screen and Inter for clarity; and a checkered pattern used sparingly. The teaser landing puts it into practice: the lights go out, and something new is about to start.

TRACKBORN · teaser landing
The teaser landing: the name, the starting-lights sequence and “Muy pronto”. No form, no data collected.
Open the teaser (opens in a new tab)

Skills and tools

Product

  • Discovery
  • Competitive analysis
  • Positioning
  • Functional specs
  • Data modelling
  • Acceptance criteria
  • AI product design
  • Privacy by design

Build

  • Lovable
  • React
  • TypeScript
  • Supabase
  • Vercel
  • GitHub
  • Claude