u/Dearokok

Hey everyone,

I’ve been helping out with HelloPartner.ai recently while they work on Sal, their AI assistant for Mac users, and we’ve reached the stage where outside feedback is becoming really important.

One thing that’s surprised me during early conversations is how often people bring up privacy before anything else. I expected most feedback to focus on features or AI quality, but a lot of users immediately ask where conversations go, whether files leave the device, and how much data gets collected behind the scenes.

Because of that, the team built Sal to run locally on the Mac instead of depending heavily on cloud processing. It definitely makes certain parts of development harder, but users seem noticeably more comfortable once they realize their conversations and files stay on their own machine.

Right now we’re mostly trying to learn how people actually feel using something like this in real-world workflows.

I’d genuinely love to hear thoughts from people here who regularly test early products:
does local/private AI actually matter to you when using these tools day to day, or do most users still mainly care about convenience and output quality?

Also curious what usually makes you keep using an AI product after the first few days versus uninstalling it completely.

I’ve been seeing more no-code founders lately experimenting outside of just software.

A friend of mine started with a small no-code tool, then later added simple physical products for his audience and said the sourcing side became way harder than actually building the SaaS itself.

Finding suppliers, dealing with MOQs, shipping, quality checks… it’s honestly a completely different world.

We recently started looking around platforms like Made-in-China.com to better understandhow people are handling supplier sourcing without needing massive budgets upfront.

Made me curious if other people here are trying something similar too.

Are you staying fully software-focused, or have you thought about adding physical products around your SaaS at some point?

I’ve been helping out around HelloPartner.ai recently while they work on Sal, their AI assistant for Mac users, and one thing keeps surprising me whenever people talk about their AI workflows.

People seem way more aware of what they’re feeding into AI tools now.

A while ago, most conversations felt centered around which model was smartest or which app had the best features. Lately though, people bring up completely different concerns first. They ask where conversations are stored, whether screenshots get uploaded somewhere, and who can actually access the information they share with these tools.

What caught me off guard is how much calmer some users become once they hear the assistant runs locally on their Mac instead of depending heavily on cloud processing. A few people testing it said they felt more comfortable using AI regularly once they knew personal notes, files, and random work conversations weren’t constantly being pushed to external servers.

At the same time, building workflows this way feels harder than I expected. Most modern AI products rely heavily on cloud infrastructure because it makes everything smoother behind the scenes. Once you move more things locally, you lose a lot of convenience from the development side too.

Still, it feels like trust is slowly becoming part of the workflow experience itself now, especially for people using AI every single day for work.

Curious whether other people here are noticing the same shift lately or if this is still mostly a niche group paying attention to it.

I’ve been helping out with Sal by HelloPartner.com recently, and something keeps catching me off guard during conversations with users.

People care way more about where their data goes than I expected.

I thought most conversations would be about AI quality, features, speed, or integrations. Instead, people keep asking whether their chats are stored somewhere, if screenshots leave their device, or who can access their files.

The product runs locally on Mac, so everything stays on the user’s machine, and for some reason that changes the entire tone of the conversation. You can almost feel people relax once they realize their data isn’t constantly being pushed to external servers.

What’s funny is that building things this way creates a lot more work behind the scenes. You lose a bunch of visibility that most SaaS products normally rely on. Even simple things like understanding how users interact with features becomes harder when you intentionally avoid tracking everything.

But at the same time, it feels like trust is becoming part of the product itself now.

I genuinely can’t tell if this is still mostly a tech/privacy crowd thing or if regular users are starting to think differently about AI products in general.

Anyone else building SaaS products noticing the same shift lately?

I’ve been spending a lot of time recently helping the team behind Sal by HelloPartner, an AI assistant for Mac users, and something unexpected keeps happening during conversations with early users.

People barely ask about features at first anymore.

Instead, they immediately ask where their data goes, whether conversations are stored somewhere, or if screenshots and files ever leave their computer. A year ago, I feel like most people mainly cared about output quality and speed. Now the tone feels completely different.

What surprised me most is how strongly some users react once they realize Sal runs locally on their Mac instead of depending heavily on cloud processing. A few people told us they stopped using certain AI tools because they became uncomfortable uploading personal notes, work documents, or client conversations to external servers.

Building software this way honestly feels harder from the SaaS side too. When you intentionally avoid telemetry and reduce cloud dependency, you lose a lot of visibility that most SaaS companies rely on. Even debugging becomes more complicated because you’re choosing to collect far less user data.

But weirdly, that tradeoff seems to increase trust.

I still can’t tell whether this is mainly a privacy-focused tech audience or if average users are genuinely starting to think differently about AI products now.

Curious whether other SaaS founders here are noticing the same shift lately.

Building the product felt exciting. Even the stressful parts were still motivating because it felt like progress every day.

What caught me off guard was everything that comes after launch.

You finally ship something you’re proud of, then suddenly you’re expected to constantly market it, publish content, work on SEO, stay active online, explain the product everywhere, and somehow keep all of that consistent while still improving the product itself.

For a while we tried doing everything manually and honestly it became exhausting fast. Some weeks we were spending more time planning content and trying to stay visible online than actually working on the product.

That cycle honestly became one of the reasons we started building SEO Rocket internally. Not because we wanted to remove the human side of marketing, but because we got tired of how repetitive the operational side of SEO had become for small teams.

I’m curious if other people building no-code or lean SaaS products have felt this too.

What’s been harder for you personally: building the product, or consistently growing it after launch?

Building the product was honestly the fun part.

The harder part came after launch when we realized how much ongoing effort it takes just to stay visible online consistently. Especially with SEO and content.

At first we tried handling everything manually. Writing articles, researching keywords, updating pages, planning content calendars… and after a while it started feeling like we were spending more time feeding the marketing machine than improving the actual product.

That’s a big part of why we started building SEO Rocket internally. We wanted to simplify the repetitive side of SEO so smaller teams could keep momentum going without needing a huge content operation behind them.

What’s interesting is that no-code tools made building products dramatically faster, but growth still feels very manual for a lot of founders.

Curious if other no-code SaaS builders here feel the same way.

What part of growth or marketing has been the most difficult thing for you to keep consistent after launch?

When we first started building our SaaS, I thought most of the pressure would come from development. I expected bugs, late nights, feature requests, all of that.

What I didn’t expect was how exhausting it would be trying to maintain steady growth after launch.

SEO especially became frustrating for us. Not because we didn’t understand it, but because the amount of work behind staying consistent started becoming difficult to manage alongside everything else. You publish for a while, traffic slowly starts moving, then something pulls your attention away for a few weeks and suddenly the momentum disappears again.

I started realizing that a lot of founders probably aren’t failing because they have bad products or bad ideas. They’re just overwhelmed trying to keep every growth channel active at the same time.

That’s honestly part of what led us to build SEO Rocket internally. We were trying to reduce some of the repetitive workload that kept slowing us down so we could focus more on the bigger picture instead of constantly chasing content schedules.

Still figuring things out as we go, but it completely changed the way I think about SaaS growth.

Curious if other founders here have had a similar experience.

What part of growing your SaaS drains the most energy for you long term?

The more time I spend around SEO and content workflows, the more I realize most businesses already understand what they’re supposed to do.

Publish consistently. Build authority around topics. Keep updating content. Stay active long enough for momentum to build.

The real problem is maintaining all of that without it turning into a full-time machine that slowly drains your energy.

I’ve seen businesses start with a lot of excitement around SEO and then quietly stop publishing a few months later because the workload just became too much to sustain consistently.

That frustration is actually what pushed us to start working on SEO Rocket internally. Not because we think automation replaces strategy, but because so much of SEO today feels operational instead of creative.

Still figuring things out as we go, but it completely changed the way I think about scaling content.

Curious what other people here think.

What’s the part of SEO/content work you personally get tired of dealing with the fastest?