MaidenSail
Where Startups Set Sail
About
Maidensail is a free startup launch and discovery platform where founders submit their products to a global community for weekly voting-based rankings. Each week, a limited number of "berths" open up for new launches; startups pick their launch week, get community upvotes, and compete for a spot on the weekly leaderboard, which locks in permanently once voting closes (Sundays at 00:00 UTC).
Beyond the launch week, every listing becomes a permanent page in the Maidensail Registry, complete with a dofollow backlink for SEO value. Startups can also apply for a verified badge by embedding it on their own site, boosting credibility with visitors.
Maidensail is part of a broader ecosystem: it's built by the same team behind MergeDeck, a verified M&A marketplace. Startups that gain traction and revenue can flag themselves as "Open to acquisition" or "Raising," creating a pipeline from public launch and community validation straight into fundraising or acquisition conversations — without ever leaving the ecosystem.
Ready to launch?
Submit your product and get discovered by builders and creators worldwide.
Launch Now
FounderPlaybooks.
What other founders did to grow.
2722 dispatches from hundreds of founders, pulled from the week's best podcasts.
we didn't even had like a nonpaying paywall for a few years because what we wanted to measure is the actual interest... a dollar is a dollar right like if you can capture a dollar you've captured something measurable and real
A dollar subscription on day zero is the best signal of real value
Mojo launched with a subscription from day one — not because the product was finished, but because charging any amount of money produces a signal you cannot fake. Free installs can hide weak product-market fit; willingness to pay reveals it. Francescu launched with a 30-day free trial at $10/month and celebrated when someone from an unknown country converted on launch day.
The server went down — one of the reasons that we track taps on the banner and the integer on the database overflow... the fallback banner that was display most of the time so it was like an accidental AB test... the fallback banner was converting twice as much as the existing.
Server crash → fallback banner accidentally doubled paywall conversion
A remote-server integer overflow forced the in-app fallback banner to render — and it doubled paywall conversions versus the live version. The text and icon were only slightly different. The lesson: hardcoded fallbacks are worth treating as real variants, and tiny copy/icon changes on a high-traffic surface can move revenue more than anyone's intuition predicts.
There's a play for whatever you're stuck on.
Read all 2722 playbooks