- Biggest Constraint: **Distribution (you have zero audience + only 5 hours/week).** Money isn’t the limiter (you’re not spending anyway). Time is tight, but the real blocker is **no built-in way to reach solo devs fast**. - Chosen Acquisition Channel: **Targeted “build-in-public” micro-content on X (Twitter), with direct replies to relevant posts (not broadcasting).** - Why This Channel (and not others): - **Fastest learning loop at $0:** You can post, get feedback, and DM/interact the same day. - **Fits 5 hours/week:** Short, repeatable actions (one post + a handful of replies) beats long-form writing or community grinding. - **Developer-native:** Solo/freelance devs already discuss workflows, tooling, ADHD/task systems, “what do you use to track work?” on X daily. - Not Product Hunt: too spiky + needs prep + you don’t have assets. - Not Reddit/Indie Hackers as primary: higher moderation/format risk and slower iteration; also easy to burn time writing “perfect” posts. - Not SEO/blogging: compounding channel, but too slow for “20 registrants in 30 days.” - Not cold email: you don’t have a list, and list-building costs time you don’t have. - 30-Day Experiment Plan: **Goal of the experiment:** Prove you can reliably turn conversations into signups. **Setup (Day 1, 60–90 min):** 1) Create a simple landing page message (even if minimal): *“A task system for solo devs: projects → next actions → today. Built for personal dev work.”* 2) Add one clear CTA: **“Join the early list”** (registrants). 3) Create 3 screenshot-worthy artifacts (can be rough): one UI screenshot, one “Today view”, one “Project breakdown” view. **Weekly cadence (Weeks 1–4, ~5 hrs/week):** - **2 posts/week (20–25 min each including drafting):** Format: very specific dev-task pain + tiny solution + invite. Example template: “Freelance dev problem: my ‘to-do’ becomes a junk drawer. I’m building a tiny tool that forces: Project → Next Action → Today. Want early access? (link)” - **5 days/week: 10 targeted replies/day (20–25 min/day):** You’re not trying to “go viral.” You’re hunting relevant threads. Search and reply to posts containing phrases like: “todo app”, “task management”, “freelance dev”, “solo dev”, “overwhelmed”, “ADHD”, “Notion”, “Trello”, “Linear”, “what do you use”, “productivity system”. Reply pattern: **give value first**, then soft invite. “I had the same issue. What helped was separating ‘projects’ from ‘next actions’. I’m actually building a tiny dev-first version—happy to send you the link if you want to try.” - **DM follow-up (2 days/week, 20 min each):** DM only people who engaged (liked/replied) or explicitly showed pain. Script: 2 lines max + link. Ask 1 question. “If you’re still looking for a cleaner way to track personal dev tasks, here’s the early access page: <link>. What’s your biggest issue today—too many tasks, or not knowing the next action?” **End of each week (30 min):** - Record: #posts, #replies, #DMs, #registrants, which post/thread produced signups. - Success Metrics: 1) **20 registrants in 30 days** (primary). 2) **Conversion efficiency:** at least **1 registrant per 50 targeted replies** (secondary, to know if the channel is viable with your time limit). - Kill / Scale Decision Rule: - **Scale (double down) if by Day 14 you have ≥8 registrants AND hit ≥1 registrant per 50 replies.** Scaling = same channel, but slightly more volume: 3 posts/week + keep replies; do not add new channels. - **Kill (abandon) if by Day 14 you have ≤2 registrants OR worse than 1 per 120 replies.** That means the message/targeting isn’t resonating fast enough for your 5 hr/week constraint. - One Execution Warning: **Don’t turn this into “content creation.”** Your job is *not* to write thoughtful threads—it’s to run a tight loop: **find pain → reply with a helpful pattern → invite → track signups**. If you spend your 5 hours polishing posts, you’ll lose the only advantage of this channel (speed).