Day 11 with Clowd — the feedback that surprised me most.
I expected early users to respond to features. Version history. Custom domains. The download toggle. Those are the things I spent the most time building and explaining.
Instead, the feedback that hit hardest came from a completely different direction.
A restaurant owner: "I've saved more money on printing than on your subscription."
A designer: "I haven't heard 'which version is this?' in weeks."
A job seeker: "I updated my resume three times and never re-sent it to anyone."
None of these mention a feature. All of them describe the absence of a problem.
This has changed how I think about positioning Clowd. I've been leading with what the product does. I should have been leading with what users stop doing.
The copy on the homepage talks about permanent links and version history. What it should probably say more clearly is: "You will never re-send a file again."
That's the outcome. Everything else is the mechanism.
Week 2 focus: rewrite more of the marketing around outcomes, not features. Test whether "you'll never re-send a file again" converts better than "one permanent link, always current."
Sharing this because I think the pattern — outcome-first vs feature-first — is one of the most common early-stage mistakes I see in SaaS positioning, and I walked straight into it myself.
