Who it's for
Growth marketing for pre-launch startups, executed.
Pre-launch startups do not need a campaign. They need the assets that take months to build started now: account standing, search presence, and a founder voice people recognise. Zway runs that work on your channels while you finish the product, so launch day lands on something rather than nothing.
Last reviewed 27 August 2026
The bottleneck
The problem with how pre-launch startups usually do this.
Pre-launch teams file distribution under launch week, so it never starts. The date slips, ready keeps moving, and the channels that needed three months of lead time get three days. Underneath that sits a second problem: there is no customer evidence yet, so every asset has to be built from the founder's own thinking rather than from results, and most founders read that as having nothing to say.
Start the slow things now, not the fast things
Distribution work splits cleanly in two, and pre-launch is the moment to be honest about which half you are doing.
Fast work can be done in a week: a landing page, a launch post, an outreach list, a demo video. Slow work cannot: an account with enough history that a post is not removed on sight, a domain that ranks for anything, a founder who has been saying interesting things long enough that people read the next one.
Pre-launch teams almost always start with the fast work, because the fast work feels like progress and finishes. Then launch day arrives, the fast work goes out, and it goes out to nobody.
What we plan backwards from
These are the planning numbers we work with. They are not measured averages and we would not present them as data. They are the lead times we have found you need to assume when you build a launch schedule backwards from a date.
| Work | Assume it needs | Can it be compressed |
|---|---|---|
| Standing in a community | 8 to 12 weeks | No |
| Search and AI search visibility | 3 to 6 months | No |
| A founder audience that reads you | 6 to 10 weeks | Partly |
| Launch-day outreach list | 2 to 3 weeks | Yes |
| Landing page and launch assets | Under a week | Yes |
Read the bottom two rows and the top three rows as different projects. The bottom two are why founders feel busy in launch month. The top three are why launch month does not work.
You have more to say than you think
The standard objection is that there is nothing to talk about yet. No users, no metrics, no screenshots you are willing to show.
True, and it does not matter, because the content that builds a pre-launch audience is not product content. It is the shape of the problem, the constraint you hit that nobody warned you about, the approach that seemed obvious and turned out to be wrong. You are one of very few people who currently holds that material, and none of it requires anything to be shipped.
What you cannot do pre-launch is claim outcomes. So we make the structural argument and leave the numbers out, which is also the only version that survives a reader who has already seen four hundred startup landing pages this year.
The newsletter starts before there is news
Most pre-launch lists are collected and then ignored until launch day, at which point the founder discovers that a list which has never heard from you is a list of strangers.
So the newsletter runs from week four, and every issue has to contain something a reader would forward to a colleague. That is harder than a monthly product update and it is the entire point. The measure is not size, it is whether people open it and reply.
By the time you launch, the list is warm, the accounts have history, and the domain has started to appear for the questions your buyers were already asking.
When we will tell you to wait
If the product is more than nine months from anything usable and you cannot yet describe who it is for in one sentence, distribution work will drift, because there is no audience definition to aim at. In that case the honest answer is to come back when you can name the buyer. We would rather say that on the first call than three months into work that had nothing to point at.
Channels that work here
- Founder-led LinkedIn from week one
- Search and AI search groundwork on the problem, not the product
- Reddit and niche communities, participation before promotion
- A waitlist newsletter that has something in every issue
- Product launch platforms, planned backwards from the date
The first thirty days
What a first month looks like for a pre-launch startups company.
| Week | Focus |
|---|---|
| Week 1 | Founder interview, positioning, and the audience definition. Decide who this is for precisely enough to aim at. |
| Week 2 | Accounts audited and warmed. Operators start participating in the communities where your first hundred users already are. |
| Week 3 | First founder-voice posts on the problem and the constraints you have found. Technical search groundwork begins. |
| Week 4 | First long-form piece published and first newsletter issue sent. Launch sequence drafted and dated backwards. |
Questions at this stage
We have no product and no customers. What is there to write about?
How far before launch should we start?
Is a waitlist number a good target?
Our launch date keeps moving. Does that break the plan?
Should we do a Product Hunt or Show HN launch?
See the plan for your company.
Thirty minutes. You leave with a written thirty-day plan either way.
30 minutes. You leave with the plan either way.