What to post before you have a product

The pre-launch founder has the hardest content problem and the best raw material, and almost always uses neither. No customers means no case studies, no numbers, no social proof — so most people fill the gap with industry takes that could have been written by anyone, or with traction language that is not quite true yet.

Both are worse than posting nothing. The takes are invisible; the inflated claims are remembered.

What you do have is the thing nobody with a mature product has any more: an unfinished decision, in public, in real time. That is the whole strategy.

The claims that cost you later

Start with what not to write, because pre-launch is where founders damage trust fastest and least deliberately.

• "Our customers are seeing…" when there are three design partners on a free tier. The plural is the lie, and someone will ask.
• "We're growing fast" off a base of 40 signups. Not false, exactly, and everyone reads it as false.
• Invented specificity. A generated post will happily produce "teams save an average of 6 hours a week" because it is the shape a post takes. If you did not measure it, that number becomes something you have to defend or quietly delete.
• Borrowed authority. Writing about scaling when you have not scaled anything. Readers who have done it can tell in one paragraph.

The rule that survives all of these: never claim a scale you cannot name. "One beta customer cut migration from four hours to twenty minutes" is stronger than "customers save hours" precisely because it is narrow. Specific and small beats vague and big, every time.

Seven angles that work with zero customers

1. The problem, described better than your buyer can describe it. If you can articulate the pain more precisely than the person living with it, you have earned attention without claiming anything. This is the single highest-value pre-launch post and most founders skip straight past it to the solution.

2. The decision you are in the middle of. Not "here's what we built" but "here's the fork we're at and what we're weighing." Live decisions get replies from people who have made them. Finished decisions get likes.

3. What you're building and why this way. The architecture, the constraint you accepted, the thing you deliberately made worse. Technical honesty travels.

4. What you were wrong about. You have been wrong about something in the last month. That post is more interesting than your roadmap and costs you nothing, because pre-launch nobody expected you to be right yet.

5. Research in public. You are talking to potential users. Post what you are hearing, anonymised, without conclusions. "Six of ten people we spoke to had already built a spreadsheet version of this" is a fact you own.

6. The thing you refuse to build. Positioning stated as a boundary is memorable and commits you publicly, which is useful discipline.

7. Work in progress with the seams showing. A screenshot of something half-finished, a migration that broke, a metric that is bad. Build-in-public works when the "in public" part includes the parts that are not going well.

Notice that six of seven require no traction at all. They require you to be doing the work and willing to describe it accurately.

Build the audience the launch lands on

The reason to post pre-launch is not the posts. It is that a launch to zero people is a press release into a void, and a launch to 800 people who have watched you reason for six months is an event.

Two things matter more than volume:

Reply to people, individually, before you need anything. Pre-launch is the only period where you have time for this, and it is the only distribution strategy that reliably works from a standing start. Twenty real conversations beat two hundred impressions.

Say what you are building, repeatedly, in one sentence. Not a pitch. A sentence people can repeat to someone else. If your audience cannot describe what you do, they cannot refer you at launch, and referral is most of what a launch is.

The frequency question

Lower than you think. Two posts a week for six months beats daily for five weeks and then silence, which is the standard pre-launch pattern: enthusiasm, exhaustion, disappearance a month before the thing you were building for.

Pre-launch is a stamina problem, not an intensity problem. The 30-minutes-a-week method exists precisely because the pre-launch period is long and the founder's attention is not.

When the product ships

Do not throw away the pre-launch archive. The decisions, the wrong turns and the research are the raw material for everything you write afterwards — a launch post that references six months of public reasoning is dramatically stronger than one that starts from "today we're excited to announce."

This is also where most founders lose the plot: the voice that got attention pre-launch was specific, uncertain and technical, and the launch flips it to marketing register overnight. Readers notice the switch immediately. Whatever else changes, keep the register.

Where a tool helps and where it does not

No tool solves the pre-launch content problem, because the problem is that only you know what happened this week. What a tool can do is stop the two failure modes: going dark when the build gets hard, and letting a generated draft quietly invent traction you do not have.

That second one is why SelfSM works the way it does — brand memory holds what is actually true, including "customers: 0", and a draft that would claim otherwise gets stopped rather than written. Pre-launch is exactly the situation where an AI writer is most dangerous and most tempting, because the gap between what you have and what a post wants is at its widest.

FAQ

What should a startup post before launch? The problem stated more precisely than your buyer can state it, decisions you are currently weighing, what you are building and why this way, things you were wrong about, and anonymised findings from user research. All of these work with zero customers.

How do I build an audience with no product? Post twice a week for months rather than daily for weeks, and spend more time replying to individuals than writing posts. Pre-launch is the only period where you have time for one-to-one conversations, and they convert into a launch audience far better than impressions do.

Should I build in public? It works when "in public" includes the parts going badly. Selective build-in-public that only shows wins reads as marketing and gets treated as such. If you are not willing to post the broken migration, the format is not for you.

Is it bad to post about traction I don't have yet? Yes, and the damage is durable. Never claim a scale you cannot name. One named result stated narrowly is more persuasive than a vague plural, and it does not become something you have to defend later.

How often should a pre-launch founder post? Two to three times a week, sustained. The pre-launch period is typically six to eighteen months, which is a stamina problem — the common failure is intense posting for a month followed by silence right before launch.