Founders and startups

Your product live, without waiting for the team.

You have validated the idea, or started selling. What's missing is the product. I design it, build it and put it into production, from UX to deployment.

Is your V1 trying to do everything?

Tap a feature to move it from V1 to "later", and back again. The bar shows the weight of your first version.

V1

    Later

      Indicative relative weight: small, medium or large feature. The real estimate is done during scoping, on your product.

      What you have at the end.

      A product, not a mock-up. And everything a future team needs to take it over.

      • A live productOn your domain, with real user accounts, ready for your first customers.
      • Code versioned on GitHubReadable, organised, with the history of every decision.
      • A clean databaseSupabase: data, authentication, storage and documented access rules.
      • The integrations that matterPayments, emails, AI, third-party tools: connected and tested.
      • A V2 driven by usageWhat we build next depends on what your users do, not on a wish list.

      Why a Product Engineer, at this stage?

      Hiring a teamMonths of recruitment and a heavy payroll, before the first euro of revenue.
      Going through an agencySeveral contacts, back-and-forth, and a cycle designed for projects bigger than yours.
      A lone developerOften specialised: the product stops at the interface, or at the backend.
      A Product EngineerA single point of contact, from scoping to production, with AI as a speed multiplier. You decide fast, we iterate fast.

      What is the one thing your V1 has to prove?