Solo Founder Marketing: A 5-Hour Week Built on Replies
Most solo founder marketing advice hands you a content calendar. Write a post on Monday, schedule a week of updates, and if there's time left over, go "engage." That order works once people follow you. With a product that has a few dozen users, almost nobody sees what you publish, while people ask for what you built in other people's threads every day. This is the 5-hour week I'd run instead: most of the time goes to replies, plus one post and one review.
Why solo founder marketing starts in the wrong place
I read three of the routines that rank for this search. Averi's 60-minute marketing week gives community replies a 15-minute slot ("three interactions"), half the time it spends making and queuing content. Gaurav Tiwari's 10-hour plan from July 2026 puts its biggest block, three hours, into one core asset, and communities get a passing mention. Jon Yongfook's coding week, marketing week split at Bannerbear is the most generous: whole weeks of marketing, with forums on the list next to blog posts, tweets and a newsletter.
All three make sense for a founder with an audience. For everyone else, posting is not the problem: any scheduler or AI tool will put a post out for you. Reach is the hard part, and a post from a small account mostly reaches the people who already follow it.
The data I have points the same way. Earlier this month I hand-coded 46 first-person "how I got my first 100 users" stories from three Reddit threads. 22 of them credited a conversation of some kind, either a reply in someone else's thread or a one-to-one chat. 13 credited a post, and 9 of those 13 had no conversation anywhere in the story. It's a small sample and my own coding, so read it as a rough signal.
How much time should a solo founder spend on marketing?
Nobody has measured a right answer. The advice runs from about an hour a week (Averi) to ten hours (Tiwari) to half your working time (Yongfook, who credits the alternating weeks with taking Bannerbear from about $800 to over $6K in monthly revenue in roughly six months). Each is one person's method that worked for them.
I'd start at five hours a week, spread across five days. That's small enough to keep through a heavy shipping week. Spreading it out matters more than the total, because founder threads move fast: when I checked r/SideProject on October 24, its 24 newest posts covered about two hours. A once-a-week session finds those threads after the conversation is over. Raise the hours only when Friday's review shows a channel bringing in signups.
The 5-hour week, day by day
Day | Time | Job | What you end with |
|---|---|---|---|
Monday | 60 min | Map where buyers ask | 3 to 5 places, saved searches, each place's rules |
Tuesday | 50 min | Reply | 2 or 3 replies in threads under a day old |
Wednesday | 50 min | Reply | 2 or 3 more, plus answers to anyone who replied to you |
Thursday | 50 min | Reply | Same as Wednesday |
Friday | 60 min | Turn the best reply into a post | One post on your blog or one platform |
Friday | 30 min | Review | A row per reply and one decision for next week |
Monday: map where your buyers ask (60 minutes)
Search for the question your buyer asks, in their words. People who need you rarely type "social listening tool" or "CRM for freelancers." They type "how did you get your first customers" or "is there a tool that does X without Y." Write down five or six phrasings like that and save each search.
Then look at where those searches land. In October I mapped where Social Cue's own buyers ask for help, with 42 Reddit searches plus the newest posts in 41 subreddits. r/SideProject had three first-users threads at 42 to 54 comments in a single week. r/SaaS, r/micro_saas and r/microsaas together had about one a day. Threads that named the tool category directly turned up about twice a week, and Hacker News had no Ask HN thread on marketing with more than three comments in a month. Your map will look different, which is why you build it yourself.
Last, read each place's rules and write them next to it. Some ban links outright. In r/startups, question titles often end in "(I will not promote)", a signal that the thread wants advice and no product names. Skip the threads where someone asks everyone to drop their product link, since the replies are other founders pitching to each other.
Tuesday to Thursday: reply where the question was asked (50 minutes a day)
Open your saved searches, sort by new, and pick two or three threads from the last day where you have a real answer. Put the answer in your first sentence. Add what you tried, with a number if you have one. Mention your product only if the poster asks for tools, and say you built it when you do. Three days at two or three replies each comes to six to nine answers a week, each in a thread where someone asked for exactly what you know.
Spend whatever's left of the block on replies to your replies. That back-and-forth is when people click through to your profile. Before you post, check your drafts for the six tells that make Reddit replies sound like AI. If your buyers are developers, the same habit works on Hacker News, where the reach is in the comments.
Friday: turn the best reply into one post (60 minutes)
Your post for the week is already written in rough form. Find the reply that got the most responses or follow-up questions and expand it into a post for your blog, LinkedIn, X or dev.to. A stranger asked about that topic this week, so you know someone wants it. Content repurposing that starts with a comment covers how to adapt one reply for each platform without tripping spam filters.
If you build in public, this is the update to share. Write it for the people who asked the question rather than for other builders (why that audience split matters).
Friday: review what worked (30 minutes)
Keep one spreadsheet row per reply: the date, the link, the place, how many replies it got, and whether anyone visited your site or signed up. Ask every new signup "how did you hear about us?" and log the answer word for word. Then make one decision. Drop a place that has produced nothing for three weeks, add a new one from Monday's searches, or move an hour from replies to posts if your Friday posts are the thing bringing people in.
If you only have one hour a week
Keep the replies and cut the post. Spend 15 minutes on your saved searches and 45 minutes answering two threads. Rebuild the map once a month instead of every week, and write a post only when a reply clearly takes off. Averi's one-hour routine gives a quarter of its time to replies. Until you have an audience, I'd give them three quarters, because that's where the people who already asked are.
Where Social Cue fits in the week
The slow parts of this routine are Monday's hunting and the scrolling that comes before each reply. Social Cue does both. It's a Claude Code plugin that runs on the Claude subscription you already have, so there's no extra AI bill. It opens a dedicated Chrome window and reads Reddit, Hacker News, X, Threads and Product Hunt the way you would, so there's no platform API deal to lose. Each thread gets a score from 1 to 10 against your brand, and the ones worth your time come with a reply drafted in your voice. Nothing posts until you approve it.
The rest of the week maps onto it too. /suggest-crosspost looks at the replies and posts you've logged and suggests how to turn them into drafts for other platforms, which is your Friday post. A weekly goals board holds you to the five hours. All of that is free. Pro is $19 a month: Claude posts the replies you've approved and tracks which ones got traction, which fills in the replies column of Friday's sheet.
Posting is solved; reach isn't, and Social Cue is the reach half. It finds the conversation and you decide what to say. Try Social Cue before your next Monday map.