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

Pauline Clavelloux, founder of IACrea

Pauline Clavelloux always wanted to build a business, but she couldn't quite get herself to start. Then, after nearly ten years at IBM, she took the leap.

She had a few failures and an exit, and she now has a portfolio of SaaS products bringing in over $100k ARR.

Here's Pauline on how she did it. 👇

Failures and exits

I’m Pauline Clavelloux, a French tech entrepreneur. I worked for 9.5 years at IBM before becoming a full-time indie hacker.

I started indie hacking during COVID and built several SaaS products from scratch; some failed, one sold, and four others serve clients:

  • IACrea, an AI-powered real estate marketing suite that transforms property photos into virtually staged images, videos, and ready-to-post social media content.

  • Feedbask, a customer feedback and support widget with different actionable modules (live chat, feedback collection, bug reports, feature requests ...) directly inside their app.

  • Subclip, a web app that automatically adds subtitles to videos, translates and dubs into other languages, etc.

  • Refindie, an affiliate management tool for SaaS creators without upfront cost.

I reached €100K+ ARR back in 2024, and revenue increased in 2025.

IACrea homepage

The first taste of indie hacking

I’ve always wanted to start a business, ever since I was a kid.

I constantly had new ideas, but before COVID, I never started anything. The main reason was fear: I didn’t know where to start, and the administrative side of running a business felt overwhelming.

During COVID, I saw some friends launching their own online projects. They already knew how to handle the business setup, and that gave me the push I needed. I teamed up with a friend and built my first product: a crypto trading bot. It was a complete business failure... but also a personal success, because it worked and traded automatically for me!

I eventually stopped it, but that experience changed everything.

I realized how much I love building things, working for myself, and having the freedom to work from anywhere. That sense of independence is something I never felt while working a 9-to-5 job. I love working from home.

A lean mindset

When I built my first real product, I had a technical background in web development, but I learned how to run a business through experience.

The first versions of my SaaS products were extremely simple. I didn’t focus on design or scalability; I just wanted to see if people would use it.

For IACrea, for instance, the very first version only supported uploading one photo at a time and returning one AI-generated image. But it was enough to get the first paying users.

I keep my process lean:

  • Build fast, even if it’s ugly.

  • Launch early, get feedback.

  • Improve only what matters.

  • Quit if no traction.

That mindset helped me ship multiple products quickly. Each one taught me something new about tech, about users, and about what drives revenue.

A simple stack for every project

My tech stack is quite simple:

  • Frontend + Backend: Next.js + Tailwind CSS

  • Auth + Database + Storage: Supabase

  • Payments: Stripe mainly, and Polar for Subclip

  • Hosting: Vercel & AWSGrowing four products

Building is easy, distribution is hard

Building the product was the easy part; making people aware of its existence was hard.

I tested many approaches: social media, video content, SEO, physical events, direct conversations with users... and over time, I learned that distribution is key.

For IACrea, we initially grew by staying close to the market: Facebook groups, in-person networking events, and partnerships with industry players. Direct conversations and trust were crucial early on.

For Feedbask, Refindie, and Subclip, we have mostly driven growth through social media. Regularly posting about the product, sharing real use cases, and building in public helped attract early users who understood the value.

Overall, adapting the distribution strategy to each product and audience made the biggest difference. Each channel compounds differently over time, and what works for a SaaS might not work for another SaaS.

I'll also say that building in public is extremely helpful. Sharing what I’m working on, what’s not working, and why lets me get early feedback and stay close to real user needs.

Solve your own problems

Start by solving a real problem you personally experience; it makes the problem clearer and the motivation stronger.

For example, customers kept asking the same questions, and answering them manually was time-consuming and unproductive. Frustration led me to build Feedbask: a centralized inbox accessible to the whole team that included context. Soon, it will also pre-fill replies based on past conversations to avoid rewriting the same answers repeatedly. Can't wait for that!

Turning internal pain points into a product was a huge advantage. When you build something you personally need, you know what's needed, and what's not working well with other solutions. And if you fail to monetize it, at least it's useful to you!

Parting advice

Here's my advice:

  • Don’t wait to be “ready” or to get the perfect product to share your work.

  • Build in public early, talk to users as soon as possible, and let feedback guide the product. People especially love to see the journey and your product evolve.

  • Systematize repetitive tasks instead of handling them manually.

  • Focus on learning fast rather than trying to get everything perfect.

  • Be resilient, and be prepared to fail. Founders who are successful on their first attempt are VERY rare. You see many successful people online, but usually, it took them a few years to get revenue.

What's next?

My main goal is to keep building useful, simple products that solve real problems for the real estate area and business owners, the two audiences I can reach. I want to grow all my SaaS sustainably to at least $30k MRR each.

And I want to continue sharing my journey openly, building in public, and showing that you don’t need a huge team or massive funding to build profitable, meaningful products.

Lastly, I recently started creating videos (find my YouTube profile here) and I'd like to growth that channel

You can follow along on my newsletter and on social media: X profile, YouTube, and LinkedIn. And here's my portfolio.

Indie Hackers Newsletter: Subscribe to get the latest stories, trends, and insights for indie hackers in your inbox 3x/week.

About the Author

Photo of James Fleischmann James Fleischmann

I've been writing for Indie Hackers for the better part of a decade. In that time, I've interviewed hundreds of startup founders about their wins, losses, and lessons. I'm also the cofounder of dbrief (AI interview assistant) and LoomFlows (customer feedback via Loom). And I write two newsletters: SaaS Watch (micro-SaaS acquisition opportunities) and Ancient Beat (archaeo/anthro news).

Support This Post

19

Leave a Comment

  1. 1

    This resonates hard. Pauline's story of going from failures to $100k+ ARR is exactly where I am right now.

    Currently building 3 AI SaaS products after similar false starts. The key insight I'm taking from her: ship quickly, iterate based on feedback, don't overthink.

    I built 3 products in 48 hours instead of perfecting one over months. Early feedback shows the portfolio approach works—different audiences, different pain points.

    Revenue model is recurring subscriptions ($97-297/mo per product). Still in testing phase with early users, but the velocity feels right.

    Questions for others building multiple products:

    - How do you balance marketing across 3 products simultaneously?

    - Did you start with one product then expand, or launch multiple at once?

    - What's your unit economics at early stage?

    Great read. Thanks for sharing the unfiltered journey, Pauline.

  2. 3

    Very cool! I am starting a small business and would appreciate feedback on how to get it off the ground!

  3. 2

    This is a great reminder that the journey is rarely linear. What stood out most to me wasn’t the €100k ARR, but the sequence: failures → learning → lean execution → distribution.

    The “build fast, quit if no traction” mindset paired with solving personal pain points feels like the real advantage here. Also refreshing to see how differently distribution worked for each product — there’s no single playbook, just constant adaptation.

    Really solid example of how consistency and resilience compound over time.

  4. 2

    A lean mindset isn’t about cutting corners—it’s about respecting your energy and attention. Build the smallest version that teaches you something real, listen to users, and let clarity emerge through action, not overthinking. 🌿

  5. 2

    Need a Fast and Flexible Loan?

    We offer loans for personal needs, investments, business expansion, home renovations, and more! With amounts from $10,000 to $5,000,000 and a low 2% interest rate, we're here to help you reach your goals.

    Loan Options Include:

    Personal & Business Loans

    Real Estate & Investment Loans

    House Renovation & Car Loans

    Debt Consolidation & Student Loans

    For fast service, / The post was too long and was therefore cut off by the system.
    For fast service, email us at [email protected]
    with your loan details. We'll respond quickly and help you move forward!

  6. 2

    Strong example of long-term product building especially valuable given how few women we still see in indie SaaS.

  7. 2

    Pauline, your journey from a decade at IBM to a $100k ARR portfolio is a masterclass in escaping what I call the 'Hierarchy of the damned', that corporate structure where potential goes to die in exchange for security.

    As a Mentor and author of 'Startup Inferno', I’ve mapped the 9 circles of entrepreneurial failure, and I see your success as a deliberate climb out of the Vestibule of indecision. Most people spend their lives 'wanting' to start; you actually chose to burn the boats.

    A few 'Mentor-level' observations on your path:

    1. The Validation Grill: your approach to IACrea (building the 'ugly' version first) is exactly how you survive the Circle of Lust. You didn't fall in love with a complex vision; you fell in love with a solved problem. In 2026, founders who prioritize feedback over 'perfect code' are the only ones who reach the purgatory of profit.

    2. The Distribution trap: you hit the nail on the head, building is technical pride, distribution is commercial humility. Many founders get stuck in the Limbo of Unseen Products because they refuse to do 'things that don't scale' like you did with Facebook groups and manual outreach.

    3. A Word of Caution on the 'Circle of Fragmentation': Managing four distinct SaaS products is a feat of strength, but as a Mentor, I have to warn you about the split focus. Diversification is a shield, but extreme focus is a sword. Be careful not to let the maintenance of four 'Infernos' prevent you from scaling one into a true $1M ARR Paradise.

    Your transition from 'Internal Pain' to 'Product Solution' (Feedbask) is the ultimate Customer Impact Map. You didn't guess the market; you lived the market.

    Keep building in public, Pauline. You are showing people that the exit from the corporate Inferno isn't a leap of faith, it's a series of validated steps.

    Respect for the hustle.


  8. 2

    Great post, appreciate the honesty about the hardships of distribution.

  9. 1

    This was such an inspiring and practical story. I love how you didn’t wait for perfect conditions, you shipped early, learned fast, and let real users guide you. The honesty about distribution being the hard part really hits home; too many founders focus only on building. Thanks for sharing not just the wins, but the mindset and steps that made it possible. Really fascinating read!

  10. 1

    Her face turned red when she received the news that the company had to let her go. ~

    In the beginning, I wrongly thought that a good product would sooner or later get noticed. What I discovered instead is a separate skill distribution you must practice just as deliberately.

    Your process break down on the stack is valuable since it shows repeatability not magic.

    Are you now biased toward ideas that have distribution baked in? Or are you still willing to brute-force distribution if the problem feels strong enough?