Zero to Public

How to Get Your First 100 Visitors Without an Existing Audience

A practical, operator-first playbook for getting your first 100 website visitors without an audience, personal brand, or big launch.

2026-07-16 · field notes for public builders

Most projects do not need an audience to get their first 100 visitors. They need a specific promise, a short list of people who already care about the problem, and enough direct outreach to create useful conversations.

Your first 100 visitors will probably come from a handful of small channels: personal messages, relevant communities, search, partnerships, and one or two experiments that do not work. The goal is not to manufacture attention. It is to find people with a reason to click, then learn what made them act.

Start with a narrow promise

“Come check out my new app” is not a compelling reason to visit. A useful promise is concrete and easy to evaluate:

The narrower the initial problem, the easier it is to find the first visitors. You are not trying to appeal to everyone who might eventually use the product. You are looking for a small group that recognizes the problem immediately.

Write one sentence that answers three questions:

  1. Who is this for?
  2. What painful or valuable outcome does it provide?
  3. Why should someone try it now?

Put that sentence on the landing page, in your outreach, and in your profile descriptions. Repetition is useful when the message is clear.

Build a list of 100 likely visitors

Do not begin by asking, “Where can I promote this?” Begin with, “Who would genuinely benefit from seeing this?”

Make a spreadsheet with 100 names, companies, communities, newsletters, podcasts, or websites connected to the problem. This is not a list of random influencers. It is a map of places where relevant attention already exists.

For each prospect, record:

Start with people who are close to the problem, not necessarily people with the largest following. A thoughtful reply from a practitioner can teach you more than a broad mention from someone who barely understands the use case.

Use direct outreach as research

Direct outreach is the fastest path to early traffic because it does not require permission from an algorithm. It also becomes unpleasant when treated like a broadcast channel.

Write short, personal messages. Explain why you chose that person, describe what you built, and ask for a small action. The action might be trying the product, reading a guide, or telling you whether the problem sounds familiar.

A simple structure:

> I noticed you are working on [specific thing]. I built [project] to help with [specific problem]. It is early, and I am looking for a few people who deal with this regularly. Would you be open to taking a look? No pressure if it is not relevant.

Do not hide the ask behind a long origin story. Do not send five follow-ups in a week. Keep a note of what people say. Their language often gives you better positioning than your original copy.

Go where the problem is already discussed

Relevant communities can produce your first visitors, but only if you contribute before you promote. Search for conversations containing the problem your project solves. Read the rules. Answer questions. Share what you learned while building. Link to your project only when it genuinely helps complete the answer.

Good places might include niche forums, Discord groups, Slack communities, Reddit communities, GitHub discussions, professional networks, and comment sections on specialist blogs. The right venue depends on the audience and the problem.

A useful rule: if your post would still be valuable after removing the link, it is probably worth publishing. “I made a thing, please click” is promotion. A concise teardown, tutorial, comparison, or set of lessons is contribution.

Create one useful distribution asset

You do not need a content machine. You need one asset that can travel.

Examples include:

The asset should solve a smaller problem than your product while naturally leading to it. If you built a project-management tool, publish a simple weekly planning template. If you built an AI workflow, publish a prompt evaluation worksheet. If you built developer infrastructure, publish a debugging checklist.

Make the asset easy to share and easy to understand without a sales call. One strong, relevant artifact can outperform several vague announcements.

Combine channels deliberately

Your first 100 visitors do not need to arrive evenly. A small campaign might look like this:

| Channel | First action | What to learn |
|---|---|---|
| Personal outreach | Message 30 relevant people | Which problem language gets replies? |
| Communities | Publish 3 useful contributions | Which questions repeat? |
| Search | Write 2 focused pages | What intent brings qualified clicks? |
| Partnerships | Contact 5 adjacent creators | Who already serves this audience? |
| Product loops | Add a shareable result | Will users bring someone else? |

Track source, landing page, activation, and the visitor’s stated reason for coming. A visitor who stays for ten seconds is not equivalent to a visitor who completes the key action. Early traffic is valuable because it reveals intent, not because the number looks impressive.

A simple first-100 checklist

Mistakes that slow down early traffic

The first mistake is waiting for a perfect product. You can learn a great deal from a rough but understandable landing page. Shipping something imperfect makes feedback possible.

The second is trying every channel at once. If you post everywhere, you will not know what worked, and you will exhaust yourself before finding a repeatable motion. Choose two primary channels for two weeks.

The third is optimizing for impressions. Impressions are easy to collect and difficult to interpret. Track meaningful actions: qualified visits, signups, replies, completed workflows, and referrals.

The fourth is making the project sound broader than it is. General language feels safe, but it gives people nothing to recognize. Specificity creates a smaller door—and makes it easier for the right people to walk through.

The fifth is treating feedback as praise collection. Ask what was confusing, what they expected, what they would replace, and what would make the project worth returning to. Polite encouragement is pleasant; observed behavior is evidence.

What happens after 100 visitors?

The first 100 are not a finish line. They are a diagnostic sample. Look for patterns in who arrived, what they understood, where they dropped off, and which acquisition paths produced the strongest conversations.

Then choose one promising channel and make it more systematic. Improve the page for the audience that responded. Create a second asset based on repeated questions. Ask active users for introductions. Turn one-off effort into a loop.

Building publicly helps because the work itself becomes part of distribution. Share decisions, experiments, failures, and lessons as they happen. People are more likely to follow a clear journey than a polished announcement with no story behind it.

If you want the fuller operating system for starting from nothing, read or buy *From Zero to Public*. It is a practical guide to building internet projects in the open, finding your first users, and turning small signals into durable momentum.

FAQ ### How long does it take to get the first 100 visitors? It depends on the problem, the clarity of the offer, and how consistently you distribute it. A focused project with daily outreach may reach 100 visitors quickly; a search-led project usually takes longer. Treat the timeline as a learning loop, not a deadline.

Do I need to build an audience before launching? No. You can begin with direct conversations, relevant communities, useful search content, and partnerships with people who already serve your target users. An audience is helpful, but it is not a prerequisite for initial distribution.

What should I do if nobody responds to my outreach? Review the audience, the message, and the ask. Make the recipient more specific, explain why you chose them, shorten the message, and ask for a small action. If the response remains weak, revisit whether the problem is urgent enough or the promise is clear enough.

Should I pay for ads to get my first visitors? Usually, no. Paid traffic can be useful once you know which audience and message convert, but early organic conversations tend to produce better learning at lower cost. Validate the offer before scaling acquisition.

Build in public from zero.

From Zero to Public is the operating manual for turning small internet projects into visible, buyable assets.

Get the book