Week 4 - Waitlist Flow Before Outreach
Another week came by and the launch date is getting closer. This week I worked on something that is not very glamorous, but felt necessary before I push harder on distribution.
I rebuilt the public waitlist flow so it feels like a real product surface instead of just "enter email and disappear into a generic next step."
I still have no real traction yet. Traffic is low, subscribers are at zero, and that is obviously the uncomfortable part of writing these updates publicly.
But product work is moving well, and I am close to finishing a feature that could open a new distribution channel for the project. So I thought this was the right moment to improve the first impression a potential user gets when they show interest by leaving their email address.
So I focused on making the post-submit experience feel more deliberate.
Before, a new signup could land too quickly in the rewards area, which did not feel right for someone who had just joined.
Now the flow is clearer:
- first-time signup goes to a proper success page
- returning users are handled differently
- the share step feels intentional instead of bolted on afterward
That may sound like a small UX change, but I think it matters a lot.
If someone gives you their email this early, the product has to respond with clarity. It has to confirm what just happened, what they should expect, and what they can do next.
And about what they can do next: I implemented a set of platform-specific share-ready messages that users can copy with one click and post on the social network of their choice.
I also spent time making the system itself more solid than it probably needed to be for this stage:
- cleaned up the waitlist response handling so errors and success states are parsed consistently
- tightened the metadata so I was not leaking query-param junk into shared URLs
- made the flow distinguish properly between first-time signups and existing subscribers
- improved the success page so sharing the product feels more natural
This is probably a mild case of over-engineering for a waitlist that still has no audience 😅
But I also think early acquisition systems are exactly where sloppiness compounds. If the first people I convince to check the product get a confusing flow, that costs more than the extra effort I spent tightening it.
## What is next:
I know UI/UX improvements never sound that exciting, and since I am a Frontend Engineer it could look like I am playing from the comfort zone. But that's not entirely true...
This week I have also been working on a feature that I will share properly in the next update: a custom UI that lets users preview and save a memory into the system, making the server feel more like a real MCP App. I want to fix a few UI inconsistencies with the main platform first and prepare a proper video, so I would rather show it once it is ready.
But I have not only been thinking about the product side of the project. I also decided to do something outside my comfort zone to let more people know this project exists.
Look, I am all in when we talk about organic content marketing and SEO. But these strategies take time, and even if they are the most cost-effective to implement, they cannot be the only thing I rely on if I want to reach real users.
So I decided to start some outreach. Right now I am trying a mix of old and modern strategies: manually sending connection requests and following up with a cold DM once accepted, plus using my dashboard to surface relevant conversations happening around the web.
Let's see if next week, besides the new feature, I will also have some numbers to share 😊
