From submission records to published links: a real product example

The product and the evidence

Where Winds Meet Calculator is a gaming website with a damage calculator and build-related resources. We used this product in our own Submora workflow, rather than presenting it as an independent customer testimonial.

Its public showcase gives us a concrete record to discuss. In the snapshot reviewed on October 28, 2026, it showed 14 submitted platforms, 7 recorded as published, and an observed Ahrefs Domain Rating change from 0.7 to 2.6. The live showcase can change as records are updated.

How to read the snapshot

It is tempting to divide the published total by the submitted total and call that an acceptance rate. That would require a well-defined submission cohort, enough time for each review, and a reliable outcome for every member. A current dashboard snapshot does not supply all of that.

The workflow another founder can repeat

1. Prepare an accurate product profile: what it does, who it is for, the correct URL and suitable images.
2. Choose destinations for audience fit. A gaming utility should not be presented as an AI product merely to fit an unrelated directory.
3. Adapt the draft to the destination’s fields, review it, and complete the platform’s own submission process.
4. Save the submission date and status. When a listing goes live, add the real public page URL.
5. Inspect the listing and target link separately, record follow-ups, and retain the dates of subsequent checks.

The value of keeping these steps together is traceability. If a listing has not appeared, you can find the original submission date. If a public page changes, you can compare it with your previous observation. If the description is inaccurate, you have a consistent source to correct it from.

What would make this a stronger outcome study?

The next layer of evidence would be dated listing checks, actual referral visits and relevant actions on the product website. Those measures answer different questions: whether the link exists, whether people use it, and whether those visits are valuable.

A credible time-saving comparison would also need recorded preparation and submission times for a comparable set of platforms. We do not have a published measurement for that in this case, so there is no percentage-saved claim here.

This example shows how a product’s submission history can be made inspectable. It is a starting point for learning which channels deserve more effort, not a shortcut to promising rankings or growth.