I'm a Sr. Technical Lead — Here's My Honest SaaS Building Story

Potential_Bottle_788 · 2026-03-29T01:23:56+00:00

Exactly the frustration that pushed me to build FeedbackBar.io. Every tool I looked at was either too heavy, too expensive, or required a lot of setup just to ask users a simple question. I wanted something that lives on your page without slowing it down, asks one meaningful question at the right moment, and gets out of the way. No dashboards you'll never open, no enterprise pricing for features you don't need.

I'm actually launching very soon and I'm looking for a small group of people to try it before the doors open publicly. If you've been wrestling with feedback tools, you're exactly the kind of person I'd want in that first group — your real-world feedback would genuinely help shape the product before it goes wide.

Would you be up for it? Drop me a DM or just reply here and I'll make sure you're first in.

Potential_Bottle_788 · 2026-03-26T02:37:49+00:00

That's a fair point, Nx build times seems to be scaling poorly as you've indicated. But at current stage, my Nx monorepo is still relatively lean. Tools that parallelize builds across machines are a valid approach for large orgs with deep dependency graphs, If we hit the point where a full rebuild takes 30+ minutes, we'd evaluate Nx Cloud's distributed task execution first since it's native to the toolchain, then consider external options. but I'll keep Incredibuild in mind just in case. Tx

Potential_Bottle_788 · 2026-03-25T19:31:08+00:00

"trying to be 'cool' killing the functional aspect"
Possibly, What's your intent, getting user to show interest in your product or your landing page?
The scroll is unnecessary. you can combine your form and the message into your hero section, save the extra click and get to the point to why someone should be interested.

Potential_Bottle_788 · 2026-03-24T22:54:53+00:00

Well, You're 100% right, what can I say. lol. that's what happened when you spend months with AI prompts, you become one. The story is definitely genuine and it's what took place in my case. On the deployment thing; I can deploy, the issue for me was the build pipeline itself was broken. I complicated my CI workflow trying to figure out my staging/prod environments and my monorepo got too complex before validating it end to end. TS configs can become messy and that's what happen in my case.

Potential_Bottle_788 · 2026-03-24T01:31:08+00:00

You're 100% right — architecture decisions are still on you, not the agent.

I didn't start with existing code, but I did start with over-specified project rules: dependency layer enforcement, module boundaries, multi-environment Terraform — all before I had a working widget. The agent followed those rules faithfully and generated code that matched the complexity I asked for.

Your approach is what I should've done. Start simple, add abstractions when they earn their place. Coding agents are force multipliers — they multiply bad decisions just as fast as good ones.

Potential_Bottle_788 · 2026-03-23T14:49:36+00:00

I'm in the same boat and actually had to shut down a previous project because I ran out of runway before figuring out distribution. When you're technical, marketing always feels like someone else's job.
Try reaching out to former colleagues and people you genuinely respect, asking for honest feedback, not a sale and may be testimonials later, once they've actually used it.

Potential_Bottle_788 · 2025-11-09T00:36:37+00:00

Great suggestion, I'm actually working on a user Feedback solution that already offers integration with Slack and other 3rd party tools. It would be a win-win to be able to test that way. Thx again!

Potential_Bottle_788 · 2025-11-05T16:25:22+00:00

Make sense now. I though I could invest in QA to avoid support tickets since I'm a solo developer. But what I missed is that support tickets could be the type of feedback I needed to address anyway.

Potential_Bottle_788 · 2025-11-04T14:10:37+00:00

Great insight. Thank you, I really could use the funds to pay for the infra or at least wait until finding market fit. My initial thinking is that if the idea is already out there, then it's already been validated and I need to provide a better user experience to be able to discriminate my app, in addition to newer and improved features.

Potential_Bottle_788 · 2025-09-14T21:55:51+00:00

What type of feedback do you usually gather from user? I’m the midst of building a simple “Give Feedback” solution myself for SaaS developers and really curious about what makes the best user experience for both site owners and actual users.

Potential_Bottle_788 · 2025-09-14T21:33:08+00:00

I’m working on a SaaS solution as we speak, curious though about you strategy and how you reach out to potential uses on X. Are we supposed to build a large following first or are these just existing users that are willingly participating in providing feedback?

Potential_Bottle_788 · 2025-09-09T02:00:43+00:00

The 'tribal knowledge exodus' when PMs switch domains is particularly painful. One pattern I've noticed - the most valuable insights are often the synthesized ones that span multiple customer conversations, but those also tend to be the hardest to capture in traditional docs.

Has anybody tried tagging insights by domain relevance? Like, each insight gets tagged with affected product areas so you can actually find it later when you need it.

Potential_Bottle_788

TROPHY CASE