How to market a consumer app without paid ads

Decide whether marketing is the next step

A working app is not automatically a useful app for people you can reach. Before you spread the word, check that a few relevant people can finish the core job, and that they would come back at the natural rhythm of the problem.

• If you cannot name a specific user, the moment that triggers the problem, and what they do today instead, talk to people first and skip the content calendar. For example: "people who just got a job offer in a new city and need to compare rents."
• If people visit but do not start, look at the promise, trust, pricing, install steps, and signup friction.
• If people start but do not get value, fix that before you send more traffic.
• If a small group gets value and returns, choose one channel where more people like them already look for help or discover similar tools.
• If the reason to switch is still vague, fill in the alternative-to-proof worksheet before you commit to recurring content.

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

Choose the first channel by audience fit

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 how users talk, what puts them off, and where they get stuck.
• Niche communities: useful when the rules allow a genuinely helpful post and the members are your users, not just other builders.
• Product Hunt or Hacker News: useful for makers and early adopters when they overlap with your audience. They are weak for job seekers, patients, parents, or local operators unless the overlap is real.
• Search: useful when people already type the problem as a query and your app can answer it or show the job without hype.
• Short-form: helps most when the use case is easy to show or explain in seconds, repeated honestly, and tied to a trackable next step. It helps less when the value is private or takes weeks to show. LaunchMax fits here: it makes both screen demos that show your app at work and UGC-style videos where a realistic AI creator talks about the app on camera (the problem, a reaction, the outcome), posts to your own accounts after you approve each one, and tracks sign-ups through a bio link.
• When time is tight, choose one channel and reject two before you commit 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. Show the before state, the shortest real path to a useful result, the result, and the next step.

• Use demo or made-up 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. "Gets you hired" is a promise you cannot keep; "rewrites one bullet for one job posting" is something you can show.
• Track qualified visits, starts, core-action completion, return use, and paid intent separately. Downloads alone do not prove people use the app.
• 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 you decide what to publish this week. The goal is a learning plan, not a promise that a channel will bring a fixed number of users.

• User: who has the problem, what triggers it, and where they already look for help.
• Alternative: what they use today, why it falls short, 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 format of your contribution, the call to action, and the activation event you will watch.
• Decision date: pick a day to choose between continuing, changing audience, repairing onboarding, improving the demo, or stopping the push.