First Hundred Users: Network First, Cold Outreach Second, Skip Paid

You need a paying customer this week, not a growth plan. The channel mix that matches that deadline is manual: your network first, cold outreach second, communities and inbound social as support, paid acquisition later.

Network first because it already knows you

The Supabase startup survey collected responses from 2,000 startup builders covering the 2025-2026 period. In that group, 56% of founders identified personal networks as the leading source of their first paying customers. Plan the week around that number. Your network is a set of people who will answer because they know you. Start with people who have felt the problem, not people who merely know your product. Ask for a short conversation, not a sale. If they say no, ask who else has the same problem. That referral is the actual asset.

Cold outreach second because it extends the network without pretending to be warm

Cold outreach works when it is narrow, named, and useful. You are not blasting a template. You are finding a person whose role matches the pain and writing a note that proves you understand it. If you cannot name the problem in a single sentence, do not send it.

Founder-led sales belongs at the start, not after you have a polished funnel. The buyer is usually a person with a role, a constraint, and a deadline. Your note should point at that constraint, not at your feature list.

Track the outcome of each note. Did it get a reply, a meeting, a referral, or a clear no? A clear no is useful. It tells you where the pain is weaker than you thought.

67% of surveyed startup founders had never attempted paid acquisition. Treat that as a signal that early buyers are usually found by hand, not bought. Paid channels can amplify a message, but they cannot replace the proof that someone will pay.

Communities and inbound social are support, not the main engine

Developer communities matter when your buyer is technical. 78% of surveyed startup founders were technical. 62% of surveyed startups had over half of their codebase generated by AI, while 41% had 76% to 100% AI-generated code. You show up to answer, not to pitch. A useful answer can create a conversation that a landing page never would.

Claude Code was the most frequently named must-have developer tool, with 31% of founders naming it. Use that as a guide to attention. It tells you which threads, which questions, and which workflows deserve your time.

Inbound social works when you publish the same manual work you are doing: the question you asked, the objection you heard, the fix you made. It functions as evidence that you are in the market, not as a content calendar.

Run these moves before touching paid

• Ask your network for a short problem interview, and ask each person for a referral.
• Send cold notes to named people whose role matches the pain, with a specific problem in the opening line.
• Post a useful answer in a developer community where your buyer already asks questions.
• Turn a user conversation into a short public note.
• Keep paid acquisition out of the week until the manual loop produces repeatable conversations.

The order matters. Network conversations are the fastest way to learn what the buyer actually says. Cold outreach tests demand beyond people who already like you. Communities reward usefulness and punish noise. Public notes turn private learning into inbound. Paid channels need a message that has already survived real conversations.

Keep a simple log: name, channel, question asked, answer, next step. Use a line for each person. This turns scattered effort into a record you can compare. Without it, every week still feels like a new experiment again. The log is the only map you need this week.

Run the week, record what each channel returns, and spend the next week on the channel that produced the most useful conversations. If a channel produces only polite interest, stop polishing it. If a channel produces a buyer, a referral, or a sharp objection, put more time there.