Week 4
First 10 Users
Find the first users where they already gather instead of hiding behind more product work.
Distribution
Use the build as proof.
The founder records screen builds, before-and-after clips, and lessons from shipping without pretending to be a guru.
Members learn to talk to buyers without overpromising outcomes.
The content works because it shows the real artifact, the rough edge, and the lesson. For this buyer, calm proof beats hype.
A useful post names the problem, shows the small build, explains the decision, and invites a specific kind of person to reply or try it.
Channels
Go where buyers already gather.
Do not start with ads. Start with the places where the target user already asks questions: professional communities, niche forums, LinkedIn threads, X searches, Slack groups, newsletters, and direct relationships.
A cold audience needs relevance before a pitch. The first message should prove you understand the workflow and ask about the current workaround.
One good channel is enough for the first 10 users. Scattered posting across every platform usually hides the fact that no conversation is being followed up.
Outreach
Direct messages are research first.
The first DM should not ask someone to buy. It should ask whether the problem is real for them and whether they would look at a rough fix.
Personalize by role, workflow, or pain signal. A short relevant note beats a polished generic script.
Track sent messages, replies, objections, interested users, trials, and follow-ups. The spreadsheet is the distribution dashboard until there is enough volume to automate.
Feedback
Ten users are a product instrument.
The first users teach which promise, workflow, and support material are unclear.
Their questions become lesson updates, FAQ entries, onboarding copy, and product fixes.
Separate politeness from behavior. Strong signals include using the product twice, sending an example, asking for a change, forwarding it to a teammate, or paying.
Weak signals still matter as copy feedback. If five people misunderstand the same line, the product has a positioning bug.
Cadence
Run one weekly loop.
Each week has the same loop: publish proof, send direct outreach, follow up, collect objections, make one product or copy edit, and document what changed.
The member should not disappear into building after a single rejection. Distribution is part of the product work, not a separate personality test.
By the end of Week 4, the goal is not virality. It is ten real people who taught you something measurable about the promise.
Run the first user loop
- Choose one primary channel where the buyer already gathers.
- Post one build-in-public update daily for five days.
- Send ten direct messages to qualified people.
- Invite interested users to try the thin product or join the waitlist.
- Follow up within 48 hours with one specific question.
- Capture every objection, confusion point, and feature request.
- Make one copy or product edit from the week's strongest signal.
Prompt starters
- Write five build-in-public posts from these product notes. Keep them specific, non-hypey, and aimed at employed professionals with this workflow pain.
- Draft a short DM that asks about the current workaround before pitching my tool.
- Turn this user objection into a clearer landing-page section and one product fix.
- Summarize this week's outreach into sent, replies, interested, tried, paid, objections, and next follow-up.
- Create a 48-hour follow-up message that asks one useful question without pressure.