book
www.indiehackers.com

Taking the leap and building a 6-figure-ARR portfolio

by Pauline Clavelloux

Read Original
arrbuilding-in-publiccase-studydistributionindie-hackerslean-startupmrrportfolio-approachproduct-strategy

TL;DR: After 9.5 years at IBM, Pauline Clavelloux became a full-time indie hacker building 4 SaaS products: IACrea (AI real estate marketing), Feedbask (customer feedback widget), Subclip (video subtitles), and Refindie (affiliate management). She reached €100k+ ARR in 2024 by following a lean mindset: build fast even if ugly, launch early, improve only what matters, quit if no traction. Distribution proved harder than building - she adapted strategies per product: Facebook groups and in-person networking for IACrea, social media and building in public for others. Key insight: solve your own problems (Feedbask was built from her own customer support frustrations). Uses simple stack (Next.js, Supabase, Stripe, Vercel) across all products for speed.

Key Insights

  • Lean Mindset: Build fast even if ugly, launch early, improve only what matters, quit if no traction
  • Portfolio Approach: Building multiple products lets the market pick the winner instead of you guessing
  • Solve Your Own Problems: Makes problem clearer and motivation stronger (Feedbask from support frustration)
  • Distribution is Hard: Making people aware is harder than building - adapt strategy per product
  • Simple Stack: Use consistent tech stack (Next.js, Supabase, Stripe) across all products for speed

Actionable Takeaways

  • Start with extremely simple first version - don't focus on design or scalability
  • Build fast even if ugly - perfection is the enemy of shipping
  • Launch early and get feedback - improve only what matters
  • Quit if no traction - don't waste time on products that don't work
  • Solve your own problems first - you'll know what's needed and what's broken
  • For B2B/real estate: use Facebook groups, in-person networking, industry partnerships
  • For SaaS tools: social media, share use cases, build in public
  • Build in public to get early feedback and stay close to users
  • Use simple consistent tech stack across all projects
  • Don't wait to be "ready" - start building and sharing early
  • Be prepared to fail - success on first attempt is very rare

Principles Validated (30)

Distribution