Five signups in three weeks. Small — and more useful than a viral spike that doesn't convert.
The framing that works isn't "GDPR-compliant tool." It's the jurisdiction question. Bluesky and Mastodon respond to the Schrems II angle; LinkedIn needs a compliance-aware audience before it lands at all. Developers engage with the architectural decisions — multi-tenant isolation, hashed emails, deletion verification across multiple databases. Agency owners need a different entry point, one that hasn't clicked yet.
A Dev.to article went out this week — making the jurisdiction argument concrete, with the decisions that followed from it. One comment here on IH, one follow on X.
June 30 is Show HN. Whether the HN audience overlaps with the people who actually need this is the thing I'm most curious about.
I think the biggest lesson here is that you didn't change the product—you changed the question you led with. "GDPR compliance" describes what it is. "Who has jurisdiction over your data?" creates a reason to care. That's a much stronger starting point because different audiences don't buy the same product; they buy different answers to their own concerns.