Every side project I build hits the same wall. The code works, the idea is fine, and then the interface makes it look unfinished. No designer, no budget for one.

So I'm curious how other solo builders actually handle this:

• What's your design process when there's no designer? Component libraries, copying layouts you like, AI tools, something else?

• How do you find out the UX is bad in the first place? I can tell when something feels off, but I can't articulate why so I end up changing colors instead of fixing the real problem.

Curious what your setup looks like.

I want to share something counterintuitive that took me two years to figure out.

Like most founders, I was obsessed with user happiness. Did they like the product? Were they satisfied? Did they leave a good review? I'd send NPS surveys, add "how are you feeling?" prompts, respond to every bit of feedback with gratitude.

But churn stayed stubbornly high. People weren't unhappy they just weren't using the product. They'd sign up, poke around, and drift away.

Then I accidentally noticed something. The users who stuck around weren't the ones who said they loved the product. They were the ones who had figured out the one specific thing the product was actually good at. They weren't confused anymore. They had clicked with the core value.

Weird domain names are the unsung heroes of the internet. I used to own pollinate dot me. Basically I was drunk and thought a dating app based on people that liked to garden was a good idea

I decided to do an experiment. For 90 days, I logged every hour of work in a spreadsheet. Not just "worked on product" but exactly what I did. Every task, every meeting, every rabbit hole.

Here's the breakdown:

• Product development: 31% (I thought it was way more)

• Admin/email/ops: 24% (this one hurt to see)

• "Research" (reading Twitter, watching YouTube, "staying informed"): 18%

• Actual customer conversations: 9%

• Marketing/distribution: 7%

• Fixing things I broke: 6%

• Staring at the screen feeling overwhelmed: 5%

The number that gutted me was the 18% I spent on "research." I was consuming content about building instead of actually building. I was reading threads like this one instead of talking to users.

I can handle the product not working. I can handle the bugs, the churn, the Stripe notifications that never come.

What I can't handle is the silence from people who used to care.

When I first started building, I had a small group of friends and early users who were genuinely excited. They'd reply to my updates. They'd test things. They'd say "this is cool, keep going." That energy carried me through the hard weeks.

Now? Nothing. Not angry messages. Not "I stopped using this." Just... quiet. They moved on and didn't tell me.

To fund early work on my iOS tracker, I offered a $19.99 lifetime pass at launch. Made $1,200 in two days, which was great for initial cash flow.

The downside is that those early buyers became my most active users and requested the most features, but they ll never pay again. Meanwhile, recurring subscription growth slowed down. Now I m maintaining the app for my core users without ongoing revenue from them to cover backend costs.

If you offered a lifetime deal at launch, how did you shift toward a sustainable model later?

People always say they want simple products. Bloat is a big reason people dislike products and migrate away from existing tools. But I don't think that bloat comes from having too many features. Instead, it's mostly a UI/IA problem.

This is something we think about a lot at @Basedash. Analytics and BI can get complicated quickly: permissions, SQL, charts, dashboards, filters, joins, data sources, teams, sharing, alerts, and so on. We can t remove all of that complexity, because real teams eventually need it. Instead, we're trying to figure out how/when to reveal that complexity. Filters only appear if you ask the AI. Access controls can get super fine-grained, but only if you start inviting more teammates.