Lesson 1 of 87 min read
Why developers lose at distribution (and how to stop)
Distribution is part of shipping. Pick one audience, write a one-line positioning, and use your technical detail as the edge marketers lack.
In this lesson you will
- See distribution as a step of shipping, not a chore after it
- Pick one specific audience instead of "developers" or "everyone"
- Write a one-line positioning that fits in a bio
You finished the feature. Tests pass, the release is tagged, the README is updated. Then nothing happens. A few stars from friends, one issue from a bot, and a quiet analytics page. It is tempting to read that silence as a verdict on the code. Usually it is a verdict on distribution: the people who would care never heard about it.
Most developers treat distribution as something that happens after the real work, if there is time left. There never is. This lesson reframes it as part of shipping, like writing the changelog or cutting the tag, and gives you the first piece you need before you post anything: a clear statement of who you build for and what changes for them.
The product won't market itself
There is a story developers like to tell: good tools spread on their own. Sometimes they do. When you look closer, the tools that "spread on their own" almost always had someone explaining them in public, early and often. A maintainer answering questions in forums. A founder writing about each release. A demo that someone else could share in one click.
The "build it and they will come" bias is comfortable because it keeps you in the editor. But think about how you found the last three tools you adopted. Probably a post, a thread, a recommendation in a chat, or a comparison someone wrote. Somebody did distribution for those tools, even if it did not look like marketing.
Here is the shift we want you to make. Shipping has these steps:
- Build the change.
- Test it.
- Release it.
- Tell the people who need it.
Step 4 is not optional and it is not separate. A release nobody hears about has the same effect on your users as a release that never happened. Once you see it that way, the question stops being "should I post?" and becomes "what is the smallest version of step 4 I can do every time?" The rest of this course answers that.
Three objections we hear from developers, and our honest answers:
- "I don't want to be a self-promoter." Then don't be. Explaining what changed and why is documentation in a different place. Your users want to know.
- "I don't have time." The smallest useful step 4 is one post per release, written from notes you already have. Lesson 3 gets that to minutes.
- "Nobody follows me, so why bother?" Everyone starts at zero. Early posts are also practice: you learn what your audience responds to while the stakes are low.
One audience beats everyone
The second mistake is writing for everyone. "A tool for developers" is not an audience. There are millions of developers, and they do not share problems, vocabulary or hangouts. A data engineer tuning pipelines and a mobile developer fighting app review will scroll past the same post for different reasons.
Pick one audience that is narrow enough to picture. Good audiences have three things:
- A shared job. "People who maintain self-hosted services at home", "solo founders running a SaaS on one server", "teams writing internal CLIs in Go".
- A shared pain you solve. Not a category, a specific moment: "the deploy failed and the logs are unreadable", "the release notes take an afternoon".
- A place they gather. A subreddit, a hashtag, a forum, a Discord server, a newsletter. If you cannot name one, the audience may be too vague.
Use this decision rule. If you cannot describe one real situation where your audience would reach for your tool, narrow it further. If you can name the situation but not where those people talk, you will find out in lesson 2.
A narrow audience feels risky because it seems to exclude people. In practice, specific posts travel further than general ones, because the people who match share them with others like them. You can widen later. You cannot get attention from "everyone" on day one.
Your edge is real technical detail
Marketers have budgets, designers and schedules. You have something they cannot fake: you know exactly how the thing works and why it was built that way. That is the most useful material for a technical audience.
Say you maintain a file sync tool. Compare two posts about the same feature:
Before:
Introducing our powerful new sync engine! Faster, smarter,
and more reliable than ever. Try it today!
After:
Sync used to re-upload the whole file when one line changed.
Now it sends a diff. A 40 MB config edit went from a full
upload to a few kilobytes on my test machine.
Here's how the chunking works ->
The second post is not more "marketing". It is more honest and more specific. It names the old behavior, the new behavior, and a measurement you actually took, and it invites the curious to read more. (Note the measurement says "on my test machine". Only quote numbers you measured, and say where they came from.)
Technical detail works because your audience is suspicious of claims and generous with explanations. "Faster" is a claim. "Sends a diff instead of the whole file" is an explanation they can check.
Write a one-line positioning
Before you write a single post, write one sentence that every post will lean on. It goes in your bio, your README's first line and your launch posts. It should name the audience, the problem and the change, in plain words.
Use this template:
[Product] helps [specific audience] [do a job] without [the painful part].
Some examples, all for clearly hypothetical projects:
Say you maintain a CLI for database migrations:
"Shiftline helps teams on Postgres ship schema changes
without hand-writing rollback scripts."
Say you run a small uptime tool:
"Pingcheck helps solo founders know their app is down
before their users tweet about it."
Check your line against this list:
- Would a person in your audience recognize themselves in the first half?
- Is the painful part something they would say out loud, in their own words?
- Does it avoid adjectives like "powerful", "seamless" or "next-generation"?
- Does it fit in a bio? On X the bio limit is short, so aim for well under 160 characters. If it does not fit, it is probably trying to say two things.
If you have two audiences, write two lines and pick one for the next four weeks. You are not deleting the other, just postponing it.
Worked example: our own positioning
We had to do this exercise ourselves. Our product does a lot: a composer, a calendar, an inbox, listening, analytics, an API, an MCP server for coding agents. The temptation was to list everything. A list is not a position.
So we asked the questions from this lesson. Who is the buyer we serve best? Developers, indie founders and small teams who already live in code and in their coding agent. What is the painful part? Posting the same update by hand to every network, in a slightly different shape each time, and remembering to do it at all. What is the change? You write once, or your agent drafts it, each network gets its own version, and nothing goes live until you approve it.
That gave us a working line for our developer-facing posts on X, Bluesky and LinkedIn:
Post to every network you connect from one place, your
code or your coding agent. Nothing goes live until you approve it.
It is not perfect, and we revise it. But every developer-facing post we write now leans on it. When we announce something like the MCP server being listed in agent directories, the post connects back to "from your coding agent". When we announce GIF support in the composer, it connects to "one place". If a planned post does not connect to the line at all, we ask whether it belongs on our developer channels or somewhere else.
We also learned what to leave out. Our first drafts listed features. Nobody in our audience wakes up wanting "a unified inbox". They want to stop missing replies. The positioning line names the outcome; features show up in the posts that follow.
How much time this takes
Budget 30 minutes for this lesson's work:
| Step | Time |
|---|---|
| List two or three candidate audiences | 5 minutes |
| Pick one and name where they gather | 5 minutes |
| Write five versions of your line | 10 minutes |
| Cut to one and check it fits a bio | 10 minutes |
Do not spend a week on it. A decent line you use beats a perfect line you never ship. You will sharpen it in lesson 8, once you have real numbers on what people respond to.
Recap
- Distribution is step 4 of shipping. A release nobody hears about has no effect.
- Pick one audience with a shared job, a shared pain and a place they gather.
- Specific technical detail is your edge; explanations beat claims.
- Write one positioning line with the template, and make sure it fits a bio.
Exercise
Write your positioning line
- Write down two or three audiences you could serve. For each, name one real situation where they would reach for your tool.
- Pick the one where you can also name a place they gather online.
- Fill in the template five times: "[Product] helps [audience] [do a job] without [the painful part]."
- Cut the adjectives. Pick the version a person in that audience would repeat to a colleague.
- Paste it into the free X character counter and trim until it fits comfortably in a bio, well under 160 characters.
- Done looks like: one sentence, under the limit, saved at the top of your notes, ready for your bio and your README's first line.
Go further
Brand voice in FoPost
Once your line is settled, save it where your drafts can use it. In FoPost, a brand holds your voice notes, audience and words to avoid, so AI drafts and per-network rewrites lean on your positioning instead of generic copy. Open brand voices, add your line and audience, and set it as the default. See Brands for what a brand can hold.
Check yourself
1Why is "a tool for developers" a weak audience?Show answer
It has no shared job, pain or gathering place, so no single post can speak to all of it. Narrow it until you can picture one real situation.
2What makes a technical post more convincing than a feature claim?Show answer
It explains the old behavior, the new behavior and how you know, which your audience can check for themselves.
3What are the four parts of the positioning template?Show answer
The product, a specific audience, the job they do, and the painful part they get to skip.
Keep reading, free
Tell us a little about you and the rest of this lesson, and every lesson in every course, opens on this device. No account and no card.