Doing one of these because I get more from reading what others are building than from any newsletter.

I'll start.

Genuine question not a trap.

I've been building browser-based tools and the one thing users tell me is:

"I don't trust random free tools with my files"

And honestly? Fair.

Hey PH community

Tomorrow I'm launching Triply.now and I wanted to share the story behind it before the big day.

I'm Raquel, a self-taught solo developer based in the Netherlands. I built Triply entirely alone Flutter, Python/Flask, Claude AI, Supabase, Stripe, Vercel, Render. No co-founder, no funding, no team.

The idea came from my friends and my own travel fails. A friend showed up to a temple in Morocco in the wrong outfit. Another one didn't know tipping in Japan is considered rude. I had the wrong adapter in Switzerland and I once brought my hair dryer to Boston and couldn't use it European voltage, American outlets. Triply would have told me that before I packed. These aren't rare every traveler has been there.

We built a sales assistant tool called ReachRobin, and here is our latest update: You can run it directly from Claude. We think it's pretty good but we've been staring at it too long. 

So we're doing something bold: we're handing over full access and asking you to roast it. UI/UX, pricing, positioning, features, whatever: the harsher (and more useful) your feedback is, the better. But not the name, we're stuck with it for now lol.

We've been live for a while but recently shipped a meaningful update across the marketplace, governance layer.

Before we push harder on distribution, want honest reads from this community.

A few specific things I'd appreciate feedback on:

- Does the messaging on the homepage actually explain what we do in 10 seconds?

We re all builders here, which usually means at some point we looked at something clunky, slow, or frustrating and thought, there has to be a better way. Most products don t start with a grand vision; they start with irritation, curiosity, or firsthand pain.

I d love to learn more about how others here have navigated that journey:

How did you uncover the problem you decided to work on?
What signals told you this problem was worth solving?
How did you validate (if at all) whether people would actually pay for a solution?
Has your product stayed true to the original problem, or did it evolve into something different?
What surprised you the most along the way?

Most interview prep tools are built for one moment: interview in 2 weeks. You cram. You close the tab. Six months later, you panic again.

The problem isn't the tools. It's the model.

Cramming 3 days before a loop is like going to the gym 3 days before a marathon. The work should've happened months ago.

DailyKnack is the daily habit layer.

For context: I freelanced for about 4 to 5 years building and digitizing small businesses. Here's the pattern that stuck with me: the build was never the hard part. It was everything after. I'd ship a solid site, hand it over, and then the owner would run into the stuff no website can handle on its own: "it got slow when my flash sale hit," "I need to move to a bigger server," "how do I add SSL," "is my data even backed up?" None of that is about the site being bad. It's that running a server is ongoing work, and a non-technical owner simply can't do it. So every time their business grew or had a busy day, they had to hire me (or someone) again. They didn't want a developer on retainer, they just wanted their thing online and stable.

So I built Cloudnan: a server management platform you operate by talking to it. Connect your own VPS or buy one in-app, then deploy from GitHub or a container registry, run WordPress and databases, manage domains, monitoring, backups, and security. The AI does the actual server work, you just say what you want in plain language. It's not AI-only, it's a full platform with the AI on top.