We Put Our Text Message Tool in Front of Everyone
Most SaaS products follow the same pattern: build something useful, put it behind an email form, and use it to generate leads.
We're doing the opposite with RelayKit.
The most useful thing we've built so far is our message configurator. You can use it right now at relaykit.ai/messages. Browse templates, see them populated with realistic values, edit them, and copy them into whatever system you're already using.
No signup. No email form. No account.
That raises an obvious question: why give away the thing that's supposed to generate leads? Because the configurator isn't really a lead magnet. It's a product demonstration.
The core promise RelayKit is making isn't that we have SMS templates. Plenty of companies have SMS templates. The promise is that adding SMS to an application should feel straightforward.
Putting an email gate in front of the configurator would undermine that message. Instead of demonstrating simplicity, we'd be introducing friction before anyone received value.
The tool exists to answer a simple question: does this feel easy?
If the answer is yes, we've accomplished something useful whether that person joins our waitlist or not.
The configurator is also the front door to everything else we're building. The messages are yours to send anywhere — and wherever you send them, you'll run into the bureaucracy that makes SMS slow: carrier registration, consent, opt-outs, rules that shift without warning. That's the part RelayKit takes over. The configurator is just where it starts.
Maybe that's the wrong approach. RelayKit is still pre-launch, and we don't have the data to know whether an ungated tool will outperform a traditional lead magnet.
But if the product is supposed to make SMS feel easier, it seemed strange to start by making the first interaction harder.
This is the right kind of tension to test before launch.
I don’t think the real question is simply gated vs ungated. The harder question is what the configurator should prove once someone has felt the product is easy.
If the tool creates usage but no buyer signal, it may look successful while still not helping RelayKit learn who is serious.
I wouldn’t solve that loosely in the thread because the answer changes the CTA, waitlist path, and what you measure before launch.
Happy to put the usable version in writing if helpful — this needs a cleaner conversion read than a thread reply.
Thanks. Once the app is ready, the user can onboard directly from the configurator using the messages they’ve chosen. So they’ll have a ‘send these messages’ choice pretty soon vs copying and leaving.