Run this test to see if a small network is worth your manual posting

The default feed is the first gate

You have a product, a handful of users, and a small network that looks like the next place to find your first hundred. The tempting move is to post daily and hope discovery does the rest. That hope is expensive when you are the only person doing outreach.

A channel can be public and still keep strangers from seeing your posts. The first hundred users are a trust problem: you need to see who is reading, answer questions, and fix the product while the feedback is still warm. A network that hides your posts from non-followers makes that harder, even if the account is technically public. Manual outreach works because you can answer in real time. A channel that buries your posts turns that advantage into a one-way feed. You want a place where your next reply can reach a stranger, not a viral channel.

Before you spend a week hand-posting, run a small-network reach test. It checks three things: default discovery, audience activity, and client behavior. A no on any item sends your manual effort to the wrong channel.

Bluesky's opt-out shows why the default matters

Bluesky announced the opt-out on August 27. It keeps a user's posts out of the Discover feed for non-followers. With the opt-out on, the posts stay public. The account itself does not become private.

Discovery is a design choice. A platform can make posts public and still keep them out of the feed that strangers see. For a founder, that is the line between being discoverable and being available. The merged change from August 16 adds an account-level record named app.bsky.actor.contentVisibilityDeclaration, and the record requires a hideFromAlgorithmicRecommendations field set to true or false. A missing record should make software treat the preference as false. Because the setting lives at the account level, third-party apps that speak Bluesky's AT Proto protocol can support it if their makers choose. That is the exact trap for a founder: the post exists, but the feed does not show it.

The reach test decides whether the channel is worth your manual effort

Use this checklist before you commit to a channel. Do not wait for analytics. The signal you need is whether a stranger can see the post at all. Each item is a quick check, and each one tells you whether your manual work has a chance of being seen.

• Is the default discovery posture hiding posts from non-followers? Open the main feed as a logged-out visitor or a fresh account. Seeing mostly posts from people you already follow, or a small group of insiders, means your manual posts may only reach people you already know.
• Is your target audience actually active there? Search for terms your ideal user would type, then look for recent posts from non-followers and replies. Stale or silent results mean the audience is not active enough for manual work.
• Do the clients your audience uses honor the setting? For platforms with a visibility preference, confirm that the app your users actually open reads it. A client that ignores the setting can hide or surface your posts in ways you did not choose.

The test is cheap because it uses the same behavior you would do in manual outreach: look, check, and watch who shows up.

A failed test tells you where to spend the week

A default feed that hides non-followers is not where you should spend your week. Your first hundred users need a channel where a stranger can find you without already knowing you. A quiet audience will not bring new users. You can post for existing users, but do not expect the platform to find them. Unclear client behavior makes the channel low-confidence.

A small network can still be worth it if your target users are already there and the app they use respects the visibility setting. In that case, start small. Post, answer every reply, and note whether the post reaches anyone outside your existing circle. Keep the channel if it does. If it does not, move the manual effort to a place where the first hundred can actually see you.