How to Submit to Go Publicly: A 2026 Walkthrough

Go Publicly is a build-in-public community: founders share progress, numbers and lessons in public. Distribution comes from the story, not the listing.

The short answer

Go Publicly belongs in the batch, not in the plan. Ten of these in one sitting costs an hour; treating each one as an event costs a week for the same dozen listings.

What Go Publicly is

A community for founders building in public, with posts, profiles and progress updates. Sign-up and submission both live at go-publicly.com.

Before you touch the form

Publish a milestone with a number attached. Build-in-public audiences follow trajectories, so a chart beats a feature list.

Submitting, in order

Choose a milestone with a number
Write the update honestly
Add what you will do next
Post in the right channel
Reply to questions

One thing that catches people out

Build-in-public audiences follow trajectories, and a profile with one post has no trajectory. The listing is not the asset here; the sequence of updates is, and a single launch update reads as an advertisement to a community that expects a series.

What it is good for

Community audiences are small, opinionated and technical. They will tell you what is wrong with the product, which is worth more than a citation.

The first three posts

Post the problem before the product: what you were doing manually, what it cost, what you tried. Then post the build. Then post the first number, however small. Three posts establish a trajectory that a single launch announcement cannot, and the third is the one people quote back at you later.

Checking what you actually got

Check whether the milestone got replies rather than just views
Note which update people referenced later
Confirm the profile links to the product, not to a newsletter
See whether the post appears under the relevant tag
Re-check after the next milestone to compare reach

Where SaasHunt fits

The other half of this decision is timing. SaasHunt takes submissions for a fixed 08:00 UTC go-live, so the listing goes on a calendar instead of a hope list. Approved listings are dofollow; paid tiers from $9.9 skip the queue, and $49 adds a newsletter slot.

Submit your product

A profile is a timeline, not a page

Build-in-public communities judge members by the shape of their updates over months. A profile with one post and a link has no shape, which is why a single launch announcement is the weakest possible use of the platform.

The listing is housekeeping. The sequence of milestones is the asset, and it starts before you need anything from anyone.

What number to publish first

Pick one metric you are willing to track weekly and publish it unchanged, including the bad weeks. Revenue, signups, active users, support tickets answered — any of them works, provided the series continues.

Changing the metric every month resets the story and reads as marketing. The single most trusted accounts in these communities publish the same number for years.

The cadence that makes a following

One update a week is enough. Two is better. Daily is a job, and most founders abandon it in month two, which is worse than never having started.

The practical version: a short post when something changes, a longer one monthly with the chart. Predictability matters more than length.

Why a single launch post fails

The audience has seen ten thousand launches and none of them had a history attached. A launch arriving with six months of prior updates reads as a step rather than an advertisement.

If you are starting from zero, do not lead with the product. Publish three posts about the problem and the build, then mention what you shipped.

What to do with comments

Reply in public and continue the thread rather than moving it to email. The visible conversation is the content that other members read before deciding to engage with you.

Ignore the hostile ones politely. A founder who argues in a comment section is remembered for the argument, not the product.

Measuring a build-in-public channel

Not traffic. Measure the number of people who reply more than once, the number who ask about the product, and the number who sign up with an identifiable route back to the community.

Those three numbers are small and they compound. Pageviews from these platforms are negligible and say nothing.

When to stop posting

When the updates become a chore you perform for an audience that has stopped responding. Consistent silence, if you must stop, is better than a slow decay into monthly promotional posts.

Pick a cadence you can hold for a year, publish the metric honestly, and let the archive do the work after that.