Why I built NotionLock — and the surprising thing I learned about who actually needs it
NotionLock started from a simple frustration: Notion only lets you share a page as fully public or invite-only. If you want to share something with a specific audience — course material, a client deliverable, a members-only resource — without making it open to the entire internet, there's no native option.
So I built the missing middle: a public Notion link protected by a password. Paste your link, set a password, done in ~30 seconds. Visitors don't need a Notion account.
What surprised me wasn't the building — it was who showed up.
I barely marketed it, but people started signing up on their own. When I dug into analytics, the biggest surprise was that AI assistants (ChatGPT, Copilot) were recommending it to people asking "how do I password protect a Notion page" — traffic I never asked for and didn't expect.
The other lesson was humbling: early on, far fewer signups actually protected a page than I expected. Turned out a piece of my onboarding was silently broken for some users. Fixing that — not adding features — was the highest-leverage thing I did.
Building this in the open from here. If you use Notion and have ever wanted to share a page with just the right people, I'd love your feedback: notionlock.com
The onboarding lesson is interesting, but I'd be careful not to assume the biggest surprise was the broken flow.
Sometimes the more important signal is not who signs up, but who feels the problem strongly enough to change how they share something.
That sounds subtle, but those can lead to very different products.
I wouldn't make that call casually in a thread.
That's a sharp distinction, and you're right that I compressed it in the post. The broken flow was the easy lesson because it was concrete and fixable. The harder one is exactly what you're pointing at: of the people who signed up, who actually felt the problem strongly enough to act on it?
What I'm noticing is that the ones who protect a page and come back tend to be people sharing client work — freelancers, agencies — where "public but gated" isn't a nice-to-have, it's the difference between sending a deliverable and not. That intensity is a different signal than raw signups, and you're right it could point to a narrower, sharper product than the generic "password for any Notion page" framing I started with.
Still sitting with it rather than calling it. Appreciate you pushing on it.
I think that's the interesting part.
Not because there's an obvious answer, but because a lot of product decisions start looking inevitable once you've already committed to one interpretation.
You've got enough signal now that I'd be more interested in the conclusion than the data.
If you ever want a second set of eyes on it, send me your email and I'll share the fuller thought.