7
16 Comments

We designed a $1M style app for a client… Now it runs our whole team.

We started this project with one goal:
build something simple, clear, and easy for real people to use.

So before touching the design, we did the work that actually matters:

  • real user research
  • task based UX flows
  • testing simple versions
  • removing screens that didn’t help

Nothing fancy.
Just honest UX work based on what people actually do.

When we finished the design, the client launched it.
And here’s the part that feels different:

We now use this app inside our agency for our daily work.

Not because we had to.
But because it genuinely helps.

For me, that’s the real win.
Not awards. Not likes.
But using something you created because it actually solves a problem.

posted to Icon for group Building in Public
Building in Public
on November 20, 2025
  1. 1

    That’s a strong signal — internal tools usually earn adoption only when they remove real friction.

    What’s the one behavior that convinced you this was worth relying on daily — fewer handoffs, faster decisions, or something else?

  2. 1

    Great post. I’m currently building an app myself and your is looks fine

  3. 1

    Love this. Most people jump straight into colors and components and forget the boring stuff that actually makes products usable. The fact that you ended up using the app yourselves is the real proof it landed — nobody forces themselves to use something that doesn’t make their day easier. That’s the kind of validation no award can touch.

    1. 1

      I love to work like this more and more 🤨

  4. 1

    Impressive turnaround—building a high-value app for a client and then adopting it internally shows strong design alignment. When a tool scales from one project to your entire team, you know it truly works.

  5. 1

    We built a $1M-style app for a client, and its impact exceeded expectations. Today, the app has become central to our operations, streamlining workflows, improving efficiency, and managing key processes across our team. What started as a client project now drives our internal productivity and daily operations.

  6. 1

    It’s amazing when a client project evolves into a tool that powers your own team. Shows how design and development can create value beyond the original scope.”

    1. 1

      True, if your team can align properly, it will be blast for sure.

  7. 1

    Impressive! Turning a client project into a tool that runs your entire team shows smart design, scalability, and real-world impact—truly a win-win for both you and the client

    1. 1

      Exactly, client also supporting us continiously.

  8. 1

    Love this approach. Starting with real user behavior instead of jumping straight into visuals is what actually leads to products people want to use. The fact that your own team adopted it internally says more than any case study or award could.

  9. 1

    Love this. Congrats on building something that actually helps the team day to day.

    1. 1

      Thank you. I believe this is the actual win for us.

Trending on Indie Hackers
Why Indie Founders Fail: The Uncomfortable Truths Beyond "Build in Public" User Avatar 139 comments Your AI Product Is Not A Real Business User Avatar 87 comments The Clarity Trap: Why “Pretty” Pages Kill Profits (And What To Do Instead) User Avatar 34 comments I built an enterprise AI chatbot platform solo — 6 microservices, 7 channels, and Claude Code as my co-developer User Avatar 29 comments Stop Building Features: Why 80% of Your Roadmap is a Waste of Time User Avatar 26 comments I got let go, spent 18 months building a productivity app, and now I'm taking it to Kickstarter User Avatar 18 comments