Bastien Renard's profile on Product Hunt

About

Twenty-five years in luxury fashion and sportswear have taught me that brand is a business lever, not a marketing function. The difference between a brand people admire and one they belong to is how the brand, product, distribution and cultural connections are assembled into something coherent, authentic and inspiring. I've run global businesses and early-stage ventures, managed P&Ls from the ground up, and led large teams across Europe, the US and Asia through product reinvention, channel transformation and brand repositioning. The work I find most meaningful sits at the inflection point: where a brand has genuine equity but the organisation hasn't yet caught up with its potential.

Badges

Tastemaker

Gone streaking

Forums

p/runevr

•

3h ago

🤝Let’s get to know each other better

I know there s a p/introduce-yourself topic here on PH, but honestly, it s hard to meet everyone there.

So let s do it here.

Who are you?

What are you working on?

p/prodshort

•

1d ago

When should founders stop building and start selling?

We all know someone who just keeps building: One more feature, One more improvement, One more thing to fix before starting sales.

And to be fair, it s easy to fall into that loop. Building feels productive, and there s always something that could be better.
But at some point, you have to ask yourself: are you really improving the product or just delaying sales?

From your experience:
When is the right time to stop building and start selling?

•

1d ago

Turns out most APIs don't actually have an "overdue" status

Working on a finance side AI tool, and one thing that surprised me: Stripe's invoice object doesn't have an "overdue" status at all. It only tells you "open" or "paid" overdue is something you have to derive yourself by checking if it's open and past its due date. If you build against the API assuming "overdue" is a real field, you'll confidently tell someone nothing is overdue when their business is full of unpaid invoices.

Feels like a small thing, but it's the kind of gap that's easy to miss until it actually costs someone money. Made me a lot more paranoid about assuming any third party API's status fields mean what they sound like they mean.

Curious if others building against Stripe/QuickBooks/accounting APIs have hit similar "the field name lies to you" surprises, feels like a common trap.