A 30-day marketing plan for indie hackers who hate marketing

There's a specific kind of dread most indie hackers feel about marketing. Code has a tight loop: you write it, it runs or it doesn't. Marketing feels like shouting into a void with no compiler errors and no test suite. So we postpone it, ship feature after feature, and then wonder why a genuinely good product has nine users, six of whom are friends. The uncomfortable truth: the average indie product doesn't die from bad code. It dies unadvertised.

The fix is not becoming a marketer. It's refusing to treat marketing as a different kind of work. This plan converts 30 days of marketing into the format you already trust: small, concrete, finishable tasks, one per day, about 20 minutes each. No campaigns, no funnels, no growth hacks. A backlog and a streak.

Why 20 minutes a day beats a marketing weekend

The instinct is to batch it: block a Saturday, 'do marketing', get it over with. It fails for the same reason weekend code sprints fail. Marketing channels reward presence, not bursts. A community remembers the person who shows up daily, not the one who posted eight times one afternoon and vanished. Search engines reward a site that publishes steadily. An audience on X or TikTok grows on cadence, not volume.

Twenty minutes is also small enough that it can't cannibalize your dev time, which is the real reason most founders quit marketing plans: the plan asked too much, dev work suffered, and the founder (correctly) chose the product. This plan is designed to lose that fight on purpose. It asks for so little that there's nothing to sacrifice.

The four channels, and why only four

Everything in this plan draws from four channels. More than four and a solo founder's 20 minutes fragments into nothing; fewer and you're betting the product on one guess.

• SEO: pages that answer questions your users actually search. Slowest to pay off, most durable once it does, and the only channel that compounds while you sleep.
• Build in public: sharing progress, numbers, and decisions as you go. It converts the work you're already doing into content, which is why it's the natural channel for builders.
• Short-form: one 30-60 second video or thread per week, usually a screen recording of something you shipped. Highest variance, occasionally explosive reach.
• Communities: Reddit, Hacker News, Discord servers, niche forums where your users already gather. Fastest feedback, best for your first ten users, and the easiest 20-minute task there is: reply helpfully to three threads.

The 30-day plan, week by week

Week 1: foundations (days 1-7)

No promotion yet. This week you build the surfaces that every later task points at. Day 1: rewrite your landing page headline to name the user and the outcome, not the technology. Day 2: add basic SEO metadata, an OG image, and submit your sitemap. Day 3: write down, in one sentence each, who your user is and where they hang out online. Day 4: create or dust off accounts in two communities and one short-form platform. Day 5: set up the simplest possible analytics plus Google Search Console. Day 6: draft your build-in-public intro post (what you're building, why, one number you'll share weekly). Day 7: publish it.

Week 2: build in public (days 8-14)

One small post per day about the work you did anyway: a screenshot of a feature, a bug that humbled you, a metric, a decision and why. Two rules keep it honest: share numbers even when they're embarrassing (especially then, small numbers are relatable), and end posts with a question, because replies are the currency. On two of the seven days, swap the post for community work: answer three questions in a forum where your users live, product unmentioned unless it genuinely answers the question. If you want the progress-sharing to be automatic, shipsolo generates a public build-in-public page from your project, so your shipped tasks and streak are visible at a URL you can just link to instead of composing a recap by hand.

Week 3: SEO and short-form (days 15-21)

Spend four of the seven days writing one focused article: a real question your users type into a search box, answered thoroughly (a comparison, a how-to, a 'best X for Y' page). Twenty minutes a day for four days is a solid 900-word post. Day 19: publish and share it in one relevant community. Day 20: record a 45-second screen capture of your product doing its single most impressive thing, post it. Day 21: read your Search Console and analytics for ten minutes and write down which pages and posts got any traction at all.

Week 4: double down (days 22-30)

Week 4 has one job: kill what didn't work and repeat what did. Look at replies, signups, and search impressions (not likes, likes are applause, not interest). Whichever channel produced actual humans, spend six of the last nine days there. Use the remaining three days to ask every new signup one question by email: what were you hoping this would do? Their words become next month's headlines and next month's articles.

Put marketing in the same backlog as code

The deepest fix in this plan is structural. Marketing dies when it lives in a separate mental bucket labeled 'should do eventually'. So don't give it one. Put 'write comparison article, day 2 of 4' in the same backlog as 'fix Stripe webhook retry', estimate its minutes, and score it on impact like everything else. Scored honestly, early-stage marketing tasks win embarrassingly often: a 20-minute community reply that might produce your third user beats a speculative refactor on any impact-per-minute scale. This is exactly how shipsolo treats it: marketing tasks sit next to dev tasks, each scored by impact (1-100) over estimated minutes, and the daily reminder email just hands you the top task, code or marketing, with a mark-as-done link. The 2:1 rhythm (two build tasks, then one marketing task) then happens naturally instead of by willpower.

You don't need to like marketing. You need to be unable to skip it. A backlog that scores marketing tasks honestly makes skipping them feel like the irrational choice it is.

After day 30

Thirty days won't make you ramen profitable. What it produces is better: one channel you know responds to your product, a small pile of content that keeps working, a handful of real users who talk to you, and proof that 20 minutes a day is sustainable next to a full development load. From day 31, drop from four channels to two (your winner plus SEO, which always stays, because it compounds), keep the daily task, and keep the weekly ten-minute metrics review. Marketing stops being the thing you dread and becomes what it should have been all along: one more task in the queue, shipped daily, like everything else.