How to Get Your First 100 Users Without Paid Ads: A 14-Day Plan

In a November 8, 2026 workshop, I asked teams to design a cold-start plan around a simple exercise target: work toward 100 early users and 10 paid conversions without assuming they had to spend the budget. The target was not a benchmark. Its purpose was to force operational detail: who will you contact, where, with what message, and what happens after they reply?

This is a 14-day validation plan, not a promise that every startup will reach 100 users in two weeks.

What counts as one of your first 100 users?

An early user is a person in the target customer profile who reaches the product’s first meaningful value. A signup is not automatically a user.

Define four events before outreach begins:

1. Qualified contact — matches the target role, situation, and problem.
2. Started — begins onboarding or the core workflow.
3. Activated — reaches the first value event you defined.
4. Paid signal — pays, starts a pilot, requests procurement information, or makes another explicit commercial commitment.

For a competitor-analysis product, activation might be completing and reviewing one report. For an API, it might be making one successful production-like call. For a creator tool, it might be exporting and sharing a usable artifact.

Write the event in plain language. If the team cannot agree on what activation means, more traffic will make the uncertainty larger.

How do you choose one customer and one problem?

Your first user segment should be narrow enough to find manually. “Startups” is not a segment. “Founder-led B2B SaaS teams preparing their first US launch without a full-time growth lead” is closer.

Use this qualification card:

Do not begin with five customer types. One narrow group gives you repeated language, comparable objections, and a realistic chance to improve the product between conversations.

Where can you find the first 100 users without ads?

The right channel is where relevant people already gather and where you can have a direct conversation. Paul Graham’s Do Things That Don’t Scale remains useful because early recruiting is often manual by design.

Build a list from four source types, but choose one primary source for the first week:

• Existing network: former colleagues, customers, partners, and relevant introductions.
• Problem communities: focused Slack groups, Discord servers, Reddit communities, forums, and local groups.
• Competitor and workflow signals: public reviewers, migration discussions, open-source issues, and users describing the workaround.
• Founder-led content: a teardown, checklist, demo, or evidence card that invites a specific reply.

Record why each person belongs on the list. “Has 20K followers” is not qualification. “Recently described the exact workflow problem and owns the decision” is.

Do not scrape and blast. Respect platform rules, privacy, and rate limits. The objective is a small number of relevant conversations, not maximum message volume.

What should you do during the 14-day experiment?

The plan below assumes one founder or operator and no paid distribution. Adjust volume to the complexity of the product and the trust required by the market.

If you reach only 20 people but learn exactly who activates and why, the experiment can still be successful. If you collect 100 signups and none reaches value, the experiment has not validated acquisition.

What should your outreach message say?

A useful outreach message is specific about relevance, the problem observed, the low-friction next step, and why the recipient’s feedback matters. It does not pretend to be a personal note when it is a mass template.

Use this structure:

Hi [name] — I noticed [specific public context]. I am testing [narrow product or workflow] for [specific user] who needs to [job]. I made [useful artifact] based on your context. Would you be open to a [short demo / live setup / feedback session]? If it is not relevant, no reply is needed.

For follow-up, use the 1-3-7-14 cadence as an operational heuristic: initial message on day 1, then respectful follow-ups around days 3, 7, and 14. Stop immediately after a clear no, an opt-out, or any platform warning. Change the message only when you have new value to add; do not send four copies of the same ask.

How should you run early-user sessions?

Early-user sessions should observe behavior, not become sales monologues. Ask the participant to share their screen and complete the real workflow when feasible. Watch where they hesitate, which workaround they use, and what information they need before trusting the product.

Capture five outputs:

1. current workflow and competitor;
2. trigger that made the problem urgent;
3. point where the user hesitated or stopped;
4. value they expected versus value they received;
5. next product, content, or offer decision.

Do not let the session turn into customer support or a founder fan conversation. Answer necessary questions, then return to the participant’s behavior. After the session, convert findings into product issues or decision notes and close the loop when something changes.

The full interview workflow is available in the Gingiris user-interview skill.

How do you decide whether to scale after day 14?

Scale only when the funnel has a real signal. Calculate the following by source:

Do not use one universal benchmark. Product type, price, onboarding effort, and market trust change the numbers. Compare channels against each other and against your own next cohort.

Continue when activation and paid intent improve as friction is removed. Change the segment or promise when people reply but do not start. Fix the product when qualified users start but cannot activate. Stop a channel when it produces attention without qualified use.

For a broader operating system beyond this 14-day test, use the Gingiris go-global skill or review the startup marketing guide for the first 1,000 users.

If you need an external review of the segment, funnel, and stop conditions before running the experiment, review the current advisory options.