How to market a consumer app without paid ads

Decide whether marketing is the next step

A working app is not the same thing as a useful app for a reachable audience. Before you scale distribution, check whether a few relevant people can complete the core job and would want to use it again on the natural cadence of the problem.

• If you cannot name a specific user, trigger, and current workaround, do discovery before producing a content calendar.
• If people visit but do not start, inspect the promise, trust, pricing, install flow, and signup friction.
• If people start but do not get value, fix activation before sending more traffic.
• If a small group gets repeat value, choose one channel where more people like them already look for help or discover similar tools.
• If the reason to switch is still vague, use the alternative-to-proof worksheet before scaling recurring content.

Source basis: Paul Graham on recruiting early users manually, Lovable first-users guide.

Choose the first channel by audience fit

Do not ask which channel is best for all apps. Ask where the people with this problem already complain, search, compare tools, watch demonstrations, or take recommendations.

• Direct recruitment: best when you still need to learn the user's language, objections, and activation failure points.
• Niche communities: useful when rules allow a genuinely helpful contribution and the members match your users, not just other builders.
• Product Hunt or Hacker News: useful for makers and early adopters when they overlap with the app's audience; weak for job seekers, patients, parents, or local operators unless the overlap is real.
• Search: useful when the problem is already expressed as a query and the app can answer or demonstrate the job without hype.
• Short-form: useful when the use case can be seen quickly, repeated honestly, and tied to a source-tagged next action.
• When time is the constraint, choose one channel and reject two before committing to recurring production.

Source basis: Show HN guidelines, Product Hunt launch guide.

Build a demo that earns the next click

A first-users demo is not a feature tour. It should show the before state, the shortest real path to a useful result, the result, and the next step.

• Use demo or synthetic data when the app handles resumes, health, money, schoolwork, private messages, or analytics.
• Show one job-specific difference from the real alternative, such as a spreadsheet, a note, a generic chat tool, or doing nothing.
• Avoid promising app-store rank, interviews, grades, weight loss, savings, revenue, or time saved unless you have dated evidence.
• Track qualified visits, starts, core-action completion, return use, and paid intent separately. Do not treat downloads as proof of adoption.
• For signups that stall, trace the promise to first value; if attention never becomes a relevant start, inspect viewer intent.

Source basis: Software demo brief template, April Dunford positioning guide.

Worksheet

Fill this out before deciding what to publish this week. The goal is a learning plan, not a promise that a channel will produce a fixed number of users.

• User: who has the problem, what triggers it, and where they already seek help.
• Alternative: what they use today, why that is not enough, and what would make switching worth it.
• Proof: one working screen path, one result, and one boundary the demo must not cross.
• Channel: one audience source, its rules, the contribution format, the CTA, and the activation event to observe.
• Decision date: continue, change audience, repair onboarding, improve the demo, or stop scaling promotion.